Develop Bugs

CUBOT GT72E (MT6572) BRICKED (Help Thread)

Hello, first than everything I'd like to thank you all in advance... Now to the problem in hand, I recently got 2 CUBOT GT72E Phones, one of them I flashed with was supposed to be a STOCK Firmware:
http://blog.geekbuying.com/index.ph...for-cubot-gt72-mtk6572-dual-core-smart-phone/
I used SP Flash Tool for this, the process went seamlessly and when I got to the final OK Green Circle and then disconnected and tried to turn on my phone, it wouldn't turn on or do anything at all, I inmediatly freaked out and tried to find out how to solve it... So after some reading and learning, trial and error, I have found out the phone is not fully bricked and that there might be a solution.
First I took the battery out, connected the phone and put on the battery again and managed to install "MTK USB Port" Driver, the computer successfully detects the device as it, though when trying to reflash the "STOCK" Firmware or some other Backups and previous "working" Firmwares I stumble on ERROR 4032 - ENABLE DRAM FAILED!
After some more reading I think the reason might be a wrong PRELOADER, or so it seems to be with many other devices of other people that had the same problem.
So then I had an idea, I considered myself an idiot for flashing a PRELOADER without backing up the previous Firmware beforehand, but I have another working phone, exact same one, came on same shipping, same stock ROM, so well I then decided hoping I wouldn't end up bricking the second one, to try and backup the Stock Firmware from my working phone, so after Rooting it I used MTK Droid Tools and successfully made a Backup that included what I'm almost entirely sure is a working PRELOADER.bin, I also downloaded some other Backups and Readbacks that meet the same criteria and that I assume work as well, or so they should.
Now... I feel I'm pretty close to REVIVING this bricked phone, just a few more issues and I'm running out of help online just by reading, I'm hoping someone can directly help my case.
After making the scatter file for my backup of the working phone using the firmware.info, and trying to load it into SP Flash Tools, it fails to load the PRELOADER (Fail to load ROM file: PRELOADER) and it apppears in red letters in list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I double click PRELOADER on list and pick the working file it keeps saying it fails, what can I do to avoid this, or is there any other tool, I have already tried MTK Flash Tools, I manage to load the PRELOADER.bin in it, but as I go ahead and "Download" it just gets stuck on the Download DA 100% Red Bar until it finally stumbles back on ENABLE DRAM FAILED!
I've tried mixing it up and using the other backups that should work as well, I have checked and they fill all the specifications and criteria for the specific phone, and what happens is that, even if I'm able to properly load the Scatter file with the PRELOADER and everything, when I try to flash it, it goes ahead and fills up the Red Bar and immediatly after that it does nothing and just stops, leaving the Format, Firmware Upgrade and Download Buttons enabled again, the Red Bar remains on the bottom but no change at all.
Now what I guess might be the missing piece would be to be able to fully load the backup I made from the working phone to flash it successfully and reviving the phone. I'm also considering I might have the wrong driver or somehow I'm not accessing the download mode on the phone needed to flash it properly. I've heard something about META mode, holding Volume UP and without battery, I've tried that, though PC identifies it with the same driver, so I'm not aware if I should be using another driver, and uninstalling and deleting the previous one first before trying...
So in conclusion I think I need some help with two specific things:
- Pinpoint the Driver needed for my CUBOT GT72E a MT6572 device.
- Find out how to load the backup from working phone into SP Flash Tool.
I'll also leave the detailed specifics of the phone (the working one) from MTK Droid Tools
Hardware : MT6572
Model : CUBOT GT72E
Build number : Z22D_CQ_E2_A_H1.00_V01_CUBOT
Build date UTC : 20131030-152620
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P18, 2013/09/07 14:55
Kernel v : 3.4.5 (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Oct 30 23:22:42 CST 2013
Uboot build v : -----
LCD Driver IC : 1-HX8379A_wvga_vdo
I don't mean to be pushy but this sort of things tend to get me very anxious and worried, I'd love some help or even replies trying to contribute, I'm doing my best and even if I'm not an expert on Phones and Android Devices, I think I can handle myself with some advice, shouldn't be too hard so just give it a try, any advice or hint will do.
This seems like a good phone, the working one I've been using so far is doing great, it's the first cheap Dual Core device I've seen and I'm really looking forward to developing custom releases for this one, I mean to contribute to this community, but if I can even un-brick this one I don't think I'd be of much help, hurts my pride a bit, I think I can do it, I just need a little help, I'm not giving up just yet so please I'd appreciate you avoid comments like "You blew it" "It's hard bricked, just give it up" or "Return to supplier"
This is a thread that explains how to unbrick MT65XX devices, so before you refer me to it and just paste the link, I've read it and found it really helpful, quoting this thread (Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE) Please refrain from telling me to give up, I haven't seen a successfull post of Cubot GT72E Unbricking and I intend to be the first one, yet I've seen many posts on both Cubot Forums and other sites of people having bricked their phones by using this "STOCK" Firmware, finding a solution for me is allowing me to help others to solve this as well
http://forum.xda-developers.com/showthread.php?t=1943442
I'll try and contact "rua1" who has developed all this tools and seems like an expert to see if he can help me.
Again thanks for taking the time to read this thread, I look forward to your replies.

BUMP
BUMP (Perhaps I posted too late in the night)

Aedirus said:
BUMP (Perhaps I posted too late in the night)
Click to expand...
Click to collapse
If you have 2 phones then you are in luck.
Use the mktool and sp flash to make a full backup of the working phone and use the back up and to restore the soft bricked one.
Loads of guides on how to do it.
Use this guide to backup the working one forum.xda-developers.com/showthread.php?t=2438752

Managed to unbrick - lost imei & baseband
I managed to revive the phone using the "Stock" firmware, it's scatter file, but writting the preloader from my other phone, the ROM had no Developer Options to enable USB Debugging, I installed an update through recovery and it was now there, rooted it, but now I've lost IMEI and Baseband on it, I also had WARNING NVRAM = ERR 0x00 on Wifi, but managed to solve it by Hex Editting the WIFI file inside data\nvram\APCFG\APRDEB with the right MAC Address.
So far so good, but from all the methods I've seen and found to write IMEI into device, none have worked...
I assume there is a problem regarding "pttycmd1" and lot of files that are on the dev\radio folder of the working phone and that the unbricked one doesn't have, strangely though I can't seem to copy the "radio" folder or any of the files inside it with Root Explorer or any other root file explorer, it simply gets stuck on the first file, permissions on the folder and files are fine... So I don't know what the problem might be or how to sort it out...
Some threads I've seen online suggest flashing the SEC_RO.img from a backup (I'd use the one from the working phone). Yet I'm not sure if I should or could do it, strangely the only Scatter file that works is the one from the "Stock" firmware, should I try loading that scatter file, only ticking SEC_RO.img and loading the one from my backup into it and hit Download?
There should be no harm in it, but I wonder if it would cause both phones to have the same IMEI...
In conclusion and to make it clear, I have revived the phone but it seems somehow NVRAM got formatted and I lost IMEI, Baseband and pretty much everything you'd lose when you format NVRAM...
Any thoughts?

Aedirus said:
I managed to revive the phone using the "Stock" firmware, it's scatter file, but writting the preloader from my other phone, the ROM had no Developer Options to enable USB Debugging, I installed an update through recovery and it was now there, rooted it, but now I've lost IMEI and Baseband on it, I also had WARNING NVRAM = ERR 0x00 on Wifi, but managed to solve it by Hex Editting the WIFI file inside data\nvram\APCFG\APRDEB with the right MAC Address.
So far so good, but from all the methods I've seen and found to write IMEI into device, none have worked...
I assume there is a problem regarding "pttycmd1" and lot of files that are on the dev\radio folder of the working phone and that the unbricked one doesn't have, strangely though I can't seem to copy the "radio" folder or any of the files inside it with Root Explorer or any other root file explorer, it simply gets stuck on the first file, permissions on the folder and files are fine... So I don't know what the problem might be or how to sort it out...
Some threads I've seen online suggest flashing the SEC_RO.img from a backup (I'd use the one from the working phone). Yet I'm not sure if I should or could do it, strangely the only Scatter file that works is the one from the "Stock" firmware, should I try loading that scatter file, only ticking SEC_RO.img and loading the one from my backup into it and hit Download?
There should be no harm in it, but I wonder if it would cause both phones to have the same IMEI...
In conclusion and to make it clear, I have revived the phone but it seems somehow NVRAM got formatted and I lost IMEI, Baseband and pretty much everything you'd lose when you format NVRAM...
Any thoughts?
Click to expand...
Click to collapse
Should be fine, extract the recovery and sec ro from working phone and flash.

Tried it
Well I did it with the SEC_RO.bin, and even managed to flash the NVRAM.bin after some pretty annoying scatter file editting, the only scatter that works is quite more complex than your regular scatter, but I managed to do it, so I know have the same files in the "radio" folder and etc...
Still can't manage to recover IMEI or write it with any tools...
I didn't flash the Recovery.bin from the working phone, would it make any actual difference? Just asking... I'm still quite new to all of this...

Recover IMEI
Any clues or thoughts on how to recover my IMEI?

IMEI doesn't remain
I managed to Write the IMEI with this tool, check this screenshot:
However when I reboot the phone IMEI's remain "Invalid", I'm assuming the phone is rolling it back, when I had problems with the Wifi WARNING ERR 0x00 I had to not only Hex Edit the WIFI file with the correct MAC Address but also change it's permission to only read to prevent the phone from rolling back to wrong file, is there a way to prevent the IMEI not being stuck to the phone? Perhaps formatting the NVRAM before trying to write the IMEI?

HELP PLZ
C'mon people, I'm so close already, just one more push, read the post and help me out, I know I can solve this!

Aedirus said:
C'mon people, I'm so close already, just one more push, read the post and help me out, I know I can solve this!
Click to expand...
Click to collapse
Try this app http://d-h.st/xGU there is a option to write IMEI
http://www.youtube.com/watch?v=4gRAlf--D8E

Doesn't work...
I don't have CDS Information Option, it doesn't appear, I'm guessing it doesn't work for MT6572...

BUMP
BUMP! C'mon guys almost there, with two phones, there must be a way to backup and flash Baseband, NVRAM or w/e is needed from the working phone to the other one, I just haven't stumbled on the right one... MT6572, CUBOT GT72E, Thanks!

Re-BUMP
Re-BUMPING, I hope I'm not abusing it, I just would like for more people to try and give me some advice... Can't be that hard, again I have two phones, one of them is working with the stock firmware and has all the Baseband and IMEI info...

I had the same problem with my Huawei Y511, I can restore with the phone of my wife, this is the same phone! For restore the NVRAM you can use MTK DROID TOOLS the last version, support the MT6572...

spawn784 said:
I had the same problem with my Huawei Y511, I can restore with the phone of my wife, this is the same phone! For restore the NVRAM you can use MTK DROID TOOLS the last version, support the MT6572...
Click to expand...
Click to collapse
Somebody progress?

Of Course!!!
h3ct0r said:
Somebody progress?
Click to expand...
Click to collapse
Yeah Friend! Any question ask me! :good:

hello ! im in the same situation here... ive revived the phone but no imei and can't write it with any tool out there... can anybody give me a hand here?? please !!!
thanks in advance !!

i have finally find a solution to our problem !! i will open a new topic with all the info and the working ( modified ) ROM !!
http://forum.xda-developers.com/showthread.php?t=2656547 check my tutorial

Great to hear!
Next week I'll have the bricked GT72E again in my hands,
I read the url what was placed here to another topic but that file is made for another MTK6572.
Anyone who can supply me the correct file for the GT72E with a small tutorial.
Thnx in advance

BUMP @Aedirus
Can you send me a scatter file, I have the device here but with the tutorials that I found on this topic I can't come further.
Thnx in advance!

[Q] How do I flash FTF without Flashtool?

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

How to full backup any qualcomm phone (no root)

Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:

If read back gets interrupted in between will it brick ?
Demon_king18 said:
Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:
Click to expand...
Click to collapse
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks

Suhi02 said:
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks
Click to expand...
Click to collapse
Nope, in backup process just don't format or delete any any thing in your phone's internal memory, your phone will be ok. But when you restore the phone, if the process broke, your phone maybe brick depen on how many percen had complete!

how to restore?

Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device

Can we backup full boot.img and system.img with that?
Or does it only backup data partition?

skeleton1911 said:
Can we backup full boot.img and system.img with that?
Or does it only backup data partition?
Click to expand...
Click to collapse
When you using this method, it will backup all of your partition: boot, recovery, efs, system, and user data too!

Rempoiiii said:
Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device
Click to expand...
Click to collapse
For my device (Obi Sf1) just long press (may up to 3 minutes) all of my 3 hard buttons to wake him up!

irwan_dcp said:
how to restore?
Click to expand...
Click to collapse
Sorry, my phone had lost, so i can't made a guide video for you. But there is a guide here: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Hope usefull!

Nice tutorial but eroor 0x80004005 when pressing download mode
Nice tutorial thanks, but I'm getting error code 0x80004005 after pressing download mode, trying to backup huawei scl-l01 in QC 9008 mode port is visible drivers are ok

Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the only thing stopping me for now. Might you know what is happening? :crying:

Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
This is the only thing stopping me for now. Might you know what is happening? :crying:

Getting the 0x80004005 error also. Any suggestion? The phone shows up as qualcomm device just fine.

find another way to boot into EDL mode. usually you have a timeout ~30 sec

Can we restore userdata with qfil ?

aIecxs said:
find another way to boot into EDL mode. usually you have a timeout ~30 sec
Click to expand...
Click to collapse
There is no other way to boot into EDL if your screen is completely blacked out and all what the computer recognises is a Qualcomm device in Device Manager.

deep flash cable? test point method?

aIecxs said:
deep flash cable? test point method?
Click to expand...
Click to collapse
I have a cable and it doesn't work.
I took my phone apart and did the test point shorting, that doesn't work either.
I have also been told that the phone is already in EDL mode but the problem is me getting that error message!

if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver

aIecxs said:
if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver
Click to expand...
Click to collapse
Done that from the start.

Flashtool available for Xperia XZ Premium and XZ1 devices

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.

Q: Sony Xperia M5 (E5603) and 30.2.A.2.1 update - lost charging.

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