Database Develop

Start EBL error when flashing. Help please.

Hi!
I was following this guide:
http://forum.xda-developers.com/showthread.php?t=2195753&highlight=ebl+writing+start
After I get to the flashing part of Step2 and select LGP920_110622.dll and 28bRTbig_AP.bin but after selecting the port 1 and clicking start, my I connect the phone while holding Vol up and it starts the process but after showing "EBL Writing start" It will stall there then eventually show:
Start EBL error!
Error WM Progress MSG twice and above that says Download FAIL! (95 sec).
I am running Windows 7 64 bits if that helps
Thanks!

[Q] Bricked phone? used to work fine!

Currently my Xperia Z stopped working. I hadn't used it in a while, since the connector broke off. I got the connector fixed, and the phone seems to function, but it wont boot.
It boots to the SONY logo, and then goes black. The thing i have tried:
- Flash stock rom using Flashtool, i keep getting this:
Code:
29/004/2014 10:04:14 - INFO - <- This level is successfully initialized
29/004/2014 10:04:14 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
29/004/2014 10:04:19 - INFO - Device connected in flash mode
29/004/2014 10:04:50 - INFO - Selected C6603 / 10.4.1.B.0.101 / CE
29/004/2014 10:04:50 - INFO - Preparing files for flashing
29/004/2014 10:04:51 - INFO - Please connect your device into flashmode.
29/004/2014 10:04:51 - INFO - Opening device for R/W
29/004/2014 10:04:52 - INFO - Reading device information
29/005/2014 10:05:16 - INFO - Unable to read from phone after having opened it.
29/005/2014 10:05:16 - INFO - trying to continue anyway
29/005/2014 10:05:16 - INFO - Start Flashing
29/005/2014 10:05:16 - INFO - Processing loader
29/005/2014 10:05:16 - INFO - Checking header
29/005/2014 10:05:16 - INFO - Ending flash session
29/005/2014 10:05:16 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
29/005/2014 10:05:16 - ERROR - Error flashing. Aborted
29/005/2014 10:05:16 - INFO - Device disconnected
29/005/2014 10:05:17 - INFO - Device connected in flash mode
Then i tried using Fastboot to install a new boot.img, which is succesfull
Code:
Flashing kernel
< waiting for device >
sending 'boot' (11048 KB)...
OKAY [ 0.355s]
writing 'boot'...
OKAY [ 0.539s]
finished. total time: 0.902s
Done !
Press any key to continue . . .
I'm able to get into Fastboot and Flashmode so the USB seems to work fine. After using fastboot i got a litte further, now it boots to SONY, then i get "the software update failed, make sure that your phone is connected to the computer and try again."
I tried using EMMA, but i have no idea what to do there. It keeps "updating the services"
Code:
Preparing service...
...service successfully prepared.
Sending data to the device...
...data sent successfully.
Finalizing service...
...successfully finalized.
Service execution completed in 139 seconds
Success
I also tried PC Companion which complains that i use unofficial software.
Anyone has any idea what else i can do?

tharealmb said:
Currently my Xperia Z stopped working. I hadn't used it in a while, since the connector broke off. I got the connector fixed, and the phone seems to function, but it wont boot.
It boots to the SONY logo, and then goes black. The thing i have tried:
- Flash stock rom using Flashtool, i keep getting this:
Code:
29/004/2014 10:04:14 - INFO - <- This level is successfully initialized
29/004/2014 10:04:14 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
29/004/2014 10:04:19 - INFO - Device connected in flash mode
29/004/2014 10:04:50 - INFO - Selected C6603 / 10.4.1.B.0.101 / CE
29/004/2014 10:04:50 - INFO - Preparing files for flashing
29/004/2014 10:04:51 - INFO - Please connect your device into flashmode.
29/004/2014 10:04:51 - INFO - Opening device for R/W
29/004/2014 10:04:52 - INFO - Reading device information
29/005/2014 10:05:16 - INFO - Unable to read from phone after having opened it.
29/005/2014 10:05:16 - INFO - trying to continue anyway
29/005/2014 10:05:16 - INFO - Start Flashing
29/005/2014 10:05:16 - INFO - Processing loader
29/005/2014 10:05:16 - INFO - Checking header
29/005/2014 10:05:16 - INFO - Ending flash session
29/005/2014 10:05:16 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
29/005/2014 10:05:16 - ERROR - Error flashing. Aborted
29/005/2014 10:05:16 - INFO - Device disconnected
29/005/2014 10:05:17 - INFO - Device connected in flash mode
Then i tried using Fastboot to install a new boot.img, which is succesfull
Code:
Flashing kernel
< waiting for device >
sending 'boot' (11048 KB)...
OKAY [ 0.355s]
writing 'boot'...
OKAY [ 0.539s]
finished. total time: 0.902s
Done !
Press any key to continue . . .
I'm able to get into Fastboot and Flashmode so the USB seems to work fine. After using fastboot i got a litte further, now it boots to SONY, then i get "the software update failed, make sure that your phone is connected to the computer and try again."
I tried using EMMA, but i have no idea what to do there. It keeps "updating the services"
Code:
Preparing service...
...service successfully prepared.
Sending data to the device...
...data sent successfully.
Finalizing service...
...successfully finalized.
Service execution completed in 139 seconds
Success
I also tried PC Companion which complains that i use unofficial software.
Anyone has any idea what else i can do?
Click to expand...
Click to collapse
As your bootloader is unlocked, what if you flash a kernel of a custom rom, that has a recovery included? From there you could try to flash a rom...

St.Jimmy90 said:
As your bootloader is unlocked, what if you flash a kernel of a custom rom, that has a recovery included? From there you could try to flash a rom...
Click to expand...
Click to collapse
you're a lifesaver. Haven't used android in a while (have WP 8.1 right now). Installed TWRP boot and after that it worked flawless... My nephew will be greatfull :good:

Solved - Z3C Downgrade for root fail despite reading all the forums

I have a D5803 that I'm trying to revert back to 4.4.4 to root. I am getting stuck at the downgrade step though and no fix I've read anywhere corrects the issue! Here's my Flashtool log:
Code:
19/005/2015 14:05:55 - INFO - (FlashJob.java:34) - Please connect your device into flashmode.
19/006/2015 14:06:00 - INFO - (MainSWT.java:141) - Device disconnected
19/006/2015 14:06:15 - INFO - (MainSWT.java:145) - Device connected in flash mode
19/006/2015 14:06:15 - INFO - (USBFlashWin32.java:20) - Opening device for R/W
19/006/2015 14:06:15 - INFO - (X10flash.java:486) - Start Flashing
19/006/2015 14:06:15 - INFO - (X10flash.java:239) - Processing loader.sin
19/006/2015 14:06:15 - DEBUG - (X10flash.java:240) - loader.sin : header size : 1024
19/006/2015 14:06:15 - INFO - (X10flash.java:218) - Checking header
19/006/2015 14:06:15 - DEBUG - (X10flash.java:222) - Sending part 1 of 1
19/006/2015 14:06:15 - ERROR - (X10flash.java:254) - Processing of loader.sin finished with errors.
19/006/2015 14:06:15 - INFO - (X10flash.java:546) - Ending flash session
19/006/2015 14:06:15 - ERROR - (X10flash.java:519) -
19/006/2015 14:06:15 - ERROR - (X10flash.java:520) - Error flashing. Aborted
19/006/2015 14:06:16 - INFO - (MainSWT.java:145) - Device connected in flash mode
At that point, nothing happens anymore. I have reinstalled Flashtool (twice), upgraded my Java, rerun the driver installation from Flashtool, downloaded the firmware again (this was the firmware from the post at the start of http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343), tried a different firmware option (23.0.1.A.5.77 - Unbranded - USA (1289-7524) this time), and downloaded the Support Zone in PC Companion. All to no avail. What else can I try?
Alternatively, does anyone know if there's a way to just root Lollipop directly without a downgrade? I mostly just want root access for TitaniumBackup and Tasker. Is a direct Lollipop root on the way?

Turns out I was using the 32 bit version of Flashtool rather than the 64 bit. FYI, for anyone else doing this, you pick 32 or 64 bit based on your computer OS, not on your phone....

nataelj said:
Turns out I was using the 32 bit version of Flashtool rather than the 64 bit. FYI, for anyone else doing this, you pick 32 or 64 bit based on your computer OS, not on your phone....
Click to expand...
Click to collapse
I had a similar error, although for different reasons. It's scary searching for that halfway through the process, isn't it? :crying:
But what joy when the downgrade finally works!!

X98 Air III M5C5 not boot

Hi guys.
I think I have bricked my one week ago purchased device. Screen stucks to Chinese logo and does not boot up.
That happenned after accidental stock UI freeze. I am only able to get into DNX mode.
I tried to fix using Manufacturing Flash Tool to reflash stock ROM, but flashing process stops at 5% and I get the message "IFW flash failed". I have read all similar threads but I do not know what the condition of device is to continue. Wouldn't be that nice to make it worse. Please help.
Thanks in advance.
P.S. I apologise for my bad English.

Matinaki said:
Hi guys.
I think I have bricked my one week ago purchased device. Screen stucks to Chinese logo and does not boot up.
That happenned after accidental stock UI freeze. I am only able to get into DNX mode.
I tried to fix using Manufacturing Flash Tool to reflash stock ROM, but flashing process stops at 5% and I get the message "IFW flash failed". I have read all similar threads but I do not know what the condition of device is to continue. Wouldn't be that nice to make it worse. Please help.
Thanks in advance.
P.S. I apologise for my bad English.
Click to expand...
Click to collapse
At last I resolved problem. After a copy-paste of the CUSTOM_CONFIG.INI file manually to C:\Program Files(x86)\Intel\MFT the problem resolved.
Now I can get into bootloader.

still not flashing ability
Well,
I resolved previous problem but still tablet does not boot. I try to flash rom through DNx mode, but bar stops at 10% and I get the message: timeout to enum adb (TIMEOUT = 180)
MTF SETTINGS
SOC devices VID 8087 PID 0A65
Android device VID 8087 PID 09EF
LOG:
# Manufacturing Phone Flash Tool Logs generated on 2016-02-09T20:58:08
######################################
#### Flash tries 1 ####
#### Flash failure 1 ####
#### Flash success 0 ####
#### ####
#### Fail IFWI 0 ####
#### Fail ENUM 1 ####
#### Fail Modem 0 ####
#### Fail OS 0 ####
######################################
02/09/16 20:52:36.131 INFO : Manufacturing Flash Tool V 6.0.43 (build on Sun May 18 12:29:29 PDT 2014)
02/09/16 20:52:36.131 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
02/09/16 20:52:36.162 INFO : Using Qt version: 4.8.1
02/09/16 20:52:36.162 INFO : Using XFSTK version: 1.5.5.
02/09/16 20:52:36.162 WARNING: Please select a flash file…
02/09/16 20:52:53.146 INFO : Loading Flash file (C:/Users/Γιώργος/Desktop/Teclast/rom debloaded/X98 Air III (M5C5) GoogleNow/flash.xml)
02/09/16 20:52:53.162 INFO : GP_Flag is set to 0x80000045
02/09/16 20:52:53.162 INFO : Ready to flash!
02/09/16 20:53:33.258 INFO : do_new_medfield_device STARTING TO FLASH
02/09/16 20:53:33.258 INFO : Port 0/0/1 #0: DNX/droidboot phase – SN : Baytrail00000832
02/09/16 20:53:38.268 INFO : Port 0/0/1 #0: Booting to droidboot.img success – SN : Baytrail00000832
02/09/16 20:56:36.484 ERROR : Port 0/0/1 #0: Device on port 0/0/1 #0 timeout to enum adb (TIMEOUT = 180)
Any idea what is going on?
Please help.
Thanks

Honor play hard brick

my phone stuck at erecovery mode . i did flash it with new rom using the dc phoenix but it turn out failed.
here is the progress :
Build number: :COR-L29 9.0.0.193(SP53C636E2R1P12)
Model: COR-L29
Battery state: 4885mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked
Process identifier:18080917
Getting build number...
Getting base version...
Getting cust version...
Getting preload version...
Erasing ver .. .
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Writing rescue_recovery_kernel partition
rescue_recovery_kernel partition UPDATE ...OK
Writing rescue_recovery_ramdisk partition
rescue_recovery_ramdisk partition UPDATE ...OK
Writing rescue_recovery_vendor partition
rescue_recovery_vendor partition UPDATE ...OK
USB Device REMOVAL
Type: @OEM83.inf,%tplinkfastboot%;Android Bootloader Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&118960b2&0&2
Looking for device in upgrade mode...
USB Device INSERTION
Type: @OEM148.inf,%busfilter.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_107E
Instance id: 5&118960b2&0&2
COM11: DBAdapter Reserved Interface (COM11)
COM12: Android Adapter PCUI (COM12)
8/29/2019 3:56:10 PM Starting to write device in UPGRADE mode...
Device found: XTX7N18830004739
8/29/2019 3:56:38 PM start to write update file
File to update: UPDATE_SD.APP
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Process identifier:18080974
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 43: SHA256RSA...OK
Writing file 2 of 43: CRC...OK
Writing file 3 of 43: CURVER...OK
Writing file 4 of 43: VERLIST...
Error downloading file 4 of 43
Error writing software
8/29/2019 3:57:16 PM Writing device finished with ERROR
anyone can help me with this ?