According to XPERIAblog, now we're able to use Flashtool for our device.
Long-term Sony Xperia users will be very familiar with Flashtool, it has been the da facto method of flashing firmware of Xperia devices to a different region. It has been around since the advent of Sony’s Android Xperia phones, but support was not added for any of the 2017 Xperia devices.
However, Flashtool developer Androxyde has updated the application to version 0.9.24.2, which now includes support for the Xperia XZ Premium, Xperia XZ1 and Xperia XZ1 Compact. Do note though that this new version of Flashtool has moved from Java 8 to Java 9, so you will need to run a 64-bit operating system. If you want to download the new version, click here.
Click to expand...
Click to collapse
Source: http://www.xperiablog.net/2018/01/1...t-xperia-xz-premium-and-xz1-devices-0-9-24-2/
Rejoice! Thanks @Androxyde
EDIT: Relevant post: https://forum.xda-developers.com/showpost.php?p=75141403&postcount=3641
Gave my thanks there, although I first saw the news from the same source as OP as well and came here to find more info.
Great news ! Thanks !
Could someone help me understand what the advantages of Flashtool are over Newflasher? I used flashtool on my old z3c...but is there a good reason to switch if newflasher works well enough?
jrbmed08 said:
Could someone help me understand what the advantages of Flashtool are over Newflasher? I used flashtool on my old z3c...but is there a good reason to switch if newflasher works well enough?
Click to expand...
Click to collapse
I think it's just nice and convenient because it's a one-stop shop for flashing xperia devices... it includes xperifirm and such, and has checkboxes for you to remove userdata.sin etc, so you don't actually have to go and do it yourself. Probably just preference and habit. If you're totally fine with newflasher I don't think there's any difference.
I've tried unsucessfully to download 9.24.2 version, can you tell me why ?
Nothing happen when i click on "Get it".
francois64 said:
I've tried unsucessfully to download 9.24.2 version, can you tell me why ?
Nothing happen when i click on "Get it".
Click to expand...
Click to collapse
The "Get it" link links to the download page you're already on, of course "nothing happens".
You need to click on one of the 3 links with your OS description, like "Windows", then decide if you want to download via BT or file host.
OK thanks
My US version XZ1c arrived Wednesday afternoon and I'm fairly new to the whole flashing scene (unrootable Samsung phones and locked bootloaders all my Android life, yay....), so forgive my stupidity. I've followed the guide on XperiaFirmware.com up to part C, which says to install drivers for Flashtool. I believe I've got Flashtool working right now, but I don't know what else I'm supposed to do. Are the drivers located somewhere not on the site, or are they included in the 47.1.A.12.34 folder from XperiaFirmware? I see it contains the newflasher program in there, but I don't understand what the other files are for.
CMT 1412-4444 'Fours' said:
My US version XZ1c arrived Wednesday afternoon and I'm fairly new to the whole flashing scene (unrootable Samsung phones and locked bootloaders all my Android life, yay....), so forgive my stupidity. I've followed the guide on XperiaFirmware.com up to part C, which says to install drivers for Flashtool. I believe I've got Flashtool working right now, but I don't know what else I'm supposed to do. Are the drivers located somewhere not on the site, or are they included in the 47.1.A.12.34 folder from XperiaFirmware? I see it contains the newflasher program in there, but I don't understand what the other files are for.
Click to expand...
Click to collapse
In the install folder for the Flashtool should be a folder called Drivers. Inside that there is an .exe you should run that will install the drivers you need. When you run it you need to select the flashtool drivers from the option as well as the drivers for your model of phone, usually down towards the bottom of the list. If you are running Windows 10 then you will need to disable driver signature checking before trying to run this file. (boot into safe mode and look under advanced menu).
Download the firmware you want to install with Xperiafirm, put it in the flashtool firmware folder.
Run the program, slect the lightning bolt, select the firmware, press ok. It will then start building the image. Then it will ask you to connect your phone.
Make sure your phone is powered off completely. Then plug the USB in whilst holding the volume down button (the led should turn green), Flashtool will recognise the phone, you can let go of the volume button and let Flashtool do it's job.
Edit: having used both Newfalsher and Flashtool, I think Newflasher is easier, but you're already there now so you may as well carry on.
Didgesteve said:
In the install folder for the Flashtool should be a folder called Drivers. Inside that there is an .exe you should run that will install the drivers you need. When you run it you need to select the flashtool drivers from the option as well as the drivers for your model of phone, usually down towards the bottom of the list. If you are running Windows 10 then you will need to disable driver signature checking before trying to run this file. (boot into safe mode and look under advanced menu).
Download the firmware you want to install with Xperiafirm, put it in the flashtool firmware folder.
Run the program, slect the lightning bolt, select the firmware, press ok. It will then start building the image. Then it will ask you to connect your phone.
Make sure your phone is powered off completely. Then plug the USB in whilst holding the volume down button (the led should turn green), Flashtool will recognise the phone, you can let go of the volume button and let Flashtool do it's job.
Edit: having used both Newfalsher and Flashtool, I think Newflasher is easier, but you're already there now so you may as well carry on.
Click to expand...
Click to collapse
I went ahead with Newflasher since the guide is much easier. +1 Thanks
I recently used Flashtool to flash my USA-purchased XZ1C to the .75 Customised DE firmware, and the process was about as simple and straightforward as I can imagine. I also like that provision of the firmware locator is built-in to the Flashtool installation, and the downloaded firmware archive contains a script which puts everything into place for flashing. By default, all user data and settings appear to be maintained. The only thing that might be confusing is that the dialog that pops up indicating it's time to connect the phone only refers to 2011 and 2012 models (both X Compact and XZ1 Compact use the 2012 method). Otherwise, everything proceeds smoothly. Have others had similar positive (or negative) experiences with Flashtool?
pseudonym58 said:
By default, all user data and settings appear to be maintained.
Click to expand...
Click to collapse
So even the apps, data, etc. remains, like when you update OTA ? I am considering updating my (very outdated) firmware without waiting for it to come from Sony, but I don't want to reinstall and reconfigure everything.
@jeff9891
As I indicated previously, nothing seems to have been lost when I used flashtool to install firmware. Of course I can't guarantee that you'll have exactly the same experience, but I have updated both an Xperia xz1 Compact and an Xperia X compact and have not lost any data. In any case I would advise backing up with Xperia companion first.
Thanks, I'll try it this week-end and report, if no OTA update arrives beforehand.
I must be dumb, but I can't find XZ1C in the list in "Flashtool-drivers.exe". Flashtools thereforce recognizes some device is connected, yet it does not display the device's name like it is supposed to do so as far as I read in tutos (even if the program says "driver installed : true") :
Code:
09/008/2018 12:08:31 - INFO - Flashtool Version 0.9.24.4 built on 01-02-2018 22:15:00
(...)
09/009/2018 12:09:10 - INFO - Device connected with USB debugging off
09/009/2018 12:09:10 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/025/2018 12:25:57 - INFO - List of connected devices (Device Id) :
09/025/2018 12:25:57 - INFO - - USB\VID_0FCE&PID_01F4\BH9043YQ9E Driver installed : true
09/025/2018 12:25:57 - INFO - List of ADB devices :
09/025/2018 12:25:57 - INFO - - none
09/025/2018 12:25:57 - INFO - List of fastboot devices :
09/025/2018 12:25:57 - INFO - - none
Sharing some XZ1C flashing process tips for those who may have to cope with the same problems I did.
1) There are no XZ1C dedicated drivers in the drivers.exe that comes with flashtools. Just select the generic "Flashmode drivers" in the list. Still necessary to install them before flashing, though.
2) It is normal that flashtools does not display your device name in its consol as it was supposed to do so with previous phones models. Source: https://www.youtube.com/watch?v=ctqKNAzrKpQ
3) Xperifirm (= the program to grab your phone's latest stock ROM from Sony) is integrated into flashtools. Click the "XF" logo in the top bar, then find your model and download it. It will automatically make it usable in flashtools without fiddling with the files.
4) Follow the general tutorial for flashing: https://forum.xda-developers.com/showthread.php?t=928343 . To enter flash mode with XZ1C, you can follow this tuto : https://www.youtube.com/watch?v=Eid4PApHffg Be aware that your screen will stay black in this mode, but your LED will turn green.
5) Once you plug the phone in flash mode, again, nothing will happen on the phone's screen, but you can follow the flashing on flashtools terminal. Do not be surprised (as I was) if the program does not indicate "flashing completed" or something like that. Just leave the phone and the computer until you obtain this (took like 10 minutes for me):
Code:
09/023/2018 17:23:49 - INFO - Sending Sync
09/026/2018 17:26:01 - INFO - Sync status : OKAY
09/026/2018 17:26:01 - INFO - Sending powerdown
09/026/2018 17:26:01 - INFO - powerdown status : OKAY
09/026/2018 17:26:05 - INFO - Device disconnected
09/026/2018 17:26:06 - INFO - Device connected in flash mode
Then you can just unplug it and turn it on.
jeff9891 said:
Sharing some XZ1C flashing process tips for those who may have to cope with the same problems I did.
[...]
Then you can just unplug it and turn it on.
Click to expand...
Click to collapse
Yes; one difference in my experience with flashtool might have been due to the fact that I had connected my XZ1C to my PC (Windows 10) using Xperia Companion first. I think that ensured that the proper Sony drivers would be in place before attempting to use flashtool. But I'm not sure.
In any case, I have restored the default USA firmware to the XZ1C, as using DE or UK, etc. seemed to restrict my ability to send group text messages (has to do with USA carrier protocols, I guess), and I don't need a fingerprint sensor at this time.
pseudonym58 said:
Yes; one difference in my experience with flashtool might have been due to the fact that I had connected my XZ1C to my PC (Windows 10) using Xperia Companion first. I think that ensured that the proper Sony drivers would be in place before attempting to use flashtool. But I'm not sure.
In any case, I have restored the default USA firmware to the XZ1C, as using DE or UK, etc. seemed to restrict my ability to send group text messages (has to do with USA carrier protocols, I guess), and I don't need a fingerprint sensor at this time.
Click to expand...
Click to collapse
I also used Xperia Companion beforehand on Windows 10, but I had to add the drivers nonetheless. Unsure of the reason it worked for you here. Future flashers will know both ways, though
With Customized_DE (before and after flashing), fingerprint sensor still works for me. Not quite sure, but I believe there are legal restrictions about that in the USA ? As for group text message, I have not tried yet. You mean sending a text to multiple people, or having actual synchronized group discussion using texts ? I thought it was impossible.
jeff9891 said:
[...] As for group text message, I have not tried yet. You mean sending a text to multiple people, or having actual synchronized group discussion using texts ? I thought it was impossible.
Click to expand...
Click to collapse
What I meant was:
Sending a text (with or without image) to a group of people, and have everyone see everyone's replies.
This seems only to be possible (when used in USA on AT&T carrier) when I have the default USA firmware flashed onto the phone. If I use the DE firmware, for instance, I can send a "mass message" to multiple recipients, but then cannot attach an image, and all subsequent replies are private, i.e. between two parties.
Related
Quick tutorial for unlocking & relocking the bootloader of the Xperia S/P/U/Sola.
this is the official way to unlock bootloader
Warning!
This procedure will wipe the /data partition of your phone, so you will loose all ur stored data, settings. SDCARD will NOT BE WIPED!!!
DRM keys WILL be lost forever
why to unlock bootloader?
u can flash custom ROMs/Kernels
u dont need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT ur device
SE/Sony gives sneak-peaks/preview builds of latest OS which requires unlocked bootloaders, as they did with Xperia 2011 line (they had ICS alpha/beta), so who knows may be SE/Sony may give early builds of ICS (JellyBean???)
Most of this is taken from lollylost100's his tutorial from ARC thread (all credits for that concise tutorial go to him, i have elaborated on a few things and added device specific changes)
btw i dont have this device, most of this testing was done on user darkpisces's phone so thanks a lot to him for helping me out!!!
[ before we begin unlocking bootloader ]
get the IMEI code for ur device: type *#06# in phone dialer to find it out, note only the digits (no dashes)
download the fastboot package
download the latest FlashTool Xperia Driver Pack and install fastboot drivers (common) & adb drivers for this device from the list!
make sure u have a windows PC with USB cable to connect the phone
power down ur phone and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, which should be automatically done
once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.
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.
Click to expand...
Click to collapse
after u have verified that u can unlock bootloader, scroll to the bottom of the page and click "Continue"
you will get "are u sure prompt" accept it by clicking "yes i am sure" (i assume that u have read an understood it)
then accept the "legal terms"
finally u will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
You should now receive your unique unlock key, its displayed on screen, SAVE THIS KEY SAFELY
Extract fastboot_with_Android_USB_file.rar and open fastboot folder
Hold SHIFT and right click on the background of the folder
Select 'Open command window here'
Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
(the above videos and some steps are for Xperia 2011 devices, but most the steps are same for Xperia S/P/U/Sola)
Info on Relocking bootloader is in next post
Relocking Bootloader
this Relock FTF is based on the package posted by Blagus in his ARC thread (all credits for this go to him, i have only added the correct loader.sin for this device)
RELOCKING BOOTLOADER WILL ALLOW YOU TO GET NEWEST UPDATES & REPAIR DEVICE USING SEUS/PCC
before we begin relocking the bootloader make sure that u have flashtool download & installed
u can get the latest version of FlashTool from:
http://androxyde.github.com/Flashtool/
download link is under "Installation" tab
if u have not use FlashTool before read this thread:
http://forum.xda-developers.com/showthread.php?t=1526866
download this FTF:
Xperia S -> Xperia-S_Relock_bootloader.ftf
Xperia U -> http://forum.xda-developers.com/showthread.php?p=26783129#post26783129 (thanks to enigma77x)
flash this FTF via FlashTool
RELOCK FTFs FOR P/U/Sola are under testing! if u are interested in testing kindly contact me via P.M., before u contact me, make sure that u have UNLOCKED the bootloader!
when it says enter flashmode, power down device and keeping VOLUME DOWN button pressed connect usb cable to phone, the device will now enter flashmode (green LED)
after this file is flashed reboot phone
bootloader will now be relocked!!!
incase device doenst boot DO NOT PANIC... u can flash stock firmware FTF anytime to get back to stock ROM... i will post link to working FTF once its available...
P.S.: there is no official way to relock bootloader
Sorry for misunderstanding, but what are DRM keys?
MasterLinuxer said:
Sorry for misunderstanding, but what are DRM keys?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Digital_rights_management
Cholek3 said:
http://en.wikipedia.org/wiki/Digital_rights_management
Click to expand...
Click to collapse
Ehum... So are there any disadvantages about deleting it?
MasterLinuxer said:
Ehum... So are there any disadvantages about deleting it?
Click to expand...
Click to collapse
Yes, some software installed on the phone stops working, i.e. trackID.
Well I hope not nothing's gonna happen to the phone when we are gonna update the phone to the ICS, right now I'm in China and it's not released over here and looking forward to get this baby in my hand.
when official ICS is out, it can be flashed via flashtool as FTF file when it will be online somewhere
PS: after unlocking bootloader via official method (official Sony website way), u wont be able to update phone's software via PC Companion / or over the air
so what is the benefit of locking the bootloader if they know your warranty is void? or it in case an un-official unlock method is found?
yea I guess it's pointless locking back the BOOTLOADER but I think with the unofficial way, they know or they have registered the serial key or IMEI which you won't be able to update it to ICS via SEUS or PcCompaninon. Either way like you said, we can use the FTF files to update it to ICS. and I saw when the run ICS on Arc S and Play, I saw that they had to unlock the bootloader to install alpha ICS and it was mentioned there that you might face lotta troubles when you update it to the official ICS, so I'm gonna wait till it gets official ICS cause it'll be out very soon like end of the March.
chesterr said:
yea I guess it's pointless locking back the BOOTLOADER but I think with the unofficial way, they know or they have registered the serial key or IMEI which you won't be able to update it to ICS via SEUS or PcCompaninon. Either way like you said, we can use the FTF files to update it to ICS. and I saw when the run ICS on Arc S and Play, I saw that they had to unlock the bootloader to install alpha ICS and it was mentioned there that you might face lotta troubles when you update it to the official ICS, so I'm gonna wait till it gets official ICS cause it'll be out very soon like end of the March.
Click to expand...
Click to collapse
NO!
After relock you can use SEUS / PCC / EMMA again. The imei is used to generate the unique unlock-key. Also it gets stored to check if you claim warranty. Arc has showed us that SE is not denying warranty at all if you unlocked. They just decline it if the cause of the failure is a custom rom etc. pp. for example if you ****ed your cpu with overclocking.
SEUS/PCC/EMMA checks TA area for the unlock key, if it is present it reject the phone and refuses to update. The relock Doom posted here is the same way we worked out on Arc. It deletes the unlockkey from TA and this way you are again able to use SEUS/PCC/EMMA.
Hope i enlighted you a bit.
Regards
thanks now could you indulge my question as a visitor to this device?
What is SEUS/PCC/EMMA ? ota updates?
TRusselo said:
thanks now could you indulge my question as a visitor to this device?
What is SEUS/PCC/EMMA ? ota updates?
Click to expand...
Click to collapse
SEUS/PCC/EMMA are all official ways to repair firmware or update device to latest firmware...
SEUS/PCC are available to all users (consumers)... EMMA is special and is only available to select individuals...
OTA updates are same as regular Over-The-Air updates for any other device...
lol thanks!.. ota updates was my guess not a second question... but thanks.
Bin4ry said:
NO!
After relock you can use SEUS / PCC / EMMA again. The imei is used to generate the unique unlock-key. Also it gets stored to check if you claim warranty. Arc has showed us that SE is not denying warranty at all if you unlocked. They just decline it if the cause of the failure is a custom rom etc. pp. for example if you ****ed your cpu with overclocking.
SEUS/PCC/EMMA checks TA area for the unlock key, if it is present it reject the phone and refuses to update. The relock Doom posted here is the same way we worked out on Arc. It deletes the unlockkey from TA and this way you are again able to use SEUS/PCC/EMMA.
Hope i enlighted you a bit.
Regards
Click to expand...
Click to collapse
Oh that's nice to hear. boo ya that means I can unlock the damn bootloader.I'm waiting to get this on my hands very soon.
Will we keep root if we re-lock the bootloader?
Rashkae said:
Will we keep root if we re-lock the bootloader?
Click to expand...
Click to collapse
yes root should still remain unless u reflash FTF
I'm having a problem here:
power down ur phone and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder
once drivers are installed just disconnect cable and power on device
"Extract the above package" - you mean fastboot, right? Ok, with you so far.
"Point the driver isntall to that location". - erm. How? I don't get that option, it just searches windows update and preconfigured driver locations for ages, and the Xperia S does not show up in the device manager as an incorrectly installed device.
Rashkae said:
I'm having a problem here:
power down ur phone and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder
once drivers are installed just disconnect cable and power on device
"Extract the above package" - you mean fastboot, right? Ok, with you so far.
"Point the driver isntall to that location". - erm. How? I don't get that option, it just searches windows update and preconfigured driver locations for ages, and the Xperia S does not show up in the device manager as an incorrectly installed device.
Click to expand...
Click to collapse
please search online on how to manually install device driver
DooMLoRD said:
please search online on how to manually install device driver
Click to expand...
Click to collapse
I did. It all pointed to going into the device manager, highlighting the troublesome device then manually installing the driver. There is no "missing" device in my device manager list.
---------- Post added at 02:52 AM ---------- Previous post was at 02:38 AM ----------
Oh, and the usual method I use of right-clicking the .inf file didn't work. It threw an error message about the driver package not being designed to work this way.
I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.
Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?
I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.
devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..
Oh my goodness......... It is pantomime season after all
Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.
my device (c6506) isn't supported by Flashtool.
how do I flash without using Flashtool
Sent from my SGH-I337M using XDA Free mobile app
bump
Sent from my SGH-I337M using XDA Free mobile app
Already responded to you in another thread. Use FlashTool by Androxyde, not the official one from Sony. Works beautifully with C6506.
kt-Froggy said:
Already responded to you in another thread. Use FlashTool by Androxyde, not the official one from Sony. Works beautifully with C6506.
Click to expand...
Click to collapse
Thanks finally someone replied .. I'll let you know if mine works or not
O1A2K said:
Thanks finally someone replied .. I'll let you know if mine works or not
Click to expand...
Click to collapse
It will work only if you have previously access to enable in security unknown sources and usb debagig.
How about for this one without the option to access security the phone is not butting and usb debagig and Unknown sources are not enable?
Any other solution to load FTF files?
styropian said:
It will work only if you have previously access to enable in security unknown sources and usb debagig.
How about for this one without the option to access security the phone is not butting and usb debagig and Unknown sources are not enable?
Any other solution to load FTF files?
Click to expand...
Click to collapse
Think you should make yourself a little more acquainted to FlashTool, it's worth the effort. You do not require any and all settings in the phone (it could even have the /data or /system partition wiped). There is no other tool and you don't need any other.
sxtester said:
Think you should make yourself a little more acquainted to FlashTool, it's worth the effort. You do not require any and all settings in the phone (it could even have the /data or /system partition wiped). There is no other tool and you don't need any other.
Click to expand...
Click to collapse
Thanks for your replay.
This xperia zl phone is not mine phone, I'm trying not to spend to much time on it and from other hand I would like to revive the phone. I did try to update few different FTF firmwares using FlashTool and sony pc companion.All this tools looks like working ,only Flash tool at the end was giving me the warning that to be able to use flashTool require to unable option in settings that makes me wondering.
After updating the TFT firmware the phone reacts exactly same way as before updating a firmware :after pressing power no vibration only red light blinks 3 times.I'm able go access download mode and by pressing volume up I can access as well fastmode (blue solid light) .When the phone is plug to charger it will show xperia logo for 2sec and bootloop.When I press reset button located inside close to card slots and plug the charger the pfone vibrates once , space 2 sec and vibrates 3 times .
Any help, idea how to revive the phone very much appreciate.
styropian said:
All this tools looks like working ,only Flash tool at the end was giving me the warning that to be able to use flashTool require to unable option in settings that makes me wondering....
Click to expand...
Click to collapse
Well, can you please post some screenshots of FlashTool, especially one of after the .FTF got successfully flashed?
15/059/2014 18:59:49 - INFO - Ending flash session
15/059/2014 18:59:49 - INFO - Flashing finished.
15/059/2014 18:59:49 - INFO - Please unplug and start your phone
15/059/2014 18:59:49 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
15/059/2014 18:59:50 - INFO - Device connected in flash mode
15/000/2014 19:00:00 - INFO - Device disconnected
Please take look at line: 15/059/2014 18:59:49 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Unlock OEM in developer mode and try it whit Kingroot
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs
Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)
Hello
First to mention - Sony Xperia M5 phone is bootloader locked.
Battery changed 3 months ago.
Software - Stock.
Latest build: 0.9.25.0
Current build : Version 0.9.23.1 built on 11-01-2017 15:12:00
Have not yet updated Flashtool, due 0.9.23.1 was suggested for downgrade by some portugese forum and video tutorial i watched.
Update was announced and i had it always on auto update - i saw message on phone while it was charging (battery was 80% or so...
It did performed update, booted up - but charging liht went red. first at glance everything seemed OK and working, but when i started to download some taken pics from phone, there was no connection with comp. Ok , i did went for BT and uploaded pics to comp.
Later i started to investigate , bo matter i did , changing cables , chargers -- no go , still red light.
I tried repair thru Xperia Companion - installs software 30.2.A.2.1-R2E - New stup and all the stuff but no change.
Is it possible - update did crash something in charging cable module inside the phone - there is some kind of chip on that cable?
So im considering downgrade, S1 fastboot driver installed (blue light) , phone gets connected and flashmode driver (Green light) as well gets detected.
Bit of concern for me - due it can't detect phone in data mode (MTP or PTP) - is proceeding with flash "safe".
Flashtool is latest and 30.0.A.1.23_R1A software downloaded to comp.
Now next step would be creating FTF file.
Suggested by tutorials around - need remove (delete) file FWINFO.XML
Done.
Now looking in to update.xml file
There appears to be boot.zip file listed - which is not in extracted file folder , instead of it is folder boot
with serveral boot-related files.
Qestion is will the flashtool pick FCS file automatically and set right order or i have to apply it to folder where extracted files
are and include in ftf creation process?
Just plug your phone in and use the latest version of flashtool then use xperifirm to download the firmware for your exact device model and then it will give you instructions and it will ask if you want to use FSC script and click yes if you click no the flash will abort