Related
Hi...
I just softkilled my phone by trying to downgrade to an older firmware I9300XXDLJ2_I9300XEFDLJ2_XEF stock by trying to flash via ODIN.
It gets stuck in the middle of the Road of the Flashing process on odin,I just realised that it is the new bootloader issue?
I was on Ultimate Rom..My bootloader is fine but can anyone link me a torrent to a newer Firmware(STOCK)?My internet connection is not very good enough to download via a single link. Waiting for your reply...
angry_machine said:
Hi...
I just softkilled my phone by trying to downgrade to an older firmware I9300XXDLJ2_I9300XEFDLJ2_XEF stock by trying to flash via ODIN.
It gets stuck in the middle of the Road of the Flashing process on odin,I just realised that it is the new bootloader issue?
I was on Ultimate Rom..My bootloader is fine but can anyone link me a torrent to a newer Firmware(STOCK)?My internet connection is not very good enough to download via a single link. Waiting for your reply...
Click to expand...
Click to collapse
Use Google if you want to find a firmware torrent .
jje
1. Follow above advice, use STOCK rom
2. if this will NOT help, use the ressurection firmware
The last option will WIPE your phone, so be wise.
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
BCityModz said:
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
Click to expand...
Click to collapse
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
mattnmag said:
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
Click to expand...
Click to collapse
Ive tried that one as well and almost all the files in that thread. When he flashed the 4.4.2 firmware the phone wouldnt boot all it did was flash the Note 2 screen. Ive used the pit file as well with no luck. Using the top file on the link fails almost instantly, VRAMC3 writes and passes but will not boot, shows the unauthorized firmware screen.
I'm wondering if he flashed a firmware onto the phone that was from a different carrier like ATT or something. If so, he may have messed up the phone so bad that it might need jtag to repair it.
You've probably already tried all the normal Odin tips like using a different usb cable, different ports on the computer (usb 2.0 port is recommended), etc... so I won't go over all those.
I've never tried it and don't know if I'd recommend it, but I recall reading some threads a while back where someone discussed trying the Nand Erase function in Odin.... (again.... I'm not saying to do that... but you may want to research it to see if it might be an option if nothing else works).
I've also read where people say that they've used Cygwin to create custom tar files... then they ODIN installed each of the separate partition files (e.g. recovery, boot, modem, system, etc...), onto their Samsung device.
I'm not knowledgeable enough to offer guidance with Cygwin and I'm not sure if either of these ideas would work, but I just thought I'd throw them out there for the sake of brainstorming for ideas. Maybe someone will respond to your request who has more knowledge and ideas.
I wish you luck with getting it fixed.
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
mrbix said:
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
mrbix said:
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
Click to expand...
Click to collapse
correct driver installation was a bit difficult also for me. good to know you solved the problem
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thank you. I had the same issue as OP, Google found me this thread and using flashtool 0.9.20.0 worked.