Related
I just purchased a phone on craigslist (might have made a mistake). I have much experience with WM, but none with android (flashing that is).
The phone has a blank screen, and shows a constant green light (led notification).
I have tried Ominous, but couldn't get it to connect. (I did have a problem with it telling me my username and password didn't match anything in their records, so I don't know if it was the phone couldn't connect, or it wasn't logged in.
I downloaded SEUS, took the battery out for 5 seconds, put it back in, held the back button, and plugged in the USB. No luck.
Does anyone have any advice to give me please?
I have been reading these forums forever, and know how to search. I spent the last two hours on google and XDA looking but all the results were people who had an exclamation point on their phone, and my screen is blank.
Any help that anyone can offer would be greatly appreciated, and I don't mind making a donation to the person that helps me fix it.
Thank you for your time,
David
I got Ominous to connect for a plit second and this is the report it gave me.
Code:
Action journal
19:04:50 Identify
19:04:50 Shows detailed information about the connected phone.
19:04:50 Operating system: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
19:04:50 Application version: 0.05.2221 (beta)
19:04:50 . The action name is 'Identification'
19:04:50 Selected phone type: Xperia™ X10
19:04:50 Selected connection method: USB EROM
19:04:50 i Instructions
19:04:50 i 1. Make sure the phone battery is charged to at least 50%.
19:04:50 i 2. Switch off the phone!
19:04:50 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
19:04:50 i 4. Press and hold the return back button, then connect the cable to the phone!
19:04:50 . The action started waiting for the user
19:05:01 . The action finished waiting for the user
19:05:01 Connecting via SEMC USB Flash Device (USB1)...
19:05:01 Device driver version: 2.2.0.5
19:05:06 e Error: Failed to start communication
19:05:06 . The action entered shutdown phase
19:05:06 . The action reported failure
Error code
# A662EA2CB5165738
Error details
---
7B 5B 6D 4B D6 66 42 B7 94 EB 86 8E 10 4A 76 B7
D3 77 1C 9A 98 09 2E 13 85 11 ED 28 8E 72 1A 81
7C 81 DB D1 A3 FC 9E 17 74 BF B9 3E D0 11 F8 4E
94 1D 6E D1 6D B1 B7 96 CA EA 36 0D 40 CB 43 0C
C1 A2 AC EA C8 E7 7E 83 2F 6D AC 0C 1E 4E 36 0F
B4 73 72 3B D8 37 12 A7 44 55 04 FE A0 DF A6 CF
3C D2 1E 6B E8 79 AA 84 62 A9 1A 83 90 21 EA 91
2C D9 10 61 76 E7
---
Okay so using a different method for connecting (leave USB plugged in, take battery out, hold down back button, put battery back in) I was able to get SEUS to connect, but it told me I had the latest firmware. I'm making progress though.
4 hours and nothing. Anyone have even some silly advice I can try?
21productionz said:
Okay so using a different method for connecting (leave USB plugged in, take battery out, hold down back button, put battery back in) I was able to get SEUS to connect, but it told me I had the latest firmware. I'm making progress though.
Click to expand...
Click to collapse
Hit repair when it tells you that you already have the latest firmware.
Thank you for taking the time to offer advice, I really appreciate it. I have attached a ss of the screen when it says it's done. Sadly I don't have an option to repair.
Take the sd card out and throw in your media card slot install pc companion and do factory reset
-------------------------------------
Sent via the XDA Tapatalk App
wrongfeifong said:
Take the sd card out and throw in your media card slot install pc companion and do factory reset
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Forgive my ignorance, but how would I do a factory reset using the SD card? I have PCC installed already.
Hi there, have you tried the X10Flash program? The procedure is the same and you can get it from here: http://forum.xda-developers.com/showpost.php?p=6514704&postcount=3
Or, you can use step 1 from here: http://forum.xda-developers.com/showpost.php?p=6970850&postcount=1
Anyways, it could be a timing issue. Remember that the phone stays in flash mode for only 5 seconds or so... you have to be quick.
This method is a bit tricky because of the nature of the program and the manual procedure to find out device ids, give it a try.
PM me in the next couple of hours and I can try to help you via skype or something.
I tried to download the one in post 3, but everytime it gets to a certain percentage and just dies. I have been downloading hotfile files all night, and that is the only one I cannot get to work. I am downloading the step 1 now. I tried the step 1 for omnious, but no luck. I did try downloading a rom from a WWE carier, and it got pretty far in omnius but failed. I'm wondering if it is a log in problem with omnius.
Code:
Action journal
22:21:47 Flash
22:21:47 Allows to change languages supported by the phone and upgrade its firmware.
22:21:47 Operating system: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
22:21:47 Application version: 0.05.2221 (beta)
22:21:47 . The action name is 'Flash'
22:21:47 Selected phone type: Xperia™ X10
22:21:47 i Instructions
22:21:47 i 1. Make sure the phone battery is charged to at least 50%.
22:21:47 i 2. Switch off the phone!
22:21:47 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:21:47 i 4. Press and hold the return back button, then connect the cable to the phone!
22:21:47 . The action started waiting for the user
22:21:59 . The action finished waiting for the user
22:21:59 Connecting via SEMC USB Flash Device (USB1)...
22:21:59 Device driver version: 2.2.0.5
22:21:59 Detected chipset: QSD8250
22:21:59 Boot mode: EROM
22:21:59 IMEI:
22:21:59 Sending loader...
22:22:01 Establishing connection to the server...
22:22:06 Receiving news...
22:22:07 i No news
22:22:08 Actual credit: 0.00
22:22:14 Writing file FILE_277365972_1273135823000_1273135823000_277365969_114475108_INFILE_LONGTERM.zip...
22:24:46 e Failed!
22:24:46 . The action entered shutdown phase
22:24:46 . The action reported failure
Error code
# 663A586958F60A0C
Error details
---
16 3B 12 50 C1 EB 2F EC 9D E0 A5 2E E9 6A C7 C9
A1 74 23 21 41 BA A1 2E 05 4B CD A5 C9 1F 09 2C
25 B0 BD AA A8 60 21 2D 03 F2 BB A2 03 98 A3 6C
7B 37 2D E0 5F 2C 27 D8 05 06 45 89 F9 DE A9 BE
7D DA 98 F2 FF 77 EF 54 A3 D8 67 06 16 E4 D7 45
35 F6 CD 0A 8E 32 20 E1 A3 7F B5 88 59 4C B7 82
1B 62 9D 3E 62 8A 1F 6D BD 4E 7B 92 D4 21 39 CA
3B F7 93 20 61 EC F9 CB 9F 77 05 49 47 62 17 7E
EF 1D 43 10 41 97 AF 6C 1D 60 25 B8 97 F2 B9 9C
F5 36 A3 ED C1 C6 DF AA CD FF F5 38 19 7E 81 01
F5 6A 23 50 8F 38 0F 4C 83 76 0D 73 5A C1
---
That is the last report I got from omnius
EDIT: deleted
Hmm... well like I said, try the X10Flash tool. By the way, doesnt look like a Omnius login problem because I remember seeing similar stuff on my Omnius logs (except the error message ofcourse)
It may very well be a timing issue, even with omnius it's hit or miss. I will keep trying. Thank you very much for taking your time to help.
It's downloading very slow, so I can't wait to try the flash utility.
Finaly omnius finished successfully.
Code:
Action journal
22:55:06 Flash
22:55:06 Allows to change languages supported by the phone and upgrade its firmware.
22:55:06 Operating system: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
22:55:06 Application version: 0.05.2221 (beta)
22:55:06 . The action name is 'Flash'
22:55:06 Selected phone type: Xperia™ X10
22:55:06 i Instructions
22:55:06 i 1. Make sure the phone battery is charged to at least 50%.
22:55:06 i 2. Switch off the phone!
22:55:06 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:55:06 i 4. Press and hold the return back button, then connect the cable to the phone!
22:55:06 . The action started waiting for the user
22:55:16 . The action finished waiting for the user
22:55:16 Connecting via SEMC USB Flash Device (USB1)...
22:55:16 Device driver version: 2.2.0.5
22:55:16 Detected chipset: QSD8250
22:55:16 Boot mode: EROM
22:55:16 IMEI:
22:55:16 Sending loader...
22:55:18 Establishing connection to the server...
22:55:22 Receiving news...
22:55:23 i No news
22:55:24 Actual credit: 0.00
22:55:30 Writing file FILE_277365972_1273135823000_1273135823000_277365969_114475108_INFILE_LONGTERM.zip...
22:59:16 Writing file FILE_277344165_1277133235000_1271857047000_277344163_16722287_INFILE_LONGTERM.zip...
22:59:55 Actual credit: 0.00
22:59:55 Turning off the phone...
22:59:57 i Please disconnect battery and cable from the phone!
22:59:57 s Successfully done.
22:59:57 . The action entered shutdown phase
22:59:57 . The action reported success
Additional details
---
5C 7F 58 8A E3 41 7F 7A 61 EA 8D C2 35 F8 D9 C2
37 EC CB 57 1D 90 31 04 31 0D 3D CE 05 E8 7F FF
C9 50 15 6A ED 6E 1F 9A FF 00 DB F5 B8 0B
---
However the screen is still black, and now the led is blinking 2 times then pausing, then cycles through that.
21productionz said:
Finaly omnius finished successfully.
Code:
Action journal
22:55:06 Flash
22:55:06 Allows to change languages supported by the phone and upgrade its firmware.
22:55:06 Operating system: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
22:55:06 Application version: 0.05.2221 (beta)
22:55:06 . The action name is 'Flash'
22:55:06 Selected phone type: Xperia™ X10
22:55:06 i Instructions
22:55:06 i 1. Make sure the phone battery is charged to at least 50%.
22:55:06 i 2. Switch off the phone!
22:55:06 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:55:06 i 4. Press and hold the return back button, then connect the cable to the phone!
22:55:06 . The action started waiting for the user
22:55:16 . The action finished waiting for the user
22:55:16 Connecting via SEMC USB Flash Device (USB1)...
22:55:16 Device driver version: 2.2.0.5
22:55:16 Detected chipset: QSD8250
22:55:16 Boot mode: EROM
22:55:16 IMEI:
22:55:16 Sending loader...
22:55:18 Establishing connection to the server...
22:55:22 Receiving news...
22:55:23 i No news
22:55:24 Actual credit: 0.00
22:55:30 Writing file FILE_277365972_1273135823000_1273135823000_277365969_114475108_INFILE_LONGTERM.zip...
22:59:16 Writing file FILE_277344165_1277133235000_1271857047000_277344163_16722287_INFILE_LONGTERM.zip...
22:59:55 Actual credit: 0.00
22:59:55 Turning off the phone...
22:59:57 i Please disconnect battery and cable from the phone!
22:59:57 s Successfully done.
22:59:57 . The action entered shutdown phase
22:59:57 . The action reported success
Additional details
---
5C 7F 58 8A E3 41 7F 7A 61 EA 8D C2 35 F8 D9 C2
37 EC CB 57 1D 90 31 04 31 0D 3D CE 05 E8 7F FF
C9 50 15 6A ED 6E 1F 9A FF 00 DB F5 B8 0B
---
However the screen is still black, and now the led is blinking 2 times then pausing, then cycles through that.
Click to expand...
Click to collapse
Did you do as it instructed? I mean, disconnect battery and cable from the phone?
I didn't do it in that order, I disconnected and then pulled the batt.
it's running through right now again I will reverse the steps this time.
I just went through it again, it completed successfully. I removed the battery, then unplugged it. Left the Battery out for 30 seconds. When I put it back in, and hit the power button I get a blue solid light and still a blank screen. I contacted the guy I bought it from and he said he would return my money. I only wasted 7 hours of my life, not bad I guess. Sorry I wasted some of yours too though. Thanks for you help I appreciate it. If you give me your PayPal email I will buy you lunch tomorrow.
21productionz said:
I didn't do it in that order, I disconnected and then pulled the batt.
Click to expand...
Click to collapse
That should be ok. The order doesn't really matter.
Ok now take a pause. Whats the situation now? What do you have and what do you get? Sorry for sounding a bit weird but forum discussion threads are not the best way to help anyone realtime.
Anyways, the thing is that since your phone shows some activity, there is a chance that it is receptive to a firmware flash that would restore the phone to its function. What is weird in your case is that even if Omnius reports success, your phone is not responding.... could be something bad with the phone itself? who knows?
The thing is... you should try one of the methods: Omnius or X10FlashTool to flash a known good firmware and see if your phone shows life... if not then I'm afraid your are in for some trouble. You see SE or your operator doesn't approve of any third party methods to mess with your firmware so you will have trouble asking for warranty replacements. But, you see your log of Omnious shines a ray of hope... the phone is accepting firmware so all roads are not yet blocked.
Its the back button you hold down when plugging in the usb cable, not power.
SEUS has just updated their program so instead of seeing a long file like this "FILE_277344675_1271909822000_1271909822000_277398125_114906833_INFILE_LONGTERM" , instead of that, it is shortened like this "FILE_277398125".
After overwriting the two files according to the tutorial, the SEUS keeps downloading the firmware files over the ones which have been overwritten.
I thought the SEUS is OK last weekend, but now, they changed their program. Anyone tried and find a solution for this issue?
Man im stuck with the same problem...someone pls help !!
Use Omnius instead? Quick and easy to use.
Download
Set up account online
Enter account details in Omnius
Then follow instructions below on how to flash
http://forum.xda-developers.com/showpost.php?p=6789689&postcount=324
Hope this helps.
wingz85 said:
Use Omnius instead? Quick and easy to use.
Download
Set up account online
Enter account details in Omnius
Then follow instructions below on how to flash
http://forum.xda-developers.com/showpost.php?p=6789689&postcount=324
Hope this helps.
Click to expand...
Click to collapse
yea ur intrustions are for the the SIn reconstructions, what if i want to reinstal using my bak ups from the seus dump (blog.fs) before i debranded??
exekias said:
yea ur intrustions are for the the SIn reconstructions, what if i want to reinstal using my bak ups from the seus dump (blog.fs) before i debranded??
Click to expand...
Click to collapse
i have the same problem . i want brand to my original A1(Austria) branded files.
now i have R2BA023 root + market fix.
and i have the 2 original A1 files ( File_ xxxxxxxxxxxxxxx_infile_longterm).
but how does omnius work with those files?
what is the application file and what the customize file?
kind regards DauL
can someone help me`` how to flash rooted phone back to A1 ( Austria) branded witfh omnius ? i have the two original files, but i dont know which file i should take for the application and the customize file
kind regards
wingz85 said:
Use Omnius instead? Quick and easy to use.
Download
Set up account online
Enter account details in Omnius
Then follow instructions below on how to flash
http://forum.xda-developers.com/showpost.php?p=6789689&postcount=324
Hope this helps.
Click to expand...
Click to collapse
Hi，Thank you for your sugestion. However, I am still failed to flash by Omnius.
Finally got error and Yellow exclamation mark on my phone after reboot it.
Here is the result after I flash the x10 with Omnious.
Code:
Action journal
22:29:08 Flash
22:29:08 Allows to change languages supported by the phone and upgrade its firmware.
22:29:08 Operating system: Microsoft Windows XP Professional Service Pack 3 (build 2600)
22:29:08 Application version: 0.07.2279 (beta)
22:29:08 . The action name is 'Flash'
22:29:08 Selected phone type: Xperia™ X10
22:29:08 i Instructions
22:29:08 i 1. Make sure the phone battery is charged to at least 50%.
22:29:08 i 2. Switch off the phone!
22:29:08 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:29:08 i 4. Press and hold the return back button, then connect the cable to the phone!
22:29:08 . The action started waiting for the user
22:29:25 . The action finished waiting for the user
22:29:25 Connecting via SEMC USB Flash Device (USB3)...
22:29:25 Device driver version: 2.2.0.5
22:29:25 Detected chipset: QSD8250
22:29:25 Boot mode: EROM
22:29:25 IMEI: [email protected]@@
22:29:25 Sending loader...
22:29:26 Establishing connection to the server...
22:29:29 Receiving news...
22:29:34 i No news
22:29:34 Actual credit: 0.00
22:29:40 Writing file phone.zip...
22:30:18 Writing file X10i_GENERIC_1234_8465R8A_R1FB001.zip...
22:33:38 e Failed!
22:33:38 . The action entered shutdown phase
22:33:38 . The action reported failure
Error code
# E39CDD9F86C3082E
Error details
---
61 C6 C0 A4 65 CB CD 00 FF 08 E1 72 F3 9F B5 AE
13 9B E7 8D E5 86 63 FA 78 BD E4 7E ED 5F 85 68
09 52 D0 4B 3E 18 6D E0 61 94 3A D6 3F 7D 06 ED
11 DB BB C5 11 03 FE 12 A2 17 E5 DB 4F B0 1E 0D
C5 5C E6 DF 47 8B A0 93 02 E4 6C 19 80 4D 59 91
46 C1 3B 15 F6 69 01 6B CA 64 A3 13 2E 26 7A 7C
7E AD 9A 9E 1D EB 00 E8 80 F0 7A 96 0F 25 D0 BA
D5 FD 93 6D 4B 5B 30 D9 6C D7 4D 92 B4 C0 04 64
F7 56 66 50 2A AA 3B E5 F3 13 07 8D EE A3 41 61
48 50 E9 72 04 6F 71 F5 55 D4 0A 0C 6D 2F 05 E8
77 58 E8 34 2A 17 BD A1 E1 9A FF 0A ED 48 D5 09
C7 38 25 15 95 C7 43 B0 6F 20 0C E7 BD 5C 0B 29
17 8E 39 EE F3 F9 7F 69 EF 5B A1 DC B3 74 21 FF
19 DE A7 ED 25 46 5D DE 0F B6 8F 34 FD F2 BB 58
E7 3F D9 C4 D5 24 2D E1 A1 DA BF 44 5B 79 BB 34
F9 22 57 42 85 66 03 14 99 C1 7C 7F
---
It still works via SEUS but some steps have changed due to the new SESU release.
Follow THIS revised tutorial and all will work again.
I know it works as I have been doing it and even used this yesterday.
Candy[MAN] said:
It still works via SEUS but some steps have changed due to the new SESU release.
Follow THIS revised tutorial and all will work again.
I know it works as I have been doing it and even used this yesterday.
Click to expand...
Click to collapse
Yes, I know the new method. however, I have already bricked my x10 and now it show me a Yellow exclamation mark after rebooting.
I have tried the new method, it did not work for my case.
Hi guys,
I have a major problem with my X10. Everything worked fine til I tried to update...
I wanted to update from 024 to 026. Battery seemed to be full enough. My PC crashed during update. Ever since then I can't turn on my phone.
I reloaded the battery with an extra charger.
Tried to repair with SEUS and PC Companion. Fails every time.
Tried to falsh the 016 with the flashtool. Said ist was successful, but still can't turn the phone on.
Then tried to falsh with Omnius and got the following error
Code:
Action journal
20:55:32 Flash
20:55:32 Allows to change languages supported by the phone and upgrade its firmware.
20:55:32 Operating system: Microsoft Windows XP Home Edition Service Pack 3 (build 2600)
20:55:32 Application version: 0.06.2254 (beta)
20:55:32 . The action name is 'Flash'
20:55:32 Selected phone type: Xperia™ X10
20:55:32 i Instructions
20:55:32 i 1. Make sure the phone battery is charged to at least 50%.
20:55:32 i 2. Switch off the phone!
20:55:32 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
20:55:32 i 4. Press and hold the return back button, then connect the cable to the phone!
20:55:32 . The action started waiting for the user
20:55:45 . The action finished waiting for the user
20:55:45 Connecting via SEMC USB Flash Device (USB2)...
20:55:45 Device driver version: 2.2.0.5
20:55:45 Detected chipset: QSD8250
20:55:45 Boot mode: EROM
20:55:45 IMEI: 35941903598910
20:55:45 Sending loader...
20:55:46 Establishing connection to the server...
20:55:52 Receiving news...
20:55:55 i No news
20:55:56 Actual credit: 0.00
20:56:04 Writing file R6A_R1FA016_FSP_X10i_CUST_DE_GENERIC_1235_7836_S1_SW_LIVE_AC12_0001_S1_PARTITION_WITH_SPARE.zip...
20:59:04 Writing file R1FA016_APP_SW_RACHAEL_GENERIC_1227_4612_S1_SW_LIVE_AC12_0001_S1_PARTITION.zip...
20:59:18 e Failed!
20:59:18 . The action entered shutdown phase
20:59:18 . The action reported failure
Error code
# E39CDD9F86C3082E
Error details
---
72 3A 36 32 AB 29 89 AE 99 F2 EB 82 13 5B 1F 88
EF E5 43 43 D5 28 39 14 A0 C3 90 D4 13 71 91 2A
2F 1A 9D FA A5 F3 E9 9C D6 52 25 A7 73 40 BF C6
96 EB 18 70 75 B8 67 70 4C 86 89 19 0E 95 A7 0F
23 85 57 AB 78 7A 04 2F 6D 73 79 08 E8 A5 F3 88
1E FF 1F DF B8 CB C4 FC 1A 09 C8 D5 AF A9 0E D5
A3 ED F0 7D C7 43 12 1C D5 03 98 A2 8C 54 48 B9
22 46 45 FF 18 30 F8 E8 0C C6 39 BD D8 A2 E3 D5
F5 D5 0D F3 36 D1 4A EF C5 C2 FC 84 F2 8C BF 7E
1E 08 F2 02 23 CD 35 F7 8F E5 D8 C7 49 59 7E 38
71 0A 82 FB 49 2D 0D 2C 7C 64 5B 2B F3 C0 3F 30
50 6C 0C 7F 5B F9 E7 82 77 5A A5 D2 DD 6B 8F 24
E0 D9 2D 93 C5 D8 37 E4 7A B7 75 E4 FD 41 21 5A
C1 36 AB AD 67 B1 D7 BF 29 CC FB 10 D7 37 AF CA
C1 ED 23 52 65 F6 29 CE F9 DC B5 8A B3 80 2F 2B
9F 1C 73 CC CB 09 D9 3E C9 14 6D 34 B3 DC 31 0A
31 02 C3 32 FB 1C 41 05 F4 D7
---
Still can't turn the phone on.
Do you have any idea what happened and how I can fix that?
By the way, I do not get the yellow exclamation mark, I get nothing...
Phone vibrates and the greed LED goes on shortly and then: nothing!
Anybody who had that problem and solved it somehow?
Your PC crashed during the update? Good lord...
If the bootloader is corrupt you're out of luck.
How can I find out, if the bootloader is ok?
I can get it into flashmode, but after flashing it won't turn on.
Hi.
You could try one of the methods to root your phone which will also update it to 026. - forum.xda-developers.com
Hello. When starting omnius unlocking procedure ( with TestPoint connection ), after testpoint, i cant establish connection to PC: it says me that i need QSH or similar drivers to install...are those drivers in the omnius folder called drivers? and wich files? there are plenty of them in the rar file...I leave here the omnius LOG:
Action journal
06:49:26 Unlock network lock by certificate replacement
06:49:26 Unlocks the phone by modifying S1 boot and recalculating simlock signature. A connection to the testpoint (TP) is required during the process.
06:49:26 Operating system: Microsoft Windows XP Home Edition Service Pack 3 (build 2600)
06:49:26 Application version: 0.23.3995
06:49:26 . The action name is 'Unlock'
06:49:26 Selected phone type: LT15
06:49:26 Selected connection method: USB ROM
06:49:26 i Instructions
06:49:26 i 1. Make sure the phone battery is charged to at least 50%.
06:49:26 i 2. Switch off the phone!
06:49:26 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
06:49:26 i 4. Connect the testpoint to ground (GND) !
06:49:26 i 5. Shortly press the power button!
06:49:26 i 6. Disconnect the testpoint!
06:49:26 i 7. Connect the cable to the phone!
06:49:26 [picture]
06:49:26 . The action started waiting for the user
06:53:48 . The action has been aborted
06:53:48 . The action finished waiting for the user
06:53:48 The operation was cancelled at the user's request.
06:53:48 . The action entered shutdown phase
06:53:48 . The action reported success
Result code
# D4D6E2DE43AA0938
Additional details
---
58 BA 31 FC 43 03 2B D8 C7 F0 26 B9 C5 26 43 55
91 3D 2F 14 92 89 F5 EF E9 72 C7 E8 72 91 8D C9
41 A0 F1 E5 B3 82 8B 46 67 FB 09 E1 DB 8A 4E B9
5F AB 8F CC 03 F8 6C C9 9C 3D 89 68 D5 D6 D3 2E
5F 26 BF B8 B8 05 92 B1
---
I have to abort the procedure because i cant get , at 100% of tries, connect to the PC.....
Also, i only can identify the Arc with USB mode and not USB ROM mode
and this is the mode that is by default in the initial step of the unlocking procedure...
Can anybody help me? Thanks
Disclaimer:
newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick your device or anything else!
How to use:
OPTIONAL STEP 1:
- if you have missing flash driver just double click exe and confirm driver extraction, an exe will become available, run it and install driver.
OPTIONAL STEP 2:
- this step is optional, this step dump trim area, you can do this and keep those file somewhere on your pc in case you hard brick your device so give it to servicians to repair your phone.
STEP 1:
- Download right firmware for your device using XperiFirm tool, put newflasher.exe into firmware dir created by XperiFirm tool. Before you double click newflasher.exe do in mind something, newflasher tool is programed to flash everything found in the same dir!!! So tool flash all .ta files, all .sin files, boot delivery (whole boot folder), partition.zip, in short all files found in dir! If you no want to flash something just move file which you no want to flash OUT OF FOLDER! Partition.zip .sin files can be flashed only if you extract partition.zip into newly created folder called partition!
STEP 2:
- To start flashing phone put your phone into flash mode, double click newflasher.exe and wait wait wait until your device gets flashed, thats it. Look into log to see if something goes wrong! If all right you are done. If not post your log so I can look!
SOME MORE THINGS:
"You do not need to unlock bootloader or to root the phone if you want to flash a stock firmware from XperiFirm.
There are no files in the stock firmware that need to be deleted. Prompts will ask you to skip some files.
Feel free to press N to every prompt since:
- TA dumping it's not related with DRM keys.
- Flash persist_* files only if you know what you are doing, since you will lose your attest keys. Backup persist partition.
If you need the firmware on both A and B slot use fastboot commands to choose the inactive partion and re-flash."
Happy flashing!
Supported platforms:
- Newflasher is working on Windows, Linux, Android and Darwin, just chose right newflasher binary. With Android version you can flash phone by using another phone!
Changelog:
- version 1: Sorry a lot of work is done in pre pre alpha version and I can't count every changes, just folow development process about version 1, a lot of work is done before it started working. One esential change was done to tool improvement and it is described in one of the my posts related to moving function "erase:" to the section before function "flash:", it is realy improvement and more safer than in time when it was at the start of flashing routine.
- version v2 (15.Aug.2017)
Implemented free disk space safety check, it was missing and danger in case flashing process gets interupted because of the lack of the free disk space needed for sin extractions and temporary files. I have also include GordonGate flash driver prompt so in case somebody have missing flash drivers, simple need to double click exe and folow drivers archive extraction procedure, later need to install these drivers trought Windos device mannager. Also I have implemented an realy pre pre alpha version of the maybe non working trim (why maybe? Because I don't own xzp so can't test) area dump routine, in case it is working we can dump some esentials trim area units from device (probably not a full dump as like it was on every oldest xperia models - no permissions for dumping drm key unit)
- version v3 (23.09.2017)
Some more security checks, it's now a bit safer than v2
- version v4 (21.10.2017)
Updated trim area dumper, now it stores log to the trimarea.log but dump is now in .ta format and writen to the 01.ta and 02.ta
- version v5 (22.10.2017)
Updated trim area dumper, add progress meter, fix y-n prompt (thanks @pbarrette)
- version v6 (22.10.2017)
Updated trim area dumper
- version v7 (23.10.2017)
Updated trim area dumper, newflasher redesigned a bit, fix new partitioning for Oreo
- version v8 (24.10.2017)
Fix trim area dumper
- version v9 & v10 (25.10.2017)
Workaorunds on trim area dumper
- version v11 (07.04.2018)
Support for 2018 devices
- version v12 (29.04.2018)
Try fix doublefree bug/crash (most noticed on Linux 64 bit binary)
- version v13 (01.05.2018)
Fix doublefree bug/crash by removing dynamic allocation from function get_reply
- version v14 & v15 (12.06.2019)
Sony XPeria 1 support added.
- version v16 (16.06.2019)
LUN0 detection optimized.
- version v17 (24.06.2019)
LUN0 detection bug fixed.
- version v18 (10.08.2019)
Untested fix for https://forum.xda-developers.com/cr...wflasher-xperia-command-line-t3619426/page105
Using builtin mkdir instead of calling it trought system call
- version v19 (08.10.2019)
Implemented prompt for flashing persist partition; print skipped .sin files
- version v20 (13.12.2019)
implemented prompt for flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots
- version v21 (29.06.2020)
implemented battery level status check before flashing, flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots is mandatory now and is flashed by default right now, more info, try fix previously reported isue on sync and powerdown command reported 2-3 years ago so I have disabled it and now enabled for test, implemented Macos support (curently need to be tested! If you have plan to test please flash only cache.sin DO NOT flash the rest because of safety for your device!)
- version v22 (30.06.2020)
trying to fix battery capacity retrieval
- version v23 (04.07.2020)
removed battery capacity retrieval (not going to work that way), fix trim area dump file name, new gordongate drivers
- version v24 (04.07.2020)
new feature - now you can run newflasher from script or console with your own command, e.g. newflasher getvar:Emmc-info , I didn't tested all the list of commands, if you do it share them with us!
- version v25 (09.07.2020)
New trim area dump tool, with this change trim area dump is created in 3 secconds. Do in mind this not dump protected units like drm key...etc! Some changes in scripting feature from v24
- version v26 (10.07.2020)
Added 4 diferent reboot modes, reboot to android, reboot to fastboot, reboot to bootloader, power off
- version v27 (11.07.2020) (not yet released)
Workaround in mac libusb
- version v28 (12.07.2020)
Workaround to sync response bug; Fully implemented support for Mac. I'm tested myself on mac 10.14 but confirmed working on mac 10.15 too
- version v29 (12.07.2020)
Mac proper libusb deinitialisation
- version v30 (13.07.2020)
Preparation for Debian packaging; I'm noticed that hex modified arm64 fake pie binary is not working so its now compiled with ndk and its true pie binary now
- version v31 (14.07.2020)
Fix cosmetic bug https://forum.xda-developers.com/showpost.php?p=83056693&postcount=1212 which might confuse somebody
- version 32, not yet released
- version 33 (30.07.2020)
Allow bootloader unlocking with newflasher; Try fix sync response bug for win and darwin too
- version 34 (08.08.2020)
Added support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line) (not yet released because of bug)
- version 35 (08.08.2020)
Updated support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line); Move trim area dumps out of root folder so it not get acidentaly flashed, dumps is now inside folder tadump
- version 36 (27.08.2020)
Some improvements and and possible bug fixes
- version 37 (09.12.2020)
Added support for Xperia 5 II with emmc instead of ufs (not working)
- version 38 (10.12.2020)
Fixed impropper implementation from v37
- version 39 (13.12.2020)
Since mark 2 devices protocol is changed a bit and on some devices OKAY reply is not in separated usb poacket, instead it is merged with data packet, added support for it
- version 40 (03.01.2021)
Temporary solution for determining partition 0 sin file caused by two diferent emmc csd info we found recently on mark 2 devices
- version 41 (03.01.2021)
Removed temporary solution from version 41 so right lun0 sin file get flashed and seccond lun0 get skipped or booth skipped if lun0 sin file do not match device storage size
- version 42 (11.03.2021)
Fix bug in flashing booth slots when current slot is A, thanks to @chrisrg for discovering bug!
- version 43 (12.06.2021)
Support for Mark 3 devices
- version 44 (19.06.2021)
Fully Mark III device implementation
- version 45 (20.06.2021)
Implemented battery level check and prompt user to take a risk and continue flashing or stop flasing if battery level is less than 15 percent
- version 46 (08.07.2021)
Fix problem with filenames which contain "_other", it need to be always flashed to the diferent slot
- version 47 (15.07.2021)
Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares
- version 48 (19.07.2021)
Flash bootloader,bluetooth,dsp,modem,rdimage to booth slots only on a,b devices
- version 49 (31.07.2021)
Support for XQ-BT41
- version 50 (12.08.2021)
Workin progress on asynchronous usb to make it more like synchronous, added progress bar during send-receive usb packets and more logging. Increased usb timeout to 2 minute. Trying fix sync command at the end of flashing as reported here -> https://github.com/munjeni/newflasher/issues/42
- version 51 (12.08.2021)
Fix empry line printed while receiving usb packets, thanks @elukyan
- version 52 (01.10.2021)
Implemented userprompt for keeping userdata, thanks @OhayouBaka for figuring out! Removed bootloader log retrieval
- version 53, 54, 55 (20.0822022)
Fix trimarea dumper crash on big endian machines, update building makefiles
Credits:
- without @tanipat and his pc companion debug logs this tool will never be possible! Thank you a lot for your time providing me logs! (by the influence of others, He was disappointed me with last post, but I still appreciate his help and can't forget it)
- without @thrash001 who helped testing our tool I never be continue building our tool since I don't have device for testing, thanks mate!
- didn't forgot @beenoliu, thanks mate for testing!
- thanks to @porphyry for testing linux version!
- thanks to @Snow_Basinger for providing sniff log from 2018 device and for testing on his 2018 device
- thanks to @frantisheq for testing newflasher on his 2018 device and for notify about doublefree bug
- thanks to @serajr for providing me some logs which helped me to figure out some things related to 2018 devices
- thanks to @noelex for helping in Xperia 1 implementation
- thanks to @Meloferz for testing on his xperia 1 mark II
- thanks to github contributors, testers and reporters: vog, noelex, TheSaltedFish, solarxraft, pbarrette, MartinX3, kholk
- thanks to Chirayu Desai for tracking addition to Debian and thanks to vog for initiating all that
- thanks to @elukyan for testing and providing me usb sniff logs for mark 3 devices imlementation, thank you so much
Common errors and how to solve:
https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228
Source code:
https://github.com/munjeni/newflasher
let me start for you and report
here my log..
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error writing command!
Drücken Sie eine beliebige Taste . . .
Common errors and what you need to do:
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
FIX --------> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84603931
Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms
FIX---------> Make sure to flash right rom model e.g. if your device is SO-01L you need to flash rom model SO-01L or e.g. your phone is H8314 you need to flash rom H8314 ... etc, otherwise you might hardbrick your phone!
Bootloop caused by rooback protection e.g. by flashing an OLD rom over NEWER one e.g. you have android 11 and want back to android 10 that will bootloop your phone if your phone have rollback protection
https://forum.xda-developers.com/t/...-xq-at51-with-flashtool.4119707/post-84509417
in short explanation your bootloader need to be unlocked. Than by relocking bootloader rollback index (rollback protection) is reset to zero. Than you can flash oldest rom because index in that case is zero so you won't get bootloop related to rollback protection.
It was confirmed working:
https://forum.xda-developers.com/t/...-xq-at51-with-flashtool.4119707/post-84637803
https://forum.xda-developers.com/t/...-xq-at51-with-flashtool.4119707/post-84673613
If neither help you to solve problem you should read boot log to get idea, use this command line option for newflasher:
newflasher Read-TA:2:2050
what I got
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#6&3a757eec&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_B00B\6&3A757EEC&0&1
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
A device attached to the system is not functioning.
- Error reaply! Device didn't replied with OKAY or DATA
Press any key to continue . . .
wait for others to report
Hm, you successfully wrote command but error on reaply Lets see new version is out
Today I have free time for development, I don't know when I will get free time again, so guys if you hurry to have flasher I am here and waiting. I do not have 2017 device model so I can't test, so can't continue development without your tests
Driver is the right.
here the next:
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Successfully write 0x0 bytes to handle.
- Error writing command!
Drücken Sie eine beliebige Taste . . .
Strange! Maybe run as admin is need?
It would be great if tanipat debug newflasher with monitoring studio so I can compare whats going on? New version is out again.
Edit:
Curent version is safe so you no need to care for brick! Tool currently nothing write to internal mem! I will tell when it is ready for flashing! Now its just pre pre alpha version, only read from phone
in the windows devicemanager is it correct as "SOMC Flash Device"
the next one:
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error write! Need nBytes: 0x18 but done: 0x0
- Error writing command!
Drücken Sie eine beliebige Taste . . .
Can you right click on .exe and run as admin?
the same
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error write! Need nBytes: 0x18 but done: 0x0
- Error writing command!
Drücken Sie eine beliebige Taste . . .
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
get_reaply:[0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
get_reaply:[0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.
- Successfully read 0x0 bytes from handle.
Raw input [0x0]:
- Error reaply: less than 4!
Drücken Sie eine beliebige Taste . . .
Sorry, i must disconnect the device for the next start
Thanks a lot! Seems some good progress here! I had set timeout to 60 secconds, seems it was not enought and caused timeout, now I have set to 120 secconds and donesome small modification, hope we get luck now, new version is out
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.
- Error reaply: less than 4!
Drücken Sie eine beliebige Taste . . .
and this, without disconect a view seconds later again start the exe
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
- Successfully write 0x18 bytes to handle.
ERROR: TIMEOUT: failed with error code 997 as follows:
▄berlappender E/A-Vorgang wird verarbeitet.
- Error reaply: less than 4!
Drücken Sie eine beliebige Taste . . .
Hmm strange realy. See https://www.lifewire.com/how-to-fix-code-31-errors-2623184 its seems your driver is not working propertly, maybe you have old flashtool driver and not one for newer device (which can be installed by installing sony pc companion software), I have no idea by now, unable to figure out why that happens Did you flashed by sony pc companion your device allready and you are sure it is working, can you confirm? Probably if you allready installed flashtool driver you will need to uninstall and reinstall pc companion, have no idea by now what might be a problem
so, i have erase the driver. restart windows, install the flashtool driver. start the exe:
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.
- Error reaply: less than 4!
Drücken Sie eine beliebige Taste . . .
now i erase the driver, restart windows and let windows install the driver over windows.
(i hope you can undersood my english)
Many thanks! Yes I understand you. I must go now, hope somebody figure out if driver is problem or bug in my tool, see you guys tommorow
New version is out, let me know please! I have researched a bit, seems get overlapped result caused some problems and returns imediatelly before thing complete, I have set to "wait complete" hope it is ok now
good morning, so i have reinstall sony companion and start the repair, the new driver is isntall but:
Code:
--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&15c311e1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&15C311E1&0&2
- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.
- Error reaply: less than 4!
Raw input [0x0]:
Drücken Sie eine beliebige Taste . . .
---------- Post added at 10:27 AM ---------- Previous post was at 10:18 AM ----------
and this is from my windows7 32bit pc, only sony companion is install.
Code:
--------------------------------------------------------
newflasher (2).exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#5&448f588&0&1#{a5dcbf10-6530-11d2-901f-00
c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_B00B\5&448F588&0&1
- Successfully write 0x18 bytes to handle.
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 4F 4B 41 59 31 30 34 38 35 37 36 30 30 OKAY104857600
- Successfully write 0xe bytes to handle.
- Successfully read 0x9 bytes from handle.
Raw input [0x9]:
00000000 4F 4B 41 59 47 38 31 34 31 OKAYG8141
- Successfully write 0xe bytes to handle.
ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:
Ein an das System angeschlossenes Gerõt funktioniert nicht.
- Error reaply: less than 4!
Raw input [0x0]:
Drücken Sie eine beliebige Taste . . .