I'm new to the flexibility of Android as a user of Blackberry 10. I have always run beta leaks in the BB world and have been reading and learning on the android world but there is so much diversity I am tentative.
I have a ZL that was a Bell Mobility locked phone. I purchased unlock code (took a few days from a reputable provider) and I have a bunch of those code groups, one of which was used as directed to unlock successfully. I am using it on Rogers and am running the latest 10.3.A.0.423.
I have installed the flash tools etc. My intent is to root in order to rid the phone of Bell crap and other nuisance things that I don't want around and hopefully get more flexibility in power consumption changes.
Can someone point me in the right direction? I had tried the root process that is posted here but find that it hangs on the "display" part of the process on a white screen and doesn't go further. My conclusion was that the process isn't supporting the firmware level that I am at.
cwoodffr said:
I'm new to the flexibility of Android as a user of Blackberry 10. I have always run beta leaks in the BB world and have been reading and learning on the android world but there is so much diversity I am tentative.
I have a ZL that was a Bell Mobility locked phone. I purchased unlock code (took a few days from a reputable provider) and I have a bunch of those code groups, one of which was used as directed to unlock successfully. I am using it on Rogers and am running the latest 10.3.A.0.423.
I have installed the flash tools etc. My intent is to root in order to rid the phone of Bell crap and other nuisance things that I don't want around and hopefully get more flexibility in power consumption changes.
Can someone point me in the right direction? I had tried the root process that is posted here but find that it hangs on the "display" part of the process on a white screen and doesn't go further. My conclusion was that the process isn't supporting the firmware level that I am at.
Click to expand...
Click to collapse
For the .423 firmware you can use DoomLord's Easy Rooting Toolkit v17, found in this thread: http://forum.xda-developers.com/showthread.php?t=2332407
If you decide to flash a newer stock firmware (.244 or .67 - which I advise you to do, after you get yourself acquainted with Android, Xperia and, of course, your ZL), the rooting process is different - until firmware .423 there was an exploit used to root our devices, but, since firmware .244, this exploit has been fixed by Sony. This rooting process is described in this thread: http://forum.xda-developers.com/showthread.php?t=2458268
Best regards and welcome to the Android world.
Tiu Fiu said:
For the .423 firmware you can use DoomLord's Easy Rooting Toolkit v17, found in this thread: http://forum.xda-developers.com/showthread.php?t=2332407
If you decide to flash a newer stock firmware (.244 or .67 - which I advise you to do, after you get yourself acquainted with Android, Xperia and, of course, your ZL), the rooting process is different - until firmware .423 there was an exploit used to root our devices, but, since firmware .244, this exploit has been fixed by Sony. This rooting process is described in this thread: http://forum.xda-developers.com/showthread.php?t=2458268
Best regards and welcome to the Android world.
Click to expand...
Click to collapse
Thanks so much for the reply. So you would say to flash .67 as my next level of "maturation" prior to messing with rooting? I assume as that is what you are running per your sig.
Oh, and will I have an issue with these things if the phone has been unlocked by an on-line provider?
cwoodffr said:
Thanks so much for the reply. So you would say to flash .67 as my next level of "maturation" prior to messing with rooting? I assume as that is what you are running per your sig.
Oh, and will I have an issue with these things if the phone has been unlocked by an on-line provider?
Click to expand...
Click to collapse
Technically once the unlock code has been accepted, that is it, it is unlocked and it is supposed to stay that way. In any case, it would be wise to keep the unlock code safe somewhere, just in case.
I said that because, with DoomLord's v17 rooting toolkit for the .423, it is basically a one click, straight-forward operation. However, for the .67, things get a tiny bit more complicated (it will seem very simple once you get familiar with flashing firmwares with Flashtools, trust me).
Anyway, I do advise you to flash .67 since it is a far more mature firmware than .423 (and by mature, I mean less bugs and a more optimized and stable OS, just as is expected of a newer firmware). You need to keep a close eye to your ZL model (C6502, C6503 or C6506). I don't know which one Bell/Rogers sells, but it is easy to find out (Settings -> About the phone -> Model Number). Flashing a firmware created for a device different than yours might be troublesome and, though I've read from time to time about people using different firmwares on different models without any problems (e.g. flashing a C6503 firmware on a C6502 ZL), I definitely advise against it.
Either way, the one true rule here is to take your time to read the info/guide/tutorial threads around in the forum.
Tiu Fiu said:
Technically once the unlock code has been accepted, that is it, it is unlocked and it is supposed to stay that way. In any case, it would be wise to keep the unlock code safe somewhere, just in case.
I said that because, with DoomLord's v17 rooting toolkit for the .423, it is basically a one click, straight-forward operation. However, for the .67, things get a tiny bit more complicated (it will seem very simple once you get familiar with flashing firmwares with Flashtools, trust me).
Anyway, I do advise you to flash .67 since it is a far more mature firmware than .423 (and by mature, I mean less bugs and a more optimized and stable OS, just as is expected of a newer firmware). You need to keep a close eye to your ZL model (C6502, C6503 or C6506). I don't know which one Bell/Rogers sells, but it is easy to find out (Settings -> About the phone -> Model Number). Flashing a firmware created for a device different than yours might be troublesome and, though I've read from time to time about people using different firmwares on different models without any problems (e.g. flashing a C6503 firmware on a C6502 ZL), I definitely advise against it.
Either way, the one true rule here is to take your time to read the info/guide/tutorial threads around in the forum.
Click to expand...
Click to collapse
it is a 6506 so I think I should be fine with the directions you provided.
cwoodffr said:
it is a 6506 so I think I should be fine with the directions you provided.
Click to expand...
Click to collapse
In that case, since there is no Generic Canadian firmware for the C6506, I would suggest the Generic US one found in this thread: http://forum.xda-developers.com/showthread.php?t=2459497
It should be absolutely fine to flash the US Generic firmware (since it is supposed to be operator/bloatware free and fully functional for any C6506 as the German/Baltic/Middle-Eastern-and-Asian/Brazilian generic firmwares are for the C6503)
For info on stock firmwares available, check this thread: http://forum.xda-developers.com/showthread.php?t=2333187
You should be able to find the small .ftf files for the "old" (.423) kernel and the "new" (.67) kernel alone. If you don't find the kernel-only files, you'll also need to download any C6506 .423 full firmware .ftf file and follow the "Using complete ftf packages" mentioned on the OP (opening post) of sanjulgupta's rooting thread (http://forum.xda-developers.com/showthread.php?t=2458268 ).
Best regards and good luck.
Done! Moved to .67, then Rooted using the small files. No issues except that I lost the native browser?
Related
Hey all, I’m pretty new to this, have been reading throughout this forum and others for weeks. I got a few things I would REALLY appreciate some help with.
I have a SE ARC lt15A running 2.3.3 with 3.0.1.a.0.145 firmware. (I’m in Canada, phone is with Rogers) I bought it locked and unlocked it as I used it for a recent trip to europe no problem there.
It seems very slow like when I press the button for my contacts it takes about 5 seconds to open, so this brings me to where I am now, I’d like to put cyanogenmod on it and get rid of all the pre-loaded stuff.
Do I need to update the firmware before I put on cyanogenmod?
If so I can’t seem to get FastBoot to recognize phone.
But I can get Wotanserver to recognize my phone, there are different firmwares but none from Canada, can I use another region firmware on my phone and have it still work on with my carrier?
I don’t know if this matters but I was trying to flash firmware earlier and phone stopped working, was able to restore it with SEUS, can that lock my phone again?
Could be that i missed a thread that answers my questions, if so would appreciated being pointed in right direction.
Thanks again
homeygomey said:
Hey all, I’m pretty new to this, have been reading throughout this forum and others for weeks. I got a few things I would REALLY appreciate some help with.
I have a SE ARC lt15A running 2.3.3 with 3.0.1.a.0.145 firmware. (I’m in Canada, phone is with Rogers) I bought it locked and unlocked it as I used it for a recent trip to europe no problem there.
It seems very slow like when I press the button for my contacts it takes about 5 seconds to open, so this brings me to where I am now, I’d like to put cyanogenmod on it and get rid of all the pre-loaded stuff.
Do I need to update the firmware before I put on cyanogenmod?
If so I can’t seem to get FastBoot to recognize phone.
But I can get Wotanserver to recognize my phone, there are different firmwares but none from Canada, can I use another region firmware on my phone and have it still work on with my carrier?
I don’t know if this matters but I was trying to flash firmware earlier and phone stopped working, was able to restore it with SEUS, can that lock my phone again?
Could be that i missed a thread that answers my questions, if so would appreciated being pointed in right direction.
Thanks again
Click to expand...
Click to collapse
mate i have the same issue. the thing is that once we (you) bought the phone locked the bootloader is locked and it cant acces fastboot - even if u got the unlocking code and even if uwill flash debranded firmware. there is no way to do so now. all u can do is root it and get rid of some bloatware. - yes root it without unlocking the bootloader. check out android dev section and DOOM'S version for windows! perfect and easy.
thats the only thing u can do so far - the same as me. just wait.
thanks
What's doom's version for windows? Can you point me to it? Is it better/easier to use than Gingerbreak?
Also can i update the firmware with a different region without screwing up my phone/provider? Is it possible to get 2.3.4 on a branded phone or do i have to wait for SE to release it for my region?
homeygomey said:
What's doom's version for windows? Can you point me to it? Is it better/easier to use than Gingerbreak?
Also can i update the firmware with a different region without screwing up my phone/provider? Is it possible to get 2.3.4 on a branded phone or do i have to wait for SE to release it for my region?
Click to expand...
Click to collapse
here u go mate
http://forum.xda-developers.com/showthread.php?t=1320350
follow the instructions - this is the easiest root ever made for android!
hit the thanks button if i helped you!
homeygomey said:
What's doom's version for windows? Can you point me to it? Is it better/easier to use than Gingerbreak?
Also can i update the firmware with a different region without screwing up my phone/provider? Is it possible to get 2.3.4 on a branded phone or do i have to wait for SE to release it for my region?
Click to expand...
Click to collapse
Make a backup of your ROM with PC Companion or Update Service then flash the latest firmware and root.
You can flash any arc firmware onto any arc.
If you still want fastboot enabled then contact me
i did...thanks god u r here..
Thanks guys i'm installing Doomlord.
For anyone else like me who dont know much of what their doing, i flashed 2.3.4 US on my phone with wotan but then had to add apn for rogers to get 3G back.
I am a proud owner of the AT&T Xperia Ion and am getting sick being unable to download the apps i want and i have read around here i can flash the international firmware so i could have ICS on my phone. Well as a noob to androids i am obviously nervous as to the effects of flashing. so i would like to know the risks of flashing it are. Once the official AT&T firmware is released can i switch to it? Will all the data stored in my phone be erased? Will i be able to use LTE? Will the warranty be voided? i would also like to know if there are other things i should know about, as well as the process in which i can carry out the flashing. thank you everybody
1. Just flash back to stock att ftf, and you should get the update. Or, flash the att ICS ftf when it becomes available.
2. It's a good idea to wipe between flashes, so if you did, all your data will be gone. I backup contacts and calendar through Google, so getting data back for me is easy. App data on the other hand will be gone. Or, risk it and don't wipe, but you will likely get some stability issues.
3. You can get lte.
4. If you flash back to stock before taking your phone for service, there should be no warranty issues. Is you take it in with Chinese firmware, that'll likely be a problem.
Sent from Rooted LT28at with ICS.
misterwhales said:
I am a proud owner of the AT&T Xperia Ion and am getting sick being unable to download the apps i want and i have read around here i can flash the international firmware so i could have ICS on my phone. Well as a noob to androids i am obviously nervous as to the effects of flashing. so i would like to know the risks of flashing it are. Once the official AT&T firmware is released can i switch to it? Will all the data stored in my phone be erased? Will i be able to use LTE? Will the warranty be voided? i would also like to know if there are other things i should know about, as well as the process in which i can carry out the flashing. thank you everybody
Click to expand...
Click to collapse
I'm also a noob in Android. Last weekend flashed ICS on my Xperia, following the procedure for rooting. It took me maybe two hours to get all the instructions and download everything I needed. You´ll basically need the firmwares, Android SDK (the link is in the post with instructions, second one in the thread), Flashtool (the latest Windows version, which comes with the drivers for Ion, is in http://androxyde.github.com/Flashtool/). I followed everything from the instructions, but wasn't getting the same response from the ADB commands, it still worked.
Two things are missing from those instructions:
1. To have hotspot activated, you'll need to first flash the international GB firmware, wiping everything in your device (be sure to make backups of everything you´ll want, don´t trust Google backup).
2. Right after flashing ICS, Flashtool won't recognize your phone, even if you have the USB debugging option on. You'll have to update your PC drivers by going to Control Panel, Device Manager, and choose to have Windows search for updated drivers (while the phone is connected, of course). You´ll know you got it right when Device Manager displays a different name for your phone, and Flashtool is able to tell you the software version. At that point you can run the second part of the rooting procedure.
Mmh...
Hello!
When will be released the official ice cream sandwich for my xperia ion lt28i? (international version, bought from Hong Kong)
No time given really. I am guessing at the same time the US releases their's so will the European (International) Version. So maybe September / October time frame, could be earlier.
I just bought a couple of days ago mi new Xperia ZL, i think the phone is great, but today when i tried to get mi phone rooted, i realized the bootloader is locked.
Im kind of new at this, but i really dont know why mi phone is on that status, so does that mean that i never be able to fully root mi phone?
I tried to do it with a dooloard applicatión, but it seems that the android compilation version is not compatible with the doomlord software.
Could someone help me please! i want to erase all the garbage from my service provider.
I have a Xperia Zl C6502, 10.1.1.A.1.253
By the way, Im From Guatemala, sorry for the crappy english.
Best Regards
wichobig said:
I just bought a couple of days ago mi new Xperia ZL, i think the phone is great, but today when i tried to get mi phone rooted, i realized the bootloader is locked.
Im kind of new at this, but i really dont know why mi phone is on that status, so does that mean that i never be able to fully root mi phone?
I tried to do it with a dooloard applicatión, but it seems that the android compilation version is not compatible with the doomlord software.
Could someone help me please! i want to erase all the garbage from my service provider.
I have a Xperia Zl C6502, 10.1.1.A.1.253
By the way, Im From Guatemala, sorry for the crappy english.
Best Regards
Click to expand...
Click to collapse
A locked bootloader doesn't stop you from rooting. Mine is locked (and is unlockable) and I have root.
Use this method: http://forum.xda-developers.com/showthread.php?t=2332407
LenAsh said:
A locked bootloader doesn't stop you from rooting. Mine is locked (and is unlockable) and I have root.
Use this method: http://forum.xda-developers.com/showthread.php?t=2332407
Click to expand...
Click to collapse
I tried before, but it seems that the app is not compatible with the version i have.
Always gave me an error.
Please any additional assistence would be appreciated.!!
Regards
wichobig said:
I tried before, but it seems that the app is not compatible with the version i have.
Always gave me an error.
Please any additional assistence would be appreciated.!!
Regards
Click to expand...
Click to collapse
In order to root the 253 build, you need to follow Nut's thread here:
http://forum.xda-developers.com/showthread.php?t=2299092
Read everything carefully before doing it, I think the build 253 was the most complicated build to root not because it's hard but it has more steps than any other builds.
Why don't you upgrade to the latest 4.2.2 build 244. It's very stable and good. Plus, it's easy to root.... :good:
Even if your BL is locked, every build can be rooted.
Crash338 said:
In order to root the 253 build, you need to follow Nut's thread here:
http://forum.xda-developers.com/showthread.php?t=2299092
Read everything carefully before doing it, I think the build 253 was the most complicated build to root not because it's hard but it has more steps than any other builds.
Why don't you upgrade to the latest 4.2.2 build 244. It's very stable and good. Plus, it's easy to root.... :good:
Even if your BL is locked, every build can be rooted.
Click to expand...
Click to collapse
Hello Crash 3338
Is not that i want to do it on that build, is just that is the software that came with mi ph, and unfortunately in my country i dont know why, we dont get OTA upgrades. So could you please show me or post the link where i can get the instructions on how to upgrade to that build, and also how to root it.
Thanks in advance for the assistence,
wichobig said:
Hello Crash 3338
Is not that i want to do it on that build, is just that is the software that came with mi ph, and unfortunately in my country i dont know why, we dont get OTA upgrades. So could you please show me or post the link where i can get the instructions on how to upgrade to that build, and also how to root it.
Thanks in advance for the assistence,
Click to expand...
Click to collapse
You are not getting the OTA because your carrier is not pushing it. If your phone is branded to xyz carrier than you need to wait for them to push their new bloaded firmware via OTA.
If you flash the Sony generic firmware, you will be getting OTA's as soon as Sony pushes them out.
If you want to flash your phone to the latest Sony generic, you will need:
Flashtool : http://androxyde.github.io/
PC Companion
C6502 FTF: http://forum.xda-developers.com/showthread.php?t=2389305
Installed drivers for your Xperia ZL (can be found inside Drivers folder when flashtool is installed)
This thread has screenshots on how to use flashtool:
http://forum.xda-developers.com/showthread.php?t=928343
Don't forget to Turn on "Unknown sources" and "USB Debugging" before flashing the phone.
Once you have flashed this firmware, you will root by
1 - Flashing the FW 423 Kernel ONLY
2 - Reboot and root with DoomLord's latest exploit (v.18)
3 - Flash back the FW 244 Kernel ONLY
4- Reboot and you are done!
Happy flashing!! :highfive:
Crash338 said:
You are not getting the OTA because your carrier is not pushing it. If your phone is branded to xyz carrier than you need to wait for them to push their new bloaded firmware via OTA.
If you flash the Sony generic firmware, you will be getting OTA's as soon as Sony pushes them out.
If you want to flash your phone to the latest Sony generic, you will need:
Flashtool : http://androxyde.github.io/
PC Companion
C6502 FTF: http://forum.xda-developers.com/showthread.php?t=2389305
Installed drivers for your Xperia ZL (can be found inside Drivers folder when flashtool is installed)
This thread has screenshots on how to use flashtool:
http://forum.xda-developers.com/showthread.php?t=928343
Don't forget to Turn on "Unknown sources" and "USB Debugging" before flashing the phone.
Once you have flashed this firmware, you will root by
1 - Flashing the FW 423 Kernel ONLY
2 - Reboot and root with DoomLord's latest exploit (v.18)
3 - Flash back the FW 244 Kernel ONLY
4- Reboot and you are done!
Happy flashing!! :highfive:
Click to expand...
Click to collapse
You are the men Crash338, i did everything like you said, and now i have my phone fully rooted. Im very thankful with you and with all the people that belongs to this forum.
Just one more thing, i hope you dont mind, which are the pros an cons of having the bootloader locked.
Thanks in advance.
Regards
Google it.
wichobig said:
You are the men Crash338, i did everything like you said, and now i have my phone fully rooted. Im very thankful with you and with all the people that belongs to this forum.
Just one more thing, i hope you dont mind, which are the pros an cons of having the bootloader locked.
Thanks in advance.
'Regards
Click to expand...
Click to collapse
Unlocked bootloader allows you to flash custom kernels so that you can flash cooked roms which may require a custom kernel. If you like the Sony stock rom and just want to root on it then dont bother unlocking it.
Also, rooting doesnt void your warranty, unlocking your bootloader does.
Glad everything worked out for you!
OK I have a UK Vodaphone G3 (LG-D855) still with their bootloader but it is rooted using the purple drake method which i did about 9 months ago, I think now is the right time to update the OS, so should i go via the OTA route and go to Lollipop or wait and go the Marshmallow or given i have rooted do i have to use another method to upgrade the OS.
Looking at my "Update Centre" it says the following "New OS Version: V20f-DEC-22-2014 (522.49MB)"
I am happy working with PC's but know very little about phones so please be gentle with me.
If you need any more info from me just ask.
All1
Allonewordinuk said:
OK I have a UK Vodaphone G3 (LG-D855) still with their bootloader but it is rooted using the purple drake method which i did about 9 months ago, I think now is the right time to update the OS, so should i go via the OTA route and go to Lollipop or wait and go the Marshmallow or given i have rooted do i have to use another method to upgrade the OS.
Looking at my "Update Centre" it says the following "New OS Version: V20f-DEC-22-2014 (522.49MB)"
I am happy working with PC's but know very little about phones so please be gentle with me.
If you need any more info from me just ask.
All1
Click to expand...
Click to collapse
Do not upgrade via ota when rooted this is a big no no can cause big problems.. If you want a new update just flash a kdz (stock rom) with flashtool. There are plenty of guides on here on how to do that.
v20f is a very old update the newest is 21a..I would probably wait for Marshmallow according to rumors it should be with us about middle of December .:good:
Edit here are a couple of links for you flashtool and guide >>http://forum.xda-developers.com/showthread.php?t=2785089 << Kdz stock roms >> http://lg-phone-firmware.com/index.php?id_mod=41 <<
Also when you are rooted you can't take ota
OK many thanks for the info tallman43 and also thx for the links, looking at the link with the rom's i'm unsure if i should go for number 520 as it say V10l or 530 as mine is Vodaphone 16GB, or does it not even matter?
Also one very newbie question if i may these "roms" are in PC talk just images of a pc when it comes out the factory, all have windows 7 for example but some will have different apps preinstalled depending if it was Dell or HP etc, just trying to get my head round it "my way" if you get my drift.
All1
Allonewordinuk said:
OK many thanks for the info tallman43 and also thx for the links, looking at the link with the rom's i'm unsure if i should go for number 520 as it say V10l or 530 as mine is Vodaphone 16GB, or does it not even matter?
Also one very newbie question if i may these "roms" are in PC talk just images of a pc when it comes out the factory, all have windows 7 for example but some will have different apps preinstalled depending if it was Dell or HP etc, just trying to get my head round it "my way" if you get my drift.
All1
Click to expand...
Click to collapse
V10 kdz are kitkat roms V20 kdz are lollipop roms obviously if you want the latest firmware then V20 is the one to go for.Also if you look through all the firmware's not just uk you will find 21a kdz this is the very latest one.Also you don't have to specifically use the uk ones technically you can flash any I am from the Uk and have used 21a without any problems.
Only thing I would say is if you flash one from another country try for ones that are closer to uk ie: Don't flash lets say a HongKong firmware but places like Poland,Spain,France etc are ok but like I said you could technically flash any.
Also in answer to your last question about pre installed apps yes some of them may have odd one or two different apps installed in them by the carrier.
One last thing if and when you use flashtool make sure you do not unplug your phone until it as fully flashed and rebooted flashtool sometimes comes up with a banner saying something like can't connect or failed. Look at the progress bar on your phone this is the best way to see if it is flashing ok.
OK mant thanks tallman43 you've been a real star with all this info.
All1
Another thing - custom ROMs are faster than stock work various improvements, so flashing a custom is highly recommended.
(insert witty signature here...)
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
the right question would be, how to get the latest security patches but staying with oreo?
vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.
metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.
Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.
cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!
That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active