Hi,
I tried for the very first time to use TWRP for Backup and Restore.
For a basic test I backuped the smartphone with TWRP to an SD card, made then a factory reset and after that I used TWRP again in order to restore the previous stored backup file.
The restore action finished without problems showing a positive result.
After that I selected the "Reboot" menu task of TWRP and tried to start a system boot. As a result the phone starts, the first boot screen pops up showing "SONY" and "XPERIA" on a white background.
Then the boot process stops and nothing more happens.
From that point I can switch off the phone using the "Volume up" and "Power on" button.
I can reenter to TWRP using the "Volume down" and "Power on" buttons.
Thats it.
The configuration is as follows:
- Sony Xperia Z5 compact (E5823/Suzuran) with Android 7.1.1
- TWRP_3.6.0_9-0-recovery_suzuran_2021-12-02.img
Any idea what's going wrong ?
Thanks for any help
Please take a look into the "Troubleshooting section", part "If you stuck in a bootloop...", in one of my threads, for example this one.
Berni-0815 said:
Please take a look into the "Troubleshooting section", part "If you stuck in a bootloop...", in one of my threads, for example this one.
Click to expand...
Click to collapse
Thanks for trying to help me.
Reading a lot of posts I don't find a solution.
Then I looked for a way to restore the original status.
I found the file E5823_32.4.A.1.54_R3E_Customized_CH-1298-7257.ftf.
But I don't find a guide to handle that file properly.
There are posts saying that TWRP can't be used to work with .ftf files.
But TWRP is the only way to work with in my situation.
So I'm lost for the moment.
Regards
FTF files can be handled by the flashtool. If you're using the windows version of this tool, you can easily find a matching FTF file too by using the integrated XPeriFirm tool ("X"-Button)
And in my mentioned help guide you can read how to grab a LOG file...
Berni-0815 said:
FTF files can be handled by the flashtool. If you're using the windows version of this tool, you can easily find a matching FTF file too by using the integrated XPeriFirm tool ("X"-Button)
And in my mentioned help guide you can read how to grab a LOG file...
Click to expand...
Click to collapse
Thank you for the info.
Finally I was able to download a Flashtool 0.9.34.0 installation file with correct SHA-256 hash.
But my antivirus software Bitdefender detected the virus "Trojan.Linux.GenericKD.42939878" in the file \.flashTool\devices\root\iovyroot\iovyroot.
There is a Xperia_Flash_Tool_Setup.exe from Sony called EMMA Version 22.1.1.202201111338.
Is this a proper alternative?
I was able to establish a connection between PC and phone using EMMA.
Then I stopped work at this point.
Regards
Disable antivirus or bypass this tool in your antivirus! There is no virus in it!
Don't use any other tool than flashtool.
Hi Bernie,
Now I'm able to handle Xperifirm v5.6.5 and Flashtool v0.9.34.0.
Both worked well. Thanks to you and a user "XB" who has provided a brief description how to use both tools in the document "Guide to installing Xperia Lollipop using XperiFirm
and Flashtool".
I flashed the phone and could then boot it like a new one.
This worked well a couple of times.
However, after flashing TWRP to the phone successfully, the original problem occurs again.
"
I tried to start a system boot. As a result the phone starts, the first boot screen pops up showing "SONY" and "XPERIA" on a white background.
Then the boot process stops and nothing more happens.
From that point I can switch off the phone using the "Volume up" and "Power on" button.
I can reenter to TWRP using the "Volume down" and "Power on" buttons.
Thats it.
"
I tested 3 different TWRP versions. TWRP is working. The result after rebooting the phone was the same. The problem remains.
Are there any ideas to overcome this?
Regards
Grab a LOG file. I can't help further without having a LOG file.
I assume you are talking about the flashtool log.
Please find the latest one from today
Regards
No. I like to have a system LOG (as described in "Troubleshooting" section "If you stuck in a bootloop..." in my 1st post; for example here).
Thank you for your patience.
I followed the procedure described in Troubleshooting section:
cd sys/fs/pstore
cp * /sdcard
but the directory "pstore" is empty, no files or directories.
I doublechecked if I'am in this directory and if there are hidden files.
Then I used TWPR V 3.6.0_9-0, >Advanced>Copy Log and was able to get 2 Log files.
No idea, if one of these files is the one you requested and can help to analyse the situation.
Regards
kefir567 said:
No idea, if one of these files is the one you requested
Click to expand...
Click to collapse
If you're fetching them with my mentioned procedure, both will help me. Please upload them to a filehoster of your choice and send me the link via PM as those LOG's may contain personal data, like call numbers etc. No worries, no password is readable in these LOG files!
Related
Updated - 6/2/14 - To reflect suggestions by - @blueether - @maxld - @polargirl - Thank you all.
This might help someone Noob like me.
This is primarily written for my C6806 however steps are similar for other z ultra devices.
Everything here is copied from other threads on this forums and Google search. I have tried to provide links to threads as much as I can.
For anyone following these steps
Please do more research on each steps.
This steps should give you clear idea as to what is involved in this procedure
You must follow steps from top to bottom for this to work.
Check Bootloader Status
Dial *#*#7378423#*#* or download this app from playstore to directly go to Service Info
Go To Service Info > Configuration > Rooting Status
If you see Bootloader Unlocked: Yes, that means your phone is bootloader unlocked
if you see Bootloader unlock allowed: Yes continue with steps.
if you see No above do not continue any further, STOP
Disable Signed Driver Enforcement on Windows 7, 8, 8.1 (This is a must step)
Reboot your computer while pressing F8
Select "Disable Driver Signature Enforcement" and press Enter
Install FlashTools and FlashTools Drivers
Download FlashTools from following link (You must use latest version)
http://www.flashtool.net/download.php
Install FlashTools
Go to Flashtool\drivers install Directory
Double Click Flashtool-drivers.exe
Select Flashmode, Flashboot, z ultra (all), xperia A and click Install
Flash 14.1.B.1.532 ftf file to phone (For locked or unlocked phones - Thanks @blueether)
Start Phone Normally
Go to Settings
Click ten times on Build Number to enable developer options
Go to Settings -> Developer options and enable USB Debugging
Go to Settings -> Security and enable install from unknown sources
Turn off phone
Download C6833_14.1.B.1.532_NUT.ftf File from this thread http://forum.xda-developers.com/showthread.php?t=2593918
or Download Directly from here http://forum.xda-developers.com/devdb/project/dl/?id=3442
Extract zip file downloaded above
Copy ftf to Flashtool\firmwares directory
Open FlashTool
Click Flash (lightning bolt icon)
Select FlashMode and click ok
Select the above file from left side and click flash
When Asked by FlashTool, keep holding vol down key connect phone to computer with usb cable
Disconnect phone (After FlashTool finish installing firmware file)
Restart phone
Root with Bin4ry method
Download Root_with_Restore_by_Bin4ry_v33 file from this thread http://forum.xda-developers.com/showthread.php?t=1886460 or direct link http://uploaded.net/file/d2w6dl7r
Follow this video for more detailed instructions https://www.youtube.com/watch?v=7EpkrCq1gfM#t=149 or continue with next step
Start Phone and enable usb debugging and install from unknown sources options.
Extract above Root_with_Restore_by_Bin4ry_v33.zip file to c:\ drive
Double Click the RunMe.bat and follow instructions
Select - Xperia phones with “older” firmware option when asked
Backup TA Partition
User this video for more help https://www.youtube.com/watch?v=kva9-rAPG5s
Download Latest Backup TA for Sony Xperia tool from this thread http://forum.xda-developers.com/showthread.php?t=2292598 or direct link https://github.com/DevShaft/Backup-TA/releases
Extract downloaded file to c:\
Start phone
Run Backup-TA.bat
Follow instructions on screen
After backup store entire Backup-TA directory at safe location for some future use
Flash 14.3.A.0.757
Download 14.3.A.0.757 file
For C6806
Download US Retail/Generic C6806 14.3.A.0.757 file from this link http://d-h.st/4vv
For other version of z Ultra
Go to this thread and download appropriate 14.3.A.0.757 ftf file http://forum.xda-developers.com/showthread.php?t=2453921&highlight=757
Extract this zip file
Copy C6806_14.3.A.0.757_1276-1569_R3C.ftf (for C6806) to Flashtool\firmwares directory
follow steps similar to “Flash 14.1.B.1.532 ftf file to phone”
Unlock Bootloader (Please read more before doing thess steps, I might have missed many things here)
Reference Post you would like to read, http://forum.xda-developers.com/showthread.php?t=2447319
Write down IMEI code for your device
dial *#06#
Write displayed IMEI and save it at safe place
FlashTool method to unlock bootloader
Start FlashTool
Click on BLU button
Connect phone in flashmode as per the instructions on screen
Once Connected click unlock
When prompted disconnect the device
ROOT 14.3.A.0.757
Instructions from Thread http://forum.xda-developers.com/showthread.php?t=2714511
This works for all c68xx devices with 14.3.A.0.757 firmware
Download kernal from this link
https://mega.co.nz/#!Vh8xEZYR!HwGosIRT1wFVCwm80KjL6vbo0NSduVlhUObM0NdNrPg
Download SuperSu from this link
https://mega.co.nz/#!t18y2SRb!WwXemirwFBTqpxeNYrJJLC1jwH7R13NQE-uU7yEBk2Y
Help video https://www.youtube.com/watch?v=uFSeSe8gQOY
Start Phone Normally
Copy Above SuperSu.zip to internal or external SD Card
Go to Settings
Click ten times on Build Number to enable developer options
Go to Settings -> Developer options and enable USB Debugging
Go to Settings -> Security and enable install from unknown sources
Turn off phone
Disconnect USB cable
Press and hold vol up button and connect USB cable to phone and PC, wait until led light turns blue
Start FlashTool
Click Flash (Lightning bolt)
Select Fastboot mode and click ok
Click Select kernel to Flash
On File chooser window change *.sin to *.img
Select above 757.img file and click ok
on FlashTool window if it says sending boot ok do not worry about any other errors
Disconnect USB cable
Go to Recovery
Press power button to start phone
As soon as you see sony logo press and hold vol down button
This will boot you into recovery
Click Install on Recovery screen
Select SuperSu.zip file uploaded earlier (from internal or external sd card)
Swipe to confirm
Click Reboot System
That is it finally you have your xperia z upgraded and rooted.
Corrections:
Move the unlock section to after the flash 757 section
.532 is the onlt firmware that has a root exploit, use the one that is linked in my downgrade thread, will work on all versions of the ZU locked and unlocked
Root with binaries tool - use option 0 or use [NUT]'s tool (see
my downgrade thread again)
That's it for now, will have a close read soon...
Thanks - @blueether -
Updated thread.
You can probably remove the section about the camera as that was a Z1 issue, not affecting the ZU
I am glad to at least see you guys trying to put everything into one thread.
This is still a huge amount of instructions for a newbie and any reduction would be great but at least having what you currently have put into one thread is still a major improvement.
Good going guys and thank you very much!
zxc1251 said:
Disable Signed Driver Enforcement on Windows 7, 8, 8.1 (This is a must step)
Hold down the Windows key on your keyboard and press the letter C
Click the gear icon (Settings)
Click More PC Settings
For Win 7 and 8
Click General
Under Advanced Startup, click Restart Now
For Win 8.1
Click Update & Revocery
Click Recovery
Under Advanced Startup, click Restart Now
After restart, click Troubleshoot
Click Advanced Options
Click Windows Startup Settings
Click Restart.
After restart, click F7 (to disable driver signature enforcement)
Click to expand...
Click to collapse
Would just shortening this to "Reboot while pressing F8 and selecting Disable Driver Signature Enforcement" work?
polargirl said:
Would just shortening this to reboot while pressing F8 and selecting 'Disable Driver Signature Enforcement" work?
Click to expand...
Click to collapse
Yep, it should do the trick
maxld said:
Yep, it should do the trick
Click to expand...
Click to collapse
Great! We got one process shortened.
I am neither a programmer nor a hacker but I will try to contribute what I can for a "Rooting Xperia For Dummies" guide.
The next suggestion is actually lengthier but may make a scared newbie feel more safe since it comes from the Google Play Store.
Instead of dialing code into the phone,
zxc1251 said:
Check Bootloader Status
Dial *#*#7378423#*#*
Click to expand...
Click to collapse
why not change that to download an app from the "safety" of the Google Play Store?
https://play.google.com/store/apps/details?id=com.neoscreenager.xperiaservicemenu
It appears to be a good app that works better than always dialing code for someone who plans to access the service menu regularly anyway.
Great guide!
Brilliant guide :good:, thanks for the hard work.
checkmateyou said:
Great guide!
Click to expand...
Click to collapse
It needs work but it is a start. I am hoping the OP returns and works on this some more. I also hope members of this site will contribute to helping on some of the processes.
polargirl said:
It needs work but it is a start. I am hoping the OP returns and works on this some more. I also hope members of this site will contribute to helping on some of the processes.
Click to expand...
Click to collapse
Or how about you stop criticizing everything and everyone around here, and start contributing yourself? You're not gaining in popularity around here right now.
LordManhattan said:
Or how about you stop criticizing everything and everyone around here, and start contributing yourself? You're not gaining in popularity around here right now.
Click to expand...
Click to collapse
I wasn't criticizing anyone in the post that you quoted. I was just explaining what I believe needs to be done.
I have posted in more than one thread that I don't have any tech skills to make contributions in that regard. The goal of simplifying and streamlining the root process for the public is going to take someone with developer skills that I simply do not have. I don't know the first thing about Linux and know nothing about writing Windows batch files. How much more humility regarding my tech skills do you want?
I get it. You guys are content with just doing rooting for yourselves and could care less about how OEMs mistreat their own customers let alone give empowerment back to the public or even stymie development to a degree that rivals Microsoft for that matter. If anything, I have seen more sympathy towards OEMs and patronization towards the public posted on this site.
I won't bother you guys any longer nor will I attempt rooting my phone with instructions on how to root and unroot all over the place in many threads with the lack of support being what it is on this site.
Have fun continuing to live in your own world indifferent to the rest of it. No wonder the rest of the world doesn't like nerds. At least I figured that one out after all these years so it wasn't a complete waste of time coming here.
polargirl said:
I wasn't criticizing anyone in the post that you quoted. I was just explaining what I believe needs to be done.
I have posted in more than one thread that I don't have any tech skills to make contributions in that regard. The goal of simplifying and streamlining the root process for the public is going to take someone with developer skills that I simply do not have. I don't know the first thing about Linux and know nothing about writing Windows batch files. How much more humility regarding my tech skills do you want?
I get it. You guys are content with just doing rooting for yourselves and could care less about how OEMs mistreat their own customers let alone give empowerment back to the public or even stymie development to a degree that rivals Microsoft for that matter. If anything, I have seen more sympathy towards OEMs and patronization towards the public posted on this site.
I won't bother you guys any longer nor will I attempt rooting my phone with instructions on how to root and unroot all over the place in many threads with the lack of support being what it is on this site.
Have fun continuing to live in your own world indifferent to the rest of it. No wonder the rest of the world doesn't like nerds. At least I figured that one out after all these years so it wasn't a complete waste of time coming here.
Click to expand...
Click to collapse
meh
Lordmanhattan and I, and a couple of others that dont post so much now have put hundreds of hours in to help others, bring all the info into a couple of threads.
If someone has a problem with the process and has not just "how do I root my ZU" we (the general users of this section) will go out of our way to help.
I feel that having all the info in one post if counter productive, it becomes too much to read, too easy to lose you way - foss mantra: small tools to do small jobs => small guides to do small steps
The process is not that difficult, but there are many permutations of what the user is starting with and what they want to end up with.
Again: If they ask an intelligent question in the guide threads they will get a concise answer, if they open a new thread with the same question that has been answered 100 times before they will get a shot answer that they may not like.
The process is not overly broken, people just need to be less self entitled, not everything in life is as simple as they are
Could not enter Recovery after flashing 757 kernel
Thanks for your helpful post.
I just have a problem at step 25 (Go to Recovery) under ROOT 14.3.A.0.757. Everything was fine until I attempted to enter Recovery mode to install SuperSU. After flashing the 757.img kernel, I disconnected the cable, pressed power button, and hold volume down (I also tried volume up) button when the Sony logo appeared on the screen. But my phone just kept booting to Home Screen.
I was wondering if anyone had had the same problem? If so, please help me to fix this.
Thank you in advance.
Update: I managed to enter Recovery mode by pressing both volume up and volume down after pressing the power button. Everything is fine now. Thanks again for a very clear and complete step-by-step guide for a Noob like me.
tennispirit said:
Thanks for your helpful post.
I just have a problem at step 25 (Go to Recovery) under ROOT 14.3.A.0.757. Everything was fine until I attempted to enter Recovery mode to install SuperSU. After flashing the 757.img kernel, I disconnected the cable, pressed power button, and hold volume down (I also tried volume up) button when the Sony logo appeared on the screen. But my phone just kept booting to Home Screen.
I was wondering if anyone had had the same problem? If so, please help me to fix this.
Thank you in advance.
Update: I managed to enter Recovery mode by pressing both volume up and volume down after pressing the power button. Everything is fine now. Thanks again for a very clear and complete step-by-step guide for a Noob like me.
Click to expand...
Click to collapse
You're not supposed to hold the volume button up/down, but you should simply press it once or twice when the LED lights up above the screen
Hi, I am trying to flash my phone following the steps for Flash 14.1.B.1.532 ftf file to phone. Once I get to step 13 I have a problem. I am using Flashtool to flash the ftf file in flash mode but there are no files to select from. I have already placed the ftf file in the firmware folder.
PS:the flashtool is version v0.9.16.1. Has anyone experienced this problem?
LazyJr said:
Hi, I am trying to flash my phone following the steps for Flash 14.1.B.1.532 ftf file to phone. Once I get to step 13 I have a problem. I am using Flashtool to flash the ftf file in flash mode but there are no files to select from. I have already placed the ftf file in the firmware folder.
PS:the flashtool is version v0.9.16.1. Has anyone experienced this problem?
Click to expand...
Click to collapse
You nolonger have to flash to 532 to root the ZU have a read of the Towelroot thread
blueether said:
You nolonger have to flash to 532 to root the ZU have a read of the Towelroot thread
Click to expand...
Click to collapse
Hi blueether. Thank you for your link. I would like to ask you a question. My ZU firmware version is .290. Should I update to 757 then downgrade to 532, root and back-up the TA partition. Or should I just upgrade from .290 to 532, root and back-up the TA partition. Which do you think is the best way? Thank you.
LazyJr said:
Hi blueether. Thank you for your link. I would like to ask you a question. My ZU firmware version is .290. Should I update to 757 then downgrade to 532, root and back-up the TA partition. Or should I just upgrade from .290 to 532, root and back-up the TA partition. Which do you think is the best way? Thank you.
Click to expand...
Click to collapse
for a start 532 (4.2) is older than 290 (4.3)
@ OP This is the porblem with yet another guide thread about rooting the ZU...
As of 4 or 5 days ago you dont have to down grade at all. With the thread I linked to you can root any of the current Sony firmware I think (untested, but 767 will root).
I would:
upgrade to the latest 4.4.2, Sony's x.x.x.767 FTF
root with the tools linked to in that thread
back up TA
unlock BL if wanted/needed
Hello. I've tried using multiple ROMs in my rooted phone with KDZ Updater, and I guess that one of the updates hanged, or maybe it was something else... I really don't know. What I do know is that my phone currently isn't able to enter recovery mode, and is also not showing any boot logos (neither 'LG' nor 'Android').
I did see some threads about this, one of them talking about starting in Download Mode and using KDZ in CS_Emergency mode with some French ROM. Well, I tried that and as soon as I press "Launch software upgrade" the program freezes until I plug my phone off the PC.
I feel as if something was stuck in my throat and the only way to get it out is by completing this... so any help will be greatly appreciated!
PS: All this happened in the process of trying to install Cyanogen Mod 10.1 (which I did not try yet).
http://forum.xda-developers.com/showthread.php?t=1119531
Need to make sure to get the right firmware, DLL file, and make sure you have the right port set on the program.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=1119531
Need to make sure to get the right firmware, DLL file, and make sure you have the right port set on the program.
Click to expand...
Click to collapse
Thanks for the reply!
I appreciate the info, and I'll be checking what you've said. All the links in that thread are inaccessible because Fileserve only lets you download what you upload. Anyway, I'm curious as to what this "DLL" file does on a smartphone... why do I need these things? I never heard of them being mentioned anywhere.
I'll start educating myself ASAP. Meanwhile, thank you very much (and by the way, if it's of help to anyone, my phone is a GT540g from Personal, Argentina.
You're welcome. Sorry, didn't check to see if the files were still there and most every other site just had reposts of the fileserve links. However, finally found what you need here:
http://files-gsm.ru/lg flesh/GT540gAT-00-V20a-722-34-DEC-28-2010+0.dz.zip
I found this dll for your phone but not sure if it works with the firmware you have for that version:
http://www.mediafire.com/download/9v9e78xronadm0c/GT540g_100506_MP.dll
"A dynamic-link library (DLL) file is an executable file that allows programs to share code and other resources necessary to perform particular tasks..."
Basically it ties together a few things in Windows to let the flash tool work for your specific device is my understanding. But they have to be specific to the phone or it won't run once it checks the build.prop of the phone vs the firmware you're trying to install.
Keep in mind, I do not have this phone and have no way to test if they will or won't work so just like any other mod or upgrade - you do so at your own risk.
Thanks, but...
First of all, I'm very sorry not to have replied before, but I've been busy. Anyway!
Thanks, I appreciate the links, but I don't understand where to put the .dll file in my phone. I know you'd think I'm an idiot who doesn't know how to use Google, but I actually did search beforehand. I simply don't get where to put it.
Also, if it's worth the shot, I just noticed that I should disable the "Modem" that activates when I plug my phone in. The problem is, KDZ just does this simple log [attached] and states "===FINISHED===" (Note that I have 2 Modems listed in my device manager [attached screenshot])
Solution GT540
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
Why does Android allow 'tinkerers' like me to tinker?? A little knowledge can be dangerous thing.
Hi.
Ok, so, I've gone and buggered it (I think but certainly hope not).
My new Z2 that I LOVE got some water in it last week. The phone continued to work but somewhat erratically, not responding to the touch screen etc etc. After leaving it for a few days on the window ledge, all signs of water ingress had disappeared and it worked ok. I’m sure the relevance of the water is only that it started me thinking…….maybe its knackered, so starting to ‘play’ isn’t a bad thing. I really doubt the water is an issue here.
Here's where the tinkering starts. I have a N5 which has been on Android L prev for months now and loaded the final build last week. It’s great, but hey, that's for the N5 group i guess.
The point of sharing that is.......even as a complete novice, I have flashed, re flashed and returned to stock my N5 many times and thus I thought......how hard can it be?
In an effort to flash a new Rom (CM11) to the Z2 I have buggered it. So in an effort to be as comprehensive as poss....please don’t ask 'why' to any of this because, to be frank, I'm not sure.........
1. I unlocked the phone (bootloader??) via the Sony website process....request code, get token etc etc........all good
2. I flashed CM11 and 'eventually' got it working. I say eventually because my ADHD means that I (perhaps) wasn’t as diligent with following instructions and it took a couple of attempts. Nonetheless it was working.
3. I saw (the next day) that 4.4.4 was available for Z2 and in conjunction with the camera features that I was missing, I thought I'd flash back to stock to see if 4.4.4 was acceptable. That’s where the fun starts.
4. Through either
a. not following instructions,
b. doing something wrong or
c. just bad luck…..the phone is now (nearly) dead. I say nearly because......
5. When you boot it up, it will.....
a. After ~2sec press on pwr, it will vibrate and show the Sony Xperia screen
b. After ~6 secs the Sony screen disappears and a screen with the following message appears….
“The software update failed. Make sure that your phone is connected to a computer and try again”.
That message is accompanied by a kind of (I guess) Ying Yang type graphic and a warning triangle.c. Then the screen goes off. I assume the phone actually goes off because the only way to revive it is to go back to the pwr button.
6. If I follow the instructions for flashmode, once I connect a cable whilst holding down the ‘vol down’ rocker, the LED flashes red momentarily and then (I’m sure) flashes instantaneously to green before going out and the phone is then dead. I say I’m sure because its so bloody quick its almost indeterminable.
7. If I follow the instructions for fastboot, once I connect a cable whilst holding down the ‘vol up’ rocker, the LED flashes red momentarily and then flashes to blue, at which point it stays blue.
I’ve tried many different threads, tutorials etc and can’t get out of this jam.
a)In flashtool, the phone is simply not recognised.
b) In Emma, the phone is obviously ‘seen’ as I get a message telling me that the phone is locked. Eh? WTF?? How is that??
c) In flash tool, when I try to BLU….I get……
07/014/2014 13:14:27 - ERROR - (Bundle.java:443) - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
d) In flash tool, when I try to flash using the fastboot toolbox (using the reboot via ADB) option….I get……
07/014/2014 13:14:44 - ERROR - (FastBootToolBoxJob.java:74) - This action needs a connected device in ADB mode
e) In flash tool, when I try to flash using the fastboot toolbox (using the reboot via Fastboot) option….I can hear the notifications from my PC that it has rebooted and the blue LED comes back on but that’s it. When I select Kernel to flash……..I haven’t got one (I don’t think).So…..devs…can you help?
I’ve tried to be as comprehensive as poss in my description and If I’m missing something, please point out the error of my ways.
I sooo want my Z2 back and promise I wont tinker again (until next time of course).
Much appreciation in advance of suggestions.
Cheers
Thommo.
In reading (and re-reading this) I wonder if ive answered myself……no kernel (whatever the feck that is)??? If that is the case….which one to flash and how??
I understand the kernel can be mismatched to a ROM and thus f**k things up??
(Edit) Also, I understand you cant flash a kernel without an unlocked bootloader???
I'd like to shed a little light on your situation. Maybe it will help you along.
I am assuming you have a program like Flashtool available and a FTF file of a relevant Sony firmware for your Z2.
The key issue seems to be a little confusion about flash mode and fastboot. On my Xperia Z, I always get a red light and then the LED momentarily flashes the colour green or blue depending on which mode I am entering.
So you shouldn't be alarmed by what your phone is doing.
The key is whether when you connect your phone in flash mode, does Flashtool continue the process and notify you in its log window that it is going through the flashing process?
This may require a little more patience as I believe your issue may just be that you don't think anything is happening when actually something is.
The kernel issue won't apply if you are using a stock FTF Sony firmware. The only consideration is to tick the option "exclude: TA" when you flash. The kernel and software will be included and automatically installed if there is no further underlying issue.
Some attention to detail is necessary and I hope this helps you out.
Good luck!
Sent from my C6603 using XDA Free mobile app
shorinryu said:
I'd like to shed a little light on your situation. Maybe it will help you along.
I am assuming you have a program like Flashtool available and a FTF file of a relevant Sony firmware for your Z2.
Click to expand...
Click to collapse
Yes.
shorinryu said:
The key issue seems to be a little confusion about flash mode and fastboot. On my Xperia Z, I always get a red light and then the LED momentarily flashes the colour green or blue depending on which mode I am entering.
So you shouldn't be alarmed by what your phone is doing.
Click to expand...
Click to collapse
The phone does seem to respond to flashtool commands but im not sure (maybe confused now) as to what to do in what order?
shorinryu said:
The key is whether when you connect your phone in flash mode, does Flashtool continue the process and notify you in its log window that it is going through the flashing process?
This may require a little more patience as I believe your issue may just be that you don't think anything is happening when actually something is.
Click to expand...
Click to collapse
Hey......thanks for helpimg.
I just tried again and yes its responding (i.e. booting using the flashttolbox etc but wont go any further. On the fastboot mode option, it asks what system to flash...when i take that route its now looking for a .sin file but i don't have any only ftf files??
I feel like im close but cant bloody fathom what im doing wrong. I wish someone could draw a picture.
Next suggestion?
Cheers
Thommo
http://forum.xda-developers.com/showthread.php?p=53220435
Here is a recovery guide
This guide should provide all the steps neccisary to recover a bricked device
So......i tried the BLU facility.
It appears the phone is going into flashmode as the waiting for device dialogue dissappears after i follow the instructions (pwr button down etc).
this is the log...
07/026/2014 14:26:39 - ERROR - (X10flash.java:255) - Processing of loader.sin finished with errors.
07/026/2014 14:26:39 - ERROR - (GetULCodeJob.java:137) - Error in processHeader : 6 : The handle is invalid.
Is there a clue on the X10Flash error??
there was (and still is) a X10_V1BLRelock.ftf file in the firmwares folder.
Ha66is said:
So......i tried the BLU facility.
It appears the phone is going into flashmode as the waiting for device dialogue dissappears after i follow the instructions (pwr button down etc).
this is the log...
07/026/2014 14:26:39 - ERROR - (X10flash.java:255) - Processing of loader.sin finished with errors.
07/026/2014 14:26:39 - ERROR - (GetULCodeJob.java:137) - Error in processHeader : 6 : The handle is invalid.
Is there a clue on the X10Flash error??
there was (and still is) a X10_V1BLRelock.ftf file in the firmwares folder.
Click to expand...
Click to collapse
Dear Brother, you're trying to flash a Sony Ericsson Xperia X10 FTF file to a Sony Xperia Z2. Please don't do that. Be aware of the things you're doing, look and read carefully. Raise your awareness.
Obtain a Sony Xperia Z2 4.4.4 FTF file on the internet and flash it. Ignore that X10 FTF.
V4LKyR said:
Dear Brother, you're trying to flash a Sony Ericsson Xperia X10 FTF file to a Sony Xperia Z2. Please don't do that. Be aware of the things you're doing, look and read carefully.
Click to expand...
Click to collapse
Actually.......Im not.........to prove a point, i deleted the X10 ftf from the firmwares folder, uninstalled Flashtool and re-installed. After re-installing the X10 FTF is back in there along with a X10 folder (X10 flasher.lib).
Ha66is said:
Actually.......Im not.........to prove a point, i deleted the X10 ftf from the firmwares folder, uninstalled Flashtool and re-installed. After re-installing the X10 FTF is back in there along with a X10 folder (X10 flasher.lib).
Click to expand...
Click to collapse
I'm sorry but V4LKyR is right, you were trying to flash the X10 bootloader relock ftf file. Please download an ftf (look in the general section for the Z2) and flash that instead.
The X10 bootloader relock ftf and the X10 folder always get installed when installing flashtool. The X10 is a completely different phone from the Z2.
So, I tried using flashtool for the first time today with my xperia z3v (verizon version). I wanted to update it to the fairly recently leaked lollipop rom (verizon is still on kitkat).
Anyways, I think what happened is that I forgot to turn on usb debugging before flashing the FTF. And now my phone is stuck saying: "the software update failed. Make sure that your phone is connected to the computer and try again."
I've tried reflashing multiple times to no avail. I've tried factory resetting by holding the volume down and power button but that won't work. And Sony PC companion won't pick up the device at all either. Can anyone help me get my phone working again? Maybe I should try flashing a different version? I've been googling for the last 4 hours trying to solve this so any input would be greatly appreciated!!
**EDIT: Nevermind I figured it out here is what I did when I had trouble with flashtool:
Quote:
Originally Posted by fixmewireless
I tired update Z3v with Flashtool to latest version and phone got soft bricked. I downloaded ftr file from server and flashed with flashtool. flashing process went thru, but phone shows message "software update failed".
Only error message I had during flash is ERROR - Error parsing TA file. Skipping
I noticed that flashtool does not have fsc preinstalled for D6708 (z3v). Did that cause the problem?
Can anybody upload fsc for z3v?
thanks
I actually ran into this same exact problem. After I had it soft bricked as you stated, I opened back up flash tool and when to set up the flash, and inside the flashtool I checked every box under Wipe, Also check all boxes under Exclude, EXCEPT SYSTEM. Leave SYSTEM un checked! Check everything under MiscTA Exclude too. I Then ran Flash and let it do its thing until it prompt me to plug in device into flashmode. It the ran the flash successfully and rebooted my device. I then followed the rest of the steps from page one and was able to root the device with no problems. Hope this helps!
If you hold volume down, and plug the usb into the pc, does the updating message appear?
zackdadams said:
If you hold volume down, and plug the usb into the pc, does the updating message appear?
Click to expand...
Click to collapse
Yes it does. So I am able to attempt re-flashing it at least but so far haven't gotten anywhere. Why?
actionjaxon77 said:
Yes it does. So I am able to attempt re-flashing it at least but so far haven't gotten anywhere. Why?
Click to expand...
Click to collapse
It's cusrious you are geting the error parsing TA file. You have a verizon phone so you must be bootloader locked. Were you roted before? Maybe just corrupt FTF file, try downloading it again or try to convert the SIN files to ext4 within flashtool and see if you can read everything correctly with ext4explore.
Sounds to me you soft bricked the phone, which is what I and others also experienced when attempting to flash.
I simply started up flashtool again, loaded the leaked lollipop ftf, and when asked, get back to the "updating" screen on the phone.
The phone should flash correctly.
Like mentioned above, try downloading the ftf again, or download the stock/shipped ftf.
http://forum.xda-developers.com/z3/xperia-z3v-general/guide-sony-xperia-z3v-t3100402
He mentions "1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download..."
That's the shipped version ftf.
The leaked Lollipop ftf link was down, so I used this one:
http://www.androidvillaz.com/2015/09/verizon-sony-xperia-z3v-d6708-android.html
zackdadams said:
Sounds to me you soft bricked the phone, which is what I and others also experienced when attempting to flash.
I simply started up flashtool again, loaded the leaked lollipop ftf, and when asked, get back to the "updating" screen on the phone.
The phone should flash correctly.
Like mentioned above, try downloading the ftf again, or download the stock/shipped ftf.
http://forum.xda-developers.com/z3/xperia-z3v-general/guide-sony-xperia-z3v-t3100402
He mentions "1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download..."
That's the shipped version ftf.
The leaked Lollipop ftf link was down, so I used this one:
http://www.androidvillaz.com/2015/09/verizon-sony-xperia-z3v-d6708-android.html
Click to expand...
Click to collapse
Thanks for the help, I was able to successfully flash it using the info I pasted in my edit to the original post!
I'm new to this forum and I hope to get some help from the community...
Device:
Sony Xperia Z Ultra (C6833), Android 5.1.1 (Lollipop) rooted, Built: 14.6.A.1.236 , Developer's mode & USB-Debugging enabled
Problem:
After updating SuperSU to 2.82 I had a bootloop. Did shutdown using small red button, restarted using recobery mode of TRWP (2.8.7.0) and did factory reset. Everything works again (WLAN, Apps, SD card access) but except the SIM card which is not recognized. IMEI not shown "About the phone", but correctly shown in diagnosis tool
Already tried:
- SuperSU 2.82 installed manually via TWRP. Works.
- Restored a full backup Sony PC-Companion, no success. Same with a Snappea backup.
- SIM proofed with different cell phone, works
- Other working SIM card tried with this phone, no success
- I blew a couple of times into the SIM card slot, no success
- Flashed the full ROM (14.6.A.1.236, rooted), no success
- Tried another factory reset, no success
I guess, there is a problem with the modem driver for the SIM card reader. Any ideas how to fix this?
I'm a newby to root & stuff but I'm hoping, that somebody could help me. I'm very thankful for any hints!
Greetings from Germany!
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
http://www.flashtool.net/downloads.php
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
SUPERUSER said:
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
http://www.flashtool.net/downloads.php
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
Click to expand...
Click to collapse
Hi @SUPERUSER can you please look int this thread and advise ... i am freaking out due to this
https://forum.xda-developers.com/xp...ev-plz-help-m-options-modem-baseband-t3623391
rgds
SUPERUSER said:
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
...URL...
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
Click to expand...
Click to collapse
Hi SUPERUSER, thanks for your quick reply!
It can't be the SIM card itself, since it works with my other phone. Also tried my GFs SIM in the C6833, also failed. Should be a ROM problem.
Tried to go back to SuperSU 2.79, 'cause that's how this mess all started (updating SuperSU), have the bootloop again, went back to 2.82. Works fine except the undetected SIM card.
Also tried 2 (probably dirty) modem fixes, this caused also loose of IMEI. Went back to my full backup using TWRP, where everything works (IMEI ok) except SIM card problem.
Just installed the flashtool, but it says, that the bootloader is locked. Unlocking it officially thru Sony website (developer.. sonymobile..com/unlockbootloader) requires installing full Android Suite (1.9GB) and further driver installtion using SDK manager. Is this the only way to use the flashtool? Other question regarding the Flashtool: Tutorials say: Copy ftf-File into the "firmware" folder, but there is no folder with this name. I checked the entire flashtool folder tree.
Isn't it possible to flash ROM in zip-format only using TWRP? Should I give DualRecovery a try too?
Thanks a lot! Appreciate your help!
ac845 said:
Hi SUPERUSER, thanks for your quick reply!
It can't be the SIM card itself, since it works with my other phone. Also tried my GFs SIM in the C6833, also failed. Should be a ROM problem.
Tried to go back to SuperSU 2.79, 'cause that's how this mess all started (updating SuperSU), have the bootloop again, went back to 2.82. Works fine except the undetected SIM card.
Also tried 2 (probably dirty) modem fixes, this caused also loose of IMEI. Went back to my full backup using TWRP, where everything works (IMEI ok) except SIM card problem.
Just installed the flashtool, but it says, that the bootloader is locked. Unlocking it officially thru Sony website (developer.. sonymobile..com/unlockbootloader) requires installing full Android Suite (1.9GB) and further driver installtion using SDK manager. Is this the only way to use the flashtool? Other question regarding the Flashtool: Tutorials say: Copy ftf-File into the "firmware" folder, but there is no folder with this name. I checked the entire flashtool folder tree.
Isn't it possible to flash ROM in zip-format only using TWRP? Should I give DualRecovery a try too?
Thanks a lot! Appreciate your help!
Click to expand...
Click to collapse
Whats causing your problem is probably that your bootloader is locked.
But I'm not getting how you use twrp and flashing files if the bootloader is locked?
You can flash stock roms with locked bootloader. It dont require to unlock it.
You don't need to download the whole SDK for just using fastboot.
If you need fastboot you can download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2588979
After install choose the right driver for your togari in device manager to "Android bootloader interface"
SUPERUSER said:
Whats causing your problem is probably that your bootloader is locked.
But I'm not getting how you use twrp and flashing files if the bootloader is locked?
You can flash stock roms with locked bootloader. It dont require to unlock it.
You don't need to download the whole SDK for just using fastboot.
If you need fastboot you can download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2588979
After install choose the right driver for your togari in device manager to "Android bootloader interface"
Click to expand...
Click to collapse
Thanks again!
Fastboot sucessfully installed using your link, but I have a driver problem. The device works fine connected to the pc using Sony PC Companion oder Snappea. Do I need a different driver for running fastboot? Found "S1Boot Fastboot" in "Devices and printers" on my pc and I'm aware that the correct driver has to be installed manually, just don't know where to get it. Google didn't help much, I'm only found a zip on Sony web, which probably does not contain the one file I need for running fastboot.... Any hints?
ac845 said:
Thanks again!
Fastboot sucessfully installed using your link, but I have a driver problem. The device works fine connected to the pc using Sony PC Companion oder Snappea. Do I need a different driver for running fastboot? Found "S1Boot Fastboot" in "Devices and printers" on my pc and I'm aware that the correct driver has to be installed manually, just don't know where to get it. Google didn't help much, I'm only found a zip on Sony web, which probably does not contain the one file I need for running fastboot.... Any hints?
Click to expand...
Click to collapse
PC companion is screwing you over because it has its own signed drivers. Perhaps these are proprietary and don't work with universal fastboot.
If you installed the 15 seconds ADB Installer v1.4.3 from the thread I linked AND installed the google driver when you were asked if you wanted.
Connect your phone in fastboot. Then choose the driver manually from a list. Scroll down to "Android Device" and select "Android Bootloader Interface"
You will get a warning that the driver might not work. Click yes and soon the device will be found and your phone will respond to fastboot commands.
If you need all drivers for example the flashmode driver you can download and install flashtool.
Then you get a folder with a driver pack in C:\Flashtool\drivers. The executable contains all the drivers to every xperia device.
Edit:
If you ever need the driver pack from flashtool I uploaded it to mega:
https://mega.nz/#!BdIlEIAQ!QQyFnhLYBZjMwe-rkfWmyVagMg9GL5qr7zwPuBKSjQw
SUPERUSER said:
PC companion is screwing you over because it has its own signed drivers. Perhaps these are proprietary and don't work with universal fastboot.
If you installed the 15 seconds ADB Installer v1.4.3 from the thread I linked AND installed the google driver when you were asked if you wanted.
Connect your phone in fastboot. Then choose the driver manually from a list. Scroll down to "Android Device" and select "Android Bootloader Interface"
You will get a warning that the driver might not work. Click yes and soon the device will be found and your phone will respond to fastboot commands.
If you need all drivers for example the flashmode driver you can download and install flashtool.
Then you get a folder with a driver pack in C:\Flashtool\drivers. The executable contains all the drivers to every xperia device.
Edit:
If you ever need the driver pack from flashtool I uploaded it to mega:
https://mega.nz/#!BdIlEIAQ!QQyFnhLYBZjMwe-rkfWmyVagMg9GL5qr7zwPuBKSjQw
Click to expand...
Click to collapse
Cheers! Couple of steps further! Drivers installed, fastboot detects the device now, I unlocked the bootloader successfully using fastboot. Device now recognized by the Flashtool too.
How to flash the custom ROM now? Better using fastboot or the Flashtool? I'd prefer the flashtool due to my limited cmd experiences. But I don't know how to select the FTF-file, which I already downloaded.
Don't know how to add screenshots here directly, so I added 2 attechments: Flashtool Main Screen and Folder sctructure of Emma. There is no "firmware" folder where I can drop the FTF-file to.
If using fastboot, ftf-file won't work, right? Zip-Files only?
How to proceed? Cheers, again!
ac845 said:
Cheers! Couple of steps further! Drivers installed, fastboot detects the device now, I unlocked the bootloader successfully using fastboot. Device now recognized by the Flashtool too.
How to flash the custom ROM now? Better using fastboot or the Flashtool? I'd prefer the flashtool due to my limited cmd experiences. But I don't know how to select the FTF-file, which I already downloaded.
Don't know how to add screenshots here directly, so I added 2 attechments: Flashtool Main Screen and Folder sctructure of Emma. There is no "firmware" folder where I can drop the FTF-file to.
If using fastboot, ftf-file won't work, right? Zip-Files only?
How to proceed? Cheers, again!
Click to expand...
Click to collapse
You downloaded the SONY EMMA flashtool. Not the one we need.
The name is a bit confusing because they are called the same.
The flashtool we need is this one. Download it via torrent its the fastest way.
http://www.flashtool.net/downloads.php
Uninstall Emma and install this flashtool.
...time for some ugly doodling
When you are done installing flashtool and are met with the UI you will see a main window as in image one. Press this button on the far right with the XF logo.
A new window will open with the name XperiFirm as in image two. Scroll down the list on the far left until you see the Togari.
Select your device. In my case I have the C6833. Now go to the list in in the middle. Click the "check all" button to fetch all updates.
When this is finished you will see a the latest "version number" on every "operator" in the collumn to the right.
Click the stock rom you would like to download in the list that correspond to where you live.
I always download customized DE because it includes the region I live in. Now look at the list to the right.
A list will appear under the "Available Firmware:". Click on the one you want to download. In this case there is only one entry.
Almost all older stock rom has been removed lately so it is very rare that you will find any old based on jelly bean or kitkat.
Anyway. When you click the one you want to download a new window will open as shown in image three
You will see some info. Double check the name is the one you want to download. If its right. Click download and make a coup of coffee.
When the download is finished you can close the window and let flashtool do its job. When its done.
You can see it in the log when it says its finished.
Now you want to press the button all the way to the left. That thunderbolt icon as shown in image four
A new window will open. Select flashmode and press ok as shown in image five
A new window will open and here you can see a list of which stock roms you have downloaded as shown in image six
Select the one you want to flash and look to the right in the "Exclude:" box. Make sure nothing is ticked.
And press flash when you are ready. And follow the instructions following by flashtool when it is ready.
Optional
If your phone is not detected in flashmode you need to install S1 - flashmode driver. You can do so by follow these steps.
Go to this folder as shown here in image seven
Execute the file as shown here in image eight
Select Flashmode Drivers as shown in image nine You don't need to select fastboot drivers. Because you already have this working.
If you want you can scroll down and select Xperia Z Ultra drivers as shown in image ten however this seems to fail in Windows due to driver signature verification.
Its not necessary to select it. Click install and hopefully the device will be seen when connected in flashmode.
For zip files. What you find here on the forum. You flash these in recovery. Not very difficult. You can find loads of guide on how to get started learning how to use recovery mode.
.img files. You flash via fastboot with cmd. Not very difficult either. Key tip here is to don't make typos or you need to rewrite the whole command again..which get boring fast.
SUPERUSER said:
You downloaded the SONY EMMA flashtool. Not the one we need.
The name is a bit confusing because they are called the same.
The flashtool we need is this one. Download it via torrent its the fastest way.
http://www.flashtool.net/downloads.php
Uninstall Emma and install this flashtool.
...time for some ugly doodling
When you are done installing flashtool and are met with the UI you will see a main window as in image one. Press this button on the far right with the XF logo.
A new window will open with the name XperiFirm as in image two. Scroll down the list on the far left until you see the Togari.
Select your device. In my case I have the C6833. Now go to the list in in the middle. Click the "check all" button to fetch all updates.
When this is finished you will see a the latest "version number" on every "operator" in the collumn to the right.
Click the stock rom you would like to download in the list that correspond to where you live.
I always download customized DE because it includes the region I live in. Now look at the list to the right.
A list will appear under the "Available Firmware:". Click on the one you want to download. In this case there is only one entry.
Almost all older stock rom has been removed lately so it is very rare that you will find any old based on jelly bean or kitkat.
Anyway. When you click the one you want to download a new window will open as shown in image three
You will see some info. Double check the name is the one you want to download. If its right. Click download and make a coup of coffee.
When the download is finished you can close the window and let flashtool do its job. When its done.
You can see it in the log when it says its finished.
Now you want to press the button all the way to the left. That thunderbolt icon as shown in image four
A new window will open. Select flashmode and press ok as shown in image five
A new window will open and here you can see a list of which stock roms you have downloaded as shown in image six
Select the one you want to flash and look to the right in the "Exclude:" box. Make sure nothing is ticked.
And press flash when you are ready. And follow the instructions following by flashtool when it is ready.
Optional
If your phone is not detected in flashmode you need to install S1 - flashmode driver. You can do so by follow these steps.
Go to this folder as shown here in image seven
Execute the file as shown here in image eight
Select Flashmode Drivers as shown in image nine You don't need to select fastboot drivers. Because you already have this working.
If you want you can scroll down and select Xperia Z Ultra drivers as shown in image ten however this seems to fail in Windows due to driver signature verification.
Its not necessary to select it. Click install and hopefully the device will be seen when connected in flashmode.
For zip files. What you find here on the forum. You flash these in recovery. Not very difficult. You can find loads of guide on how to get started learning how to use recovery mode.
.img files. You flash via fastboot with cmd. Not very difficult either. Key tip here is to don't make typos or you need to rewrite the whole command again..which get boring fast.
Click to expand...
Click to collapse
Followed all your instructions. Custom ROM flash with (the correct) Flashtool was succesful. Now comes the hopefully magic moment, where I'm gonna reboot and see if SIM card will be detected....
ac845 said:
Followed all your instructions. Custom ROM flash (C6833_14.6.A.1.236_Customized_DE.ftf) with (the correct) Flashtool was succesful. Now comes the hopefully magic moment, where I'm gonna reboot and see if SIM card will be detected....
Click to expand...
Click to collapse
SIM card NOT detected. I'm freakin' out!
Again tried the SIM card in 2 other phones, no problems. Tray and contacts shouldn't be the problem either, because I didn't to anything with SIM card and tray when the problem came up first after the stupid update of SuperSU and the following bootloop. Just pressed the tiny red panic button to shut down and went into recovery mode.
Just tried to use some thin folie between the tray and the SIM card in order to have some more pressure between SIM card and the contacts, failed.
Is it technically possible that a full custom ROM flash (with no ticked exceptions) still not formated the probably damaged SIM card modem portion/driver?
User pintspin has the same problem as above and he is much more into the topic than I am.
Still any hints? Wanted to avoid buying a new smartphone, still love the Ultra C6833 and its large screen...
ac845 said:
SIM card NOT detected. I'm freakin' out!
Again tried the SIM card in 2 other phones, no problems. Tray and contacts shouldn't be the problem either, because I didn't to anything with SIM card and tray when the problem came up first after the stupid update of SuperSU and the following bootloop. Just pressed the tiny red panic button to shut down and went into recovery mode.
Just tried to use some thin folie between the tray and the SIM card in order to have some more pressure between SIM card and the contacts, failed.
Is it technically possible that a full custom ROM flash (with no ticked exceptions) still not formated the probably damaged SIM card modem portion/driver?
User pintspin has the same problem as above and he is much more into the topic than I am.
Still any hints? Wanted to avoid buying a new smartphone, still love the Ultra C6833 and its large screen...
Click to expand...
Click to collapse
I will ask him if I can obtain the ones that worked for him/her.
The modem should be flashed when you flashed the ftf file if the baseband portion is included.
This is the one I found in the thread ResurrectionRemix 5.8.3 25/05/17 [7.1.2] Nougat for Togari,
https://forum.xda-developers.com/showpost.php?p=56234199&postcount=16
And this:
https://forum.xda-developers.com/xperia-z-ultra/help/aosp-rom-sim-detection-t3185526/post62481536
I know I have used one other way back. It was two zips. You flashed them in a specific order or the phone would not boot.
But I can't find this one.
I uploaded my own modem files. Its the same files that is in the zip above but with the stock rom Im running.
Im guessing it might do something because its working on my phone. And its the same files that is being flash in the above zip file.
File is not flashable. Unzip and replace the in system/etc/firmware. Permissions 644. And reboot.
Or you could do it from twrp. Take a bit longer. Manually delete the three files one by one and then copying the files one by one.
Setting the permissions to 644 one by one.
SUPERUSER said:
I will ask him if I can obtain the ones that worked for him/her.
The modem should be flashed when you flashed the ftf file if the baseband portion is included.
This is the one I found in the thread ResurrectionRemix 5.8.3 25/05/17 [7.1.2] Nougat for Togari,
https://forum.xda-developers.com/showpost.php?p=56234199&postcount=16
And this:
https://forum.xda-developers.com/xperia-z-ultra/help/aosp-rom-sim-detection-t3185526/post62481536
I know I have used one other way back. It was two zips. You flashed them in a specific order or the phone would not boot.
But I can't find this one.
I uploaded my own modem files. Its the same files that is in the zip above but with the stock rom Im running.
Im guessing it might do something because its working on my phone. And its the same files that is being flash in the above zip file.
File is not flash-able. Unzip and replace the in system/etc/firmware. Permissions 644. And reboot.
Or you could do it from twrp. Take a bit longer. Manually delete the three files one by one and then copying the files one by one.
Setting the permissions to 644 one by one.
Click to expand...
Click to collapse
@SUPERUSER done , uploaded here the working modem patch strangely from a different variant but worked fine... thanks for above help as well.
I can confirm that the attached modem patch is working perfectly fine ... on AOSP build ( 6.0.1 )
(*) @ac845 steps i suppose you already have your system.img and boot.img
Flash the aosp Rom images ( system.img ) and (boot.img) via fast boot OR if you dont have images of stock then just flash any stock rom zip from recovery i used twrp recovery after FULL WIPE OR if you even dont have both then just use Scrubber port GPE for togari 6833 z ultra
don't reboot
Flash the attached modem patch i.e. C6802_modem_patch.zip
reboot to system
on first boot it will take a bit ( 1 minute may be ) to detect and register the sim.
I have finished worked on my rom as well , will going to upload it hopefully today ... its purest aosp stock , can be rooted and gapps are also tested working fine , there is no Imei base band issue as well.
pintspin said:
@SUPERUSER done , uploaded here the working modem patch strangely from a different variant but worked fine... thanks for above help as well.
I can confirm that the attached modem patch is working perfectly fine ... on AOSP build ( 6.0.1 )
(*) @ac845 steps i suppose you already have your system.img and boot.img
Flash the aosp Rom images ( system.img ) and (boot.img) via fast boot OR if you dont have images of stock then just flash any stock rom zip from recovery i used twrp recovery after FULL WIPE OR if you even dont have both then just use Scrubber port GPE for togari 6833 z ultra
don't reboot
Flash the attached modem patch i.e. C6802_modem_patch.zip
reboot to system
on first boot it will take a bit ( 1 minute may be ) to detect and register the sim.
I have finished worked on my rom as well , will going to upload it hopefully today ... its purest aosp stock , can be rooted and gapps are also tested working fine , there is no Imei base band issue as well.
Click to expand...
Click to collapse
I (partially) understand, what you guys mean, but I don't know how to proceed and thus have to ask more beginner questions:
As recommened by SUPERUSER like 2 days ago I flashed a the .276 stock ROM. The device is of course unrooted now, bootloader open. I don't have a recovery mode (f.i. TWRP) where I can flash ZIPs. What would be the easeast way to flash a ZIP-file in this situation? I could try flashing with fastboot, but I don't know where to get the right .imgs. Wished I still had TWRP though. Sorry for bothering you, but for beginners like me it's too complex sometimes...
ac845 said:
I (partially) understand, what you guys mean, but I don't know how to proceed and thus have to ask more beginner questions:
As recommened by SUPERUSER like 2 days ago I flashed a the .276 stock ROM. The device is of course unrooted now, bootloader open. I don't have a recovery mode (f.i. TWRP) where I can flash ZIPs. What would be the easeast way to flash a ZIP-file in this situation? I could try flashing with fastboot, but I don't know where to get the right .imgs. Wished I still had TWRP though. Sorry for bothering you, but for beginners like me it's too complex sometimes...
Click to expand...
Click to collapse
Download this file https://www.androidfilehost.com/?fid=24415232478676273
To make it more simple. Rename the file to "recovery" without the quotes when the download is finished.
In your download folder on your computer hold down shift on your keyboard and right click on an empty space.
In the right click menu select "open command window here".
In the cmd. Type "fastboot flash recovery recovery.img".
Turn your phone off. And boot it to fastboot. Hold volume up or down and simultaneously connect the usb cable to the computer.
If you did it right the phone should have a blue led on.
Now press enter on your keyboard inside the command window.
Hopefully you will see something like flashing and then finished.
How to boot to recovery?
Pull out the usb cable.
Now hold volume down and press power button.
When it vibrates let go. A few seconds you will se the twrp ui.
In addition to super user post above : For fast boot you need to press volume up and then connect PC USB cable when your PC is on and USB cable is connected to it ( you also need yo ensure that USB debugging is turned on ) goto phone setting and you need to press 8 times on build number in your about phone n phone will open a hiden option called developers option under phone settings and goto developer options n under that option you need yo select USB debugging on .
pintspin said:
In addition to super user post above : For fast boot you need to press volume up and then connect PC USB cable when your PC is on and USB cable is connected to it ( you also need yo ensure that USB debugging is turned on ) goto phone setting and you need to press 8 times on build number in your about phone n phone will open a hiden option called developers option under phone settings and goto developer options n under that option you need yo select USB debugging on .
Click to expand...
Click to collapse
TWRP succesfully installed. Great to have it back!
But now it comes: SIM CARD DETECTED AGAIN after 2 weeks and endless hours of fiddling, reading forums and bothering you guys. You both are awesome :angel: and made my day!
What I did:
1. TWRP installed
2. full wipe
3. installed prerooted custom rom 14.6.A.1.236: Customized Germany (DE), source: https://www.android-hilfe.de/thema/stock-roms-mirror-root-tools-anleitung.559556/ Link: https://mega.nz/#!PoEElBZa!DlejjkTzCZGMXbJR0ZvgTk5i0gNqo4QSM0LIyyRKl1M
4. installed SUPERUSER's modem patch from above
5. rebooted: 1. time no SIM card detected. Wanted start crying :crying:, but rebooted 2nd time: SUCCESS! Broadband of my provider is back!
Now restoring messages, contacts and apps right now using Snappea. After reorganzing apps I'll do full TWRP backup and I hope that this problem never will occur.
During restore app process I'll go to a German beer garden and will raise my glass to you guys! :laugh: Want to donate both of you some money, please let me know how. Paypal?
Greetings from Germany!
George
Happy midsummer!
Well I find my joy in helping someone with their technical issues and it makes me happy when we find a solution. Its why I'm here..
I don't believe in exchanging knowledge for money unless its my job.
But I thank you for your gratefulness! cheers! :highfive:
:good::laugh: great to know you solved this ... Enjoy the weekend with ur phone revive ... I am glad that it worked coz I can feel what it like to be Co I went some what same situation .... Just keep us in ur prayers ...
pintspin said:
:good::laugh: great to know you solved this ... Enjoy the weekend with ur phone revive ... I am glad that it worked coz I can feel what it like to be Co I went some what same situation .... Just keep us in ur prayers ...
Click to expand...
Click to collapse
Unfortunately it's not over yet!
SIM still not detected very often, but sometimes it does. SIM works for some hours but then it's accidently not detected anymore in locked-screen mode or in the middle of operation, app usage etc. Rebooting with detected SIM works in 1 of 5 times maybe. Restoring full backups doesn't make any difference.
Had the idea that it is a temperature problem and cooled the device down in the frosting fridge for a couple of minutes, but rebooting incl SIM detection works more often, but not always. Beside SIM problem operation is normal, no problems with WLAN, apps etc.
IMO it can't be a software bug since problem occures not generally. Before I'd send it in to Sony I wanted to ask the community if you have any ideas or recommendations?
Cheers!