Hi, I'm living in Costa Rica, I have a friend that was coming from Germany and he offered to bring something from there (phones are expensive here). My previous Z1 compact was almost dead (almost half screen without touch) so I bought a second hand XZ1 (I'm not a big fan of big screen phones) thru ebay kleinanzeigen. The phone got to my friend, he tried it and everything worked fine. When he brought it to me, I realized there was a demo mode activated on the phone. Tried deactivating it from system ('lock screen and security' tab is locked), *#*#sellmore#*#* ('Device is for store use only, Retail mode cannot be activated') and firmware reinstall thru sony companion but no luck. My friend it's going to be traveling back in over 6 months to Germany :crying: . Is there a way to remove this demo mode since returning it it's not an option? Thanks for your time!
craspo said:
Hi, I'm living in Costa Rica, I have a friend that was coming from Germany and he offered to bring something from there (phones are expensive here). My previous Z1 compact was almost dead (almost half screen without touch) so I bought a second hand XZ1 (I'm not a big fan of big screen phones) thru ebay kleinanzeigen. The phone got to my friend, he tried it and everything worked fine. When he brought it to me, I realized there was a demo mode activated on the phone. Tried deactivating it from system ('lock screen and security' tab is locked), *#*#sellmore#*#* ('Device is for store use only, Retail mode cannot be activated') and firmware reinstall thru sony companion but no luck. My friend it's going to be traveling back in over 6 months to Germany :crying: . Is there a way to remove this demo mode since returning it it's not an option? Thanks for your time!
Click to expand...
Click to collapse
Use the flashtool or newflasher to flash a different rom, if it's demo FW Sony companion will just keep reflashing it.
SXUsr said:
Use the flashtool or newflasher to flash a different rom, if it's demo FW Sony companion will just keep reflashing it.
Click to expand...
Click to collapse
Thank you very much for your reply! For using this tools, do I have to root or unlock bootloader or both?
craspo said:
Thank you very much for your reply! For using this tools, do I have to root or unlock bootloader or both?
Click to expand...
Click to collapse
Neither, just flash, but remove the persist file before flashing to keep the Android attest key in tact.
SXUsr said:
Neither, just flash, but remove the persist file before flashing to keep the Android attest key in tact.
Click to expand...
Click to collapse
Thanks again for your response! And sorry to break you ba**s again. I've dowloaded the last firmware from Xperfirm (47.2.A.11.228). I had Android 8 and this is 9. Is it worthy to upgrade? or I might encounter problems later on if I want for example to root or unlock boot loader? (I don't care much for customization I just use Titanium Backup for freezing or deleting bloatware)
And last question: I been reading about getting the persist file backed up and I just found this thread for motorola G5 would this still work? If not, would you mind guiding me in the right direction?
Thank you very much for your time again!
craspo said:
Thanks again for your response! And sorry to break you ba**s again. I've dowloaded the last firmware from Xperfirm (47.2.A.11.228). I had Android 8 and this is 9. Is it worthy to upgrade? or I might encounter problems later on if I want for example to root or unlock boot loader? (I don't care much for customization I just use Titanium Backup for freezing or deleting bloatware)
Click to expand...
Click to collapse
I'm sticking with Oreo because I don't like Pie, so that's down to your personal preference. You can find Oreo FW ending .20 in threads knocking about here. As for the persist.sin, you simply don't flash it, I think in the flashtool you can exclude it but if you use Newflasher you just delete it from the folder before flashing.
Give THIS thread a read.
SXUsr said:
I'm sticking with Oreo because I don't like Pie, so that's down to your personal preference. You can find Oreo FW ending .20 in threads knocking about here. As for the persist.sin, you simply don't flash it, I think in the flashtool you can exclude it but if you use Newflasher you just delete it from the folder before flashing.
Give THIS thread a read.
Click to expand...
Click to collapse
Ok I have the fw and deleted the persist file (persist_X-FLASH-ALL-C93B.sin, is this the right one?). Now just flash with newflasher? I do not have to backup TA partition (drm keys) or anything else?. Sorry for so many questions, I do not have a lot of experience on this and I do not want to mess it up.
Thanks again for your time!
craspo said:
Ok I have the fw and deleted the persist file (persist_X-FLASH-ALL-C93B.sin, is this the right one?). Now just flash with newflasher?
Click to expand...
Click to collapse
Yes, and yes.
craspo said:
I do not have to backup TA partition (drm keys) or anything else?. Sorry for so many questions, I do not have a lot of experience on this and I do not want to mess it up.
Thanks again for your time!
Click to expand...
Click to collapse
You only need to backup your TA if you're going to unlock the bootloader, if you're just flashing FW it doesn't matter.
SXUsr said:
Yes, and yes.
You only need to backup your TA if you're going to unlock the bootloader, if you're just flashing FW it doesn't matter.
Click to expand...
Click to collapse
Everything worked perfectly! Thank you, thank you very much for your time an patience!
craspo said:
Everything worked perfectly! Thank you, thank you very much for your time an patience!
Click to expand...
Click to collapse
You're welcome!
Related
Here it is. Got my buddies c6606 us T-Mobile. Rooted fine, recovery went fine, but rom flash boot loops. And the best part is I cant get into recovery. So im stuck with fastboot, which gives me the same errors everytime, or flashmode with flashtool which I can put 100 fw's in the firmware folder and only a.1.253 shows up. Really need a.2.66 or 166 but I download them , place them in firmware folder with others and they're not there. My S3 is a dream compared to this. Takes me back to my HTC days! Anyway, I know its something small, its on .253 with some random rom asking for .66 or .67. Please, I'll pay. This is tying up my J-Tag repairs and other devices. Please, someone. I'll try whatever.
P.S. locked bootloader, apparently not unlockable.
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
jtford said:
jtford said:
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
Thanks. I was suprised with the errors using SUS. The device has a lot more potential to be exploited I think.
Click to expand...
Click to collapse
Sorry i got a message to you too late.
one thing: if you flashed over a different firmware, like for a 6603 or 6602 the sony software often says there is no update for your device because it sees it as a different phone.
The firmwares that you are placing in the /firmware folder are. Ftf files, and around 700mb? You can find firmware for download that comes in a different format, but flashtool wont see them.
I want to try the lollipop that everyone loses their mind with so is it okay to flash d5803 firmware to d5833 phone? Is there a very simple guide here that explains everything? And when I flashed that d5803 firmware will I lose my keys?
Also, if I dont like the lollipop, can I flash back to d5833 kitkat firmware?
Thank you guys! I dont have any knowledge about this flashing things so I wanna ask you guys first.
I'm no pro and not sure if folks will answer without telling you to search. But I'm almost sure this is a surefire way to brick your phone. Differences between radios and stuff will have a significant impact on your device functionality. Talking from experience of flashing a lot of roms, not a dev by any means.
Sent from my D5803 using Tapatalk
braveally said:
I'm no pro and not sure if folks will answer without telling you to search. But I'm almost sure this is a surefire way to brick your phone. Differences between radios and stuff will have a significant impact on your device functionality. Talking from experience of flashing a lot of roms, not a dev by any means.
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
I actually searched about it here and this is the only thread that I saw. http://forum.xda-developers.com/z3-compact/help/flashing-d5803-to-d5833-make-difference-t3068857
One member said that he has d5833 singapore version with d5803 italy firmware. I am convinced that nothing will happen but I know there will be. But I want to ask also for assurance
With your experience in flashing a lot of roms, I can reflash back to kitkat( d5833 firmware) from my bricked phone right?
giotzkie05 said:
I want to try the lollipop that everyone loses their mind with so is it okay to flash d5803 firmware to d5833 phone? Is there a very simple guide here that explains everything? And when I flashed that d5803 firmware will I lose my keys?
Also, if I dont like the lollipop, can I flash back to d5833 kitkat firmware?
Thank you guys! I dont have any knowledge about this flashing things so I wanna ask you guys first.
Click to expand...
Click to collapse
I am using 5803 firmware Italy on my 5833. Everything works. You will have absolutely no problems. In fact i didn't even wipe data. (Using flashtool)
Also you can flash back to 5833 kitkat firmware but it has to be a clean flash (must wipe data).
Sent from my D5803 using XDA Free mobile app
Sadman Khan said:
I am using 5803 firmware Italy on my 5833. Everything works. You will have absolutely no problems. In fact i didn't even wipe data. (Using flashtool)
Also you can flash back to 5833 kitkat firmware but it has to be a clean flash (must wipe data).
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
You're the one that I am talking about!
Btw, when I flash back to kitkat, is it the same procedure but Im wiping data this time? I saw this guide from xperia blog and I think this is the guide that I will follow through http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
Is that a good guide? Thank you for your reply!
Been out of the flashing world for some time now, as i need my phone for work and can't risk a bricked phone for even a day. Do we still have to worry about losing Sony licenses for the camera and bravia engines from unlocking the bootloader? Forgive me, i can't remember all of the terms. Do we need top unlock the bootloader to boot still?
Sent from my D5803 using Tapatalk
braveally said:
Been out of the flashing world for some time now, as i need my phone for work and can't risk a bricked phone for even a day. Do we still have to worry about losing Sony licenses for the camera and bravia engines from unlocking the bootloader? Forgive me, i can't remember all of the terms. Do we need top unlock the bootloader to boot still?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
If you root with this tool http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598 your bootloader will stay locked with TA keys, if you want to unlock the bootloader - FIRST backup the TA keys with this http://forum.xda-developers.com/showthread.php?t=2292598 then you can unlock bootloader and if you need to send your phone in for repairs just restore the TA keys
giotzkie05 said:
I want to try the lollipop that everyone loses their mind with so is it okay to flash d5803 firmware to d5833 phone? Is there a very simple guide here that explains everything? And when I flashed that d5803 firmware will I lose my keys?
Also, if I dont like the lollipop, can I flash back to d5833 kitkat firmware?
Thank you guys! I dont have any knowledge about this flashing things so I wanna ask you guys first.
Click to expand...
Click to collapse
If you look here this guy flashed it, seems to work fine as well
NaminatoR1254jaime.sier said:
Yeah, I did flash it.
I used xperifirm to download a Generic Latinamerican Firmware, because Im from Chile, and I use carrier Movistar, and their firmware is soooooo old, is the number version you use to root the z3c (the one finishing in .93)
After that, I used flashtool (I used 0.9.18.3) and built the firmware, but left cust-reset.ta and the other reset.ta out of it.
Finally, with the same flashtool I flashed everything, except baseband and in wipe I unticked data.
Took a long while to flash and a longer to boot (optimizing apps blabla) but it runs great.
EDIT: Working with it a little more, the only thing I dont have working is the led notifications.
EDIT2: Yes I do. Turns out I love to use the phone in silent mode...but silent mode [and priority mode] disables led notifications (even if they are in fact enabled in settings). So I have to use "sound mode" and vibration.
Click to expand...
Click to collapse
ALSO
giotzkie05 said:
You're the one that I am talking about!
Btw, when I flash back to kitkat, is it the same procedure but Im wiping data this time? I saw this guide from xperia blog and I think this is the guide that I will follow through http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
Is that a good guide? Thank you for your reply!
Click to expand...
Click to collapse
Usually when you downgrade from a newer firmware (this is from experience) without wiping data there will be an unlimited wave of error messages popping up. so yes if you want to go back to KitKat wipe data as well - you can make a backup of data using TWRP then restore only the data (that worked for me a few times)
And yes that guid looks good - although you can just download the .ftf file from here http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 Just makes the process a bit easier
giotzkie05 said:
You're the one that I am talking about!
Btw, when I flash back to kitkat, is it the same procedure but Im wiping data this time? I saw this guide from xperia blog and I think this is the guide that I will follow through http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
Is that a good guide? Thank you for your reply!
Click to expand...
Click to collapse
Yes it's the best guide. go for it! When you flash back to kit kat you have to wipe data. But when you upgrade to lollipop from kitkat you don't necessarily have to wipe data. Have fun
And like he said, just grab the ftf from that link. That will save you the trouble of going through the xperifirm steps. Just follow the flashtool steps. Make sure you copy the ftf you download from that link to flashtool>firmwares. Then it will show up in the list. Follow the rest of the steps from the xperiablog link
Sent from my D5803 using XDA Free mobile app
Hello there!
I am with Nordic (5803) version on my 5833 phone since a week ago. No problems so far, i am just not using 4G (where the most differences are assumed to be).
The only issue I had, was the battery drain in the first hours after I've flashed. Then i just restarted the phone, and since then, no problems.
http://forum.xda-developers.com/z3-compact/general/d5833-23-1-0-690r9c-t3071901
nzzane said:
Usually when you downgrade from a newer firmware (this is from experience) without wiping data there will be an unlimited wave of error messages popping up. so yes if you want to go back to KitKat wipe data as well - you can make a backup of data using TWRP then restore only the data (that worked for me a few times)
And yes that guid looks good - although you can just download the .ftf file from here http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 Just makes the process a bit easier
Click to expand...
Click to collapse
When I will go back to kitkat is it the same procedure? Just like the instructions in the link that you have given?
Sadman Khan said:
Yes it's the best guide. go for it! When you flash back to kit kat you have to wipe data. But when you upgrade to lollipop from kitkat you don't necessarily have to wipe data. Have fun
And like he said, just grab the ftf from that link. That will save you the trouble of going through the xperifirm steps. Just follow the flashtool steps. Make sure you copy the ftf you download from that link to flashtool>firmwares. Then it will show up in the list. Follow the rest of the steps from the xperiablog link
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. I am now on lollipop and enjoying it so far. Ill try that another method next time
maranBG said:
Hello there!
I am with Nordic (5803) version on my 5833 phone since a week ago. No problems so far, i am just not using 4G (where the most differences are assumed to be).
The only issue I had, was the battery drain in the first hours after I've flashed. Then i just restarted the phone, and since then, no problems.
Click to expand...
Click to collapse
That's true. I had battery drain at first and very lag phone but after some restarts and some usage it came back to its fast and snappy UI.
giotzkie05 said:
When I will go back to kitkat is it the same procedure? Just like the instructions in the link that you have given?
Click to expand...
Click to collapse
Yep when you go back same procedure just wipe data
I'm using the Baltic D5803 Lollipop update on my Australian D5833. No issues or noticeable change in radio connectivity, I'd say flash away.
Seems 100% cross compatible with D5833. No idea why some users are suggesting it will soft brick or otherwise harm your device.
AndIKnow said:
I'm using the Baltic D5803 Lollipop update on my Australian D5833. No issues or noticeable change in radio connectivity, I'd say flash away.
Seems 100% cross compatible with D5833. No idea why some users are suggesting it will soft brick or otherwise harm your device.
Click to expand...
Click to collapse
I must admit, I'm pretty surprised to see this. Haven't rooted anything since my Z1. When i had my previous Samsung and HTC phones, using firmware from models usually bricked the phone. Nice to see it possible here.
Sent from my D5803 using Tapatalk
---------- Post added at 09:05 AM ---------- Previous post was at 09:03 AM ----------
nzzane said:
If you root with this tool http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598 your bootloader will stay locked with TA keys, if you want to unlock the bootloader - FIRST backup the TA keys with this http://forum.xda-developers.com/showthread.php?t=2292598 then you can unlock bootloader and if you need to send your phone in for repairs just restore the TA keys
If you look here this guy flashed it, seems to work fine as well
ALSO
Usually when you downgrade from a newer firmware (this is from experience) without wiping data there will be an unlimited wave of error messages popping up. so yes if you want to go back to KitKat wipe data as well - you can make a backup of data using TWRP then restore only the data (that worked for me a few times)
And yes that guid looks good - although you can just download the .ftf file from here http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 Just makes the process a bit easier
Click to expand...
Click to collapse
Think i have to wait until there is compatibility with lollipop. Already upgraded, and tool not working unfortunately. Thanks for the info though, I'll keep a close eye.
Sent from my D5803 using Tapatalk
I want to know if it's possible to backup using iovryroot my DRM keys using "tabackup" command from mm 6.0.1 model E6533.☺
MoeDia said:
I want to know if it's possible to backup using iovryroot my DRM keys using "tabackup" command from mm 6.0.1 model E6533.☺
Click to expand...
Click to collapse
Ivyroot only works on certain devices and certain lollipop kernels dated before Dec 15th you'll probably have to downgrade back to lollipop first.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Ivyroot only works on certain devices and certain lollipop kernels dated before Dec 15th you'll probably have to downgrade back to lollipop first.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
So, I downgraded my Xperia from MM to Loip.. and I backed up the TA partition, and now I messed up and I want to know how to fix what I have done.. the only thing I can access is Fastboot Mode, and Recovery Mode... both have nothing just blue LED for fastboot Green LED for recovery mode.. Help me Plz.
MoeDia said:
So, I downgraded my Xperia from MM to Loip.. and I backed up the TA partition, and now I messed up and I want to know how to fix what I have done.. the only thing I can access is Fastboot Mode, and Recovery Mode... both have nothing just blue LED for fastboot Green LED for recovery mode.. Help me Plz.
Click to expand...
Click to collapse
If you have backed up your TA, all you need to do is to start the phone in flash mode (Google it) and use flashtool (Google it) and flash the ftf i.e. the firmware of your choice (Google it). Or use Sony Xperia companion to repair the firmware.
Remember that the advice of strangers is never a replacement for your own personal research. Take a look at the guide that I have posted in the general forum.
najoor said:
If you have backed up your TA, all you need to do is to start the phone in flash mode (Google it) and use flashtool (Google it) and flash the ftf i.e. the firmware of your choice (Google it). Or use Sony Xperia companion to repair the firmware.
Remember that the advice of strangers is never a replacement for your own personal research. Take a look at the guide that I have posted in the general forum.
Click to expand...
Click to collapse
Okay, Just do u know how to flash a custom recovery and enter it? I have an unlocked bootloader
MoeDia said:
Okay, Just do u know how to flash a custom recovery and enter it? I have an unlocked bootloader
Click to expand...
Click to collapse
Well, of course I know! That is why I wrote the above-mentioned guide for you: http://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Please read it. Makes me feel less remorse for the hours I spent on writing it...
najoor said:
Well, of course I know! That is why I wrote the above-mentioned guide for you: http://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Please read it. Makes me feel less remorse for the hours I spent on writing it...
Click to expand...
Click to collapse
Okay, I was a very nice guide, everything went well but every time I flash a custom rom i get command saying this device in not ivy
I'm currently on rooted:
XQ-AT51_Customized UK_1321-7192_58.0.A.0.1040_R8A
Looking to update to:
XQ-AT51_Customized UK_1321-7192_58.0.A.3.31_R8A
What's the best way to do this?
Research seems to suggest delete all .TA files aswell as the userdata file and if that works, to flash an extracted/pactched boot.img that I've already prepped. Though some users mention that they then get a decryption error resulting in the need to fully wipe.
I'd be grateful to hear from anyone who has successfully updated their Xperia 1 ii (with Flashtool or newflasher?).
Many thanks
Bump - anyone successfully updated their rooted firmware yet?
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Montane said:
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Click to expand...
Click to collapse
Hmm I thought that by being rooted/bootloader unlocked it's messed with the system updates. See attached, as Xperia Assist says there's an update available yet then clicking via Software Update it says I'm up to date.
I'm on 58.0.A.0.1040 customized UK and yet there's 58.0.A.3.39 available via Xperifirm
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Winrahr said:
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Click to expand...
Click to collapse
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Winrahr said:
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
Click to expand...
Click to collapse
Thanks yeah I may try that, or just stick to clean flashes
Montane said:
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Click to expand...
Click to collapse
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
cd993 said:
Thanks yeah I may try that, or just stick to clean flashes
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
Click to expand...
Click to collapse
Feels good to have an sd card to put all your backups on again doesn't it haha. I will not miss having to back up the internal storage slowly through USB2.0 just in case I have to wipe the entire storage.
I'm going to try a dirty flash on the next firmware update and hopefully I don't soft brick it again. Not having TWRP is new and scary to me.
Bump
With an updated firmware slowly rolling out (the one adding the RAW support and July security update) patch) etc, anyone managed to update when bootloader unlocked and rooted, avoiding losing data?
If I have to do a clean flash it wouldn't be the end of the world but I would love to avoid the hassle of (even with the usage of Swift Backup etc) and little things like not losing my autobrightness settings which have been learning my usage etc
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
YandereSan said:
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
Click to expand...
Click to collapse
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Newflasher guy gets mad when you talk about anything other than flashing every file so I'll post my update here.
Removed persist.sin and userdata.sin from the 3.88 update and ran through newflasher v33. Booted right back up and lost no data. YMMV.
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
By "rooting" for WiFi calling did you just flash another customization or did you unlock the bootloader? AFAIK there's no reason to root for getting WiFi calling as flashing another firmware is the easiest way.
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
Do you mean to say you received at OTA update notification via the system update option when rooted? Or you did a manual flash via newflasher?
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Montane said:
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Click to expand...
Click to collapse
If you unlocked your bootloader then you will not be able to take OTAs. You do not need to have bootloader unlocked to flash another stock firmware (ie through flashtool or newflasher). You do need to have bootloader unlocked to obtain root privileges.
cd993 said:
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Click to expand...
Click to collapse
I unlocked my Xperia 1 II, downloaded the latest raw update from XperiFirm, deleted the userdata file, put the phone into download mode (vol. down + power), flashed via NewFlasher v33.
Phone booted up perfectly fine. Running the latest update and have raw option for all 3 cameras.
The only time your device will wipe is when you first unlock the bootloader. Otherwise, you shouldn't have any issues updating it.
I've recently purchased an XZ1c since my old z3c was basically falling apart at this point. (Would have kept it if the repair guy didn't royally screw things up.)
The phone is practically untouched physically and has been great for the past two weeks... It was when I tried taking pictures that I've noticed my first problem.
Green pictures had to reboot to see if the bootloader was unlocked and to my chagrin, the previous owner never told me they had unlocked the phone in the first place and didn't even know about DRM keys so those are lost.
I've rooted my old z3c before a long time ago and it was painless. Now with this phone, I'm having a bit of a problem and I'm hesitant to even try rooting it since I haven't rooted a phone since and I would prefer getting advices.
I am aware of the guide on rooting the phone and would have no problems following it if it wasn't for the fact that my phone's build was currently 47.1.A.12.270 and the guides use the .16.20 update but can't find the files to update to the September build. Model G8441
Since the phone is unlocked, I can't update through the normal means in order to get to that update or get 9.0 for that matter in order to do the root. Is there a guide on updating the phone to those before using the guide to root it? I haven't done this in a long time and don't remember anything. Thanks in advance!
Kesymos said:
I've noticed my first problem.
Green pictures had to reboot to see if the bootloader was unlocked
Click to expand...
Click to collapse
Every time to you boot or reboot it should tell you it's been unlocked. I'd have sent it back as soon as I booted it up.
Kesymos said:
Since the phone is unlocked, I can't update through the normal means in order to get to that update or get 9.0 for that matter in order to do the root.
Click to expand...
Click to collapse
As you don't need to worry about your TA partition use the Flashtool or Newflasher to upgrade to Pie, flash TWRP, install Magisk, done.
SXUsr said:
As you don't need to worry about your TA partition use the Flashtool or Newflasher to upgrade to Pie, flash TWRP, install Magisk, done.
Click to expand...
Click to collapse
I don't need to worry about going to .16.20 before upgrading to pie, just go directly?
If so, it's a lot easier than I thought. With my z3c I had to upgrade to a specific build prior rooting.
Just to make sure, the phone comes from the US so I should get the Customized US version for 47.2.A.11.228?
Kesymos said:
I don't need to worry about going to .16.20 before upgrading to pie, just go directly?
Click to expand...
Click to collapse
Correct.
Kesymos said:
Just to make sure, the phone comes from the US so I should get the Customized US version for 47.2.A.11.228?
Click to expand...
Click to collapse
Sure. If you have issues with the fingerprint reader give some of these THREADS a read.
SXUsr said:
Sure. If you have issues with the fingerprint reader give some of these THREADS a read.
Click to expand...
Click to collapse
Thanks, I'm not really going to use the feature but if It causes problem, I'll look into it. My only problem now is finding and downloading the tft file for the update so I can flash but I'm having difficulty finding such thing.
I was able to download the DE version that is over 2 gigs. Does the version truly matter?
Kesymos said:
My only problem now is finding and downloading the tft file for the update so I can flash but I'm having difficulty finding such thing.
Click to expand...
Click to collapse
Open the flashtool, run Xperifirm and it's there.
Kesymos said:
I was able to download the DE version that is over 2 gigs. Does the version truly matter?
Click to expand...
Click to collapse
Not really, apart from bloatware.
SXUsr said:
Open the flashtool, run Xperifirm and it's there.
Click to expand...
Click to collapse
Oh wow, even more proof I haven't done this in a while, I completely forgot about xperifirm, still have it on my computer, just need to update it. Now I feel dumb.
Thanks again for the reminder!