I have a branded Z5C. I would like to remove the branding, and I guess this can be done by flashing an unbranded firmware?
Are there any trustable sources for the stock firmwares?
How would I then flash the firmware?
Ok, found the http://www.flashtool.net
Seems this does the job, branding free images are availabe.
Should I hard reset the device before I flash? Currently MobileIron ist installed and the device is encrypted.
esackbauer said:
Ok, found the http://www.flashtool.net
Seems this does the job, branding free images are availabe.
Should I hard reset the device before I flash? Currently MobileIron ist installed and the device is encrypted.
Click to expand...
Click to collapse
Yea i would do a clean install but you can always back up your data with the Sony PC Companion 2.1 app and then install the clean firmware.
Hi can I ask you when did you find brand free images?
j0sh0 said:
Hi can I ask you when did you find brand free images?
Click to expand...
Click to collapse
With this tool: http://forum.xda-developers.com/attachment.php?attachmentid=3490614&d=1443565578
Then you can flash the downloaded firmware with flashtool. I did it yesterday and it works perfectly.
Unfortunately I've a mac so I can't use it ?
---------- Post added at 07:09 PM ---------- Previous post was at 06:47 PM ----------
Drakorcarnis0 said:
With this tool: http://forum.xda-developers.com/attachment.php?attachmentid=3490614&d=1443565578
Then you can flash the downloaded firmware with flashtool. I did it yesterday and it works perfectly.
Click to expand...
Click to collapse
I've installed it using virtualbox. Which version did you pick? Does customized mean unbranded? Thanks.
j0sh0 said:
Unfortunately I've a mac so I can't use it ?
---------- Post added at 07:09 PM ---------- Previous post was at 06:47 PM ----------
I've installed it using virtualbox. Which version did you pick? Does customized mean unbranded? Thanks.
Click to expand...
Click to collapse
I choosed "Customized FR" as I'm French and it's unbranded. You should choose à "Customized" firmware of your country.
Envoyé de mon E5823 en utilisant Tapatalk
Drakorcarnis0 said:
I choosed "Customized FR" as I'm French and it's unbranded. You should choose à "Customized" firmware of your country.
Envoyé de mon E5823 en utilisant Tapatalk
Click to expand...
Click to collapse
Ok thanks I guess I'm going for the central europe 1 so as there is no customized Ireland.
Hi guys,
I have a problem when I want to flash my Z5c with an original firmware from XperiFirm I Flashtool which freezes the transfer at this file : fotakernel.sin
I tried lots of stuff, update, USB cable, different version of Flashtool, change the driver but nothing doing ...
Whenever this is my phone was Brick and I have reinstalled it with PC companion the official branding firmware.
Do you have a solution or idea of the problem please?
21/012/2015 10:12:24 - INFO - Flashtool Version 0.9.19.10 built on 04-10-2015 21:00:00
21/012/2015 10:12:24 - INFO - Executing search strategies to find proxy selector
21/012/2015 10:12:24 - INFO - No proxy found for IE. Trying next one
21/012/2015 10:12:24 - INFO - Strategy firefox failed trying next one : No Firefox installation found
21/012/2015 10:12:24 - INFO - No proxy found for java. Trying next one
21/012/2015 10:12:24 - INFO - Syncing devices from github
21/012/2015 10:12:24 - INFO - Scanning devices folder for changes.
21/012/2015 10:12:31 - INFO - Pulling changes from github.
21/012/2015 10:12:32 - INFO - Devices sync finished.
21/012/2015 10:12:36 - INFO - Device disconnected
21/012/2015 10:12:52 - INFO - Selected Bundle for Sony Xperia Z5 Compact (E5823). FW release : 1299-1743_32.0.A.4.11_R10B. Customization : Customized_FR
21/012/2015 10:12:52 - INFO - Preparing files for flashing
21/017/2015 10:17:50 - INFO - Please connect your device into flashmode.
21/018/2015 10:18:05 - INFO - Device connected in flash mode
21/018/2015 10:18:06 - INFO - Opening device for R/W
21/018/2015 10:18:06 - INFO - Reading device information
21/018/2015 10:18:07 - INFO - Phone ready for flashmode operations.
21/018/2015 10:18:07 - INFO - Opening TA partition 2
21/018/2015 10:18:07 - INFO - Current device : E5823 - CB5A2xGJPx - 1298-7796_R8B - 1295-6639_32.0.A.4.16 - GENERIC_32.0.A.4.16
21/018/2015 10:18:07 - INFO - Closing TA partition
21/018/2015 10:18:07 - INFO - Start Flashing
21/018/2015 10:18:07 - INFO - Processing loader.sin
21/018/2015 10:18:07 - INFO - Checking header
21/018/2015 10:18:07 - INFO - Flashing data
21/018/2015 10:18:07 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_114 / Bootloader status : ROOTABLE
21/018/2015 10:18:07 - INFO - Max packet size set to 4096K
21/018/2015 10:18:20 - INFO - Making a TA backup
21/018/2015 10:18:20 - INFO - Opening TA partition 1
21/018/2015 10:18:20 - INFO - Start Dumping TA partition 1
21/018/2015 10:18:21 - INFO - Finished Dumping TA partition 1
21/018/2015 10:18:21 - INFO - TA partition 1 saved to C:\Documents and Settings\xxxxx\.flashTool\registeredDevices\CB5A28GJP7\s1ta\2015-10-21_10-18-20\1.ta
21/018/2015 10:18:21 - INFO - Closing TA partition
21/018/2015 10:18:21 - INFO - Opening TA partition 2
21/018/2015 10:18:22 - INFO - Start Dumping TA partition 2
21/018/2015 10:18:22 - INFO - Finished Dumping TA partition 2
21/018/2015 10:18:22 - INFO - TA partition 2 saved to C:\Documents and Settings\xxxxx\.flashTool\registeredDevices\CB5A28GJP7\s1ta\2015-10-21_10-18-20\2.ta
21/018/2015 10:18:22 - INFO - Closing TA partition
21/018/2015 10:18:22 - INFO - Parsing boot delivery
21/018/2015 10:18:22 - INFO - No flash script found. Using 0.9.18 flash engine
21/018/2015 10:18:22 - INFO - Opening TA partition 2
21/018/2015 10:18:22 - INFO - Writing TA unit 00002774. Value : [01]
21/018/2015 10:18:22 - INFO - Closing TA partition
21/018/2015 10:18:22 - INFO - Processing partition.sin
21/018/2015 10:18:22 - INFO - Checking header
21/018/2015 10:18:22 - INFO - Flashing data
21/018/2015 10:18:22 - INFO - Phone boot version : S1_Boot_MSM8994_LA1.2_114. Boot delivery version : S1_Boot_MSM8994_LA1.2_114
21/018/2015 10:18:22 - INFO - Boot delivery up to date. Nothing to do
21/018/2015 10:18:22 - INFO - Opening TA partition 2
21/018/2015 10:18:23 - INFO - Closing TA partition
21/018/2015 10:18:23 - INFO - Opening TA partition 2
21/018/2015 10:18:23 - INFO - Processing amss_fsg.sin
21/018/2015 10:18:23 - INFO - Checking header
21/018/2015 10:18:23 - INFO - Flashing data
21/018/2015 10:18:23 - INFO - Processing amss_fs_1.sin
21/018/2015 10:18:23 - INFO - Checking header
21/018/2015 10:18:23 - INFO - Flashing data
21/018/2015 10:18:23 - INFO - Processing amss_fs_2.sin
21/018/2015 10:18:23 - INFO - Checking header
21/018/2015 10:18:23 - INFO - Flashing data
21/018/2015 10:18:23 - INFO - Processing apps_log.sin
21/018/2015 10:18:23 - INFO - Checking header
21/018/2015 10:18:23 - INFO - Flashing data
21/018/2015 10:18:23 - INFO - Processing cache.sin
21/018/2015 10:18:23 - INFO - Checking header
21/018/2015 10:18:23 - INFO - Flashing data
21/018/2015 10:18:24 - INFO - Processing diag.sin
21/018/2015 10:18:24 - INFO - Checking header
21/018/2015 10:18:24 - INFO - Flashing data
21/018/2015 10:18:24 - INFO - Processing fotakernel.sin
21/018/2015 10:18:24 - INFO - Checking header
21/018/2015 10:18:24 - INFO - Flashing data
Click to expand...
Click to collapse
What should I flash my phone with, The UK or Australia Customized, FOr use in the United States. Or one of the Internal versions?
will one get the next update OTA faster than another?
esackbauer said:
I have a branded Z5C. I would like to remove the branding, and I guess this can be done by flashing an unbranded firmware?
Are there any trustable sources for the stock firmwares?
How would I then flash the firmware?
Click to expand...
Click to collapse
for a Sony novice like myself, what does it mean to have a branded phone. I have only ever used a nexus but wont be getting the new phones.
coleburns said:
for a Sony novice like myself, what does it mean to have a branded phone. I have only ever used a nexus but wont be getting the new phones.
Click to expand...
Click to collapse
It can be software branded and/or physically branded by the network. Software branded means they've customised the software (things like network logo shown as start-up, custom themes in the network's colours, applications linked to the provider etc). Physical branding means it has the network's logo on the handset. Branded phones will usually come in packaging that's covered in the networks branding.
Some brandings will get software updates later than stock ROMs
dsteinmann said:
What should I flash my phone with, The UK or Australia Customized, FOr use in the United States. Or one of the Internal versions?
will one get the next update OTA faster than another?
Click to expand...
Click to collapse
You can pick whatever because they all have USA in the settings so most regions will work.
esackbauer said:
It can be software branded and/or physically branded by the network. Software branded means they've customised the software (things like network logo shown as start-up, custom themes in the network's colours, applications linked to the provider etc). Physical branding means it has the network's logo on the handset. Branded phones will usually come in packaging that's covered in the networks branding.
Some brandings will get software updates later than stock ROMs
Click to expand...
Click to collapse
Thank you. I bought the z5 yesterday off ebay which is EE locked. But i dont believe i have seen any signs to it being hardware or software branded. I will double check though. I noticed on the flashtool site that you need to be rooted and bootloader locked. I assume you will no longer get updates at that point right?
coleburns said:
Thank you. I bought the z5 yesterday off ebay which is EE locked. But i dont believe i have seen any signs to it being hardware or software branded. I will double check though. I noticed on the flashtool site that you need to be rooted and bootloader locked. I assume you will no longer get updates at that point right?
Click to expand...
Click to collapse
Nah the flashtool is made by sony so no root needed https://www.youtube.com/watch?v=PKSyZ2amVNY
And i only think you need to unlock your bootloader when you install custom roms so for official one's you dont need a unlocked bootloader.
RiTCHiE007 said:
Nah the flashtool is made by sony so no root needed https://www.youtube.com/watch?v=PKSyZ2amVNY
And i only think you need to unlock your bootloader when you install custom roms so for official one's you dont need a unlocked bootloader.
Click to expand...
Click to collapse
Thanks a lot for the info, i didnt know Sony was this active with the developer network. I wonder why they dont get much love.
I'm certain I'm doing something stupid, but I can't seem to connect the phone into flashmode when flashing. I turn off the phone, unplug the usb cable, hold down the volume button, and simultaneously plug the cable back in, but nothing seems to happen. The little guide screen that tells me how to do all the above just sits there until I cancel out of it. What am I doing wrong?
Edit: Nevermind, I think its the type of usb cable i'm using. Doesn't seem to be recognizing the phone.
So, just to be sure, flashing an unbranded firmware downloaded with xperifirm doesn't require to unlock the bootloader ? It's my first Sony device so i'm kinda noob right now ... Don't want to lose those precious DRM haha
No, youre not losing DRM keys by flashing generic unbranded stock firmware. You can lose DRM keys by unlocking bootloader and that is not neccessery for flashing unbranded firmware
bubimir13 said:
No, youre not losing DRM keys by flashing generic unbranded stock firmware. You can lose DRM keys by unlocking bootloader and that is not neccessery for flashing unbranded firmware
Click to expand...
Click to collapse
Ok thank you !
And I guess I'll get the unbranded OTA after the unbranded update ?
Related
Hi!
I got my Xperia S a day ago, rebranded it to Nordic firmware while waiting for my sim unlock code. Today received a message from second place that there some trouble with imei and code can not be provided. So I need to get back on rogers firmware in order to exchange it.
I have tried to do it my self but when flashing in the middle it returns an error
18/048/2012 14:48:50 - INFO - Phone ready for flashmode operations.
18/048/2012 14:48:50 - INFO - Start Flashing
18/048/2012 14:48:50 - INFO - Flashing loader
18/048/2012 14:48:51 - INFO - Ending flash session
18/048/2012 14:48:51 - ERROR - Error in processHeader
18/048/2012 14:48:51 - ERROR - Error flashing. Aborted
18/048/2012 14:48:51 - INFO - Device connected in flash mode
18/048/2012 14:48:52 - INFO - Device disconnected
18/048/2012 14:48:55 - INFO - Device connected in flash mode
now redownloaded and install flash tool again, created bundle now with error:
18/002/2012 15:02:27 - INFO - <- This level is successfully initialized
18/002/2012 15:02:30 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
18/002/2012 15:02:30 - INFO - You can drag and drop ftf files here to start flashing them
18/002/2012 15:02:39 - INFO - Device disconnected
18/002/2012 15:02:54 - INFO - Decrypting FILE_3
18/003/2012 15:03:58 - INFO - Decrypting FILE_2
18/004/2012 15:04:00 - INFO - Decrypting FILE_1
18/004/2012 15:04:01 - INFO - Decryption finished
18/004/2012 15:04:29 - INFO - Starting bundle creation
18/004/2012 15:04:29 - INFO - Adding loader.sin renamed as loader.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding apps_log_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as apps_log.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding partition-image_S1-SW-LIVE-DE72-PID1-0002-MBR.sin renamed as partition-image.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding cache_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as cache.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding amss_fsg_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fsg.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding amss_fs_1_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fs_1.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding system_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as system.sin to the bundle
18/005/2012 15:05:27 - INFO - Adding simlock.ta renamed as simlock.ta to the bundle
18/005/2012 15:05:27 - INFO - Adding amss_fs_2_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fs_2.sin to the bundle
18/005/2012 15:05:27 - INFO - Adding userdata_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as userdata.sin to the bundle
18/005/2012 15:05:32 - INFO - Adding kernel_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as kernel.sin to the bundle
18/005/2012 15:05:32 - INFO - Adding fotakernel_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as fotakernel.sin to the bundle
18/005/2012 15:05:33 - INFO - Finished bundle creation
18/005/2012 15:05:58 - INFO - Selected S_73_rogers.ftf
18/005/2012 15:05:58 - INFO - Preparing files for flashing
18/006/2012 15:06:20 - INFO - Please connect your device into flashmode.
18/006/2012 15:06:24 - INFO - Device connected in flash mode
18/006/2012 15:06:25 - INFO - Opening device for R/W
18/006/2012 15:06:25 - INFO - Reading device information
18/006/2012 15:06:25 - INFO - Phone ready for flashmode operations.
18/006/2012 15:06:25 - INFO - Start Flashing
18/006/2012 15:06:25 - INFO - Flashing loader
18/006/2012 15:06:27 - INFO - Loader : null - Version : R5C004 / Bootloader status : NOT_ROOTABLE
18/006/2012 15:06:27 - INFO - Flashing kernel.sin
18/006/2012 15:06:32 - INFO - Flashing fotakernel.sin
18/006/2012 15:06:36 - INFO - Flashing amss_fs_2.sin
18/006/2012 15:06:39 - INFO - Flashing amss_fs_1.sin
18/006/2012 15:06:40 - INFO - Flashing partition-image.sin
18/006/2012 15:06:40 - INFO - Ending flash session
18/006/2012 15:06:40 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0076";ERR_DYNAMIC="failed to set ta config";
Corrected ftf bundle by not including partition-image.sin
So far so good, flashed correctly.
Now everything is good.
hows the phone run on nordic firmware?
glad I've been reading, I'm having a hard time figuring out if i need to sim unlock before i unlock the boot loader.
as the statement above it seems you did not sim unlock first.
do i need to sim unloack a rogers locked xperia s first, before i unlock the bootloader?
Thanks
I just got an unlock code from MobileInCanada, took about 18 hours. Popped in my Bell Simcard and it worked. The thing is that the bootloader is still locked.
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
I think that if you use official boot loader unlock you have to sim unlock your phone first.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
What i noticed that before I sim unlocked my first xperia S (had dead pixels returned same day) it said No in that menu, and after sim unlock it changed to Yes.
Sim unlock does not unlock bootloader. You got to use sony mobile developer website and follow all instruction on there.
unlockbootloader.sonymobile.com/instructions
ok mine says unlock boot loader allowed = no
I ordered my sim unlock 2 hours ago, so i guess im done tonight. really dont want to setup my new toy just to do it again in a day or two.
Thanks
zimbashka said:
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
I think that if you use official boot loader unlock you have to sim unlock your phone first.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
What i noticed that before I sim unlocked my first xperia S (had dead pixels returned same day) it said No in that menu, and after sim unlock it changed to Yes.
Sim unlock does not unlock bootloader. You got to use sony mobile developer website and follow all instruction on there.
unlockbootloader.sonymobile.com/instructions
Click to expand...
Click to collapse
Mine didn't change to yes...
Matt1408 said:
Mine didn't change to yes...
Click to expand...
Click to collapse
Have you try unlockbootloader.sonymobile.com/instructions ?
zimbashka said:
Have you try unlockbootloader.sonymobile.com/instructions ?
Click to expand...
Click to collapse
2.In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Mine says no, can't be unlocked... I can try the rest of the steps, nothing will happen...
sorry don't know what to advise, have no phone on me any longer.
zimbashka said:
( make sure you got rogers back up firmware just in case)
Click to expand...
Click to collapse
How did you back up the rogers firmware?
still waiting for my sim unlock key from canadagsm.ca, might be a late one tonight. lol
What I did to back up rogers firmware is use SEUS to update your phone even if it has latest software. After update is successful go to C:\Program Files\Sony Ericsson\Update Service\ db folder there should be 3 files named FILE_XXXXX, (their size is 64kb,9487kb,288381kb you should have something similar).
Copy those 3 files to some folder that is easy for you to find.
Then open latest flashtool go to advanced>decrypt files
when window opens select folder where those files saved.
Select those 3 file and wait for it to finish decrypting.
Once it is done another window will pop up that will assist you to create ftf bundle. Just select all files accept for partition-image.sin and wait for it to finish. Created ftf bundle will be in directory where falashtool was instaled in folder called firmwares.
You are done!
Now you can flash your phone anytime you need to put Rogers firmware back in.
thanks, i have been using htc for a few months and coming back to se (sony) i feel as though im starting all over again.
do you know if you can enter the sim unlock code with out using a different sim? i don't have one.
if you need a sim from another carrier i guess ill have to buy one.
Yeah, you will need to use another sim card. I found an old Bell one and I cut it up to fit. Worked, but easy to screw up.
Matt1408 said:
Mine didn't change to yes...
Click to expand...
Click to collapse
I think that rebranding of the phone is necessary step for your phone to be boot loader unlockable. At least that is what I understand from reading forum.
I just got new xperia S (sim unlocked it few hours ago) will put another software and let you know if that changed anything.
edit:
Just finished with flasing still boot loader not unlockable.
ok i entered my sim unlock code and the service menu still says bootloader unlock allow=no
does this mean i cant use sony's site to unlock the bootloader?
I guess it's the same boat as I am on. I guess we have to wait for the test point method to become active. (And in the proccess tear apart our phones)
I really want to like this phone but it's hard to do with the Sony interface. I would love to load up some CM9 right now but I can't due to this stupid carrier crap. I do wish it was more like Europe were unlocked phones are not some kind of secret market.
Oh well, I guess I will have to do with using a custom launcher for now...
yeah it might be a while before the test point id ready.
i have a question for rogers users, in the service menu my model says, LT26i, should we not be LT26a
I thought se versions with i at the end was for international versions?
Yeah, I noticed that right away. I don't think an "a" version of the phone exists. I believe the "i" is just capable of all bands.
zimbashka said:
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
Click to expand...
Click to collapse
just had a thought, i wonder if using the ftf files of a rogers phone that can have the boot loader unlocked and using the se update service with those files would allow me to unlock the bootloader on se sites.?
maybe a dev can answer this.
Hi
I've just found FTF file with Lollipop for my SGP612
But.. Do I have to unlock bootloader when I flash stock firmware or not?
Bruce666 said:
Hi
I've just found FTF file with Lollipop for my SGP612
But.. Do I have to unlock bootloader when I flash stock firmware or not?
Click to expand...
Click to collapse
No you don't, but you will have no root if you flash stock ftf via flashtool. And the only way to get root until a lollipop flaw is discovered is to follow the tutorials on 4.4.4 and then upgrade via flashable zip.
lowtraxx said:
No you don't, but you will have no root if you flash stock ftf via flashtool. And the only way to get root until a lollipop flaw is discovered is to follow the tutorials on 4.4.4 and then upgrade via flashable zip.
Click to expand...
Click to collapse
So.. OK if I don't have to unlock bootloader it's impossible to void warranty?
lowtraxx said:
No you don't, but you will have no root if you flash stock ftf via flashtool. And the only way to get root until a lollipop flaw is discovered is to follow the tutorials on 4.4.4 and then upgrade via flashable zip.
Click to expand...
Click to collapse
tried to flash and had an error in FlashTool...
Code:
19/026/2015 22:26:25 - INFO - Flashtool Version 0.9.18.5 built on 14-02-2015 15:30:00
19/026/2015 22:26:25 - INFO - Executing search strategies to find proxy selector
19/026/2015 22:26:25 - INFO - No proxy found for IE. Trying next one
19/026/2015 22:26:25 - INFO - Strategy firefox failed trying next one : No Firefox installation found
19/026/2015 22:26:25 - INFO - No proxy found for java. Trying next one
19/026/2015 22:26:25 - INFO - Syncing devices from github
19/026/2015 22:26:25 - INFO - Scanning devices folder for changes.
19/026/2015 22:26:35 - INFO - Pulling changes from github.
19/026/2015 22:26:35 - INFO - Devices sync finished.
19/026/2015 22:26:43 - INFO - Device connected with USB debugging off
19/026/2015 22:26:43 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/003/2015 23:03:15 - INFO - Device disconnected
19/003/2015 23:03:18 - INFO - Selected Bundle for Sony Xperia Z3 Tablet Compact (SGP612). FW release : 23.1.A.0.690. Customization : Generic
19/003/2015 23:03:18 - INFO - Preparing files for flashing
19/009/2015 23:09:10 - INFO - Please connect your device into flashmode.
19/010/2015 23:10:03 - INFO - Device connected in flash mode
19/010/2015 23:10:04 - INFO - Opening device for R/W
19/010/2015 23:10:05 - INFO - Start Flashing
19/010/2015 23:10:05 - INFO - Processing loader.sin
19/010/2015 23:10:05 - INFO - Checking header
19/010/2015 23:10:05 - ERROR - Processing of loader.sin finished with errors.
19/010/2015 23:10:05 - INFO - Ending flash session
19/010/2015 23:10:05 - ERROR -
19/010/2015 23:10:05 - ERROR - Error flashing. Aborted
19/010/2015 23:10:05 - INFO - Device connected in flash mode
19/010/2015 23:10:10 - INFO - Device disconnected
yes if haven't unlock the bootloader your warranty maybe good that being said if you don't have root cos root can void warranty as well in some cases. but without unlocking the bootloader the DMR keys are intact. just make sure that if you run into a technical problem and need to return it for exchange or repair set the devise to stock.
jaime4272 said:
yes if haven't unlock the bootloader your warranty maybe good that being said if you don't have root cos root can void warranty as well in some cases. but without unlocking the bootloader the DMR keys are intact. just make sure that if you run into a technical problem and need to return it for exchange or repair set the devise to stock.
Click to expand...
Click to collapse
but what means this error in FlashTool?
I tried updating my Sony Xperia Z3v with Flashtool
Flashtool 9.19.10 is installed. Download firmware 23.0.A.2.93 and 23.4.A.1.264 (tried both)
I get the error "Processing of partition-image.sin finished with errors" and, of course, my phone can't boot anymore.
Code:
18/058/2016 17:58:07 - INFO - Please connect your device into flashmode.
18/058/2016 17:58:30 - INFO - Device connected in flash mode
18/058/2016 17:58:30 - INFO - Opening device for R/W
18/058/2016 17:58:30 - INFO - Reading device information
18/058/2016 17:58:30 - INFO - Phone ready for flashmode operations.
18/058/2016 17:58:30 - INFO - Opening TA partition 2
18/058/2016 17:58:30 - INFO - Current device : D6708 - BH9011T61N - 1288-1477_R19B - 1278-4381_23.0.E.1.44 - VERIZON-LTE_23.0.E.1.44
18/058/2016 17:58:30 - INFO - Closing TA partition
18/058/2016 17:58:30 - INFO - Start Flashing
18/058/2016 17:58:30 - INFO - Processing loader.sin
18/058/2016 17:58:30 - INFO - Checking header
18/058/2016 17:58:30 - INFO - Flashing data
18/058/2016 17:58:31 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_22 / Boot version : S1_Boot_MSM8974AC_LA3.0_59_VZW / Bootloader status : NOT_ROOTABLE
18/058/2016 17:58:31 - INFO - Max packet size set to 512K
18/058/2016 17:58:31 - INFO - Making a TA backup
18/058/2016 17:58:31 - INFO - Opening TA partition 1
18/058/2016 17:58:31 - INFO - Start Dumping TA partition 1
18/058/2016 17:58:32 - INFO - Finished Dumping TA partition 1
18/058/2016 17:58:32 - INFO - TA partition 1 saved to C:\Flashtool\registeredDevices\BH9011T61N\s1ta\2016-03-18_05-58-31\1.ta
18/058/2016 17:58:32 - INFO - Closing TA partition
18/058/2016 17:58:32 - INFO - Opening TA partition 2
18/058/2016 17:58:32 - INFO - Start Dumping TA partition 2
18/058/2016 17:58:32 - INFO - Finished Dumping TA partition 2
18/058/2016 17:58:32 - INFO - TA partition 2 saved to C:\Flashtool\registeredDevices\BH9011T61N\s1ta\2016-03-18_05-58-31\2.ta
18/058/2016 17:58:32 - INFO - Closing TA partition
18/058/2016 17:58:32 - INFO - Parsing boot delivery
18/058/2016 17:58:32 - INFO - No flash script found. Using 0.9.18 flash engine
18/058/2016 17:58:32 - INFO - Opening TA partition 2
18/058/2016 17:58:33 - INFO - Writing TA unit 00002774. Value : [01]
18/058/2016 17:58:33 - INFO - Closing TA partition
18/058/2016 17:58:33 - INFO - Processing partition-image.sin
18/058/2016 17:58:33 - INFO - Checking header
18/058/2016 17:58:33 - ERROR - Processing of partition-image.sin finished with errors.
18/058/2016 17:58:33 - INFO - Ending flash session
18/058/2016 17:58:33 - ERROR -
18/058/2016 17:58:33 - ERROR - Error flashing. Aborted
18/058/2016 17:58:33 - INFO - Flashing finished.
18/058/2016 17:58:33 - INFO - Please unplug and start your phone
18/058/2016 17:58:33 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
18/058/2016 17:58:33 - INFO - Device connected in flash mode
18/058/2016 17:58:33 - INFO - Device disconnected
How can I get my phone to work again? And ideally updated to the latest version. Thanks!
I'm using Windows 10 and since I use it outside of USA and don't have Verizon, automatic update doesn't work so I believe flashing is the only way to get an update. It is a stock Z3v phone with all the Verizon crap.
Edit:
Here's the error part of the log with Debug output, in case it can give something useful
Code:
18/026/2016 19:26:14 - INFO - Processing partition.sin
18/026/2016 19:26:14 - INFO - Checking header
18/026/2016 19:26:14 - DEBUG - Writing packet to phone
18/026/2016 19:26:14 - DEBUG - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1032 / Data CRC32 : [AC, 28, 7A, AB]
18/026/2016 19:26:14 - DEBUG - Reading packet from phone
18/026/2016 19:26:14 - DEBUG - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
18/026/2016 19:26:14 - DEBUG - Writing packet to phone
18/026/2016 19:26:14 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
18/026/2016 19:26:14 - DEBUG - Reading packet from phone
18/026/2016 19:26:14 - DEBUG - IN : CommandID : 7 / Flags : false,false,false / Data length : 61 / Data CRC32 : [BC, 39, C4, 26]
18/026/2016 19:26:14 - ERROR - Processing of partition.sin finished with errors.
You can follow my guide for a much simpler way to upgrade to the latest and get root. Doesn't require flashtool or anything.
I could have before I started, but not anymore.
Now I tried flashing while unchecking "partition.sin" to see what happens. Now the phone can't turn on at all... dead. What can be done? Perhaps a hardware flash by a very competent technician with the right equipment is the only option at this point?
MysteryXx said:
I could have before I started, but not anymore.
Now I tried flashing while unchecking "partition.sin" to see what happens. Now the phone can't turn on at all... dead. What can be done? Perhaps a hardware flash by a very competent technician with the right equipment is the only option at this point?
Click to expand...
Click to collapse
Flashtool 9.19.10 is installed. Download firmware 23.0.A.2.93 and 23.4.A.1.264 (tried both)
Click to expand...
Click to collapse
There's your obvious problem. You used firmwares that weren't designed for the Z3v. Therefore it's time to get another Z3v.
GigaSPX said:
There's your obvious problem. You used firmwares that weren't designed for the Z3v. Therefore it's time to get another Z3v.
Click to expand...
Click to collapse
I followed instructions that were specifically for the Z3v...
Can it be fixed through flashing the hardware chip directly? I guess I'll see tomorrow.
MysteryXx said:
I followed instructions that were specifically for the Z3v...
Can it be fixed through flashing the hardware chip directly? I guess I'll see tomorrow.
Click to expand...
Click to collapse
Instructions from where? You downloaded firmwares made for other Xperia devices, which are entirely different from the Verizon Variant. And I understand you wanted to have it debloated from the Verizon crapware, but that's part of the system you can easily use root to freeze them. No technician can fix this unless you really can try to flash the firmware that are specifically branded for the Z3v.
If a technician is equipped to flash the hardware, where can I download the specific firmware that needs to be written on it? Having the equipment is one thing; but he might not know what to put on it to make it work.
OK found a Thai guy in Panthip Plaza who has the equipment to flash the chip and who can repair for $20. He hasn't succeeded after 4 hours but he told me to give him 3 more days; he just needs more time. These Thai people can repair anything. You just need to find the right guys and give them enough time.
Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK
MysteryXx said:
OK found a Thai guy in Panthip Plaza who has the equipment to flash the chip and who can repair for $20. He hasn't succeeded after 4 hours but he told me to give him 3 more days; he just needs more time. These Thai people can repair anything. You just need to find the right guys and give them enough time.
Click to expand...
Click to collapse
http://forum.xda-developers.com/z3/xperia-z3v-general/stop-flash-roms-z3-section-t3252918
Just leaving this here to get some common sense grounds established. While it's great to know you're in BKK, not everyone is going to be hands on in knowing much about the Z3v since it's a US based phone, not structurally the same as the international Xperia variants. Good luck.
Haiboy said:
Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK
Click to expand...
Click to collapse
Thanks I'll tell him to try that firmware!
GigaSPX said:
http://forum.xda-developers.com/z3/xperia-z3v-general/stop-flash-roms-z3-section-t3252918
Just leaving this here to get some common sense grounds established. While it's great to know you're in BKK, not everyone is going to be hands on in knowing much about the Z3v since it's a US based phone, not structurally the same as the international Xperia variants. Good luck.
Click to expand...
Click to collapse
Even him thought that Z3 and Z3v would be the same; so not surprised he failed on the first day.
Haiboy said:
Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK
Click to expand...
Click to collapse
He tried that firmware and many other things and hasn't succeeded yet. He'll keep trying.
Any other ideas that could help him?
MysteryXx said:
He tried that firmware and many other things and hasn't succeeded yet. He'll keep trying.
Any other ideas that could help him?
Click to expand...
Click to collapse
There is nothing you can do. Your phone is done for, it's bricked. As I've said this earlier, whatever guide you followed outside of the Z3v forum, you were already heading towards a path to ruining your phone.
You're in BKK, there are plenty of Sony devices available. Just go buy yourself of Z5/Z5 Premium or at least a Z3.
In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.
MysteryXx said:
In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.
Click to expand...
Click to collapse
Try taking a computer from 1995 and install Windows 10 on it. Or take any Windows computer and install Mac OS X on it. Even take any Android phone, and try installing a ROM that's specifically made for a certain phone (Samsung Galaxy Phone with an LG ROM).
You should get my point, it's the compatibility issues. I've already explained several times, and you may as well ask for a second and third opinion, it's all the same. You're taking something and forcing it into a host that's incompatible. It's much like anatomy, transplanting an incompatible organ from one donor into the person who needs it will be all for naught because the white blood cells will attack thinking it's a threat.
Basing on what you've said so far, why can't you do it? You're spending time and money on a dead phone. It's a waste.
He hasn't succeeded; said maybe going to Sony Center, but might require changing the motherboard.
Installing MacOS on a PC won't start the install at all, but once my cousin accidentally installed Linux on a computer, flushed the partitions with all the important data and created new types of partitions. I was able to re-install Windows and recover most of the data (with undelete programs) without problem.
MysteryXx said:
He hasn't succeeded; said maybe going to Sony Center, but might require changing the motherboard.
Installing MacOS on a PC won't start the install at all, but once my cousin accidentally installed Linux on a computer, flushed the partitions with all the important data and created new types of partitions. I was able to re-install Windows and recover most of the data (with undelete programs) without problem.
Click to expand...
Click to collapse
Sony Center isn't going to help with consumer negligence and using tools outside of Sony's official programs, you also void warranty and support.
I never stated Linux since I knew very well that PCs can do Linux. And
Installing MacOS on a PC won't start the install at all...
Click to expand...
Click to collapse
There you go, you could never get the install process to fully go through, and therefore messed up your phone. Done deal.
MysteryXx said:
In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.
Click to expand...
Click to collapse
It is true, if you can get the EEPROM to a clean flashable state you can reflash an OS on it, getting it to that clean flashable state is another thing. People put Ubuntu Linux on phones, even Windows 98, heck one guy put Android on an iPhone. You are correct in that software doesn't always hurt the hardware.
I do a lot of work in Automotive computers, ECU, PCM, TCM, use to you had the take the EEPROM out of the com to flash, now we can flash through the OBD port, if a flash goes bad during the erase phase the EEPROM is toast, but if anything happens after that it is recoverable, only question is at what phase of the flash process did the fault happen here.
Use to you could flash BIOS on coms (probably still can), PROMs on CD/DVD drives, graphic cards all had a flashable PROM, haven't built a com in years but during the overclocking water cooling CPU gaming com days it wasn't unusual to flash new things and reload the OS cause you overclocked the CPU, Memory, or GPU too far and corrupted Winders (I dual booted and Linux would boot when Winders wouldn't).
So have flashed a few EEPROMs before.
GigaSPX said:
There you go, you could never get the install process to fully go through, and therefore messed up your phone. Done deal.
Click to expand...
Click to collapse
With a PC, you could make a scratch on the hard drive, fix the bad sectors (if the rest of the hard drive is still OK), recreate the partitions and re-install from scratch and you're good to go.
1linuxfreak said:
I do a lot of work in Automotive computers, ECU, PCM, TCM, use to you had the take the EEPROM out of the com to flash, now we can flash through the OBD port, if a flash goes bad during the erase phase the EEPROM is toast, but if anything happens after that it is recoverable, only question is at what phase of the flash process did the fault happen here.
Click to expand...
Click to collapse
You mean that you can toast the chip if something goes wrong?
At first it was giving error on "partition-image.sin" and was then rebooting on loop. Then I did the mistake of disabling partition from the flash process to see what happens... thinking that the software can never break the hardware. After that, it wasn't booting at all. And it appears that from his tests with flashing the chip directly, he wasn't able to get it to turn back on either even to that reboot loop.
Hello Guys,
my question is, if I'm going to unlock the bootloader the official way (place developers sonymobile link here) will my data be gone? I know it from HTC devices that they say all data will be formatted but the tutorial by sony doesnt mention anything in that way.
So, will the phone be formatted after unlocking or nah?
Thanks!
Edit: Well I searched about 30 Minutes for something what says that the data will be deleted before i created the thread. 1 Minute after I created the thread I found the part of the Info text where it says "Unlocking the boot loader will trigger a factory reset that erases all device settings, user data, third-party applications and associated data from the device’s hardware storage"
Well, sorry for the spam lol~
Synytrix said:
Hello Guys,
my question is, if I'm going to unlock the bootloader the official way (place developers sonymobile link here) will my data be gone? I know it from HTC devices that they say all data will be formatted but the tutorial by sony doesnt mention anything in that way.
So, will the phone be formatted after unlocking or nah?
Thanks!
Edit: Well I searched about 30 Minutes for something what says that the data will be deleted before i created the thread. 1 Minute after I created the thread I found the part of the Info text where it says "Unlocking the boot loader will trigger a factory reset that erases all device settings, user data, third-party applications and associated data from the device’s hardware storage"
Well, sorry for the spam lol~
Click to expand...
Click to collapse
Hi @syntrix
Im trying to unlock boot loader mode using flashtool but all it gives me when i use the BLU is this
09/038/2016 20:38:10 - INFO - Please connect your device into flashmode.
09/038/2016 20:38:11 - INFO - Opening device for R/W
09/038/2016 20:38:11 - INFO - Reading device information
09/038/2016 20:38:11 - INFO - Phone ready for flashmode operations.
09/038/2016 20:38:11 - INFO - Current device : E2353 - YT91158958 - 1293-8832_R7A - 1296-0230_26.1.A.3.111 - GENERIC_26.1.A.3.111
09/038/2016 20:38:11 - ERROR - root : this bundle is not valid
09/038/2016 20:38:12 - INFO - Processing loader.sin
09/038/2016 20:38:12 - INFO - Checking header
09/038/2016 20:38:12 - INFO - Flashing data
09/038/2016 20:38:12 - INFO - Processing of loader.sin finished.
09/038/2016 20:38:13 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_37 / Bootloader status : NOT_ROOTABLE
09/038/2016 20:38:13 - INFO - Start Reading unit 000008B2
09/038/2016 20:38:13 - INFO - Reading TA finished.
09/038/2016 20:38:13 - INFO - Ending flash session
09/038/2016 20:38:13 - INFO - Your phone bootloader cannot be officially unlocked
09/038/2016 20:38:13 - INFO - You can now unplug and restart your phone
What do i do??
Also my phone cannot connect to wifi and when it does it shuts itself off and keeps restarting
Is your status in service info, Bootloader unlock allowed:Yes ?
Hey.
I just downloaded latest firmware (32.4.A.1.54, Customized NOBA) with Xperifirm, but it just wont flash. I tried downloading it 3-4 times, and also tried Sweden 3's version of it. No luck. The previous FTF I have works thou..
The output i get in FlashTool is (and yes, I have the latest version);
Code:
25/019/2018 18:19:23 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 32.4.A.1.54. Customization : Customized NOBA
25/019/2018 18:19:23 - INFO - Preparing files for flashing
[COLOR="Red"]25/019/2018 18:19:25 - ERROR - invalid distance too far back[/COLOR]
25/019/2018 18:19:25 - INFO - Cannot open bundle. Flash operation canceled
25/019/2018 18:19:25 - INFO - Device disconnected
Tried searching for the solution, but just found stuff related to java coding. It seems so be some problem while unpacking the files? Unpacking it manually worked fine though. Anyone have an idea what the heck is wrong?
What version of flashtool are you using? Try rolling back to 0.9.18 version!
zynexx said:
(and yes, I have the latest version)
Click to expand...
Click to collapse
Strange, I tried to flash a Belgian FTF yesterday and it also failed (failed to process partition.sin)
Also using the latest version of flashtool (because newer is better )
I'll try to roll back to the previous version...
Kind regards,
Jan
Chronic2k13 said:
What version of flashtool are you using? Try rolling back to 0.9.18 version!
Click to expand...
Click to collapse
I have tried that to, trow the same error. Never had this problem before.
I tried flashing the system.sin file manually with flashtool, but give a size error (don't remember the exact error) and fails.
Hi all,
Flashing is still failing.
I'm now using Flashtool 0.9.18.6, but I've got the same results.
Recreated a new FTF-file from the firmware downloaded with the XperiFirm software.
26/029/2018 21:29:40 - ERROR - root : this bundle is not valid
26/029/2018 21:29:40 - INFO - Selected Bundle for Sony Xperia Z5 Compact (E5823). FW release : 32.2.A.5.11. Customization : Customized BE
26/029/2018 21:29:40 - INFO - Preparing files for flashing
26/031/2018 21:31:17 - INFO - Please connect your device into flashmode.
26/031/2018 21:31:38 - INFO - Device connected in flash mode
26/031/2018 21:31:39 - INFO - Opening device for R/W
26/031/2018 21:31:39 - INFO - Reading device information
26/031/2018 21:31:40 - INFO - Phone ready for flashmode operations.
26/031/2018 21:31:40 - INFO - Current device : E5823 - CB5A2B0MJY - 1299-0271_R4E - 1295-6639_32.4.A.1.54 - GENERIC_32.4.A.1.54
26/031/2018 21:31:40 - INFO - Start Flashing
26/031/2018 21:31:40 - INFO - Processing loader.sin
26/031/2018 21:31:40 - INFO - Checking header
26/031/2018 21:31:40 - INFO - Flashing data
26/031/2018 21:31:41 - INFO - Processing of loader.sin finished.
26/031/2018 21:31:41 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2.3_47 / Bootloader status : ROOTABLE
26/031/2018 21:31:42 - INFO - Processing partition-image.sin
26/031/2018 21:31:42 - INFO - Checking header
26/031/2018 21:31:42 - INFO - Flashing data
What bothers me is the first line: this bundle is not valid.
The last 'Flashing data' goes on forever...
Any suggestions?
Try downloading another ftf! And have you disabled driver verification? And you should leave flashtool to do its thing! Sometimes it can take a while
... and then, after uninstall version 0.9.18.* and upgrade to the latest version, it's starting to work (lucky me) (relieved)
Thanks for the comments though!
Jan
herrJones said:
... and then, after uninstall version 0.9.18.* and upgrade to the latest version, it's starting to work (lucky me) (relieved)
Thanks for the comments though!
Jan
Click to expand...
Click to collapse
Hi, I ran into the same problem and solved it by replacing the offending file by hand (for me it was loader.sin).
It seems to me that the 0.9.24's Bundler is producing invalid FTFs.
I'm wondering now: After uninstalling 0.9.18, did you create another FTF with 0.9.24 or did you use the one produced by 0.9.18?
Hi, sorry for the delay.
No, I just kept the original versions
-- Jan
TpmKranz said:
Hi, I ran into the same problem and solved it by replacing the offending file by hand (for me it was loader.sin).
It seems to me that the 0.9.24's Bundler is producing invalid FTFs.
I'm wondering now: After uninstalling 0.9.18, did you create another FTF with 0.9.24 or did you use the one produced by 0.9.18?
Click to expand...
Click to collapse
Hi, I have the same problem, but could not solve it.
What exactly do you mean by "replacing"? Copy loader.sin from "extracted" to "prepared? Didn't work for me though...
Anyone found a working solution to this problem? Tried again a couple of days ago, with both latest and prev. versions. Both fails.
Hi i have oem.sin error, anyone have solution for my problem? I've tried different ftf file but ended in oem.sin error