Develop Bugs

protocol fault (status 44 72 63 6f?!) solved

for some reason, I flash back CN 2.2.1 sbf, then i want to root it with superoneclick,, but it comes with error protocol fault (status 44 72 63 6f?!)
what does it mean? I can't use adb shell at the same time with same error.

Check your computer can recognice the phone, with rsd lite

unrafa said:
Check your computer can recognice the phone, with rsd lite
Click to expand...
Click to collapse
i juts flash it with RSD, not the problem

[Q] ok i got a wierd problem

ok so i have my play (r800x) unlocked and everything but i installed omnius and it gave me this log when i identified the phone
Code:
[code]
Action journal
17:09:32 Identify
17:09:32 Shows detailed information about the connected phone.
17:09:32 Operating system: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
17:09:32 Application version: 1.38.4753
17:09:32 . The action name is 'Identification'
17:09:32 Selected phone type: Xperia™ PLAY
17:09:32 Selected connection method: USB EROM
17:09:32 i Instructions
17:09:32 i 1. Make sure the phone battery is charged to at least 50%.
17:09:32 i 2. Switch off the phone!
17:09:32 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
17:09:32 i 4. Press and hold the return back button, then connect the cable to the phone!
17:09:32 . The action started waiting for the user
17:09:44 . The action finished waiting for the user
17:09:44 Connecting via SEMC USB Flash Device (USB1)...
17:09:44 Device driver version: 2.2.0.5
17:09:44 Detected chipset: MSM7X30
17:09:44 Boot mode: EROM
17:09:44 EROM version: 1241-3656 R9A021
17:09:44 IMEI: A100001713D1A9
17:09:45 Device ID: 65EE28BC0613A8CC0C72EE449ED67DF6ED81A858
17:09:45 Minimum loader AID: 0001
17:09:45 Color: Red SEMC
17:09:45 The phone is rooted.
17:09:45 i Unsigned flashing is disabled.
17:09:45 Sending loader...
17:09:45 Waiting for loader response...
17:09:47 Phone model (from TA): R800x
17:09:47 Current CXC (from TA): 1243-3001_3.0.1.E.0.88
17:09:47 Current CDA (from TA): 1245-4101_R91C
17:09:47 Current FS (from TA): VERIZON_3.0.1.E.0.88
17:09:47 i The phone is not locked to a network.
17:09:47 i Simlock origin: SEMC
17:09:47 s Successfully done.
17:09:47 . The action entered shutdown phase
17:09:47 . The action reported success
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
[/CODE]
does this mean that my bootloader is still locked i'm wondering from line "17:09:45 i Unsigned flashing is disabled." or is it unlocked as i used fastboot and it erased the blocks from the bootloader and it completed successfully

Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x

Lordomn said:
Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x
Click to expand...
Click to collapse
ok thanks a whole bunch for your input but what about the unsigned flashing being disabled?

IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.

chevyowner said:
IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.
Click to expand...
Click to collapse
OK thanks so much as this is my first device other then the Samsung fascinate that I will flash kernels with so I'm just cautious as also this is my only phone
Sent from my GBTweaked v7.1 r800x using Tapatalk 2

M8 / Bootloop

Hi,
and sorry for my poor english...*
My Device:
HTC One M8
M8_UL UNKNOW
Tampered / Unlocked / Root / S-OFF
CID 11111111
TWRP: latest
Rom: viperone
Problem: bootloop.
The problem occurred after installation of the dualsim adapter from the Magicsim (magic-sim.com]). That did not work, so I tried to reinstall the rom with full wipe.
Result: bootloop and no access to the viper's rom, and no access to recovery.
M8 is seen by the fastboot:
fastboot devices returns <ùOu☼ÚQÞÁ¾ £ ╦ <~)
M8 is not seen by ADB:
adb devices returns nothing
*
I think the drivers are OK. But I can reinstall drivers if necessary?
What I have noticed abnormal, it is in fastboot getvar all:
INFOserialno <ùOu☼ÚQÞÁ¾ £ ╦ <~)
INFOmodelid: ☻◄
I have incomprehensible symbols. I can not rewrite the mid or serial ...
Anyway ... I can not fix the problem ...
*
Also HBOOT gives:
Loading ... [0P6BDIAG.zip]
No image!
Loading ... [0P6BDIAG.nbh]
No image or wrong image!
Loading [0PGBIMG.zip]
Loading [0PGBIMG.nbh]
No image or wrong image!
*
Do you know how can I fix it ?
Thx!

Sorry, I haven't a verizon, but HTC M8.
If a moderator can redirect it ?
Thx

noxarv said:
Hi,
and sorry for my poor english...*
My Device:
HTC One M8
M8_UL UNKNOW
Tampered / Unlocked / Root / S-OFF
CID 11111111
TWRP: latest
Rom: viperone
Problem: bootloop.
The problem occurred after installation of the dualsim adapter from the Magicsim (magic-sim.com]). That did not work, so I tried to reinstall the rom with full wipe.
Result: bootloop and no access to the viper's rom, and no access to recovery.
M8 is seen by the fastboot:
fastboot devices returns <ùOu☼ÚQÞÁ¾ £ ╦ <~)
M8 is not seen by ADB:
adb devices returns nothing
*
I think the drivers are OK. But I can reinstall drivers if necessary?
What I have noticed abnormal, it is in fastboot getvar all:
INFOserialno <ùOu☼ÚQÞÁ¾ £ ╦ <~)
INFOmodelid: ☻◄
I have incomprehensible symbols. I can not rewrite the mid or serial ...
Anyway ... I can not fix the problem ...
*
Also HBOOT gives:
Loading ... [0P6BDIAG.zip]
No image!
Loading ... [0P6BDIAG.nbh]
No image or wrong image!
Loading [0PGBIMG.zip]
Loading [0PGBIMG.nbh]
No image or wrong image!
*
Do you know how can I fix it ?
Thx!
Click to expand...
Click to collapse
Did you try to reflash your recovery ? Your recovery may has been corrupted. I would try flashing the newest twrp 2.8.1.0 recovery and see if that fixes your issue.

Hi, and thx,
Yes, I do it.
I've try to reflash my recovery (latest ie 2.8.1.0) and RUU.
But fastboot returns error :
FAILED (remote: 41 model id check fail)
That the reason why I think it's probably a problem with M8 identification (mis & seial) ?

No idea ?

noxarv said:
No idea ?
Click to expand...
Click to collapse
Until this thread gets moved and/or you look in the I international section you likely won't get a response here.
Sent from my HTC6525LVW using Tapatalk

dottat said:
Until this thread gets moved and/or you look in the I international section you likely won't get a response here.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Moved to International, thanks.

Thanks !
At this level, I think it is not possible to repair my M8.
I've read this related post : http://forum.xda-developers.com/showthread.php?t=2627411
Because of this thread and of the failure of my attempts, I would like to send my phone to HTC. The warranty period is valid, BUT, I have red text, SuperCID tampered and S-OFF...
How can I build a "good" android-info.txt ?
Correct modelid : 0P6B10000
Corrupt modelid : ☻◄
Can you suggest me a solution to find a issue ?!

I try to do somthing...
With an Hexaditor, I have write this android-info.txt :
Hexa :
Code:
6d 6f 64 65 6c 69 64 3a 20 e2 98 bb e2 97 84 0a
63 69 64 6e 75 6d 3a 20 31 31 31 31 31 31 31 31
0a 6d 61 69 6e 76 65 72 3a 20 33 2E 31 36 2E 30 2E 30 30 30 30 0A
Texte :
Code:
modelid: ☻◄.cidnum: 11111111.mainver: 3.16.0.0000
In the android-info.txt, it gives the following result :
Code:
modelid: ☻◄
cidnum: 11111111
mainver: 3.16.0.0000
But after flashing process, fastboot return a 41 model id check fail.
At this point, do I persist in this way?
Thx a lot,

[Help][Warning] Hard Bricked Xperia XA1 G3125 (Android 8.0) Phone

Hi all,
Due to some supidity on my part, and a small share of bad luck I have hard bricked my Xperia XA1 G3125 phone. I'm posting this with a couple of questions at the bottom in the hope that someone can suggest something useful, or that someone will read this and avoid a similar fate. If you are considering rooting a Sony Xperia XA1 G3125, especially if you are running android 8.0 then please read this post.
My goal was to root the phone so that I could install the Xposed module
I unlocked the bootloader with the Sony website (https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/)
I already had ADB with a generic android USB driver. I later installed the specific sony ADB driver (Sony so0119 ADB interface driver) as part of troubleshooting but the two appear to function exactly the same.
For TWRP I followed this guide by JanJan (https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886). I downloaded the correct release for my phone model and flashed the recovery and boot images. Here was my first mistake, I (stupidly) thought that flashing the boot was a necessary step for installing TWRP. I am given to understand that I should have executed "fastboot boot boot.img" to test the boot image before flashing it to my storage. The recovery image worked great (props to JanJan), but now my phone was soft-bricked. It could boot to bootloader and TWRP recovery, but booting it normally led it to stall on a white screen with black sony text on it. For any of you intending to install TWRP, I would recommend this guide (https://www.getdroidtips.com/twrp-recovery-sony-xperia-xa1/). Follow the steps carefully and hopefully avoid bricking your phone.
At this point, I played around with a few more boot images from this post (https://forum.xda-developers.com/xa1/development/xperia-xa1-plus-stock-kernel-advanced-t3729856). As those of you with some experience might expect, none of them worked. I decided to cut my losses and attempt to restore my phone to stock through the Xperia Companion software. Unfortunately, because the bootloader had been unlocked the Xperia Companion software would no longer perform a factory reset on my phone. For those of you seeking to unlock the bootloader, please be aware of this.
I then attempted to flash the stock rom using Newflasher as according to this guide (http://www.xperiablog.net/2018/01/2...-firmware-for-xperia-xz-premium-xz1-and-more/) but Newflasher failed to find my phone when connected via usb. Part of this guide, though, involves installing the Sony Mobile Flashtool by Androxyde. When Newflasher didn't work, I used the flashtool by Androxyde in an attempt to flash the stock rom. My phone was (I believe) charged to at least 70-80% but I still encountered an error during the flashing process. I'll post the full log at the bottom of this post, but the offending lines appeared to be
08/038/2018 13:38:06 - INFO - Opening TA partition 2
08/038/2018 13:38:06 - INFO - Processing oem.sin
08/038/2018 13:38:06 - INFO - Checking header
08/038/2018 13:38:06 - INFO - Flashing data
08/038/2018 13:38:09 - INFO - Ending flash session
08/038/2018 13:38:09 - ERROR - Have read only 524256 byte(s) instead of 599884 byte(s)
08/038/2018 13:38:09 - ERROR - Error flashing. Aborted
08/038/2018 13:38:09 - INFO - Flashing finished.
08/038/2018 13:38:09 - INFO - Please unplug and start your phone
Click to expand...
Click to collapse
For those of you seeking to restore the phone to factory setting, I would recommend Emma instead of Androxyde's tool. Emma appears to be the officially endorsed solution by Sony, and I would assume it is less likely to brick your phone.
I disconnected and attempted to reboot my phone, but no luck. If I boot normally, no reaction from the phone. If I hold down the on key, no reaction from the phone. If I boot into recovery (vol down + power button), the light flashes white for half a second, followed by no response from the phone. Connecting the phone via usb causes the LED light to turn red, but no further response by the phone. Connecting the phone in bootloader mode (vol up button) again causes the LED light to turn red and no further response from the phone.
When connected via usb (bootloader or no), the phone could not be recognised by anything. After reinstalling the drivers (Sony so0119 ADB interface driver), it can be recognised by device manager. Currently, it cannot be recognised by the Xperia Companion or the Emma tool. Androxyde's tool detects it, but indicates that "Device connected with USB debugging off". It then cycles every ~30 seconds between device disconnected and device connected with USB debugging off. you can see this in the logs posted below.
I've exhausted everything that I can think of (in my limited experience) to fix this phone. If anyone would like to offer advice (or commiseration) then I am all ears. I backed up all of my user data with the Xperia Companion tool before beginning this entire process. Two questions I would ask:
If I obtain a new Xperia XA1 G3125 running android 8.0, can I use the companion tool to transfer my old backed up user data to the new phone?
Is it possible/feasible to rescue a phone from hardbrick by physically replacing the internal storage and/or other components? I lack the technical expertise for this, but I'm planning to contact Sony tech support or a third party phone repairer as a final attempt to rescue this phone.
At the very least, I do hope that someone reads this and is able to avoid my mistakes. To repeat, do not flash the boot image unless you are 100% sure that it will work, and you have made all reasonable attempts at backing up your current boot image.
Cheers,
DoneGoofed

The full text of the Sony Mobile Flashtool by Androxyde is as follows. If anyone can tell me how to upload this as an attachment, I would be grateful.
08/034/2018 13:34:25 - INFO - <- This level is successfully initialized
08/034/2018 13:34:25 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
08/034/2018 13:34:25 - INFO - Executing search strategies to find proxy selector
08/034/2018 13:34:26 - INFO - No proxy found for IE. Trying next one
08/034/2018 13:34:26 - INFO - No proxy found for firefox. Trying next one
08/034/2018 13:34:26 - INFO - No proxy found for java. Trying next one
08/034/2018 13:34:26 - INFO - Syncing devices from github
08/034/2018 13:34:26 - INFO - Opening devices repository.
08/034/2018 13:34:26 - INFO - Scanning devices folder for changes.
08/034/2018 13:34:29 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
08/034/2018 13:34:29 - INFO - Pulling changes from github.
08/034/2018 13:34:31 - INFO - Quietly closing devices repository.
08/034/2018 13:34:31 - INFO - Devices sync finished.
08/034/2018 13:34:31 - INFO - Loading devices database
08/034/2018 13:34:31 - INFO - Loaded 112 devices
08/034/2018 13:34:31 - INFO - Starting phone detection
08/034/2018 13:34:35 - INFO - Device disconnected
08/034/2018 13:34:51 - INFO - Flash canceled
08/035/2018 13:35:11 - INFO - Device connected in fastboot mode
08/036/2018 13:36:48 - INFO - Selected Bundle for Sony Xperia XA1(G3125). FW release : 40.0.A.3.7. Customization : Customized AU
08/036/2018 13:36:48 - INFO - Preparing files for flashing
08/037/2018 13:37:30 - INFO - Please connect your device into flashmode.
08/037/2018 13:37:50 - INFO - Device disconnected
08/037/2018 13:37:57 - INFO - Device connected in flash mode
08/037/2018 13:37:58 - INFO - Opening device for R/W
08/037/2018 13:37:58 - INFO - Reading device information
08/037/2018 13:37:58 - INFO - Phone ready for flashmode operations.
08/037/2018 13:37:58 - INFO - Opening TA partition 2
08/037/2018 13:37:58 - INFO - Current device : G3125 - RQ3006HZV8 - 1307-5285_R2B - 1306-2967_48.1.A.2.21 - GENERIC_48.1.A.2.21
08/037/2018 13:37:58 - INFO - Closing TA partition
08/037/2018 13:37:58 - INFO - Start Flashing
08/037/2018 13:37:58 - INFO - No loader in the bundle. Searching for one
08/037/2018 13:37:58 - INFO - No matching loader found
08/037/2018 13:37:58 - WARN - No loader found or set manually. Skipping loader
08/037/2018 13:37:58 - INFO - Loader : S1_Root_4a6c - Version : S1_Boot_MT6757_O0.MP103_207 / Boot version : S1_Boot_MT6757_O0.MP103_207 / Bootloader status : ROOTED
08/037/2018 13:37:58 - INFO - Max packet size set to 8M
08/037/2018 13:37:58 - INFO - USB buffer size set to 512K
08/037/2018 13:37:58 - INFO - Parsing boot delivery
08/037/2018 13:37:58 - INFO - No flash script found. Using 0.9.18 flash engine
08/037/2018 13:37:58 - INFO - Opening TA partition 2
08/037/2018 13:37:58 - INFO - Writing TA unit 00002774. Value : 01
08/037/2018 13:37:59 - INFO - Closing TA partition
08/037/2018 13:37:59 - INFO - Processing partitions.sin
08/037/2018 13:37:59 - INFO - Checking header
08/037/2018 13:37:59 - INFO - Flashing data
08/037/2018 13:37:59 - INFO - Phone boot version : S1_Boot_MT6757_O0.MP103_207. Boot delivery version : S1_Boot_MT6757_N0.MP103_120
08/037/2018 13:37:59 - INFO - Going to flash boot delivery
08/037/2018 13:37:59 - INFO - Opening TA partition 2
08/037/2018 13:37:59 - INFO - Flashing Hinoki_S1BootConfig_MiscTA.ta to partition 2
08/037/2018 13:37:59 - INFO - Writing TA unit 0000084F. Value : 1A CE 2C 00 01 00 07 05 00 02 02 10 00 10 05 00 01 02 68 00 10 04 00 03 01 01 00 04 00 04 81 01 00 02 00 04 85 05 00 05 82 68 00 10 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 00 FA BE BA 00 FA 00 00 04 00 03 00 02 00 04 00 04 00 C4 09 0E 00 06 00 58 1B 01 4B 00 00 00 03 96 00 96 00 07 00 07 00 00 00 00 40 00 03 00 09 00 01 05 00 08 00 01 96 00
08/037/2018 13:37:59 - INFO - Writing TA unit 000008FD. Value : 00
08/037/2018 13:37:59 - INFO - Closing TA partition
08/037/2018 13:37:59 - INFO - Opening TA partition 2
08/037/2018 13:37:59 - INFO - Processing lk_PLATFORM-MT6757-LIVE-6164-EMBEDDED_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/037/2018 13:37:59 - INFO - Checking header
08/037/2018 13:37:59 - INFO - Flashing data
08/037/2018 13:37:59 - INFO - Processing lk2_PLATFORM-MT6757-LIVE-6164-EMBEDDED_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/037/2018 13:37:59 - INFO - Checking header
08/037/2018 13:37:59 - INFO - Flashing data
08/037/2018 13:37:59 - INFO - Processing logo_PLATFORM-MT6757-LIVE-6164-EMBEDDED_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/037/2018 13:37:59 - INFO - Checking header
08/037/2018 13:37:59 - INFO - Flashing data
08/037/2018 13:37:59 - INFO - Processing preloader_s1sbl_PLATFORM-MT6757-LIVE-6164-ROOT_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/037/2018 13:37:59 - INFO - Checking header
08/037/2018 13:37:59 - INFO - Flashing data
08/038/2018 13:38:00 - INFO - Processing tee1_PLATFORM-MT6757-LIVE-6164-EMBEDDED_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/038/2018 13:38:00 - INFO - Checking header
08/038/2018 13:38:00 - INFO - Flashing data
08/038/2018 13:38:00 - INFO - Processing tee2_PLATFORM-MT6757-LIVE-6164-EMBEDDED_S1-BOOT-LIVE-4A6C-0004-MMC.sin
08/038/2018 13:38:00 - INFO - Checking header
08/038/2018 13:38:00 - INFO - Flashing data
08/038/2018 13:38:00 - INFO - Closing TA partition
08/038/2018 13:38:00 - INFO - Opening TA partition 2
08/038/2018 13:38:00 - INFO - Closing TA partition
08/038/2018 13:38:00 - INFO - Opening TA partition 2
08/038/2018 13:38:00 - INFO - Processing cache.sin
08/038/2018 13:38:00 - INFO - Checking header
08/038/2018 13:38:00 - INFO - Flashing data
08/038/2018 13:38:01 - INFO - Processing fotakernel.sin
08/038/2018 13:38:01 - INFO - Checking header
08/038/2018 13:38:01 - INFO - Flashing data
08/038/2018 13:38:03 - INFO - Processing kernel.sin
08/038/2018 13:38:03 - INFO - Checking header
08/038/2018 13:38:03 - INFO - Flashing data
08/038/2018 13:38:04 - INFO - Processing md1arm7.sin
08/038/2018 13:38:04 - INFO - Checking header
08/038/2018 13:38:05 - INFO - Flashing data
08/038/2018 13:38:05 - INFO - Processing md1dsp.sin
08/038/2018 13:38:05 - INFO - Checking header
08/038/2018 13:38:05 - INFO - Flashing data
08/038/2018 13:38:05 - INFO - Processing md1img.sin
08/038/2018 13:38:05 - INFO - Checking header
08/038/2018 13:38:05 - INFO - Flashing data
08/038/2018 13:38:06 - INFO - Closing TA partition
08/038/2018 13:38:06 - INFO - Opening TA partition 2
08/038/2018 13:38:06 - INFO - Processing oem.sin
08/038/2018 13:38:06 - INFO - Checking header
08/038/2018 13:38:06 - INFO - Flashing data
08/038/2018 13:38:09 - INFO - Ending flash session
08/038/2018 13:38:09 - ERROR - Have read only 524256 byte(s) instead of 599884 byte(s)
08/038/2018 13:38:09 - ERROR - Error flashing. Aborted
08/038/2018 13:38:09 - INFO - Flashing finished.
08/038/2018 13:38:09 - INFO - Please unplug and start your phone
08/038/2018 13:38:09 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
08/038/2018 13:38:09 - INFO - Device connected in flash mode
08/038/2018 13:38:14 - INFO - Device disconnected
08/038/2018 13:38:16 - ERROR - Drivers need to be installed for connected device.
08/038/2018 13:38:16 - ERROR - You can find them in the drivers folder of Flashtool.
08/038/2018 13:38:37 - INFO - Device disconnected
08/039/2018 13:39:06 - ERROR - Drivers need to be installed for connected device.
08/039/2018 13:39:06 - ERROR - You can find them in the drivers folder of Flashtool.
08/039/2018 13:39:45 - INFO - Device disconnected
08/040/2018 13:40:45 - ERROR - Drivers need to be installed for connected device.
08/040/2018 13:40:45 - ERROR - You can find them in the drivers folder of Flashtool.
08/041/2018 13:41:23 - INFO - Device disconnected
08/042/2018 13:42:14 - ERROR - Drivers need to be installed for connected device.
08/042/2018 13:42:14 - ERROR - You can find them in the drivers folder of Flashtool.
08/042/2018 13:42:15 - INFO - Device disconnected
08/042/2018 13:42:17 - ERROR - Drivers need to be installed for connected device.
08/042/2018 13:42:17 - ERROR - You can find them in the drivers folder of Flashtool.
08/042/2018 13:42:56 - INFO - Device disconnected
08/043/2018 13:43:56 - ERROR - Drivers need to be installed for connected device.
08/043/2018 13:43:56 - ERROR - You can find them in the drivers folder of Flashtool.
08/044/2018 13:44:34 - INFO - Device disconnected
08/045/2018 13:45:06 - ERROR - Drivers need to be installed for connected device.
08/045/2018 13:45:06 - ERROR - You can find them in the drivers folder of Flashtool.
08/045/2018 13:45:44 - INFO - Device disconnected
08/046/2018 13:46:15 - ERROR - Drivers need to be installed for connected device.
08/046/2018 13:46:15 - ERROR - You can find them in the drivers folder of Flashtool.
08/046/2018 13:46:54 - INFO - Device disconnected
08/047/2018 13:47:25 - ERROR - Drivers need to be installed for connected device.
08/047/2018 13:47:25 - ERROR - You can find them in the drivers folder of Flashtool.
08/048/2018 13:48:03 - INFO - Device disconnected
08/048/2018 13:48:34 - ERROR - Drivers need to be installed for connected device.
08/048/2018 13:48:34 - ERROR - You can find them in the drivers folder of Flashtool.
08/049/2018 13:49:13 - INFO - Device disconnected
08/049/2018 13:49:44 - ERROR - Drivers need to be installed for connected device.
08/049/2018 13:49:44 - ERROR - You can find them in the drivers folder of Flashtool.
08/050/2018 13:50:23 - INFO - Device disconnected
08/050/2018 13:50:53 - ERROR - Drivers need to be installed for connected device.
08/050/2018 13:50:53 - ERROR - You can find them in the drivers folder of Flashtool.
08/051/2018 13:51:32 - INFO - Device disconnected
08/052/2018 13:52:03 - ERROR - Drivers need to be installed for connected device.
08/052/2018 13:52:03 - ERROR - You can find them in the drivers folder of Flashtool.
08/052/2018 13:52:42 - INFO - Device disconnected
08/053/2018 13:53:13 - ERROR - Drivers need to be installed for connected device.
08/053/2018 13:53:13 - ERROR - You can find them in the drivers folder of Flashtool.
08/053/2018 13:53:51 - INFO - Device disconnected
08/054/2018 13:54:22 - ERROR - Drivers need to be installed for connected device.
08/054/2018 13:54:22 - ERROR - You can find them in the drivers folder of Flashtool.
08/055/2018 13:55:01 - INFO - Device disconnected
08/055/2018 13:55:32 - ERROR - Drivers need to be installed for connected device.
08/055/2018 13:55:32 - ERROR - You can find them in the drivers folder of Flashtool.
08/056/2018 13:56:11 - INFO - Device disconnected
08/056/2018 13:56:42 - ERROR - Drivers need to be installed for connected device.
08/056/2018 13:56:42 - ERROR - You can find them in the drivers folder of Flashtool.
08/057/2018 13:57:20 - INFO - Device disconnected
08/057/2018 13:57:31 - ERROR - Drivers need to be installed for connected device.
08/057/2018 13:57:31 - ERROR - You can find them in the drivers folder of Flashtool.
08/058/2018 13:58:10 - INFO - Device disconnected
08/058/2018 13:58:27 - ERROR - Drivers need to be installed for connected device.
08/058/2018 13:58:27 - ERROR - You can find them in the drivers folder of Flashtool.
08/058/2018 13:58:51 - INFO - Device connected with USB debugging off
08/058/2018 13:58:51 - INFO - For 2011 devices line, be sure you are not in MTP mode
08/059/2018 13:59:05 - INFO - Device disconnected
08/000/2018 14:00:00 - INFO - Device connected with USB debugging off
08/000/2018 14:00:00 - INFO - For 2011 devices line, be sure you are not in MTP mode
08/000/2018 14:00:39 - INFO - Device disconnected
08/002/2018 14:02:57 - INFO - Flash canceled
Click to expand...
Click to collapse

DoneGoofed said:
Hi all,
Due to some supidity on my part, and a small share of bad luck I have hard bricked my Xperia XA1 G3125 phone. I'm posting this with a couple of questions at the bottom in the hope that someone can suggest something useful, or that someone will read this and avoid a similar fate. If you are considering rooting a Sony Xperia XA1 G3125, especially if you are running android 8.0 then please read this post.
My goal was to root the phone so that I could install the Xposed module
I unlocked the bootloader with the Sony website (https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/)
I already had ADB with a generic android USB driver. I later installed the specific sony ADB driver (Sony so0119 ADB interface driver) as part of troubleshooting but the two appear to function exactly the same.
For TWRP I followed this guide by JanJan (https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886). I downloaded the correct release for my phone model and flashed the recovery and boot images. Here was my first mistake, I (stupidly) thought that flashing the boot was a necessary step for installing TWRP. I am given to understand that I should have executed "fastboot boot boot.img" to test the boot image before flashing it to my storage. The recovery image worked great (props to JanJan), but now my phone was soft-bricked. It could boot to bootloader and TWRP recovery, but booting it normally led it to stall on a white screen with black sony text on it. For any of you intending to install TWRP, I would recommend this guide (https://www.getdroidtips.com/twrp-recovery-sony-xperia-xa1/). Follow the steps carefully and hopefully avoid bricking your phone.
At this point, I played around with a few more boot images from this post (https://forum.xda-developers.com/xa1/development/xperia-xa1-plus-stock-kernel-advanced-t3729856). As those of you with some experience might expect, none of them worked. I decided to cut my losses and attempt to restore my phone to stock through the Xperia Companion software. Unfortunately, because the bootloader had been unlocked the Xperia Companion software would no longer perform a factory reset on my phone. For those of you seeking to unlock the bootloader, please be aware of this.
I then attempted to flash the stock rom using Newflasher as according to this guide (http://www.xperiablog.net/2018/01/2...firmware-for-xperia-xz-premium-xz1-and-more/) but Newflasher failed to find my phone when connected via usb. Part of this guide, though, involves installing the Sony Mobile Flashtool by Androxyde. When Newflasher didn't work, I used the flashtool by Androxyde in an attempt to flash the stock rom. My phone was (I believe) charged to at least 70-80% but I still encountered an error during the flashing process. I'll post the full log at the bottom of this post, but the offending lines appeared to be
For those of you seeking to restore the phone to factory setting, I would recommend Emma instead of Androxyde's tool. Emma appears to be the officially endorsed solution by Sony, and I would assume it is less likely to brick your phone.
I disconnected and attempted to reboot my phone, but no luck. If I boot normally, no reaction from the phone. If I hold down the on key, no reaction from the phone. If I boot into recovery (vol down + power button), the light flashes white for half a second, followed by no response from the phone. Connecting the phone via usb causes the LED light to turn red, but no further response by the phone. Connecting the phone in bootloader mode (vol up button) again causes the LED light to turn red and no further response from the phone.
When connected via usb (bootloader or no), the phone could not be recognised by anything. After reinstalling the drivers (Sony so0119 ADB interface driver), it can be recognised by device manager. Currently, it cannot be recognised by the Xperia Companion or the Emma tool. Androxyde's tool detects it, but indicates that "Device connected with USB debugging off". It then cycles every ~30 seconds between device disconnected and device connected with USB debugging off. you can see this in the logs posted below.
I've exhausted everything that I can think of (in my limited experience) to fix this phone. If anyone would like to offer advice (or commiseration) then I am all ears. I backed up all of my user data with the Xperia Companion tool before beginning this entire process. Two questions I would ask:
If I obtain a new Xperia XA1 G3125 running android 8.0, can I use the companion tool to transfer my old backed up user data to the new phone?
Is it possible/feasible to rescue a phone from hardbrick by physically replacing the internal storage and/or other components? I lack the technical expertise for this, but I'm planning to contact Sony tech support or a third party phone repairer as a final attempt to rescue this phone.
At the very least, I do hope that someone reads this and is able to avoid my mistakes. To repeat, do not flash the boot image unless you are 100% sure that it will work, and you have made all reasonable attempts at backing up your current boot image.
Cheers,
DoneGoofed
Click to expand...
Click to collapse
Hello DoneGoofed
You will be able to restore your backup if the backup is made on Oreo through Backup and Restore app on your phone or Xperia Companion and, If you do not have any backups then if you have made an Xperia Transfer backup then you should try to restore it through the mobile app Xperia Transfer or Xperia Companion, if you can get it repaired or obtain a new Sony Xperia XA1 G3125.
Sent from my Sony Xperia XA1 using XDA Labs

sieghartRM said:
Hello DoneGoofed
You will be able to restore your backup if the backup is made on Oreo through Backup and Restore app on your phone or Xperia Companion and, If you do not have any backups then if you have made an Xperia Transfer backup then you should try to restore it through the mobile app Xperia Transfer or Xperia Companion, if you can get it repaired or obtain a new Sony Xperia XA1 G3125.
Sent from my Sony Xperia XA1 using XDA Labs
Click to expand...
Click to collapse
Thanks kindly for your advice Sieghart! Good information to know

Xperia M boot loop after 29 sec. whatever installed/done (TWRP, ROM sony flash tools)

Dear Xperia M experts of the xda community,
I really messed up my Sony Xperia M single sim C1905, android 4.3 and it is continious (boot?) looping, that means whatever mode I put the device (TWRP, fastboot, ADB, Hardware: Flash-Mode (as well while flashing system.sin), Fastboot-Mode) -> reboot latest after 29 seconds.
Xüeria M is in usage since 5 yeas and has long lasting battery - on day at least - an did a very good job. Device was bought in Germany. It never let me down, so I somehow stick to it. I'm new to the xda forum.
With some tricks I can install working TWRP 2.8.7.0 or CWM6 (ohter TWRP will freeze), but there is no chance to install a file bigger than approx. 80 MB within the given time.
So formatting an deleting works with TWRP 2.8.7.0.
I "just" wanted to update to a new ROM i.e. like this Resurrection Remix Nougat v5.8.5
https://forum.xda-developers.com/legacy/xperia-m/rom-resurrection-remix-nougat-v5-8-0-t3512094
Before I made a full android backup to my SD Card by installing twrp-3.0.2-0-nicki.img. At this ime TWRP worked properly.
As well I used the Sony Android 4.3 Backup & Restore tool in advance to backup via SD card (At this time the android system was still working).
I wanted to install a new ROM (CM13, cM14, Resurrection Remix Nougat v5.8.5, or something similar xda-dev. is full of options) according to this really nice instruction:
https://www.youtube.com/watch?v=SJBLq19NrfY
Bottomline is, whatever I found out to be a possible solution -> reboot latest after 29 seconds.
Here is what I did until now (since 7 days and night I'm really trying hard, and google must be emty...). I learned a lot about android devices.
P.S.: 3 days ago I escaped the boot loop and could enter TWRP2.8.7 - but I messed up because my knowledge (full data wipe) wasn't to big at this time and I didn't remember what I exactly did in the night before. Now I could bit myself into the ass....
The good point: I 'm convinced, that the bricked device still has a chance. I have more ideas, so at the end, but I don't have such deep knowledge as an developer.
Here we go: my Computers are
Lenovo M57, Win10
Lenovo W540, Linux Mint 20
1) checked if my Xperia M can be unlocked -> yes. Mobile Phone rooted with SuperSu. At this time under still working Android
2) installed minimal ADB & Fastboot (on both computer)
3) got my sony bootloader unlock code and unlocked bootloader via Terminal:
fastboot oem unlock 0x<mycode>
-> OKAY
4) Start twrp-3.0.2-0-nicki.img and tried to install ROM. Something went wrong an I got into a boot loop. Then my trouble started. ADB didn't work anymore. Only fastboot and flash mode.
At the end nothing seemed to work an final I decided to flash new
1) install sony moile flash tool and drivers. I reinstalled the drivers und WIN10 several times until all systems were running. Under Linux, things were easier and there were no driver issues at all.
At the end I installed 0.9.8, 0.9.12.1, 0.9.13.0, 0.9.16.0, 0.9.18.6, 0.9.20.0, 0.9.22.3, 0.9.28.0, 0.9.29.0
on windows and linux.
2) for all flash tool I had the same issue:
I could flash all ftf files (*.sin) perfectly and without error message, except:
system.sin
ended with an error message (because device disconnected after 29 seconds)!
Same procedure for all these firmwares:
C1905_15.1.C.2.8_Customized ZA.ftf (stock firmware)
C1905_15.4.A.1.9_Customized MEA.ftf
C1905_15.4.A.1.9_Customized+UK.ftf
Xperia_M_C1904_4.3_15.4.A.1.9.ftf
I tried all firmwares with all versions of flashtools (yes I really did...)
error message:
20/014/2020 18:14:17 - INFO - Current device : C1905 - YT910V0YHX - 1274-5576_R2C - 1272-2325_15.4.A.1.9 - WORLD-i_15.4.A.1.9
20/007/2020 21:07:14 - INFO - Processing system.sin
20/007/2020 21:07:14 - INFO - Checking header
20/007/2020 21:07:14 - INFO - Flashing data
20/007/2020 21:07:43 - ERROR - Processing of system.sin finished with errors.
20/007/2020 21:07:43 - INFO - Ending flash session
20/007/2020 21:07:43 - ERROR - null
20/007/2020 21:07:43 - ERROR - Error flashing. Aborted
20/007/2020 21:07:43 - INFO - Flashing finished.
I also flashed for all flash tool versions everything except system.sin -> worked with nearly all versions perfectly
An then flashed for all flash tool versions only system.sin -> worked produced the same error messeage after 29. sec.
Another issue: after flashing (with system.sin error) I wasn't able to enter ADB mode again, so only possibility is i.e. to
fastboot flash boot twrp-3.0.2.0-nicki.img -> only then I will be able to access ADB interface again during TWRP bootup.
With the Sony boot-up (logo appears) no ADB access is granted. But I partially solved, see 4.0)
3) Because of system.sin error I tried to access the device via TWRP in order to install CM13, CM14 or Resurrection Remix Nougat v5.8.5, see https://forum.xda-developers.com/legacy/xperia-m/rom-resurrection-remix-nougat-v5-8-0-t3512094
fastboot flash boot twrp-3.0.2-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-3.0.1-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-3.0.0-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-2.8.7.0-nicki.img -> full action possible, but: -> reboot after 29 sec.
fastboot flash boot <file from here>:
https://forum.xda-developers.com/showthread.php?t=2480556
-> full action possible, but: -> reboot after 29 sec.
Re-gaining ADB access for 29 sec.:
4.0) OK again flash with flash tool - I kept sticking to 0.9.18.6 and C1905_15.1.C.2.8_Customized ZA.ftf (stock firmware) which seem to have reproducible results:
fastboot flash boot twrp-2.8.7.0-nicki.img -> full action possible, but: -> reboot after 29 sec.
Then for 29 sec. I could access the internal storage via Linux und use ADB:
What I tried to interupt bootloop:
4.1)
adb shell
dd if=/sdcard/twrp-2.8.7.0-nicki.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
-> OKAY, but has no effect -> -reboot after 29 sec.
4.2)
adb shell
dd if=/sdcard/twrp-3.0.2.0-nicki.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
-> OKAY, but has no effect, that is: current twrp in boot install stays in place -> -reboot after 29 sec.
yes, I rebooted into recovery as well: VOL-UP but nothing changed
4.3)
try to interrup boot loop with
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
4.4)
use flashtool to flash everything except system.sin an then:
fastboot flash system system.sin
error message:
target didn't report max-download-size
sending 'system' (1012135 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
fastboot flash -S 512M system system43.sin
error message:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 484528096 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (517800 KB)...
error: write_sparse_skip_chunk: don't care size 484528096 is not a multiple of the block size 4096
FAILED (data write failure (Protocol error))
finished. total time: 14.530s
data failure by: -> -reboot after 29 sec.
4.4)
I can do:
# fastboot erase system:
erasing 'system'...
OKAY [ 0.294s]
finished. total time: 0.294s
# fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.128s]
finished. total time: 0.128s
But not:
# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
# fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
# fastboot format system
Formatting is not supported for file system with type ''.
# fastboot format data
Formatting is not supported for file system with type ''.
# fastboot format userdata
Formatting is not supported for file system with type ''.
4.5) I'm aware of all button combinations
Vol. Up + USB = Fastboot Mode
Vol. Down + USB = Flash Mode
Vol Up during startup = boot recovery (if flash wir system.sin error -> no effect nothing appears)
4.6 Sony PCC
Tried, but can't register the device anymore.
4.6.1) Software reapair -> USB & Vol. Down attached to PC -> Devices is locked is stated.
4.6.2) If connected before and repair process is started, the process end after 29 sec. ahhhh!
4.7)
With
fastboot flash boot twrp-2.8.7.0-nicki.img
I can access the interal storage, mount all partition, do a factory reset, wipe data, dalvik cache etc. no effect -> reboot after 29 sec.
fastboot flash boot twrp-3.0.2-0-nicki.img or any other 3.x.x.x for nicki will free at the start-up picture. Don't ask me why, shouldn't be this way.
So the issue: I can't backup the 3.0.2.0 with 2.8.7.0. At least I tried. The issue are:
a) no partitons are asked for an twrp does not know where to write
b) -> reboot after 29 sec. even if it would work...
4.8)
After flash rooted with
-magiskV20.zip
and tried to install or do something useful with TWRP2.8.7.0 nicki
-> reboot after 29 sec.
4.9)
Also this doenst finally work, but its a very nice instruction, an works "best" until the 29 sec. are over
https://forum.xda-developers.com/showthread.php?t=2480556
-> -reboot after 29 sec.
5.0) My possibilities are limited an I only have some ideas but dont know how to proceed
5.1) Why does the loop after flash show the sony logo and then the devices seems to be fored to go into reboot. For me it looks like there is a file or a process on the boot partition, which tries to find something - if not -> interrupt an reboot.
Possible solution find the file an interrupt this Sony procedure. Maybe someone has a clue where to search or which file could be corrupted.
5.2) Flash tool is sending packages (can be seen from the debug mode). for system.sin the reboot comes aber about 150 packages are transferred to the system partition. I could think to start sending the file packages 1 to 150 first, then 151 to 300, then 301 to 450 etc.
Is there any possibility to write packagewise with flashtool?
5.3) Since I can access the internal storage I thought about just copying the linux files from a 4.3 Android there, or the files which are required by the sony boot loop checking process, so the boot loop interrupts and the linux an fix itsself.
5.4) Is it possible to place an smaller recovery file at the adequate place, so that there is a chance to rebuild the linux system sucessively
5.5) Is it possible to flash an small system file, which acesses the *.tft file on the sd card an can do the installation process (only possible if the device stops rebooting after 29 sec.)
5.6) Extrakt something useful from the TWRP 3.0.2.0 backup, that might interrupt the boot loop? I don't know how to.
5.7) Maybe things are simple and somebody has a set of proven files for Xperia C1905 (tft, DRM-fix.zip? ), that would help to exclude failures possibilities.
You see I spent over a week on this issue, now my holiday time is over, and I'm almost fed up. But I have the ambition to fix it. Of course its easier an cheaper to simply buy a new android device - but thats not the point, since I'm a technical geek, but have no experiance fixing android devices.
So I'm positive, that some superman in this forum here in this xda-forum who has an idea.
Appreciate any ideas from experts.
Best regards
Dirk

Hey bro,
it's been 3 years since I first flashed my Xperia M so I am not sure whether I can give any solutions but try this if it helps: https://forum.xda-developers.com/xp...cypheros-3-1-cheesecake-t3505798/post72627720

hhjadeja007 said:
Hey bro,
it's been 3 years since I first flashed my Xperia M so I am not sure whether I can give any solutions but try this if it helps: https://forum.xda-developers.com/xp...cypheros-3-1-cheesecake-t3505798/post72627720
Click to expand...
Click to collapse
Hey bro, tnx a lot for your reply. Good hint. Tried to install according your instruction, partially in some way an advance to before: ...
1. Boot into TWRP recovery
->fastboot flash boot bootAOSP.img
->TWRP3.0.2.0 booted properly and this was new I could it would fully work again!
-> This step OK
2. Wipe system, data, cache, dalvik - cache
->TWRP3.0.2.0 boot - and deleted each single partition bit by bit (I had to hurry), because: After 29. sec. reboot.
The system, cache, data, sd card etc. were properly mounted and no errors were shown
-> This step OK
3. Flash ROM
-> ->TWRP3.0.2.0 boot and installed ROM: aoscp_nicki-3.6.3-20170610-unofficial.zip
will start to install the ROM without error message, until the screen turns black und is interruptecd by -> reboot
After this mount "system" error is indicated and with the help of flashtool 09.18.6 the *.ftf firmeware, see above, will properly fix the partiation and everything is mountable again -> so I ran over the proceedure several times.
At least an advance, compared to the state before, where only TWRP 2.8.6.0 was fully operational ( until -> reboot after approx. 29 sec.)
Some how the reboot has to be stopped.
I found a log file unter /cache/recovery/last_log (opend it shortly before the . reboot occoured) an here are the boot protocols. I saw Jan 2020
So some old system files still remain in the linux depths oif the android which seem to cause the reboot.
I managed to extract via TRWP the recovery.log to sd card. I don't know how to attach the log-file here. Just ask for it via PM.
The pity is, whatever I (sucessfully) do - I have appro29 sec. time. Its like mission impossible and the bomb . If this time lock could be broken things would appear possible. Shell script to fix (but I don't have any Idea)?
Best regards an Thank you for your help/ideas.
Dirk
P.S.:
What I tried as well:
Somehow it has a similar effect like here: reboot after 30 sec. reason Firmware corrupted
https://forum.xda-developers.com/xperia-z/help/solved-phone-disconnects-flashmode-t2240960/page2
so maybe someone has proper tested firmeware for 4.1 or 4.3...
Boot loop issue. A pity this didn't work
https://forum.xda-developers.com/showthread.php?t=2513568&page=2
because system.sin flash doesnt finish, because the mobile is switching off due to reboot after 29 sec.
I also tested backup C1905 stock firmware
https://forum.xda-developers.com/showthread.php?t=2703161
CWM and everything installs nicely until comes to flash proceedure, which is nicely starting, but interrupted by the continious reboot...
Maybe a little chance is this, but I can't manage to find sony flash tool 0.6.6 and according driver. Maye somebody still has the stuff?
Solve system.sin flashing error with sony flash tool 09.18.8.8 and sony flash tool 0.6.6
https://forum.xda-developers.com/showthread.php?t=2658952&page=24
Page 24:
Hi all, if anyone is having trouble flashing with flash tool because usb debugging isn't enabled error then do this procedure.......
1. Dowload latest flash tool 0.9.18.8 and also version 0.6.6
2. Try use the latest version first to Flash the tft rom. NOTE: remember the file it has error flashing e.g on my experia sp file system.sin was not able to Flash bcoz usb debugging error (enable usb debugging and unknown sources) ALL THE REST of the files flashed ok!
3.try flash again the rom but this time tick system.sin (or error file) in flashtool to exclude it from flashing. Make sure all other files are included. Also tick all wipe caches options and flash rom without system.sin (or error file).
4. Flash procedure will work. Now disconnect phone and leave it off without restarting it.
5. Uninstall flashtool latest version 0.9.18.8 and install flashtool 0.6.6 old version and open it to Flash the same rom BUT THIS TIME only select the system.sin file (or error file) to be flashed and rest excluded. Make sure all wipe options in flashtool are enabled and Flash! THE FLASH WILL WORK WITHOUT USB DEBUGGING ERROR and your phone will be fixed!
Maybe a chance?