Hey guys!
Since there was no thread about it yet, and since Sony released recently a new bootloader update for the Xperia M2, I decided to open a new one, and explain a little more how it works.
The bootloader update is used, in the Xperia M2, to unlock the R/W features in the recovery partition. This means that, if you've an UBL device, and you flash the update, you'll get permissions to install a new UBL recovery inside the partition itself. So, you won't need to include an external ramdisk inside your boot image.
How can I obtain it?
You've currently 2 ways:
1. Download and install Emma and apply the update from there, which will be always the latest available.
2. Download it through an FTF (explained below).
How can I install it if I choose FTF way?
First, download the latest FTF from below. Once downloaded, place it in flashtool's firmware folder, which is located in C:\Users\<your-name>\.flashTool\firmwares\.
Now, launch Flashtools (it needs to be version 0.9.18.6 or below, mandatorily), choose the FTF update (you'll easily notice which one it is), and simply hit flash.
Once prompted, connect your device while off to the Micro-B end of the USB cable, and, while you press & hold the Vol- key, connect the USB-A end to the PC. Then flash will start.
How can I install a custom recovery?
Download my ADB Pack 'Herramientas-de-flasheo.zip'.
Now, unzip my ADB Pack 'Herramientas-de-flasheo.zip', which contains basic ADB and Fastboot executables to a folder in your desktop. Also, copy the file Recovery file you downloaded to that folder.
Put your phone in Fastboot mode, this means, while pressing and holding the Vol+ button, connect the USB cable. Once the Led goes blue, stop pressing it.
Now, execute the following keyboard shortcut (Win+R) and type inside the Run prompt CMD. Inside the Command Prompt, using CD (change directory), navigate to the folder you created in the desktop. It'll be something like...
Code:
cd C:\Users\linuxct\Desktop\adbpack\
Now, execute the following command:
Code:
fastboot flash recovery <[COLOR="Purple"]NAME-OF-THE-RECOVERY[/COLOR]>.img
How can I access the recovery?
To enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the Sony logo, stop holding the Vol- Button.
DOWNLOAD: Latest Bootloader Update FTF [ver 1.716]
--------------------
DOWNLOAD MIRROR: Latest Bootloader Update FTF [ver 1.716]
Amazing work as always @linuxctt
Maybe be our Cyanogenmod 13 maintainer...? I'll walk my self out
There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy
imzihad said:
There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy
Click to expand...
Click to collapse
That's the one I commonly use, but I found easier the one I wrote in the tutorial
Thanks
Thank you Linuxct, It works as always.
Do i need install Ric disabler this time?
Can I update D2302 with this
I can't see any file in the flashboot firmware selector dialog box.
{
"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"
}
nishchayv said:
I can't see any file in the flashboot firmware selector dialog box.
Click to expand...
Click to collapse
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...
linuxct said:
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...
Click to expand...
Click to collapse
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.
nishchayv said:
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.
Click to expand...
Click to collapse
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.
linuxct said:
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.
Click to expand...
Click to collapse
Thanks fo your help. BTW I have downloaded version 0.9.18.6 from this linkhttps://drive.google.com/file/d/0B1AAC4lt7nzOQzR3aTZKUFZqem8/view?pli=1 and it's working fine for me.
hi, I have stock kitkat so can i still update my bootloader using flashtool, i have root and unlocked bootlloader
Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37
gabrielmr said:
Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37
Click to expand...
Click to collapse
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.
linuxct said:
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.
Click to expand...
Click to collapse
It worked, I just started Flashtool in administrator mode.
Flashtool and Emma gives a hard time (Jul 2016)
Hi,
Same as gabrielmr... Emma installed, seems to update and restart, and then disappear in the background. Ok, then I'll use flashtool. Oh wait, there is a new version, before all, I'll update it and then flash the ftf. So I updated to latest version and... no way to see that firmware. If I had read the tread closely, I would have seen that flashing with Flashtool Version 0.9.19.8 would have taken 2 seconds, instead of trying my best to use the last flashtool version, which doesn't show the downloaded firmware XPERIAM2_1.716_BOOTLOADER_UPDATE_(ONLY_OPEN_DEVICES).ftf.
Just saying for noobs following the procedure.:cyclops:
Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance
aleksa069 said:
Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance
Click to expand...
Click to collapse
Basically yes only for unlocked bootloader devices
Hey, i have got problem with Flashtool. AVAST Says, that version have malware. Can someone send my that version witchout malware?
Hello, it will work with Xperia m2 dual d-2302?,
Thanks in advance
Sent from my D2302 using Tapatalk
Related
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
bozo089 said:
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
Click to expand...
Click to collapse
fastboot clockwork recovery then flash a rom.
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
bozo089 said:
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
Click to expand...
Click to collapse
do you have the recovery.img file in the same folder as fastboot?
simms22 said:
do you have the recovery.img file in the same folder as fastboot?
Click to expand...
Click to collapse
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
bozo089 said:
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
Click to expand...
Click to collapse
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
simms22 said:
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
Click to expand...
Click to collapse
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
bozo089 said:
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
Click to expand...
Click to collapse
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
bozo089 said:
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
Click to expand...
Click to collapse
OK, i did a system restore and now i have pdaNet back. I have no idea how to use it or what to do next.
Please help!
EDIT: when i typed "fastboot devices" into CMD, it shows my device!
take a screenshot of your /sdk/tools folder.
(seriously do it).
OR if you don't want to.. does fastboot appear as "fastboot" or "fastboot.exe" ?
Uploaded with ImageShack.us
There you go
bozo089 said:
Uploaded with ImageShack.us
There you go
Click to expand...
Click to collapse
Okay, yeah. I see the problem, your extensions are hidden "recovery.img" is actually "recovery.img.img" so you're fastbooting a invalid file. What I want you to do is on the top left of a Windows explorer, it says Organize. Press that and go to folder options -> view -> hide extensions for known file types (UNCHECK THIS). Rename recovery.img.img so it appears as recovery.img not recovery.img.img
Put your phone in bootloader mode if it isn't already with USB plugged in.
The phone needs to be in bootloader mode in order for it to recognize the fastboot command.
{
"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"
}
^ appears as that.
through command prompt
cd C:\android-sdk-windows\tools\
(optional -- do this if your phone isnt in bootloader mode) adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
and you're set. click on "thanks" if this helped you!
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
bozo089 said:
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
Click to expand...
Click to collapse
yeah that meant it worked. you can access clockwork menu by going down to RECOVERY in the menu or "adb reboot recovery"
you install a ROM by...
1. Shop around the Dev forums and look for what ROM you want to use. I personally use CM7.
2. Use netarchy's kernel (its worth it).
Steps:
1. Put ROM onto your sdcard
2. Boot into Clockwork Recovery (told you above on how to do it)
3. Wipe Factory, Dalvik, Cache
4. Flash ROM (Proceed to flash CM7 Gapps afterwards if you decide to go with CM7)
5. Flash Kernel (Optional)
6. Reboot!
Ahhh, i updated without looking at your post first. Can i put the kernal on now that ive rebooted?
thank you for your help and time
Hello guys!
Today I'm bringing you a tutorial on how to achieve root permissions on the Xperia M2 with Android 5.1.1 Lollipop. As of right now, this is only available for UNLOCKED BOOTLOADERS, so those with LBL have to wait a little more until I find a suitable solution.
What do we need?
Upgrade your bootloader using this guide.
My ADB pack.
My modded TWRP for unlocked bootloaders.
Ric Disabler by my friend @AleksJ [MIRROR]
The procedure:
First, flash Lollipop if you didn't flash it before. Once done, upgrade your bootloader using Emma or the FTF I linked before.
WARNING: If you updated your bootloader BEFORE FLASHING LOLLIPOP, you MUST upgrade it again since Lollipop FTF overwrites it.
Now, turn on the phone, go to Settings, Info. about the device, and tap 7~8 times the Compilation Number. This will un-hide the developer options. Press back button once and go inside the Dev. Options. Now turn them on if they were off, and enable USB Debbuging. Now turn off your phone.
Now, unzip my ADB Pack 'Herramientas-de-flasheo.zip', which contains basic ADB and Fastboot executables to a folder in your desktop. Also, copy the TWRP Recovery .img you downloaded to that folder.
Put your phone in Fastboot mode, this means, while pressing and holding the Vol+ button, connect the USB cable. Once the Led goes blue, stop pressing it.
Now, execute the following keyboard shortcut (Win+R) and type inside the Run prompt CMD. Inside the Command Prompt, using CD (change directory), navigate to the folder you created in the desktop. It'll be something like...
Code:
cd C:\Users\linuxct\Desktop\adbpack\
Now, execute the following command:
Code:
fastboot flash recovery [COLOR="DarkOrchid"]RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME[/COLOR].img
Once it finishes, disconnect the USB cable. Now, to enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the BIG Sony logo, stop holding the Vol- Button.
This will load Erikcas TWRP. After few seconds, it'll ask you to allow /system modifications, so slide it to allow modifications. Now navigate to Reboot, and choose System. In a moment or so it'll ask you if you want to root your device. To do that, slide again.
The device will reboot in a few seconds. When it's succesfully booted up, go to the App Drawer and look for 'SuperSU Installer'. Open it and hit the 'Play' button. This will open SuperSU in Google Play. Now update SuperSU.
When it's done updating [Don't open SuperSU yet!], unzip the Ric Disabler from AleksJ in your PC, and open the Install.bat OR Use the following Bash Script if you're on Linux, thanks to @luichi. Once it's opened, connect again your device via USB. In the M2, the script will prompt a question about USB Debbuging key. Tick the 'Remember this PC' checkbox and hit Allow. After some secs, it'll ask you for root permissions, so hit Allow.
In a while, when in CMD it says 'Press any key to continue', disconnect your cable and open SuperSU in your device. Now it'll ask you about updating su binary. Hit Update, and then hit on 'Normal' method.
And that's it! Enjoy your Lollipoped device with Root!
Don't forget to hit the thanks button and thank all people mentioned in this post too!
Thanks for this tutorial! All working
Can you make bootloader in FTF file for D2305 plz? Thanks!
Thanks
Do you know if Xposed is fully working?
Laura158 said:
Can you make bootloader in FTF file for D2305 plz? Thanks!
Click to expand...
Click to collapse
It's generic, don't worry, you can use it in any D230X and any D240X you want.
KolikKitsune said:
Thanks
Do you know if Xposed is fully working?
Click to expand...
Click to collapse
I have no idea...
KolikKitsune said:
Thanks
Do you know if Xposed is fully working?
Click to expand...
Click to collapse
@KolikKitsune for me nope. i might do something wrong but its saying with the current version it doesnt work
{
"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"
}
It is only for M2 or for Aqua too?
Evedammo said:
It is only for M2 or work in Aqua too?
Click to expand...
Click to collapse
Aqua too! Any M2 in general can use it :good:
via emma ? can you show how upgrade bootloaders via emma ?
WoW, nice work. Have a fully working recovery AND root now.
If you want something "simpler", you can flash a boot.img with integrated recovery instead of using the first method.
BlazingBullets said:
WoW, nice work. Have a fully working recovery AND root now.
If you want something "simpler", you can flash a boot.img with integrated recovery instead of using the first method.
Click to expand...
Click to collapse
But then you'll need to go back to 5.1.1 kernel in order to boot the device, loosing the recovery. This recovery is permanent as it's isolated in it's own partition.
faizal21 said:
via emma ? can you show how upgrade bootloaders via emma ?
Click to expand...
Click to collapse
Follow this nice guide made by Sony
vampirian said:
@KolikKitsune for me nope. i might do something wrong but its saying with the current version it doesnt work
(img)
Click to expand...
Click to collapse
Guys, you need to install the experimental Xposed for Lollipop 5.1.1! The 4.x installer is not working anymore!
BUT, take this into account:
- Sony seems to have shipped some ROMs with corrupted services.odex (the embedded .dex is invalid). Those ROMs will bootloop with a "Fatal signal 6" or "No pending exception expected: java.lang.ArrayIndexOutOfBoundsException" error, which I unfortunately cannot fix.
Click to expand...
Click to collapse
@linuxct
I dunno if I flashed back or not, but if i didn't then I think FKernal works with 5.1.1
Don't really want to test it either
Guys dont even try xposed...Bootloop because of corrupted services.odex
Too late... -.-
after Flashtool by sony
after taht, what the next step ?
faizal21 said:
after taht, what the next step ?
Click to expand...
Click to collapse
After flashing the bootloader update, turn the phone on, enable USB Debugging and then turn it off; and go ahead to flash erikcas twrp. (2nd and 3rd points)...
after step 8 i reboot like normally but touch wont work, but the touch in RecoveryMode work well..
Hello experts!
I followed this tut here https://www.youtube.com/watch?v=dTlosea6SJE to root my Sony Xperia Z5 phone and to use a costum ROM. Everthing worked, but after (~09:00 min.)
Code:
adb reboot bootloader
fastboot flash boot boot.img
[I]Okay[/I]
fastboot flash revovery recovery.img
[I]Okay[/I]
fastboot reboot
and entering TWRP (2.8.7.0) by pressing ON + VOL DOWN
I am stuck here.
- I cant get a connection from my PC to the phone, its not recongnized anymore in ADB (result blank) after
Code:
adb devices
- the extra SD card (in SD card slot) is not mounted and the TWRP-mount option dont let me select "Micro SDcard" or "USB OTG".
- I cant copy images or zips or any files to the phone plus I cant read data from the ext. sd card (fat32, 4096 bytes) when inserted in the phone.
Asking for help:
How can I mount the SD card via TWRP-Teminal ?
How can I adb connect the phone to my PC again ?
Any suggestions to reflash the phone ?
I really appreciate any help!
Thans a lot !
Superblond
P.S. sorry for my poor english ...
hold Vol Up and power button to soft reset, then flash your phone using flashtool and thats it
---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------
i PMed you. if you need any help send me a message. Cheers
Power on + Vol up dosent work for me...nothing , black screen no vibration
L33Tgod said:
hold Vol Up and power button to soft reset, then flash your phone using flashtool and thats it
---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------
i PMed you. if you need any help send me a message. Cheers
Click to expand...
Click to collapse
Hi & thx,
Power on + Vol up dosent work for me...nothing , black screen no vibration.
I will pm you...
Blue led on = not bricked !?
Connecting the phone to my PC via USB, with holding Volume up, brings up the blue LED.
But with
Code:
adb devices
the phone is still not recognized.
Dont know what to do next...
SB
[SOLVED] Re-flashing a ROM with TWRP only on phone
After failing to manually mount the SD-Card or a USB-Stick via OTG-cable through the Terminal with command line function, the xda-user L33Tgod gave me the (simple) tip via pm to use the flashtool and flash the phone with a valid ROM (again)... THX a lot L33tgod!
As a result, I can access my phone & my SD-Card again. Now I have a working ROM on my phone and I am no longer stuck in a TWRP-Menue only, without the chance to communicate with the phone via ADB etc.
So I followed the below how-to (nothing new, I know, but the solution for my problem)
Flash your FTF firmware file
This section details the steps needed in order to flash new firmware onto your Sony Xperia device.
First of all, open Flashtool and then click on the lightning bolt in the top left of Flashtool as highlighted below.
{
"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"
}
Select “Flashmode” and click “OK”.
You should already be in the source folder where the FTF firmware files are located. If not, navigate to: “C:\Users\[Your PC Name]\.flashTool\firmwares”
Select the firmware build version that you want to flash from the “Firmware” pane. Ensure the device variant is the same as the model number of your Sony Xperia device.
If you want to retain your apps, data and media (photos, videos, music), then ensure that the “USERDATA” option within the “Wipe” pane is unticked. However, we recommend that when upgrading a major new Android version, a clean install is the way to go. In this case, tick all options under the “Wipe” pane. This will wipe all of your data though including your photos and videos, so please ensure you have these backed up elsewhere.
IMPORTANT – For FlashTool 0.9.19.10 and older: If you skipped Part 2 of the guide as you already had your own FTF firmware file, then you may see the following ‘SIMLOCK’ option ticked under the “MiscTA Exclude” pane. DO NOT untick SIMLOCK as it could lead to problems with the network lock on your device.
IMPORTANT – For FlashTool versions 0.9.22.0 to 0.9.22.2: The developer has changed the meaning of the tick box in newer versions of Flashtool, which means ticking the box includes “SIMLOCK”. Either way, you want to ensure you are NOT including SIMLOCK when flashing firmware. So to be clear, when presented with the “SIMLOCK” option below, you must NOT tick the box.
NOTE – For FlashTool 0.9.22.3 onwards: The developer has disabled “SIMLOCK”, which means you no longer have to worry about accidentally including it in your firmware flashing. The option is only enabled by entering ‘Pro’ mode. Unless you know what you are doing, then stay well away from Pro mode.
Click “Flash”. Flashtool will then indicate that it is “preparing files for flashing”.
You may have to wait around 60 seconds for the pop-up below to appear. Once it does, you should now connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. Once the pop-up disappears and flashing has started, you can let go of the ‘volume down’ button.
Flashtool will then start flashing your Xperia device.
Once you see “Flashing finished” as indicated below, your Sony Xperia has been successfully flashed.
Congratulations you have just installed Android Marshmallow! Now disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected.
To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
If you would also like to confirm the region firmware that you have downloaded, you will need to access the service menu option. To do this, open the dialler and enter the following: *#*#7378423#*#*
Then click ‘Service info > Software info’. The CDF is an eight digit number under the “Customization Version” that should tie in with the firmware you downloaded from XperiFirm. For example, you will notice below that the CDF (software customisation version) of 1298-7362 matches the same firmware that we downloaded in the XperiFirm screenshots above.
Thx to all the helpers !
SB
Hi dear friends. I have a interesting problem with Flashtool and Sony's last OREO update.
I want to flash 41.3.A.2.58 with flashtool. If I use old version of flashtool v0.9.23.2, I can connect my phone flash mode, but I can't flash last oreo update from Sony I get "NULL" error.. If I use newest version of flashtool 0.9.24.2, The FW was preparing to flash but my phone doesn't connect with flash mode so this time I get this "ERROR - Device connected in flash mode but driver is too old". I installed driver which is in the folder of newest Flashtool.I didn't understand what I did wrong. I am using Flashtool many years but I can't solve this problem. Please check the pictures.
FLASHTOOL v0.9.23.2
{
"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"
}
FLASHTOOL v0.9.24.2
There is an update for flashtool. I suggest you update and try again
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Tonio78r said:
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Click to expand...
Click to collapse
I am using last version too. And I installed last version driver but no luck you can see the pictures up
koekoek91 said:
There is an update for flashtool. I suggest you update and try again
Click to expand...
Click to collapse
I am using last version also but I get old driver error...
Mazellat said:
I am using last version also but I get old driver error...
Click to expand...
Click to collapse
Oh nevermind I now see your second screenshot is from the latest version.
Have you tried reinstalling drivers?
And have you tried redownloading the firmware or a different firmware maybe?
koekoek91 said:
Oh nevermind I now see your second screenshot is from the latest version.
Have you tried reinstalling drivers?
And have you tried redownloading the firmware or a different firmware maybe?
Click to expand...
Click to collapse
Bro I tried to install again and again Flashtool and drivers. But no luck...
Best to use flashtool version 0.9.24.2 to flash version 41.3.A.2.24_R3E(or equivalent) and then wait for an OTA to the latest version (41.3.A.2.58).
okubax said:
Best to use flashtool version 0.9.24.2 to flash version 41.3.A.2.24_R3E(or equivalent) and then wait for an OTA to the latest version (41.3.A.2.58).
Click to expand...
Click to collapse
I have unlocked bootloader So I think I can't use OTA update
boot ur phone in to download (flash) mode, go to device manager, expand universal serial bus controllers, then find somc device. "uninstall" delete the driver software. than unplug usb and repeat againg, boot into flashmode (not need flashtool any time) go into device manager, expand universal s b c, look for somc devices, or "semc device" if find delete again, if u see in un/recognized "android" u are done. now go to drivers from flashtool and install flashmode... i was installed flashmode and fastboot. while u installing that drivers look at "Android" now is again "somc device" and already version like a last flashmode driver. but different now is, now u can flash ur phone with latest flashtool by "ANDROXYDE" sorry about bad english, but i hope u understand me.
As G-Un1t say, start in flash mode and unistall all "semc" devices, and do that until u get the "semc" unrecognized, then disconnect, reinstall the flashmode and fastboot drivers again and then once again connect in flash mode.
Works for me on triying upgrade a Sony C5 Ultra(for latin america) From Lollipop to Mashmallow.
U have to repeatedly uninstall the SOMC devices, then SEMC devices till you see an "Android Driver" with a yellow ? mark..... Your are good to go after that...... thanks G-UN1T
Try this one
1. Download the relevant driver package from developer.sonymobile.com/downloads/drivers/. Make a note of the package folder name and of where you unzip the files.
2. Open Device Manager. You can do this by clicking Start, and then typing device manager. Then click Device Manager.
3. In Device Manager, right-click the name of your computer at the top of the device list, then click Add legacy hardware.
4. In the Welcome to the Add Hardware Wizard dialog, click Next.
5. Select the Install the hardware that I manually select from a list option, and then click Next.
6. Highlight Show All Devices and click Next.
7. Click Have Disk....
8. In the Install From Disk dialog, click Browse, and then find (see your note from step 1) and select the driver file ending with adb (written as xxxxxadb, where xxxxxx is the unique file name). Click Open.
9. In the Install From Disk dialog, click OK.
10. Highlight the Sony xxxxxx ADB Interface Driver file, then click Next twice. The installation starts.
11. Click Finish and then restart your computer.
hope this one help you guys
on this thread i finally found my problem solver for Device connected in flash mode but driver is too old, thank you
i just deleted SEMC driver on Device Manager of my 7-64bit, install driver from the folder of Flashtool,
Checklist Fastboot, Flashmode Drivers, and also Xperia Z3+ drivers, followed the instruction about 2012 method, and its worked
mine is E6553 Single...almost lost hope and thinking about suicide.
solved my undetected Sim Card problem too, after trying many Custom ROMs without any luck..
but some problem of noise sounds like sound of mouse while accessed internet or transmitted data was still unsolved
im using this one..E6553_32.3.A.0.372_R3D_Customized RU_1295-0592.ftf
all Nougat custom roms that i found cannot solved my undetected simcard was RR, and LA
now im going to put TWRP and root this one...
btw, i found that this Stock Rom made my Z3+ coolest that any Nougat Custom Roms, is so conform like never before
I had similar issue last week, turns out the cable was connected to the usb3 port on my laptop. once I plug it into usb2 port then it was fine.
Mazellat said:
Hi dear friends. I have a interesting problem with Flashtool and Sony's last OREO update.
I want to flash 41.3.A.2.58 with flashtool. If I use old version of flashtool v0.9.23.2, I can connect my phone flash mode, but I can't flash last oreo update from Sony I get "NULL" error.. If I use newest version of flashtool 0.9.24.2, The FW was preparing to flash but my phone doesn't connect with flash mode so this time I get this "ERROR - Device connected in flash mode but driver is too old". I installed driver which is in the folder of newest Flashtool.I didn't understand what I did wrong. I am using Flashtool many years but I can't solve this problem. Please check the pictures.
FLASHTOOL v0.9.23.2
FLASHTOOL v0.9.24.2
Click to expand...
Click to collapse
I have the same issue! ERROR - Device connected in flash mode but driver is too old.
Flashtool old drivers fix
I had the same problem with latest flashtool tool 0.9.24.4 but was fixed. Just go to Sony developer page and download and install Sony flash tool (emma), as simple as that and that error is gone
https://developers.sony.com/file/download/flash-tool-for-experia-devices/
Same problem (ERROR - Device connected in flash mode but driver is too old) with flashtool-0.9.24.2, I will try flashtool-0.9.24.4 today.
Thanks.
Hi, I had the same issue. I solved it by plugging into a USB 2.0 port instead of 3.0. I 'm not sure why but this is what works for me all the time. Hope it works for someone too.
Tonio78r said:
v9.24.2 is the latest version. You may update your drivers from C:\Flashtool\drivers\Flashtool-drivers.exe and select the correct drivers you need (capture in attachment).
Click to expand...
Click to collapse
Thank you so much for your great work:good::good:
This guide is for downgrading /Unbrick /Flash Stock Firmware Nokia 5.1 plus to Android Pie or Oreo.
This is STRICTLY for Global Nokia 5.1 plus variant NOT for Chinese variant Nokia X5. If you want to downgrade Chinese variant then follow this guide by hikari_calyx
Guide For Chinese Variant (X5).
What you need ::
1.MTK- Smart Phone Flashing tool which can be downloaded here. (v5.1804) Download
2.Android platform tools and ADB and fastboot drivers . Download
3. MTK Port drivers , For windows only. Download
4.FIRMWARE -
Oreo - PDA-1100-0-00WW-B01_unpacked.7z from . Download
Pie - PDA-214A-0-00WW-B01.full.zip from here . Download
STEP 1 : Backup your important files from internal storage and remove all google accounts from your phone to prevent FRP lock.
STEP 2 : Install all drivers and files mentioned above and extract your desired Firmware .
STEP 3 : Create a full backup using SP Flash tool (must do).
Open Smart Phone Flash Tool, choose the Download Agent file and Scatter File from the unpacked firmware.
DO NOT USE DOWNLOAD AGENT FROM THE FLASH TOOL ITSELF, USE ONLY THE ONE PROVIDED IN THE FIRMWARE.
Should look like this-
{
"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"
}
TROUBLESHOOTING.
If you get this error
Then go to options and disable "Check LIB DA Match".
Click to expand...
Click to collapse
Then move to "Readback" and tap on add and choose you location where you want save you backup after that you double click on the created readback section and you will see this :
Use any text editor to open the scatter file from extracted firmware , and find "userdata". You'll need the start address of userdata as the length of the full backup.
And change the length from the address you found under "userdata" in scatter file like this and tap ok.
Click on "Readback" and the connect you phone in flashing mode with both volume button pressed and release upon the readback process starts ( you can see it in the lower progress bar).
STEP 4 : Upon completion of the readback process , close SP Flash tool and unplug you phone and trigger it to fastboot mode and change your Active partition to "a" by this command.
Open cmd to use this command.
Code:
fastboot --set-active=a
After this process completes , power off you phone .
STEP 5 : Flashing your firmware.
Open SP Flash Tool and check that DA and Scatter is loaded from your extracted Firmware.
Choose "DOWNLOAD ONLY" mode , not any other or you will loose important partitions.
Then click on download and connect your phone in flashing mode by both volume button pressed and release upon the download process starts ( you can see it in the lower progress bar).
After its finished, it will show "Download OK" popup.
Now just close SP Flash tool , unplug you phone and reboot.
Enjoy your downgraded/ Unbricked Nokia 5.1+.
Special thanks to :
hikari_calyx for Firmware and solving all the errors.
Someone , Someone and Someone for testing this guide.
Hit Thanks if it worked for you.
Tested, guide works perfectly. Also, the given Android version in this guide is 9 (February SP) for those who want to know.
For some reason, the wifi doesn’t work for me, it just falls off and connects again (how to fix it?
Pelmewek said:
For some reason, the wifi doesn’t work for me, it just falls off and connects again (how to fix it?
Click to expand...
Click to collapse
Check your imei and baseband...is it there???
Readback not processing
Cant compltete the readback prccess what should i do?
xdriv3r said:
Cant compltete the readback prccess what should i do?
Click to expand...
Click to collapse
Which version of SP flash tool are you using ??
bx2_nero said:
Which version of SP flash tool are you using ??
Click to expand...
Click to collapse
I used the latest version. I'm going to try again with the recommended version. Thank you .
xdriv3r said:
I used the latest version. I'm going to try again with the recommended version. Thank you .
Click to expand...
Click to collapse
Use Sp flash tool version 5.1804 or 5.1824.
Read the instructions carefully ..
How to backup using sp flashtool?
How to backup using sp flashtool?
bx2_nero said:
Use Sp flash tool version 5.1804 or 5.1824.
Read the instructions carefully ..
Click to expand...
Click to collapse
xdriv3r said:
How to backup using sp flashtool?
Click to expand...
Click to collapse
You must backup your personal data and remove Google account before starting.
The readback process is the backup process in SP flash tool.
Android 10 firmware not available
bx2_nero said:
Pie-PDA-214A-0-00WW-B01.full.zip from here https://androidfilehost.com/?fid=1899786940962585502 (recommended if you are downgrading to root and install Androdi 10).
Click to expand...
Click to collapse
Alas, no mirror found:
mll2 said:
Alas, no mirror found:
Click to expand...
Click to collapse
https://tpedutw-my.sharepoint.com/:...dFks--5G6V4vYBGTwLw1BsthbtIuJqMUN3tQ?e=wOfytH
Try from here
Make sure you download the file mentioned.
PDA_214A_0_00WW_B01_full
bx2_nero said:
https://tpedutw-my.sharepoint.com/:...dFks--5G6V4vYBGTwLw1BsthbtIuJqMUN3tQ?e=wOfytH
Try from here
Make sure you download the file mentioned.
PDA_214A_0_00WW_B01_full
Click to expand...
Click to collapse
Thank you!
I tried downgrading from Android 10 Internal Beta and cannot skip the update screen on reboot. How to fix this?
xdriv3r said:
I tried downgrading from Android 10 Internal Beta and cannot skip the update screen on reboot. How to fix this?
Click to expand...
Click to collapse
Did you follow step 1 - remove Google account to prevent FRP Lock.
Try hard resetting, reset from recovery.
bx2_nero said:
Did you follow step 1 - remove Google account to prevent FRP Lock.
Try hard resetting, reset from recovery.
Click to expand...
Click to collapse
It's just one compulsary update. Around September 2019 sp. I'm good now. I thought I had hardbricked the device when I changed primary partition to b and got stuck in bootloop unable to go into recovery. Then I used volume down + power and usb to directly get into fastboot.
xdriv3r said:
It's just one compulsary update. Around September 2019 sp. I'm good now. I thought I had hardbricked the device when I changed primary partition to b and got stuck in bootloop unable to go into recovery. Then I used volume down + power and usb to directly get into fastboot.
Click to expand...
Click to collapse
Why did you changed your primary partition to B.
bx2_nero said:
Why did you changed your primary partition to B.
Click to expand...
Click to collapse
I'm noob.
xdriv3r said:
I'm noob.
Click to expand...
Click to collapse
Your phone is fine right now?
bx2_nero said:
Your phone is fine right now?
Click to expand...
Click to collapse
Yeah now on feb sp with mtksu and suboot.