I'm going crazy with this.
I installed the lastest version of flashtool, along with the x10flasher.jar that makes it the latest version.
Both fastboot and google drivers are installed (from the drivers included in flashtool), the device is recognized, the fastboot mode too, USB debugging is activated, but Flashboot gives me these errors messages:
ERROR - No device is registered in Flashtool.
ERROR - You can only flash devices.
I did the same in another PC and is the same error.
Please help it's 3 hrs already with this i'm about to kill my PC i can't see where the problem is, any help is appreciated.
So do you want to flash with fastboot or do you want to flash an FTF? For flashing FTF you need to boot the phone with the other volume key pressed.
ypnos42 said:
So do you want to flash with fastboot or do you want to flash an FTF? For flashing FTF you need to boot the phone with the other volume key pressed.
Click to expand...
Click to collapse
I want to flash a FTF. The phones need to be in flashmode right? i tried with both flashmode and fastboot and it's the same result:
When i go to "flashmode" the device list that should pop up won't appear so i can't select the firmware that is in .flashTool > firmwares.
https://imgur.com/bSOpRM7
This has nothing to do with your phone. The dialog should work even without any device connected. In fact I always prepare the flash before I connect the phone to avoid that it falls asleep before flashing starts.
You seem to not have any flashable ROMs available. When the device filter is empty, you are supposed to see _all_ of your ROMs. Did you bundle the FTF as described in various guides? You cannot flash FTF directly, you have to bundle first.
Also the device filter selector should be populated with all models supported by flashtool. Again it has nothing to do with connected devices. Is your flashtool installation ok?
ypnos42 said:
This has nothing to do with your phone. The dialog should work even without any device connected. In fact I always prepare the flash before I connect the phone to avoid that it falls asleep before flashing starts.
You seem to not have any flashable ROMs available. When the device filter is empty, you are supposed to see _all_ of your ROMs. Did you bundle the FTF as described in various guides? You cannot flash FTF directly, you have to bundle first.
Also the device filter selector should be populated with all models supported by flashtool. Again it has nothing to do with connected devices. Is your flashtool installation ok?
Click to expand...
Click to collapse
When i try to create the bundle i can't complete the "device" field because the device list is empty. I reinstalled flashtool multiple times and still no list. I don't know if it's a problem with the installation, i had installed flashtool in april and use it to flash a FTF with my Compact without problems, the same installation wasn't working yesterday and today i reinstalled and still nope.
I think last time i didn't create a bundle bc flashtool does it automatically when you use the integrated xperifirm, i can't remember exactly anyways.
dnnz said:
I don't know if it's a problem with the installation
Click to expand...
Click to collapse
Well it certainly is.
Related
It seems that people are confused with these to terms and some misguidens has occured. I started this thread to clear it up
1. Flashtool is like using pc companion or SEUS to flash a specific FW. It uses a .ftf file extension and works on phones with or without locked bootloaders. It can only flash stock roms. You get into flashtool mode by turning off your phone and pressing the hardware 'back' button and then connecting the USB cable to your phone. Done correctly and you should se a green light on the power button.
Link to flashtool. Make sure you use the beta version (0.2.9.1) wich is the one that supports our play.
http://forum.xda-developers.com/showthread.php?t=920746
2. Fastboot is a tool you use with a command promt (cmd) on your pc. It's only for people with unlocked bootloaders. It's used for flashing custom roms, kernels, splashscreens, custom recovery etc. everything modyfied. It is also used to unlock your bootloader. You get into fastboot mode by turning off your phone, then pressing the hardware 'search' button and connecting the USB to your phone. Done correctly and you should see a blue light on the power button. Afaik carrier and sim locked devices can't unlock the bootloader this way. If you fall under that category check this link out for help. It will cost you a little money, but by the response of people who already done it, itsems woth the dough
http://forum.xda-developers.com/showthread.php?t=1232050
A link to a thread started by RacecarBMW. It's a reference thread for easy access to info and links to roms/kernels/guides etc.
http://forum.xda-developers.com/showthread.php?t=1076660
Regards Dousan...
I have meizu m2 note. Its now bricked. I was using sp flash tool to unlock the bootloader and install twrp recovery.
i was following the guide giving on youtube. I can't attach an outside link here.
So i did everything this guide said, but on the last step when i switched off my phone and connected to the usb port. The sp flash tool stopped working i waited for 5-10 mins. Finally it crashed. Now when i try to connect my phone it says usb device not recognised (the last device you connected to this computer malfunctioned). I cannot start my phone. I tried pressing the power button for 10 secs, tried pressing volume + with power button, nothing happens.
Anybody have any idea how to solve this.
Go to download old version Flyme os 4+ any but original rom you have must install,
And dow load any latest sp tool,
And also downlaod latest all mtk devices drivers,
If you have system knoledge you can install all of these pc softwares,
Test it once again your phone connecting to computer,
Just detected only nothing. Can do that its just detected your will be alive soon but its very easy if you know a little bit mobile knowledge,
Lets go to process
Step 1 check best and good branded usb connecting cable, test to connect usb cable to your phone,
Step 2 extract Flyme stock rom, and extract mtk sp tool,
Step 3 open sp tool showing error there is no any scatter. Or download file dont worry, da file availble at sptools folder you can go and select, and scatter. File availble at flyme stock rom folder lets check it then select firmware all formate and install that you have to select that option, then you select download and now connect your phone just leave ituntill done then your phone is will alive feel happy like me if you need any more information any other problem connect. To. Me
Can you speak more clearly?I don't understand.Because my English is not very good.
zzx3731 said:
Can you speak more clearly?I don't understand.Because my English is not very good.
Click to expand...
Click to collapse
What problem with your phone?
Hi ! I have the same problem right now, when I plug it, it says device not recognised, what could I do now ?
Thank you very much，This is my mobile phone. It's done.Thank you for your kindness.
：○
Hagadou said:
What problem with your phone?
Click to expand...
Click to collapse
I been able to install LineageOS, I fixed it by pressing home and menu button, it disconnect and reconnect and i been able to Re-flash it with the recovery and when i tried to install Lineage, my error was gone (error 7)
I'd installed TWRP and was playing with some ROMs/Kernels when I hit a boot loop. I then used Flashtool ("Emma") to restore to factory. I haven't been able to send Fastboot commands since. I was wondering if anyone here might be able to point me in the right direction to help me sort this out.
When I connect the phone while holding volume up I still get a blue LED, but when I try to send a fastboot command besides "help", I get "waiting for any device" on Windows. On Mac, Terminal just hangs. I've been able to get the Mac to return the device ID using the "devices" command, but this is intermittent. Normally even this command causes Terminal to hang.
ADB debugging is "on". Flashtool works. ADB commands work. The phone can boot without issue. I can successfully get "fastboot help" to work.
What I've tried:
wiping the Mac HD, installing a fresh OS and installing the latest version of Fastboot from the SDK
Installing the Windows drivers directly from Sony and the latest Platform Tools directly from Google
Running "sudo fastboot" from Terminal on the Mac
Using various usb ports on both machines
Rebooting both machines between steps
Reflashing both Marshmallow and Nouget using Flashtool.
The USB cable I'm using is the one included with the phone. I could issue fast boot commands over this cable a few days ago.
Anyone got any ideas about what I've done wrong here? I'm really confused and I'd like to get rooted again if at all possible.
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
ondrejvaroscak said:
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
Click to expand...
Click to collapse
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
I got that error last time I updated, and was puzzled but tried to leave the phone in flash mode (green led) and flash it again. (I did not unplug the phone so I did not see the result of the first flash) This did leave flashtool without the initial phone info, checking for root and all that but this time the firmware flashed. I did include the fsc file into the ftf, I have no idea if it was a fluke or something but second flash with the phone already in flash mode worked. I know it sounds crazy but It might be worth a shot. Other than that it sounds like a bad cable with the inconsistent fastboot behavior but then again you could flash with Emma, which in turn should not affect fastboot. Odd.
88% said:
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
Click to expand...
Click to collapse
I would definitely try diferrent cable!
The Software update error means there is inconsistency in flash memory and bootloader fails to load initial image after flash. Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode. Then let it boot and when it work, flash your desired version of firmware..
So I tried a number of images built from Xperifirm downloads and finally got one of them to flash properly. I'm not sure if this was due to the specific image or if I just got lucky, but my phone can boot again!
ondrejvaroscak said:
I would definitely try diferrent cable!
Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode.
Click to expand...
Click to collapse
OK, I can try that. Just to confirm, is this a step that I should still take given that I can boot now? While I can boot, I still can't get into Fastboot through Terminal. I was successfully able to get a device ID using the "fastboot devices" command once, but running this command a second time caused a full system freeze on my desktop.
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
edit: I ran into this issue again and noticed that I missed a step in my original reply. In order to get Fastboot working again, I needed to connect using adb and tell the phone to remember my computer on the prompt.
88% said:
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
Click to expand...
Click to collapse
thanks for posting the cause/what you did to fix it.
it might help others, which is what the community is about.
I solved the problem by manually let the FlashTool sync the devices databases from Github
1 - Connect to the internet
2- From FlashTool > Devices > Device Sync > Manual Sync
3- after it's done syncing close FlashTool and open it again..
4- it should say loaded ninety something devices (in my case 94)
5- choose flash > flashmode and choose a folder that contains any correct FTF (not corrupted FTF file) whatever the names of the files are..
you should now have your device(s) listed in the Firmwares box with the FTF files after expanding the device name..
if this method doesn't work for you simply install an older version of FlashTool
here is a link of Ver 0.9.18.6 for windows
https://www.androidfilehost.com/?fid=24562946973630873
Have a good flashing
thanks........it works
After hard reset mobile not working only showing sony logo. Connect to pc by flash tool its not showing any device connect.
Sumaiya basha said:
After hard reset mobile not working only showing sony logo. Connect to pc by flash tool its not showing any device connect.
Click to expand...
Click to collapse
Had the same problem with my Xperia T (LT30P). Just disconnect the battery and hold power and volume up for a few seconds (dunno if it does something, just repeating what i've read somewhere). After that it should connect to your pc just fine so you can flash another kernel and/or ROM.
Please delete this.
firmware detected but it is not able to flash as the drop down is not coming after pressing sony firmware
Click on very left arrow not in content..... Working 100%......click untill the end of the arrow
View attachment flashtool_2020-08-05_05-13-41.logflashtool is not flashing my xperia z3 it just stays in connect your device and says connected with usb debbugin of 2011 devices make sure mtp is off help asap
Didn't work in my case, tried on Flashtool v0.9.34 for windows and linux and v0.9.28 for windows, it refused to read the Xperia SO-02K firmware which I needed to flash for DRM keys backup.
Flashtool v0.9.18.6 and v0.9.15 for windows were both able to read it, but threw "root : this bundle is not valid" and "Cannot open bundle. Flash operation canceled" errors during flashing. I tried four different versions of the firmware and ultimately used newflasher v20 instead.
Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!
deepbluev7 said:
Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!
Click to expand...
Click to collapse
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.
levone1 said:
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.
Click to expand...
Click to collapse
Thank you for your response.
I don't think it's a driver issue. I flashed via flashmode before on Linux and Windows, and in those cases the green light stayed on, until I switched the phone off. Now the green light goes off, before it can even connect to my computer, so it seems like the flashmode crashes on the phone. Nonetheless I tried the driver install, but that didn't change anything.
The phone only lights the green light for a second, before it goes off and then it starts looping red -> green -> off -> repeat.