Hi,
I'm restore my last backup on twrp. Restore success but my phone enter loop on boot.
Than i want flash stock rom via xperifirm but i failed, error message; The bundle does not match the connected device
How can i fix this? || Current device : Unknown: Jul 24 2016/19:28:59 - BH90A7YR1L
14/004/2018 00:04:08 - INFO - Selected Bundle for Sony Xperia Z3(D6603). FW release : BH90A7YR1L. Customization : BH90A7YR1L
14/004/2018 00:04:08 - INFO - Preparing files for flashing
14/006/2018 00:06:10 - INFO - Please connect your device into flashmode.
14/006/2018 00:06:26 - INFO - Using Gordon gate drivers version 3.1.0.0
14/006/2018 00:06:26 - INFO - Opening device for R/W
14/006/2018 00:06:26 - INFO - Device ready for R/W.
14/006/2018 00:06:26 - INFO - Reading device information
14/006/2018 00:06:26 - INFO - Phone ready for flashmode operations.
14/006/2018 00:06:26 - INFO - Opening TA partition 2
14/006/2018 00:06:27 - INFO - Current device : Unknown: Jul 24 2016/19:28:59 - BH90A7YR1L - Unknown: Jul 24 2016/19:28:59 - 23.5.A.1.291_23.5.A.1.291 - GENERIC_23.5.A.1.291
14/006/2018 00:06:27 - INFO - Closing TA partition
14/006/2018 00:06:27 - ERROR - The bundle does not match the connected device
14/006/2018 00:06:27 - INFO - Ending flash session
14/006/2018 00:06:28 - INFO - Device disconnected
14/006/2018 00:06:32 - INFO - Device connected in flash mode
14/006/2018 00:06:39 - INFO - Device disconnected
Help
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you
castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you
Click to expand...
Click to collapse
Hi,
Emma works perfectly! Thank you
Yummy!
21/028/2018 21:28:17 - INFO - Reading device information
21/028/2018 21:28:17 - INFO - Phone ready for flashmode operations.
21/028/2018 21:28:17 - INFO - Opening TA partition 2
21/028/2018 21:28:17 - INFO - Current device : D6603 - BH90A7YR1L - 1288-5531_R9D - 1282-2729_23.5.A.0.575 - GLOBAL-LTE_23.5.A.0.575
21/028/2018 21:28:17 - INFO - Closing TA partition
21/028/2018 21:28:17 - INFO - Start Flashing
21/028/2018 21:28:17 - INFO - Processing loader.sin
21/028/2018 21:28:17 - INFO - Checking header
21/028/2018 21:28:17 - INFO - Flashing data
21/028/2018 21:28:18 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_M_2 / Bootloader status : ROOTED
21/028/2018 21:28:18 - INFO - Max packet size set to 512K
21/028/2018 21:28:18 - INFO - USB buffer size set to 512K
21/028/2018 21:28:19 - INFO - No flash script found. Using 0.9.18 flash engine
21/028/2018 21:28:19 - INFO - Opening TA partition 2
castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
I hope I could help you
Click to expand...
Click to collapse
thank you
my phone z5p e6833
but my different rom install "xz2 thema rom", "xz3 thema rom" vb. different most rom install my phone device name e6883 change
flashtool-0.9.25.0-windows install and flashing E6833_32.4.A.1.54_1298-2968_R2E and error Bundle does not match device yor phone device e6883
uninstall flashtool-0.9.25.0-windows
install flashtool-0.9.23.1-windows
not redownload E6833_32.4.A.1.54_1298-2968_R2E old time download E6833_32.4.A.1.54_1298-2968_R2E
flashing ok
re thankyou
castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
. . .
I hope I could help you
Click to expand...
Click to collapse
Thank you so much for that answer. I spent hours trying to find a solution, but using an older version of the software would never have occurred to me. Thank you so much for that answer. I spent hours trying to find a solution, but using an older version of the software would never have occurred to me.
Now my Z2 Tablet runs with Android 9; great:good::highfive:
emad
it work for me thanxs:good::good:
我的Z5P Dual E6883 閃光成 E6853之後無法復原 終於在0.9.18.6得到解決的方法 無法表達如此感謝
I can confirm that it works by using the older version of FlashTool, with an Xperia ZR :good: I also disabled the "verification" part as this posed some problems with reading from the device. I was able to install two different types of .ftf files (one at a time), and then reinstall recovery and LineageOS. My original problem was a bootloop, only showing the TWRP or Sony splash screen beforing screen going black again and rebooting.
castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you
Click to expand...
Click to collapse
Thank Youuu !!!! You made my day . I was stuck here for around an year . It never occurred to me to try an older release of flashtool. :good::good:
LOL! Newer is not always better haha. I just ran into this issue while trying to flash my Xperia Z2 back to stock. It was showing "Unknown" and complaining with "The bundle does not match the connected device" then refusing to flash. I thought it had to do with the LineageOS kernel it was running at the time, but no, flashing a stock-based kernel didn't fix that either.
Thanks for saving me from a headache!
Related
Hi all,
I'm trying to downgrade my stock Lollipop ROM (23.1.A.1.28) in order to root it afterwards. I'm using FlashTool 0.9.8.15 on Linux, and it seems to work correctly - but the downgrade fails
Here's the log output of FlashTool:
Code:
30/009/2015 10:09:57 - INFO - Device connected in flash mode
30/010/2015 10:10:07 - INFO - Selected Bundle for Sony Xperia Z3 (D6603). FW release : 23.0.A.2.93. Customization : Generic GLOBAL
30/010/2015 10:10:07 - INFO - Preparing files for flashing
30/010/2015 10:10:40 - ERROR - No space left on device
30/010/2015 10:10:40 - INFO - Cannot open bundle. Flash operation canceled
30/010/2015 10:10:58 - INFO - Device disconnected
30/011/2015 10:11:10 - INFO - Device connected with USB debugging on
30/011/2015 10:11:11 - INFO - Connected device : Sony Xperia Z3
30/011/2015 10:11:11 - INFO - Installed version of busybox : N/A
30/011/2015 10:11:11 - INFO - Android version : 5.0.2 / kernel version : 3.4.0-perf-g4d6e88e / Build number : 23.1.A.1.28
Opening that FileCommander coming with the ROM I get the info that there's 11.6 GB free on the phone and all 59,4 GB on the SD card. So - how's this??? And (more important): How to fix it?
Thanks for your kind help
Where have you stored the FTF?
Argh, the problem was so easy to solve - I just had to understand that error message - my hard drive simply got filled up when FlashTool tried to unpack the FTF :-/
Hi, I'm trying to do the same thing. I'm using flashtool 0.9.18.6 on windows 8 computer. I keep getting an error prompt stating "processing of loader.sin finished with errors."
Iceberg1914 said:
Hi, I'm trying to do the same thing. I'm using flashtool 0.9.18.6 on windows 8 computer. I keep getting an error prompt stating "processing of loader.sin finished with errors."
Click to expand...
Click to collapse
Please double check FTF integrity.
If necessary, downlaod a fresh uncorrupted FTF
Hello, I have done the procedure from this thread: http://forum.xda-developers.com/xperia-e3/general/simplified-guide-to-root-sony-xperia-e3-t3012248 , then I got a issue where my phone was stuck endlessy on black Sony Logo window, then I tried to fix using this method here: http://forum.xda-developers.com/xperia-e3/help/xperia-e3-stuck-boot-screen-sony-logo-t2938585 (flashed again with indicated kernel from this thread) and now I have my phone stuck on CWM everytime I try to turn it on doesn't matter which option I use for reboot or turn off it always go back to CWM mode. I have tried to fix using PC Companion and PC Companion tells me I have modified software and can not help me.
I have googled all over internet and couldn't find anything to solve this issue... A little help here, please?
Regards
Cristy0505 said:
Hello, I have done the procedure from this thread: http://forum.xda-developers.com/xperia-e3/general/simplified-guide-to-root-sony-xperia-e3-t3012248 , then I got a issue where my phone was stuck endlessy on black Sony Logo window, then I tried to fix using this method here: http://forum.xda-developers.com/xperia-e3/help/xperia-e3-stuck-boot-screen-sony-logo-t2938585 (flashed again with indicated kernel from this thread) and now I have my phone stuck on CWM everytime I try to turn it on doesn't matter which option I use for reboot or turn off it always go back to CWM mode. I have tried to fix using PC Companion and PC Companion tells me I have modified software and can not help me.
I have googled all over internet and couldn't find anything to solve this issue... A little help here, please?
Regards
Click to expand...
Click to collapse
You have to install the rom stock . download FlashTool( http://forum.xda-developers.com/showthread.php?t=920746 ) and Xperia Firm(for download rom stock) of attachment within the C: // FlashTool / drivers run the installer for the drivers choice Flashmode and fastboot and Xperia Z2 device driver is equal to E3 after installing FlashTool and xperia firm follow this tutorial that is universal
http://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
Koshigawa said:
You have to install the rom stock . download FlashTool( http://forum.xda-developers.com/showthread.php?t=920746 ) and Xperia Firm(for download rom stock) of attachment within the C: // FlashTool / drivers run the installer for the drivers choice Flashmode and fastboot and Xperia Z2 device driver is equal to E3 after installing FlashTool and xperia firm follow this tutorial that is universal
http://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
Click to expand...
Click to collapse
Thank you for your kind help, but when I try to flash my device (again) I click BLU for pluging phone holding Vol Down and after when I connect it does not flash my device again it only gives me option for relock my device. What should I do?
I must say I finished rooting and flash first time which lead me to be stuck in Sony Logo window, then I tried to fix it by using the method mentioned on second Tutorial http://forum.xda-developers.com/xperia-e3/help/xperia-e3-stuck-boot-screen-sony-logo-t2938585 which lead me to this issue stuck in CWM loop...
Dude BLU for bootloader unlocking and you wanna click On thunder icon and choose flashmode(off and holding volume down & connect)for flashing ftf and fastboot mode(off and Holding volume up while connect to pc) for Flashing Kernel image files
Mainaharen said:
Dude BLU for bootloader unlocking and you wanna click On thunder icon and choose flashmode(off and holding volume down & connect)for flashing ftf and fastboot mode(off and Holding volume up while connect to pc) for Flashing Kernel image files
Click to expand...
Click to collapse
yep that's right @Cristy0505
Follow the instructions
Mainaharen said:
Dude BLU for bootloader unlocking and you wanna click On thunder icon and choose flashmode(off and holding volume down & connect)for flashing ftf and fastboot mode(off and Holding volume up while connect to pc) for Flashing Kernel image files
Click to expand...
Click to collapse
I did that in many ways... Maybe I could be doing this wrong but I can not manage to flash it again... Please if you could watch this video I recorded from my flashtool try and let me know what's wrong I would be grateful.
@Koshigawa could you please watch this video and tell me what's wrong?
Video link: http://www.dailymotion.com/video/x2ylbj1
Thanks in advance.
Cristy0505 said:
I did that in many ways... Maybe I could be doing this wrong but I can not manage to flash it again... Please if you could watch this video I recorded from my flashtool try and let me know what's wrong I would be grateful.
@Koshigawa could you please watch this video and tell me what's wrong?
Video link: http://www.dailymotion.com/video/x2ylbj1
Thanks in advance.
Click to expand...
Click to collapse
Easy boy you have download FTF XperiaFirm first, you did not do the full download of the rom in XperiaFirm you just selected the side of the roms list is written a number have to click there, attached is an example , after downloading without connecting the device , do the same process that will appear the window to put in flashmode mode ( with the device turned off press volume down and connect usb )
FlashTool run as administrator.
Koshigawa said:
Easy boy you have download FTF XperiaFirm first, you did not do the full download of the rom in XperiaFirm you just selected the side of the roms list is written a number have to click there, attached is an example , after downloading without connecting the device , do the same process that will appear the window to put in flashmode mode ( with the device turned off press volume down and connect usb )
FlashTool run as administrator.
Click to expand...
Click to collapse
My device firmware version was 18.4.B.2.14 and not 18.5.B.0.26 like this one shown from Xperia Firm I did never updated firmware since I bought this device... Is it ok if I flash it again using newer firmware?
Thanks.
Cristy0505 said:
My device firmware version was 18.4.B.2.14 and not 18.5.B.0.26 like this one shown from Xperia Firm I did never updated firmware since I bought this device... Is it ok if I flash it again using newer firmware?
Thanks.
Click to expand...
Click to collapse
EDIT,: You can use this is the last version to Android 4.4.4 d2212 you are with 4.4.2
Koshigawa said:
EDIT,: You can use this is the last version to Android 4.4.4 d2212 you are with 4.4.2
Click to expand...
Click to collapse
Now I got this after downloading firmware from XperiFirm.
Video: http://www.dailymotion.com/video/x2ypp7q
Any clue what I am doing wrong?
Thank you in advance.
Cristy0505 said:
Now I got this after downloading firmware from XperiFirm.
Video: http://www.dailymotion.com/video/x2ypp7q
Any clue what I am doing wrong?
Thank you in advance.
Click to expand...
Click to collapse
Guy follow this video.You have install rom stock.
http://www.youtube.com/watch?v=abzUMeVvlr8
Installation mode of xperia rom 's all the same.
Koshigawa said:
Guy follow this video.You have install rom stock.
http://www.youtube.com/watch?v=abzUMeVvlr8
Installation mode of xperia rom 's all the same.
Click to expand...
Click to collapse
Now it does not let me open bundle, says the follow when I try to flashmode new firmware:
22/019/2015 21:19:04 - INFO - Flashtool Version 0.9.18.3 built on 10-20-2014 08:00:00
22/019/2015 21:19:04 - INFO - Executing search strategies to find proxy selector
22/019/2015 21:19:04 - INFO - No proxy found for IE. Trying next one
22/019/2015 21:19:04 - INFO - Strategy firefox failed trying next one : No Firefox installation found
22/019/2015 21:19:04 - INFO - No proxy found for java. Trying next one
22/019/2015 21:19:04 - INFO - Syncing devices from github
22/019/2015 21:19:04 - INFO - Scanning devices folder for changes.
22/019/2015 21:19:11 - INFO - Pulling changes from github.
22/019/2015 21:19:11 - INFO - Devices sync finished.
22/019/2015 21:19:17 - INFO - Device disconnected
22/019/2015 21:19:18 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:18 - INFO - Preparing files for flashing
22/019/2015 21:19:18 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:18 - INFO - Cannot open bundle. Flash operation canceled
22/019/2015 21:19:25 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:25 - INFO - Preparing files for flashing
22/019/2015 21:19:25 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:25 - INFO - Cannot open bundle. Flash operation canceled
22/019/2015 21:19:50 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:50 - INFO - Preparing files for flashing
22/019/2015 21:19:50 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:50 - INFO - Cannot open bundle. Flash operation canceled
What should I do next?
Cristy0505 said:
Now it does not let me open bundle, says the follow when I try to flashmode new firmware:
22/019/2015 21:19:04 - INFO - Flashtool Version 0.9.18.3 built on 10-20-2014 08:00:00
22/019/2015 21:19:04 - INFO - Executing search strategies to find proxy selector
22/019/2015 21:19:04 - INFO - No proxy found for IE. Trying next one
22/019/2015 21:19:04 - INFO - Strategy firefox failed trying next one : No Firefox installation found
22/019/2015 21:19:04 - INFO - No proxy found for java. Trying next one
22/019/2015 21:19:04 - INFO - Syncing devices from github
22/019/2015 21:19:04 - INFO - Scanning devices folder for changes.
22/019/2015 21:19:11 - INFO - Pulling changes from github.
22/019/2015 21:19:11 - INFO - Devices sync finished.
22/019/2015 21:19:17 - INFO - Device disconnected
22/019/2015 21:19:18 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:18 - INFO - Preparing files for flashing
22/019/2015 21:19:18 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:18 - INFO - Cannot open bundle. Flash operation canceled
22/019/2015 21:19:25 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:25 - INFO - Preparing files for flashing
22/019/2015 21:19:25 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:25 - INFO - Cannot open bundle. Flash operation canceled
22/019/2015 21:19:50 - INFO - Selected Bundle for Sony Xperia E3 (D2212). FW release : 18.5.B.0.26. Customization : Customized IN
22/019/2015 21:19:50 - INFO - Preparing files for flashing
22/019/2015 21:19:50 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
22/019/2015 21:19:50 - INFO - Cannot open bundle. Flash operation canceled
What should I do next?
Click to expand...
Click to collapse
download the rom again the files should be corrupted
I have flashed my Z3 with the 23.0.A.2.93 Unbranded Generic. Everything was succesful and when asked for it, I unplugged my phone. Now I start it again but it keeps rebooting. I see the boot animation and then it restarts again. Could someone please help!!! I have shut it down with Power and Volume Up pressed, but no luck here as well.....
I have used the lastest Flashtool , the .10 version with the additional jar file. I am now flashing with the Nordic FTF, so see if a different FTF has the same problem.
Same problem and since it keeps restarting, PC Companion also cannot do anything to repair it.
HELP
I have flashed it again and during flashing it also said:
13/034/2015 13:34:51 - WARN - Unit 2212 not found in bundle
13/034/2015 13:34:51 - INFO - Closing TA partition
13/034/2015 13:34:51 - INFO - Opening TA partition 2
13/034/2015 13:34:51 - INFO - Closing TA partition
13/034/2015 13:34:51 - INFO - Opening TA partition 2
13/034/2015 13:34:51 - WARN - Unit 2404 not found in bundle
I also saw that during the drivers install, only the Sony Net failed. But since the flash seem to work and finish properly, except the above two warnings, it guessed this should not be an issue?
OK, fixed it myself!!!!
- uninstalled Flashtools
- redownloaded it from flashtools.net (instead of from a faster source I did before)
- Unblocked the x10flasher.jar in Windows (right click, properties, click unblock)
- set in Windows in Advanced options (troubleshooting) option to Disable Drive signature (http://windows.microsoft.com/en-us/...tup-options-including-safe-mode#1TC=windows-7) and reboot
- ran the drivers install as an administrator
- started flashtools as an administrator
- flash, select the FTF and also check the Wipe User data and Apps Log
- after that Solved
Part from that I now have flashed it with a Android 4.4.4 FTF !!!!
So as the title says, when i connect my M2 to my PC it's shown as Z3. I can't flash any M2 ftf via Flashtool.It always failed saying :
07/013/2015 17:13:00 - INFO - Start Flashing
07/013/2015 17:13:00 - INFO - Ending flash session
07/013/2015 17:13:00 - ERROR - Can't read a byte value
07/013/2015 17:13:00 - ERROR - Error flashing. Aborted
07/013/2015 17:13:00 - INFO - Device connected in flash mode
07/013/2015 17:13:01 - INFO - Device disconnected
I can flash only CM13 from a russian site like xda :/
Any help will be appreciated...
Thanks in advance :/
Edit : I found out that..when it's in recovery and i connect to PC it says Z3 but when i turn on the system and connect the phone to PC it says M2 or D2303.
If you had searched up a bit on Google, you'd have come up with this... Which clearly says that you need to clean everything up (the .flashTool folder), uninstall Flashtools and install it again. I always recommend using the 0.9.18.6 version to avoid compatibility issues with this device.
linuxct said:
If you had searched up a bit on Google, you'd have come up with this... Which clearly says that you need to clean everything up (the .flashTool folder), uninstall Flashtools and install it again. I always recommend using the 0.9.18.6 version to avoid compatibility issues with this device.
Click to expand...
Click to collapse
Actually i've searched before makin the thread. Done it few times...at the beginning it was not makin any difference.. but after that somehow it worked...anyway thanks :highfive:
Hello XDA, longtime reader, first time poster.
I tried flashing a custom ROM the other day, but something went wrong, and I now have a device that bootloops (unlocked screen, SONY logo, followed by a "the software update failed" message). I think the cause of all of this came from a few missing drivers that Flashtool/Windows 7 didn't install properly. I'm not sure if this matters, but this happened after trying to update to the latest stock nougat firmware (downloaded via Xperifirm) from a custom 6.0.1 ROM.
I went through as many solution threads as possible, but I'm still having trouble. The last thing I did just before this post was create an ftf via Flashtool, added "41.fsc" script when asked, prepared flash with full wipe/no exclusions, connected phone to USB via Flash Mode, selected F83XX when prompted for device, and this was the log I received...
29/021/2017 00:21:58 - INFO - Device connected in flash mode
29/021/2017 00:21:59 - INFO - Opening device for R/W
29/022/2017 00:22:00 - INFO - Reading device information
29/022/2017 00:22:00 - INFO - Phone ready for flashmode operations.
29/022/2017 00:22:00 - INFO - Opening TA partition 2
29/022/2017 00:22:00 - INFO - Start Flashing
29/022/2017 00:22:00 - INFO - No loader in the bundle. Searching for one
29/022/2017 00:22:44 - INFO - No matching loader found
29/022/2017 00:22:44 - WARN - No loader found or set manually. Skipping loader
29/022/2017 00:22:44 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Bootloader status : ROOTED
29/022/2017 00:22:44 - INFO - Max packet size set to 4M
29/022/2017 00:22:44 - INFO - USB buffer size set to 512K
29/022/2017 00:22:54 - INFO - Parsing boot delivery
29/022/2017 00:22:54 - INFO - Found a template session. Using it : C:\Users\[name]\.flashTool\firmwares\prepared\41.fsc
29/022/2017 00:22:54 - INFO - Set loader configuration : [00 01 00 00 00 0C]
29/022/2017 00:22:54 - INFO - Flashing finished.
29/022/2017 00:22:54 - INFO - Please unplug and start your phone
29/022/2017 00:22:54 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Extra information...
PC
- Windows 7 64-bit
- Flashtool 0.9.23.2 installed
- As far as I know, every driver I need has been downloaded and installed (Sony's website, Flashtool-drivers.exe)
(↑ "Sony sa0115 ADB Interface Driver" under Device Manager reads "This device cannot start. (Code 10)", if that makes any difference)
- Xperia Companion doesn't detect my phone, so I can't use their "software repair" option
Phone
- F8332
- Bootloader unlocked
- *Backup TA missing*
- Device rooted
- TWRP 3.1.1-0 installed
- Android 6.0.1 (firmware unknown)
Files
- Latest Nougat firmware (F8332_Customized FR_1305-9679_41.2.A.7.76_R1D) -- folder only (ftf can be created anytime, just need to know what to keep/exclude. I've been seeing different answers regarding when to add "41.fsc" to ftf (before/after flashing, or adding at all), and excluding .sin files before flashing, so if anyone has a definite answer to these, I'd really appreciate it.)
Otherwise, if none of that matters and the problem lies somewhere else, I'm all ears.
Thank you in advance.
@simpleflips
wow - your post should stand out as a prototype for HOW TO ASK FOR HELP!
I had the same problem recently when trying to flash my F8331 under Windows 10. Did not try Linux on the same machine since there are some issues with Mono here.
My drivers where not giving me any clues (PC-Manager, logging under Windows?).
So I dug out my spare laptop (Win 7 bitness?): installed the XZ-driver and it worked there after a full wipe in TWRP (I had encrypted the device and TWRP did not take the key properly).
You can try the drivers I link in my Guide.
Under both Windows installations I had no problems with adb and fastboot.
So I can only guess that my "solution" was the full wipe or some unkwon differences in driver magic between the notebooks used.
@DHGE
Apologies for the delay, thank you for the words and response. I should've noted that before my OP and bootloop, I tried to flash the custom Nougat ROM via TWRP, but got an error. (Zip file is corrupt! Error installing zip file '/sdcard1/[rom].zip') (Tested after transferring the file via AirDroid, don't remember if I even downloaded directly from my phone.) Now if I run a full wipe through TWRP and re-flash the original 6.0.1 ROM that's in my microSD, it *does* install, but bootloop still exists. I tried wiping/flashing the custom ROM via fastboot out of curiosity, and received the following:
wipe (entered bootloader mode from my Downloads folder, where the ROM is found)
C:\Users\[name]\Downloads>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (status read failed (Too many open files in system))
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command failed (Invalid argument))
erasing 'userdata'...
FAILED (command write failed (No such device or address))
finished. total time: 0.020s
(Afterward, I get a message saying fastboot.exe has stopped working. Not on Minimal ADB, though.)
flash
C:\Users\[name]\Downloads>fastboot update [rom].zip
'archive does not contain 'android-info.txt' ,
error: update package '[rom].zip' has no android-info.txt
Do these errors relate with each other? Was my file just not downloaded properly?
Regarding the drivers, I downloaded the official Xperia XZ ADB interface driver (Sony sa0115) from SONY's website, and installed via Device Manager, but get the Code 10 Error mentioned in OP. According to some user posts, the solution was changing their phone's USB configuration to MIDI, afterward Windows would properly detect and install the Sony sa0115 driver. (I reckon that's not possible on a soft bricked device, is it...?) No devices are found after entering adb devices in command prompt, so I'm going to presume installing/flashing anything via ADB is out of the question. Right now, Device Manager shows 2 devices-- One of them being the actual XZ when connected in fastboot mode (labeled "Android Phone"), the other being the Sony sa0115 driver I downloaded/installed. The trick now is mounting the two together.
At this point, fastboot/TWRP seem to be the only way out of this. The custom ROM notes that no kernel flashing is necessary, but your guide includes a link to the AndroPlus kernels (for stock, and other roms, I take it). Unfortunately, until I figure out how to properly flash the firmware via Flashtool, AndroPlus will have to wait. (Unless there's a way to find out what firmware my phone is using right now.) The next option is to directly send the custom 7.1.1 ROM from my PC to the microSD card, but I can't find my SD card adapter right now, so I'll update later this week.
simpleflips said:
@DHGE
At this point, fastboot/TWRP seem to be the only way out of this
Click to expand...
Click to collapse
Unfortunately this is not a way out. And what you wrote above sounds rather weird for me...
The only way out is to flash a SONY ROM properly. THE tool for this is flashtool.
There are some mentions of SONY's recovery tool(s?) but last time I tried one I could not get it to work. Flashtool to my rescue.
Maybe you can take your phone to a qualified repair shop and they flash you a SONY ROM.