I upgraded my 85' with the "official" wm6 rom and now I cannot go to other roms. The process was solid, meaning I was fully charged, no power loss, and it was synced. I've tried every version of rom available and get the same results. I went through the "brick" thread and I'm affraid I don't quite fit into any category. I can get phone calls and everything works, I just happen to like all of the great ROM's everybody is cooking and want to try them to see which one I favor. I tried using the Hard-SPL and all of the other bootloaders out there and I always get that ERROR [206]. I've tried to restart the machine, and hard reset the 85'. Any good idea's.... Maybe I need to search more? I'll try that.
==============================================================================
UPDATE:
What I should really do is rent a gun, and buy a bullet...
I'm not saying I'm some sort of season veteran of flashing... but I've never had to touch anything after I accept all terms. For some reason, when it came down to the last "Next" form, my phone flashes "Accept" super fast. So what to do?... I push "Yes" soft key fast as I can and it runs like grease lightening... I had to choose SS for the boot loader because it couldn't figure it out... Maybe next time around.
Have you tried to flash a coocked ROM using the microSD card?
Hi,
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?
I did not try to do flash it woth the MicroSD card... I just found out that I could flash it with the MicroSD card about 2 seconds ago. And I wanted to Hard-SPL at the tri-color as a last result in fear of bricking but everything is okay now. As I said before, I've never had to touch my 85' while flashing the rom, it just did it on it's own, but that "official" rom was not about being neglected. And then when I saw it flash something and say "yes", I pushed it and never looked back. It's alllllllllllllllllll good.
I do have one question, is the SSPL preferred over the other choices? Or is there one that is recommended?
Hi joshkrajnak,
How did you solve this problem exactly cos I dont understand what your saying:
http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Click to expand...
Click to collapse
To Clarify: Whenever I went to upgrade my 85' to a different ROM, it wouldn't recognize my bootloader, and then after selecting any of the options, it would give the "ERROR [206]" message and fail miserably with any rom.
What I did to correct it was this: On the "official release" whenever I went to upgrade the ROM, the 85' would show a message at the bottom, the same as any "Notification" would giving me the option to either "confirm" or "dismiss". I did not notice the messages up until it caught my attention out of the corner of my eye on the very last attempt. The messages would quickly appear and disappear, so when the time came and it stated:
Current Rom: 3.25.###.###
Upgrade: 1.##.###
I had to press a confirm notification to continue on or I would get the "206" error message. The quote posted by Binyo is correct, but it does not apply in my situation.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
Although that may be true that some applications may interfere with the upgrade process, I had turned off all applications and killed any services during this process.
guys,my plus got trouble so many days help!
At first I update the kitkat,maybe its low electricity
after reboot it shows 'recovery mode'
but I dont konw what means
Then I start named the earliest fireware as
ko12_sd update and use the sd-card to save it.
As a result,my tablet often shows error and a fall android robot,always like this.
after a few repetitions,the next is bootloop.
Finally,(by some day)it only have
a white usb sign,in seconds charge red and in a constant cycleI have to seach the way.
but by time goes on ,my plus just show the red usb then turn on.unless contect pc it doesnt repeat.
I used to find some ways,but they all need the fastboot-doesnt have with my plus such as
video:'asus dead…solved'
short days before,I find a intel tool.
'xfstk downloader.exe' it likes very useful to fix my tablet ,but I didnt have the necessary files.
I also find a guy who has same problem
his article called 'a fluke…fe171cg'
lean from him,I try to do with myself.
seem that I have no luck like him.the xfstk appear many error .like
'Windriver Error: 0x20000015, Timeout expired'
'FW + OS download*did not complete'
Errors encounter during FW download. Aborting ...
XFSTK-STATUS--Error Code:*0*-Success
etc:crying:
only once it shows
success: FW download completed!os download skipped but my tablet doesnt reboot…
I try use it in another pc,but it is also the same.:silly:
I think a tablet running Intel processors is very special. unbricking it is a big challenge.
Anyone with the same experience?I want to know how flash it correctly.Or my method has wrongs?please give me some Inspired.thanks!!!
All credits for this go to @tora33, c/p from here, he tested it himself, and confirmed it working.
This should bring back your bricked phone from the dead, it's a low level flash procedure, meaning don't play around with it unless absolutely necessary, IT WILL WIPE YOUR PHONE CLEAN!
Charge your mobile phone
download :
New link for qfil file Qfil_zl1_ufs
and put in C:/
download : FlashOne2.0 , put in a folder and extract it ,
run "FlashOne2.0"
How to qfil Flash
When select qfil flash type, press power key, volume up and volume down key at the same time, then the phone enter into qfil mode, connect USB cable with PC, wait for PC install driver automatically, then press ‘Refresh’ button on the tool, serial port will display on UI, select the port you want to flash, and make sure there is no other qcom device connected.
Select corresponding flash zip file, the path of zip file should not contain Chinese and special character. (Under qfil mode, the tool can’t get hardware information, you should check if the software and hardware is matching yourself.)
Press ‘Flash’ button, then start to unzip flash zip file to current folder, but if there is already a corresponding unzip file existing, ‘Decompression folder is exist, re-decompress or not?’ dialog will pop up, if select yes, will re-decompress, else not. After unzip finished, start to flash the phone automatically, and the progress bar display flashing progress, and at the same time, the flashing log will also be shown on UI.
After flash complete or error happened, a notification dialog will pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can this restore bands? I have tried everything and i cant get b20 active.
the links are death , look here
tora33 said:
the links are death , look here
Click to expand...
Click to collapse
fixed
This is very neat. Kind of like an odin-restore program for Le Pro3! Is there any way to get the stock LEX727 file for this?
the link of: le_zl1_qfil_ufs
Continue offline for me
kmkzneguin said:
the link of: le_zl1_qfil_ufs
Continue offline for me
Click to expand...
Click to collapse
New link posted
18:36:37: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
18:36:37: ERROR: function: sahara_main:854 Sahara protocol error
18:36:37: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
If you did the process correctly, it could be a hardware problem (I hope not)
kmkzneguin said:
18:36:37: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
18:36:37: ERROR: function: sahara_main:854 Sahara protocol error
18:36:37: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Hi,
I had the same error trying to revive my x727 while I was using a Qfil file provided by Tora33 on the w w w.leeco.re/topic/1906-helpx720-bricked
2017-06-11 02:18:18 QfilFlashThread >>> 02:18:17: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
2017-06-11 02:18:18 QfilFlashThread >>> 02:18:17: ERROR: function: sahara_main:854 Sahara protocol error
However, i finally succeeded with the qfil file from another link that was provided on page 2 of the leeco.re forum.
Just follow the same guidelines with the "newer" Qfil file.
One downside for me is that my x727 now thinks it is a dual sim x720
@tora33 --> Many many thanks for providing a working solution to revive our devices.
Thanks for this!
Sent from my LEX727 using Tapatalk
Can confirm that this works. It took a lot of tries to work but it did. The things that I had to try before this actually worked include: hold the button combo to get into qfil mode for like 2 minutes, use the original charging cable, use a usb 2.0 port connected to the motherboard (e.g. use the back usb ports if you're using a desktop), holding the power button for a really long time, and charging for like 2-3 hours to make sure that the phone had enough battery. It is a finicky process, but it does work. The phone, if you were on a US rom, now reads as a 720 Chinese edition. That being said, I'm just glad the phone is back up and running lol.
I think, we can flash this rom by this tool. But, name of rom needs to be very short, example 1.zip.
Incidentally.. After the phone comes back to life... Your Le Pro 3 will be running a Developer Version of EUI. However, you can install the latest version of Official EUI version. Unfortunately, the method isn't simple and requires a bit more steps.
After the flashing is successful, your Le Pro 3 may not boot automatically. Press the Power Button for a LOOOONG time... about a a minute or so... for it to leave the QFIL Mode. After a long vibration, the phone will start and will take its sweet time to boot up. Have patience.
Incidentally... after flashing and first boot... you may notice that the Internal Storage is abnormally low... about 10GB Only. A simple solution to restore the internal storage to 32GB / 64GB is by going to Backup/Restore in Settings and Factory Resetting the Phone with the "Format Virtual SD Card" Option selected.
To install the latest Official EUI download the ROM from preferably official sources... Rename the file to Update (The file should read Update.zip... not Update.zip.zip) and Paste in the phone. Using the Inbuilt File Manager.... tap on the Update.zip file and choose upgrade. If this method works... Great...
If not... You will need to Flash TWRP Recovery, Wipe EVERYTHING... and flash the ROM using a Flash Drive and after mounting USB OTG Storage.
To Flash TWRP simply shut down the phone and By Keeping the Volume Down Button Pressed Hit the Power Button to Enter the Fastboot Mode.
Thereafter... flash TWRP Recovery... Boot into TWRP Recovery... Restart TWRP Recovery... Insert the USB Flash Drive Using USB OTG Adapter... and flash the ROM using the Install Tab in TWRP Recovery.
Thanks for ultimate guide, I bricked my phone trying to root it and this guide just helped me revived my dead phone. Thanks a bunch!
Just so everyone knows, when I phone was dead, it was just dead, I pressed the power button for several min, no response, completely black screen, while putting on charge, there was no light. So no sign of life at al.
Now it's revived and I have successfully rooted and installed AICP ROM.
help!
bocondo said:
Thanks for ultimate guide, I bricked my phone trying to root it and this guide just helped me revived my dead phone. Thanks a bunch!
Just so everyone knows, when I phone was dead, it was just dead, I pressed the power button for several min, no response, completely black screen, while putting on charge, there was no light. So no sign of life at al.
Now it's revived and I have successfully rooted and installed AICP ROM.
Click to expand...
Click to collapse
Hello, I have exactly the same problem you had. How did you enter qfil mode when the smartphone was no longer responding. The software flashone me brand to re-connect me in flash mode. But the screen is still black. Thank you in advance.
help!
Hello.
I have a leeco x722. I tested everything I could find but my smartphone is still in hard brick. No reaction, no sound, no vibration, no led, no screen.
It is still detected by the software flashone in QFIL. I have tested a lot of QFIL file but it still marks me "QFIL flash failed, please re-enter into the flash mode!" I try to stay pressed on the volume and power buttons and re-flash but still the same. Would you have a trick to switch to QFIL mode by being in hard brick. Or do you have a QFIL file for x722 and not x720.
Thank you.
QFIL X722
Hey! "Accidentally" Bricked my phone on pure stupidity. Is there any QFIL for the Le Pro 3 Elite X722 I need it so badly to have a chance to bring my phone back to life.
Tried your file but im getting this error:
6:46:51: ERROR: function: rx_data:247 Error occurred while reading from COM port
06:46:51: ERROR: function: sahara_main:854 Sahara protocol error
06:46:51: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Thanks in advance
konevolan said:
Hey! "Accidentally" Bricked my phone on pure stupidity. Is there any QFIL for the Le Pro 3 Elite X722 I need it so badly to have a chance to bring my phone back to life.
Tried your file but im getting this error:
6:46:51: ERROR: function: rx_data:247 Error occurred while reading from COM port
06:46:51: ERROR: function: sahara_main:854 Sahara protocol error
06:46:51: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Thanks in advance
Click to expand...
Click to collapse
Did you solve this problem? I made the same error with the X722 and am in exactly the same situation.
Qfil gives the same error. In an attempt, Qfil was able to download FireHose, but content.xml was in error. After that, I could no longer get Qfil down Firehose. And now this message always appears.
I already know that it is possible, just not how to get around this problem of Qfil.
after do that my storage show 9gb after format data and stock rom install and again formad sd card vs... but i cant up the storage more than 20gb
when i install the stock rom it show i have 32gb storage but computer says 19gb
i installl omni rom its says 24gb and comouter says 19gb again i stuck here what cani do ?
Hello everyone
i decided to write a new post because a bit lost on this one and need the help of a guru
First i've of course read and try to follow this complete guide but failing for me so i'll try to be the most concrete as i bet i'm near the solution
i bricked my moto G5 XT1676 stupidly trying to downgrade it (no error message ==> after boot screen is black and i have a flashing led when i connect)
since i downloaded the original rom and need to get back in fastboot mode
Using ADB tool my device is not seen but checking my com port it is still seen under a COM port (so still a bit of life)
as said i tried to burn to a sdcard the famous mmcblk0 using linux (or rufus under windows) it succeed , create a complete file system with around 48 partitions but inserting into my moto ==> no boot (tried to remove battery and add it again, tried VOL DOWN + POWER)
so i contacted a company called ARYKTECH and had 2 loader.img file dedicated in theory for my device , burn it on sdcard ==> no boot
i found on this forum a file called blankflash_CEDRIC and tried it ==> it failed each time with a sahara protocol error
then i tried QFIL tool with a programmer file comming from a file with a name called 8675_W00 ==> same, failed on sahara protocol error
I've read there is a tool called TOOLSTUDIO 4.6 that could help but a nice trojans is hidden in it
I also read SAHARA eerror come from the fact it would not be the good programmer file
As you understand i'm turning around and need just someone to highlight me a bit
neness2000 said:
Hello everyone
i decided to write a new post because a bit lost on this one and need the help of a guru
First i've of course read and try to follow this complete guide but failing for me so i'll try to be the most concrete as i bet i'm near the solution
i bricked my moto G5 XT1676 stupidly trying to downgrade it (no error message ==> after boot screen is black and i have a flashing led when i connect)
since i downloaded the original rom and need to get back in fastboot mode
Using ADB tool my device is not seen but checking my com port it is still seen under a COM port (so still a bit of life)
as said i tried to burn to a sdcard the famous mmcblk0 using linux (or rufus under windows) it succeed , create a complete file system with around 48 partitions but inserting into my moto ==> no boot (tried to remove battery and add it again, tried VOL DOWN + POWER)
so i contacted a company called ARYKTECH and had 2 loader.img file dedicated in theory for my device , burn it on sdcard ==> no boot
i found on this forum a file called blankflash_CEDRIC and tried it ==> it failed each time with a sahara protocol error
then i tried QFIL tool with a programmer file comming from a file with a name called 8675_W00 ==> same, failed on sahara protocol error
I've read there is a tool called TOOLSTUDIO 4.6 that could help but a nice trojans is hidden in it
I also read SAHARA eerror come from the fact it would not be the good programmer file
As you understand i'm turning around and need just someone to highlight me a bit
Click to expand...
Click to collapse
Same issue here, mainboard fault for sure. Hope you will find another one it in Amazon, eBay. etc. No other solution at this point.