Find contentHello.
First off, thanks for the most complete tutorial on this problem. I read all the 52 pages (at this very moment) on the XDA thread regarding this same problem but did not find it very easy to follow: http://forum.xda-dev...d.php?t=2646405
Your one, is more straight to the point and nonetheless does not omit a thing.
Have a Sony Z1 (6903) for 1,5 yrs now. NEVER root-ed by me at least.
Around two months ago made a gap to Lollipop through phone's system update (I think it was 5.0.2 or 14.5.A.0.270 but could be mistaking and it was 14.5.A.0.242 - both Italian).
Q1: the problem with the people listening my robotized voice definitely happened, which version was it or in which version of Sony's Lollipop was it solved?
Around 10 days ago the Z1 has become to say that apps are closing unexpectedly. The phone at some point asked me whether I'd like to install a new version (of something, maybe firmware I was sleepy). I said NO. In the morning it was still functioning. Some apps closed again unexpectedly but nos as many as previous evening. Then in 5 minutes, all the sudden, I see the screen of the phone is black lighted and wasn't reacting to anything, not even disconnect button. I did hard reset by pushing the red little button in the SIM slot. It vibrated 3 times and disconnected itself.
From that time is unresponsive. Can't power on; no LCD or LED reaction for power button or charger; no reaction to connection to PC (unknown device); PC cannot detect the phone with Vol -or Vol +; phone doesn't vibrate when holding Vol+ and Power together.
Flashtool says that I connected a phone with USB debugging OFF.
S1 Tool does see the it in the Emergency mode (SEMC Flash device does installs fine).
But gives the following error:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : CFCEFF01
HARDWARE ID : 04000100E1007B00
PRODUCT DETECTED: "MSM8974 OEM1 fused"
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
can't get S1 command header
LOADER NOT RESPONDING
I DID use till now the bootloader (APPSW) that you provided for the 6903: 14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
Same result as above...
Few days ago I did what you described above in this thread: made my own APPSW.SIN_FILE_SET based on the newer official firmware version 14.5.A.0.270.
The phone VIBRATED as it was (trying) to connect ON. Even S1 Tool acted a bit different - did not give the S1 command header (at least for now).
I got the phone up to see whether it had some movement on the screen but it was OF already and the error came back in S1 Tool:
can't get S1 command header
LOADER NOT RESPONDING
ATTENTION: my APPSW DID NOT INCLUDE THE "boot.zip". I only did what you taught us, above. My .sin_file_set did not also include the two .XML files that the .sin_file_set archive (which it is after all): update.xml & boot_delivery.xml.
I learnt their existence in the 14.2.A.0.290 bootloader of yours only later, out of curiosity.
Q2: do you think S1 tool could accept only "newer" firmware versions ? Why it vibrated only at that time..
Q3: if so, then probably the phone didn't start because MY sin_file_set didn't have the boot.zip archive and the two .XML files to "tell" the phone to flash them the boot loader too?
Next day I created my other APPSW.SIN_FILE_SET. This time with the above mentioned boot.zip and the .XML files (took them from the Bundler that Flashtool created after downloading the version, very comfy by the way, no need to un-archive the firmware' .FTF).
Unfortunately - same result as above.
Q4: does it want now a NEWER version of APPSW.SIN_FILE_SET ? or it doesn't matter of kind of bootloader are we giving to it (even if the currently installed is higher, I mean)
Q5. if positive, the APPSW of which Z1 firmware version should I make and flash it to the phone? (which current official firmware is newer?)
Q6: maybe I should give other type of files to rewrite the boot loader section, for instance the ACPU" which contain boot.sin (only)?
Q7: when it tried to boot, what is the reaction of the phone when S1 Tool actually works (after the "LOADER AID: ...." message I intend? It boots and then flashes its stuff onto the phone or everything goes silent (without booting/ON)?
MY SEARCHES on the net on this error (very few!).
I found these following suggestions in such situations:
1. install latest usbflash drivers - 3.0.0.7 installed, latest
use different usb cable - I used another, and shortest too
use different usb port - did that, switched PC's also, tried on Win XP too (besides my Win7 Ultimate)
use external usb hub - did NOT try that
switch usb mode in BIOS of your PC to HIGH SPEED, NOT "FULL SPEED" - don't have this option
2. the only thread on XDA that cover this problem , there's a Dutch person (herogjan) with same problem (page 17), and he eventually gave up, tried a few things.
The_laser , the writer of S1 tool, answered to the Dutch:
"main loader not responding, this is abnormal for your situation.
you doing testpoint job with or without battery ? try to connect battery, when s1tool ask you to remove testpoint and try to change usb port."
I tried to connect battery: A. from the very beginning (gives an error about device) B. connected the battery before releasing the TestPoint and clicking the S1tool button the 2nd time)..
Same result: can't get S1 command header
3. "install usbflash drivers from s1tool package,do not use usb 3.0 port, use short usb cable."
I used same those ones (even formatted and started from zero). Did not use usb 3.0 (although tried). Used short cable too as I mentioned.
4. The_laser suggests that if in such situation you don't have trim backup - you're toast and should give it out for spare parts..
Q8: is it so? I repeat, I didn't do ANY root or Flashtool updates. Maybe, I interrupted one, true. although I don't understand how it did downloaded in the first place, I had very low speed Internet at that time and it would've taken an eternity to download it.
5. You write above:
"5. Set up compatibility with Windows XP SP3 to avoid problems on windows Vista or newer."
Q9: what do you mean exactly and how to do it?
6. Some other person on the same XDA thread says:
"i used testpoint while holding volume down key and it worked, before it did not work by testpoint only"
Q10. Unfortunately he didn't mention what he did exactly, his steps. Didn't remodel this. Any advice?
7. Other guy mentioned on a Russian forum
"they've flashed the boot loader and then it started so they've then flashed the firmware and it works"
Q11. I should be able to flash the boot loader. Where from and which one should I take?
Q12: Medusa box, would be of help? How much does it cost?
Q13: Setool 3, expensive, would it help? What other things does it do. I might need it for my phone shop.
Q14: you mentioned above: "1. Make sure, that you have fully charged battery. 50% is absolute minimum."
I just thought, maybe it is TRYING to boot and to flash.. but the battery is not full enough. How can I measure it.. maybe it is NOT CHARGING at all from the wall charger.
Would appreciate any of your help. Thanks in advance the moderator and the users.
