Firmware Upgrade Guide For Amlogic S805, S905 Devices - Android Stick & Console AMLogic based Computers

Upgrade Guide can help you in reflashing your device based on Amlogic S905 S805 SoC
Thanks for materials and answering questions to Ugoos Blog and ChinaGadgetReviews
What you need:
Image file
Host PC
USB OTG Cable
TF Card (Micro SD or SD)
USB_Burning_Tool_v2.0.5.15 (maybe another v)
Supported host OS: Windows XP (32/64bit) Windows 7 (32/64bit) Windows 8 (32/64bit) Windows 10 (32/64bit)
Start:
1. You need to download the firmware archive. You should be sure, that using current firmware fits for your device otherwise it could cause harmful consequences.
2. Unpack zip archive. In directory, you can find firmware file “img” and USB_Burning_Tool_v2.0.5.15.
3. Installing USB_Burning_Tool_v2.0.5.15. During installation, you should allow to install additional drivers for amlogic devices detection.
4. Run and Change to English language in menu
{
"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"
}
5. Open firmware file (File-Import Image) and press start.
6. Connect device to PC via otg usb using usb A type cable. Device turns on automatically.
7. When PC detects device, reflashing starts automatically. If it has not happened, you should check amlogic drivers in device manager and repeat it’s installing.
8. After reflashing device you should see “result: burning successful” message and disconnect device from host PC
9. Disconnect device from host PC.
Reflashing firmware from recovery menu:
1. Insert usb flash drive with OTA update package in Box
2. Hold recovery button and turn on the device
3. In recovery menu choose option “update from ext”
4. System let you choose sd card or usb drive. You should choose udisk.
5. Then you choose update zip file previously downloaded on usb drive and system start uploading, checking and installing firmware.
If you suddenly (!!!!) bricked your device:
The easiest way to solve this, without need of short circuit of the NAND pins, is to use Amlogic Bootcard Maker to make a bootable micro SD card with your device stock firmware.
Just upload firmware image on (Micro) SD Card and put it in your device
You will be able to enter into recovery and the firmware will be flashed automatically. When the TV BOX reboots, remove the micro SD Card, this step is very important, wait 4-5 minutes and the update will completed.
Thanks for materials and answering questions to Ugoos Blog and ChinaGadgetReviews

My mxq box shuts my toshiba tv off when I connect it any ideas to solve this issue

Dan82 said:
My mxq box shuts my toshiba tv off when I connect it any ideas to solve this issue
Click to expand...
Click to collapse
Shuts, do you mean power off or just black screen? If power on and just black screen it may can be inappropriate resolution. If power off, Looks like hardware issue in MXQ make a short circuit in HDMI and power security system turns of TV screen. Did you try to connect device to another screen?

I have MK809V, and in recovery menu I can't choose anything because there is no any buttons, please help

Ssshin1010 said:
I have MK809V, and in recovery menu I can't choose anything because there is no any buttons, please help
Click to expand...
Click to collapse
To operate in recovery menu you can use usb mouse and move it very slightly

This guide looks very useful and I may be able to use it but where can i get the files from? Firmware and usb tool?
Here is my situation:
I have this MXQ android box that I believe is AMlogic. Its is an s805 if that helps.
I recently purchased a newer model (S905) and was going to use the S805 for another room. When I plugged in the S805 again the blue light was solid and I had no display. I tried on different TV's with different HDMI cables. I also tried using an AV cable. Also tried the AV reset option. Even tried the PSU from the S905 unit I had. No matter what I do I can;t get a display. I'm sure it's bricked but wanted to confirm and see if maybe there was a way I could reflash it. Can anyone assist?

grod777 said:
This guide looks very useful and I may be able to use it but where can i get the files from? Firmware and usb tool?
Here is my situation:
I have this MXQ android box that I believe is AMlogic. Its is an s805 if that helps.
I recently purchased a newer model (S905) and was going to use the S805 for another room. When I plugged in the S805 again the blue light was solid and I had no display. I tried on different TV's with different HDMI cables. I also tried using an AV cable. Also tried the AV reset option. Even tried the PSU from the S905 unit I had. No matter what I do I can;t get a display. I'm sure it's bricked but wanted to confirm and see if maybe there was a way I could reflash it. Can anyone assist?
Click to expand...
Click to collapse
Hi, usualy when you download firmware, there is instalation file for reflashing application. ugoos.net/downloads have firmware for mxq S805 model, but you ned to make sure which wifi chip you have on your device. The best way to find out it is to open the housing case and check by your own eyes

Appreciate the help. I opened the unit. There are several circuit boards. How do I determine the wifi chip? On the site you put a link to, where is the reference to the wifi that would be on my unit?

I just completed the shorting out NAND method. I saw the light go out and heard the windows sound indicating a new device. I opened the usb burning tool and saw the hub5 device connected. I chose the image I downloaded (MXQ_112k4.img) and received the error attached.

So I kept trying but no luck . I decide to try an older version of the USB Burning tool and still kept getting the error. I tried again and success. I opened tool, loaded image file, held in the reset button using paper clip, plugged in using OTG cable and waited for tool to connect to it. Then clicked start and it ran 100%.
I plugged into my TV and I started to get the Google TV screen. It got to a point where it said click next to setup. Remote would not respond so I tried keyboard but there was no next to click on. I guess I'll have to try another image.

grod777 said:
So I kept trying but no luck . I decide to try an older version of the USB Burning tool and still kept getting the error. I tried again and success. I opened tool, loaded image file, held in the reset button using paper clip, plugged in using OTG cable and waited for tool to connect to it. Then clicked start and it ran 100%.
I plugged into my TV and I started to get the Google TV screen. It got to a point where it said click next to setup. Remote would not respond so I tried keyboard but there was no next to click on. I guess I'll have to try another image.
Click to expand...
Click to collapse
Please check which wifi you have (just open the housing case very carefully and take a photo from both sides) and may suggest you several firmwares. and take a photo of RC also

Fido what exactly am I looking for? I opened it up and there are several chips. The board itself says MXQ.
BTW, I found a package that actually works. I used the sd card method and it loaded and booted up. Only real issue I have is that wifi does not work only hard wire. When it boots up it says MXQ first then MBOX. I'm sure its a driver issue but the packages that I have found don't mention anything about wifi chip-unless I am missing it.

Olá pessoal, Eu tenho um projetor de marca VIVIBRIGHT modelo GP90UP que deu problema no módulo Android dele com processador s805 chip wi-fi Azurewave aw-nH655,está em boot infinito, porém não consigo encontrar de jeito nenhum uma forma de entrar no modo recovery,não tem usb não tem chip nand e não tem cartão sd, é um tipo de conexão PC-EXPRESS, já tentei usar uma pinça nos pontos de teste pointer da placa na tentativa de acessar o recovery e não deu em nada.
Me ajudem por favor

I can't find a firmware for MXQ android TV box, CPU Amlogic S805, motherboard is S805Q_V2.0 2016.08.11, WiFi chip is S9083C.

Quiero actualizar mi MXQ Box Amlogic hx805a Android 4.4.3 a una version mayor a 5.0. Alguien me puede ayudar?

I want firmware for my device. It has 4gb ram and 64gb rom. Mxq 805 model (Amlogic). I tried every thing available on internet but could not find any solution. The device not turning on , but when connect to pc using usb shows connected in Amlogic usb tool. I am also sharing images if some has the same box, do copy the firmware from their box using some copying tool and share it with me. I will be very thankful.

I need too

To many different MXQ device revisons to choose from, you have to know which memory, flash storage, wi-fi chip do you have, to find matching firmware.
Search in this topic on russian forum - h**ps://4pda.to/forum/index.php?showtopic=621980
Maybe is not S805, but box with S905 cpu ?

totonji said:
I need too
Click to expand...
Click to collapse
If you find somewhere please do share it with me

Hi All,
I have an old MiniX Neo X6 running with Amlogic S805 left unused for quite a while. Recently, I have tried several times to find a way to install Armbian on the device. I tried googling but I did not find a completed guide and resource on how to do the work in details. Can anyone help providing me a custom ROM (rooted) or guide me to flash Linux on the box with thanks.

Related

Stock firmware to unbrick dead t95z plus.

Hi guys. I tried to flash my nearly new t95z plus 2/16 ap6255 with atvXperience rom with flash tool and something went wrong.
Now it only lights the case around on blue and doesnt boot (no hdmi signal is sent, empty lcd screen on the case). It cant also be found by flashing tool while connected to PC ( with or without Fn button pressed)
Id like to try card burner method but cant find proper firmware, will appreciate any help.
Please refer to logic board photos I uploaded if Im correct with identifying my hardware as Its my first amlogic box.
I want also prepere for short pins method if card wont work. But while googling t95z short pin I always get different looging logic boards so cant actually use tutorials.
If you guys could show which exactly pins do I need to short on the photo I would be more than gratefull.
{
"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"
}
Wysłane z mojego MIX 2 przy użyciu Tapatalka
Bricked my t95z plus ap6255 2GB/16GB days ago. I had no led lights, no clock display, no signal, no boot & no recovery when holding reset button and plugging in, so SD card method was a no go. Hear me out as I'm guessing SD card method may not work for you either. The easiest and safest method of fixing the device is by using the amlogic usb burning tool. You need a usb male to male cord (data transfer cord) plus some patience. You can get instructions and tool at the end of this post...
Some videos on amlogic devices (other boxes) show holding reset pin with toothpick or a q-tip and connecting the male to male USB then flashing happens, but this method won't work with the t95z plus, the device will light up and amlogic usb burning software will attempt to write but will fail due to low power. Needless to say what worked for me was... first pressing & holding the reset button, next plug in the device to a power source, then finally plug in the USB cable and release the reset button once the flashing begins. This device needs to be plugged in to power source for flashing to work.
Link to amlogic software/instructions
https://www.cnx-software.com/2018/0...BRAB&usg=AOvVaw1VTva_XVvyti2SZQTFeNn2&ampcf=1
Link to Support/Firmware & Roms
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s912
Short pin photos & info
http://freaktab.com/forum/main-category/main-forum/637675-nand-chip-mask-rom-mode-short-location
I hope this helps you out or at least gets you closer to fixing your device. Make sure you find correct ROM. You need to know things such as if you have 2GB/16GB or 3GB/32GB for example, and also need to know if box is older normal RAM model or newer LP RAM model. My device is a 2GB/16GB normal ram, S912, ap6255 model by Weily. The firmware I found and used was the Sunvell T95Z Plus box firmware running android nougat v7.1.2, build T5ZP1016.
One last thing is I've read of some issues when running certain windows 10 versions. If your on windows 10, run installer with compatibility set to windows 7 and also run it as administrator. also run the flashing software the same way. Worked for me.
Hopefully this will help you out. Good luck with your recovery! :fingers-crossed:
Thank you so much mate. This is where I made a big mistake. I tr8ed to flash it with USB male to male connected only. Thats why it must have bricked.
What firmware did you use to recover yours mate?
Still cant find stock firmware for my ap6255 wifi chip. I could only find one to 3/32gb edition while my is 2/16. Is it the same firmware if wifi chip fits ?
Can I recover it with some custom rom or it has to be stock?
Wysłane z mojego MIX 2 przy użyciu Tapatalka
I flashed mine with poison ROM found on XDA. Worked like a charm. I flashed it with Poison ROM v4.1 initially after messing up my t95z plus, but last night after writing you I saw they've added version v4.3 so Im now running that. Follow the steps carefully as you need to flash to the correct version of Android v7.1.2 stock first to get updated bootloader. The Stock version you use depends on your RAM type (LP RAM/Older RAM) but it comes with twrp recovery baked in. Then you flash poison ROM using a .zip file in twrp recovery which is baked In. For my machine I used Older Ram method.
Poison ROM
https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
It's based on the 3GB/32GB version of the T95Z Plus build 1076 for S912 devices and works with my ap6255 wifi 2GB/16GB model. Says it works with....
v3.0+ and newer is compatible with 1/8, 1/16, 2/8, 2/16, 3/16 and 3/32 variants.
If you need image to flash without twrp and want device closest to the way it was I stumbled upon this link but can't recall where I found it.
It's labeled as for... T95Z PLUS S912 2GB 16GB AP6255 Nougat Build 1013 Multi Wifi. it runs fine on "my t95z plus" and it is Android v7.1.2 but can't be sure it'll run on everyone's. If yours is good as garbage maybe it's worth trying, but poison ROM is much better, runs smoother, better updated Google play store, and other apps like kodi v17.6
Cheers!
https://mega.nz/#F!GvQBmIjS!WTmS0qpRz4Xb_ocVnaC5hg
Thank you mate. Everything is worth of trying.
My box is only recognized when i short pins on logoc board. Unfortunately all roms I tried ends at 2% with following error:
[0x10105004]Romcode/initialize DDR/Read initialize status/Error result
[emoji848]
Youre the boss mate! Top Man! Connected to Pc with shorted memory pins, now flashing LP DDR3 ram version from poison rom post. Its going quite slow but didnt get any error so far! Fingers crossed!
Update. I forgot to connect power source and it flashed properly by USB cable only with no errors
Waiting for initial boot now
Wysłane z mojego MIX 2 przy użyciu Tapatalka
energy_drink said:
Youre the boss mate! Top Man! Connected to Pc with shorted memory pins, now flashing LP DDR3 ram version from poison rom post. Its going quite slow but didnt get any error so far! Fingers crossed!
Update. I forgot to connect power source and it flashed properly by USB cable only with no errors
Waiting for initial boot now
Wysłane z mojego MIX 2 przy użyciu Tapatalka
Click to expand...
Click to collapse
Could you please upload an image that shows what pins did you shorted to start the flashing. I have the same issue as you did and I can not find the pins I need to short to flash the rom.
Thank you in advance.
Ramestin said:
Could you please upload an image that shows what pins did you shorted to start the flashing. I have the same issue as you did and I can not find the pins I need to short to flash the rom.
Thank you in advance.
Click to expand...
Click to collapse
Only in very rare cases should you need to short pins. Use USB male to male data transfer cable & Flashing software method is best. Sd card/software writing method can be hit or miss. A cut q-tip or toothpick will be needed to insert into the audio jack hole (reset button straight at bottom inside), if you press it correctly you'll feel a light click.
Steps... Open software on your pc and load the .img firmware... only continue if no errors! keep software open then connect box power supply while you Press and hold reset button inside the audio jack. Then you connect usb cable & don't release the reset button until the flashing begins. You will see this on the pc software. Again, "USB method only" without ac/dc usually isn't enough power for the box that's why box power supply is needed. NOTE... This must be done with (main) USB port 1 on box, USB 2 will not flash for you. If you need pin short method still you can search here....
Pins different for each box, cannot guarantee correct photo but this site will help.
https://forum.freaktab.com/forum/ma...637675-nand-chip-mask-rom-mode-short-location
donmecca81 said:
Tylko w bardzo rzadkich przypadkach należy zwierać szpilki. Użyj kabla USB męskiego do męskiego do przesyłania danych i flashowania oprogramowania jest najlepsza. Metoda pisania na karcie SD/oprogramowaniu może być trafiona lub chybiona. Aby włożyć do otworu gniazda audio (przycisk resetowania bezpośrednio na dole wewnątrz), potrzebna będzie odcięta patyczek lub wykałaczka, jeśli naciśniesz go prawidłowo, poczujesz lekkie kliknięcie.
Kroki... Otwórz oprogramowanie na komputerze i załaduj oprogramowanie układowe .img... kontynuuj tylko, jeśli nie ma błędów! pozostaw oprogramowanie otwarte, a następnie podłącz zasilanie skrzynki podczas gdy ty Naciśnij i przytrzymaj przycisk resetowania wewnątrz gniazda audio. Następnie podłączasz kabel USB i nie zwalniaj przycisku resetowania, dopóki nie zacznie migać. Zobaczysz to na oprogramowaniu komputera. Ponownie, "tylko metoda USB" bez prądu przemiennego/stałego zwykle nie wystarcza dla urządzenia, dlatego potrzebne jest zasilanie skrzynki. UWAGA... Należy to zrobić z (głównym) portem USB 1 na pudełku, USB 2 nie będzie migać. Jeśli potrzebujesz metody pin short, nadal możesz szukać tutaj....
Piny różne dla każdego pudełka, nie mogą zagwarantować prawidłowego zdjęcia, ale ta strona pomoże.
https://forum.freaktab.com/forum/main-category/main-forum/637675-nand-chip-mask-rom-mode-shor
Click to expand...
Click to collapse
Hi. I have a T95z plus Sunvell 912, before uploading a new ROM and after opening the USB Burn Tool it found my box without any problems, but I unchecked Erase Botloader and it did not start anymore, only the LEDs are lit no reaction. Tried to repair botloader with Burn Card Maker, everything is loaded to sd card but it doesn't work. Shorting the pins also did not help, is the board damaged? Please help

[SOLVED] BRICKED x96mini (Amlogic S905W) - red LED no display

Long story short, I accidentally deleted my bootloader flashing atvXperience (aml_sdc_burn.ini had "erase_bootloader = 1" in it and sh*t hit the fan).
Result: red LED, no screen, no magic sdcard, no recovery, lots of tears :crying:
Searching for solutions I found this very helpful blog post: https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
but... my board was different (Q6X V4.0 17392) and the pin wasn't the same or even in the same general place.
images:
{
"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"
}
The advise in that blog post allowed me to find the correct pin for my board using a multimeter and some time&luck
I then describe the procedure that revived my box:
1.- watch image and mimic wire solder (marked with a red circle and GND label)
2.- short marked resistor using the grounded wire and plug power. Hold the wire for 2-3s and disconnect wire from resistor. Unplug power.
3.- connect usb to pc and otg connector on board. When pc recognizes it, plug power. (if you don't plug in the power, the board has not enough minerals energy and the flashing fails.
4.- use flashing utility to reflash your device (not explaining that here; lots of advise on other threads).
Also, if someone needs the stock Android 9 firmware, here it is:
https://mega.nz/#!UcQ12KpL!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I hope this helps
DanAlucard said:
Long story short, I accidentally deleted my bootloader flashing atvXperience (aml_sdc_burn.ini had "erase_bootloader = 1" in it and sh*t hit the fan).
Result: red LED, no screen, no magic sdcard, no recovery, lots of tears :crying:
Searching for solutions I found this very helpful blog post: https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
but... my board was different (Q6X V4.0 17392) and the pin wasn't the same or even in the same general place.
images:
The advise in that blog post allowed me to find the correct pin for my board using a multimeter and some time&luck
I then describe the procedure that revived my box:
1.- watch image and mimic wire solder (marked with a red circle and GND label)
2.- short marked resistor using the grounded wire and plug power. Hold the wire for 2-3s and disconnect wire from resistor. Unplug power.
3.- connect usb to pc and otg connector on board. When pc recognizes it, plug power. (if you don't plug in the power, the board has not enough minerals energy and the flashing fails.
4.- use flashing utility to reflash your device (not explaining that here; lots of advise on other threads).
Also, if someone needs the stock Android 9 firmware, here it is:
https://mega.nz/#!UcQ12KpL!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I hope this helps
Click to expand...
Click to collapse
thank you for sharing this. by the way this is the first time i read that there is already android 9 for x96 mini. have you already tried to install this rom? do you have screenshots also?
thanks sir.
claishem said:
thank you for sharing this. by the way this is the first time i read that there is already android 9 for x96 mini. have you already tried to install this rom? do you have screenshots also?
thanks sir.
Click to expand...
Click to collapse
I don't have screenshots right now, as I'm not in my home right now, but that is the exact rom that came installed on my box. Asked the seller for it and he sent it. Flashed and tested. Android 9.
Also, atvXperience is working on an android 9 version. Seems like amlogic distributed a pie sdk. Can't confirm though.
My box is a 2g/16g version. Can't assure it will work on 1g/8g or 4g/32g
DanAlucard said:
I don't have screenshots right now, as I'm not in my home right now, but that is the exact rom that came installed on my box. Asked the seller for it and he sent it. Flashed and tested. Android 9.
Also, atvXperience is working on an android 9 version. Seems like amlogic distributed a pie sdk. Can't confirm though.
My box is a 2g/16g version. Can't assure it will work on 1g/8g or 4g/32g
Click to expand...
Click to collapse
thanks. by the way, i attempted to flash the android 9 img in the link you provided but when i import it in the usb burning tool it says something like img parse error. i wonder why.
claishem said:
thanks. by the way, i attempted to flash the android 9 img in the link you provided but when i import it in the usb burning tool it says something like img parse error. i wonder why.
Click to expand...
Click to collapse
Well... I make the magic sdcards on linux manually, so I can't test the usb burning tool as I don't have any windows machines
This is the original link the seller sent me: https://mega.nz/#!QXhWTCiQ!NPjAQlFLUHwVxf7y_Lw9V4vZAaCYeuD6f1RpqwgmCH8
I can reupload to see if that is the problem, but I can't do it before monday :angel:
Hi recently I was trying to update Atvxperience rom but by mistake i installed s905x version. Thus it ended with a red light and black screen... I have no usb to usb cable so I was using sd card method for flashing.. Now the issue is that i have a different board and test pins as shown in your post i could not find in my board. Now help please. My board is this. Please help me.
mmrx said:
Hi recently I was trying to update Atvxperience rom but by mistake i installed s905x version. Thus it ended with a red light and black screen... I have no usb to usb cable so I was using sd card method for flashing.. Now the issue is that i have a different board and test pins as shown in your post i could not find in my board. Now help please. My board is this. Please help me.
Click to expand...
Click to collapse
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
My board also is Q6X V4.0 17392, but my eMMc chip is SK Hynix. I tried to short these 2pins but nothing happend. The light flashes red and blue continuously, and the PC can't detect the board , though my PC can detect X96 MAX+.:crying:
update: I found the solution. In fact, I didn't flash the bootloader. I shorted the pin in the green circle and ground with TF card inserted and it began to flash the firmware automatically...
mmrx said:
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
Click to expand...
Click to collapse
I´m shorting the two gold colored circles and it still doing nothing.
In my version with a toshiba nand flash I had to short this resistor here for it be detected by the pc again:
Napalm_PT said:
In my version with a toshiba nand flash I had to short this resistor here for it be detected by the pc again:
Click to expand...
Click to collapse
Hi what firmware did you use for the Toshiba Chip i cant find firmware for mine anywhere
mmrx said:
thanks it worked.. however i shorted pins by looking here... https://forum.freaktab.com/forum/tv...icussions/791910-help-x96-mini-q6x-v2-2-17355
Click to expand...
Click to collapse
Hi what nan chip do you have on that board i also have the v 2.2 but mine has the toshiba nan chip and i seem t have very bad luck finding firmare
Tenho uma Q6X V3 pc reconhece mais o flash para em 7%,[0x32030201]Uboot/Get result/DiskInitial error.tentei cum varias firmwares diferentes
Mod translation: I have a Q6X V3 pc that recognizes the flash at 7%,[0x32030201]Uboot/Get result/DiskInitial error. I tried with several different firmwares

A95X F3 - help me save it?

I bought the A95X F3 after I had lots of fun from the A95X F3 which should be inferior, anyway, I received a bricked the device, and my refund request has been turned down even though I completely shows the TV not booting etc.
Anyways, as a last resort to not throw my $40, I'm trying to revive the device. I have previously re-flashed a ROM I've found for the A95X F3, and it actually worked, I managed to boot and everything, it worked just fine for around 2 weeks and then I noticed that it got stuck. I tried to disconnect and reconnect the power cable to the TV box, and since then nothing happens...I can see some red light, but no boot, nothing.
I tried re-flashing again, but it doesn't seem to work this time. Previously I had an issue which I had to uncheck the erase flash and erase bootloader options, and afterwards it simply worked, but this time even if I'm unchecking this it doesn't seem to work and gets stuck on Download DDR on 1%(which is what happened with the erase flash and bootloader checked).
Even though it's unchecked, I do see the status of "erasing bootloader" in the beginning, so I wonder if that could somehow be the reason for that, but I can't understand why would this happen?
Anyway, kinda lost, would love to get some suggestions on how to fix this if possible.
These are the logs:
[20:25:38 565][HUB1-2][Inf]--------------ERASE BOOTLOADER------------
[20:25:38 565][HUB1-2][Inf]-------------Download DDR.USB-----------
[20:25:38 565][HUB1-2][Inf]--Close device handle 0x00000464
[20:25:38 616][HUB1-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#8&1bffc6b3&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000464
[20:25:38 667][HUB1-2][Inf]--3-2-0-0
[20:25:38 667][HUB1-2][Inf]--Control write pll reg1 0xfffa0000:0x000000b1
[20:25:39 169][HUB1-2][Inf]--Control write pll reg1 0xfffa0000:0x00005183
[20:25:39 670][HUB1-2][Inf]--Control write pll reg1 0xfffa0000:0x000000b1
[20:25:40 171][HUB1-2][Inf]--Control write pll reg1 0xfffa0000:0x00005183
[20:25:40 672][HUB1-2][Inf]--Write initial succeed
[20:25:40 672][HUB1-2][Inf]--Upload encrypt at 0xff800228
[20:25:40 672][HUB1-2][Inf]--ulValue = 0x20444142
[20:25:40 672][HUB1-2][Inf]--Read encrypt value succeed
[20:25:50 673][HUB1-2][Err]--Download file failed, sequence 0
[20:25:50 673][HUB1-2][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error
[20:25:50 673][HUB1-2][Inf]--Failure : 1, FailureMax : 3
[20:25:50 673][HUB1-2][War]--[20:26:00 675][HUB1-2][Err]--Download file failed, sequence 0
[20:26:00 675][HUB1-2][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error
[20:26:00 675][HUB1-2][Inf]--Failure : 2, FailureMax : 3
[20:26:00 675][HUB1-2][War]--[20:26:10 676][HUB1-2][Err]--Download file failed, sequence 0
[20:26:10 676][HUB1-2][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error
[20:26:10 676][HUB1-2][Inf]--Failure : 3, FailureMax : 3
[20:26:10 678][HUB1-2][Err]--[0x10103003]Romcode/Initialize DDR/Download buffer/USB transfer error
[20:26:10 678][HUB1-2][Inf]--Close device handle 0x00000464
Click to expand...
Click to collapse
This is what it gets stuck on:
{
"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"
}
msacco4 said:
I bought the A95X F3 after I had lots of fun from the A95X F3 which should be inferior, anyway, I received a bricked the device, and my refund request has been turned down even though I completely shows the TV not booting etc.
Anyways, as a last resort to not throw my $40, I'm trying to revive the device. I have previously re-flashed a ROM I've found for the A95X F3, and it actually worked, I managed to boot and everything, it worked just fine for around 2 weeks and then I noticed that it got stuck. I tried to disconnect and reconnect the power cable to the TV box, and since then nothing happens...I can see some red light, but no boot, nothing.
I tried re-flashing again, but it doesn't seem to work this time. Previously I had an issue which I had to uncheck the erase flash and erase bootloader options, and afterwards it simply worked, but this time even if I'm unchecking this it doesn't seem to work and gets stuck on Download DDR on 1%(which is what happened with the erase flash and bootloader checked).
Even though it's unchecked, I do see the status of "erasing bootloader" in the beginning, so I wonder if that could somehow be the reason for that, but I can't understand why would this happen?
Anyway, kinda lost, would love to get some suggestions on how to fix this if possible.
These are the logs:
This is what it gets stuck on:
Click to expand...
Click to collapse
You have the usb tool? If not find it.. (DO NOT CONNECT THE BOX) start the tool, add the image file and click start.. Now, using a toothpick press the reset button in the a/v port and while still pressing it connect the box to your pc.. it will automatically start rewriting the firmware..
Have fun
I found the solution.
msacco4 said:
I bought the A95X F3 after I had lots of fun from the A95X F3 which should be inferior, anyway, I received a bricked the device, and my refund request has been turned down even though I completely shows the TV not booting etc.
Anyways, as a last resort to not throw my $40, I'm trying to revive the device. I have previously re-flashed a ROM I've found for the A95X F3, and it actually worked, I managed to boot and everything, it worked just fine for around 2 weeks and then I noticed that it got stuck. I tried to disconnect and reconnect the power cable to the TV box, and since then nothing happens...I can see some red light, but no boot, nothing.
I tried re-flashing again, but it doesn't seem to work this time. Previously I had an issue which I had to uncheck the erase flash and erase bootloader options, and afterwards it simply worked, but this time even if I'm unchecking this it doesn't seem to work and gets stuck on Download DDR on 1%(which is what happened with the erase flash and bootloader checked).
Even though it's unchecked, I do see the status of "erasing bootloader" in the beginning, so I wonder if that could somehow be the reason for that, but I can't understand why would this happen?
Anyway, kinda lost, would love to get some suggestions on how to fix this if possible.
These are the logs:
This is what it gets stuck on:
Click to expand...
Click to collapse
after 3hrs of head bang I FOUND THE SOLUTION.
use ver 2.1.7.3 usb burning tool.
feed the pasword .bin file under view>password
try temprature range 10-65 .
if range does not work, uncheck the tempurature range check box.
give firmware image path and press start.
then press recovery botton inside audio jack hole, while pressing connect box to PC (using 2.0 usb port of box), AS SOON AS TOOL RECOGNIZES BOX, LEAVE THE RECOVERY BUTTON.
process will start.
this worked for me....... got my box working back.
FILE LINKS ARE GIVEN BELOW
FIRMWARE
A95X F3 rgb
download1127.mediafire.com/as...191017senk.img
USB BURNING TOOL
freaktab.org/693ba67a9b3e3236?download_token=1ddd6134221bf1dd6ec19b855306a54b0473c616ac54524c153793ecc9896938
PASSWORD FILE
forum.freaktab.com/filedata/...2&d=1581683185
@Setting.Out and friends.
I'm using the A95X F3 with another launcher:
1) I can't use widgets (neither with the factory launcher),
2) I can't access the items in the notification bar (neither with the factory launcher).
Any tips, please?
Thank you.
Setting.Out said:
You have the usb tool? If not find it.. (DO NOT CONNECT THE BOX) start the tool, add the image file and click start.. Now, using a toothpick press the reset button in the a/v port and while still pressing it connect the box to your pc.. it will automatically start rewriting the firmware..
Have fun
Click to expand...
Click to collapse
plugging the adapter is not required while flashing?? And I also want to ask whether I should connect a display with it while flashing??
trueAK said:
plugging the adapter is not required while flashing?? And I also want to ask whether I should connect a display with it while flashing??
Click to expand...
Click to collapse
plua is there any specific firmware for version of my box which is 2 GB/16 GB??
karan_rob7 said:
I found the solution.
after 3hrs of head bang I FOUND THE SOLUTION.
use ver 2.1.7.3 usb burning tool.
feed the pasword .bin file under view>password
try temprature range 10-65 .
if range does not work, uncheck the tempurature range check box.
give firmware image path and press start.
then press recovery botton inside audio jack hole, while pressing connect box to PC (using 2.0 usb port of box), AS SOON AS TOOL RECOGNIZES BOX, LEAVE THE RECOVERY BUTTON.
process will start.
this worked for me....... got my box working back.
FILE LINKS ARE GIVEN BELOW
FIRMWARE
A95X F3 rgb
download1127.mediafire.com/as...191017senk.img
USB BURNING TOOL
freaktab.org/693ba67a9b3e3236?download_token=1ddd6134221bf1dd6ec19b855306a54b0473c616ac54524c153793ecc9896938
PASSWORD FILE
forum.freaktab.com/filedata/...2&d=1581683185
Click to expand...
Click to collapse
Can anybody give me link to firmware of a95x f3 air?

Mi Box 3 (MDZ-16-AB) downgrade Android 9 Pie to Android 8 oreo

My English is very poor, I use Chinese, with the original Chinese tutorial. Use GOOGLE Translate to English to share the downgrade process. The process is very simple. I hope to help people who want to downgrade from pie to oreo without losing the DRM copyright, WIFI, Bluetooth, and Netflix SN.
Model: MI BOX 3 ( MDZ-16-AB) downgrade Android 9 Pie R2926 to Android 8 oreo R2167
Tools needed:
PC Windows 7 OS or higher, it is recommended to use the rear USB port of the computer
Download MDZ16AB.IMG firmware
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
Download Amlogic-USB_Burning_Tool_v2.2.0
https://mega.nz/file/Hd0CmACT#OPws8xFAPOGR6SmFJKfkVQ4SXjXpetJHmZZZ7nqkRHc
Download MI BOX3 Oreo R2167 Update.zip
https://mega.nz/file/gh0xCCrR#ctdPivezVFNAuMLq19eOepO1LHJCfVNhowmZz7Fx87s
USB Male to Male cable, buy it or make it yourself.
USB flash disk-Format Fat32
--------Start----------
1. Open Amlogic-USB_Burning_Tool and click the upper left corner to load MDZ16AB.IMG firmware. After the firmware verification is completed, pay attention to the option on the right, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to'Normal erase', this is to keep DRM keys which allows Netflix to work. Once again, confirm that there is no selection error and click "Start".
{
"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"
}
2. Use a USB Male to Male cable to connect the PC and MI BOX 3 that is not powered on, and then press and hold the Bluetooth remote control hold Back+Okay, turn on the power of MI BOX 3, and enter Recovery mode.
3. On the Recovery interface, use the Bluetooth remote control, select Reboot to bootloader, press confirm, MI BOX 3 will restart, and the TV will display a gray MI LOGO interface, successfully enter the official bootloader preload certification, be careful not to disconnect USB Male to Male cable.
4. Unplug the power of MI BOX 3 again, wait for 5 to 10 seconds, press and hold the Bluetooth remote control hold Back+Okay, turn on the power of MI BOX 3, you will see the Amlogic-USB_Burning_Tool progress bar moving, from 1 % To 100%.
5. After the Amlogic-USB_Burning_Tool progress reaches 100%, click Stop and unplug the USB cable, power off and restart MI BOX 3. Then MI BOX 3 will enter the recovery cycle, don't be afraid.
6. Power off MI BOX 3, save the oreo R2167 upgrade file into a FAT32 format U disk, insert the USB port of MI BOX 3, turn on the power, it will automatically update, the update process is about 5 minutes, after the update is complete, you will Successfully fall back to Android oreo r2167. Enter Recovery mode again, Wipe clears the date and cache and restarts to complete.
For the recovery cycle, please check the tutorial:
http://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
This method may help restore the mirror image of the mi box that can enter the Recovery mode and become a brick. For example, Amlogic-USB_Burning_Tool displays a 1% Low_Power error, but it is not guaranteed.
Please download the complete img file, it cannot be damaged. Use high-quality USB cable, high-quality U disk, use computer rear USB interface
中文流程 Chinese process:
适用型号:MI BOX 3 (MDZ-16-AB)国际版
需要使用工具:
电脑 Windows 7 或更高,建议使用电脑后置USB接口
下载 MDZ16AB.IMG 固件
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
下载 Amlogic-USB_Burning_Tool_v2.2.0
https://mega.nz/file/Hd0CmACT#OPws8xFAPOGR6SmFJKfkVQ4SXjXpetJHmZZZ7nqkRHc
下载 MI BOX3 Oreo R2167 Update.zip 升级ZIP文件
https://mega.nz/file/gh0xCCrR#ctdPivezVFNAuMLq19eOepO1LHJCfVNhowmZz7Fx87s
USB 公对公电缆 ,可以使用废弃USB线制作,长度0.5米内为佳。
U盘(USB硬碟) Fat32 格式 ,在最后步骤使用。
--------开始----------
1、打开 Amlogic-USB_Burning_Tool ,点击左上角加载MDZ16AB.IMG固件,固件校验完成后,注意右边选项 -- 烧录配置:勾选--擦除FLASH --普通擦除 ,不要勾选:擦除bootloader,这很重要,选择错误会删除DRM授权,Netflix SN将会丢失,再一次确认没有选择错误,点击“开始”。
2、使用USB 公对公线缆 连接电脑和没有接通电源的MI BOX 3,然后按住蓝牙遥控器 返回+确认 不放手 ,接通MI BOX 3 电源,进入Recovery模式。
3、在Recovery界面,使用蓝牙遥控器,选择 Reboot to bootloader ,按确认,MI BOX 3会重启,电视会显示一个灰色 MI LOGO 界面,成功进入官方 bootloader 预加载密钥认证,这是刷机成功的关键,注意不要断开USB线 。
4、再一次拔下 MI BOX 3 的电源,等待5至10秒钟,按住蓝牙遥控器 返回+确认 不放手,同时接通 MI BOX 3 电源,你会看到 Amlogic-USB_Burning_Tool 进度条在动,过程从1%到100% 。
5、Amlogic-USB_Burning_Tool 进度达到100%后,点击停止并拔下USB电缆,断电重启MI BOX 3 。然后MI BOX 3 会进入 recovery 恢复循环,不要紧。
6、将MI BOX 3 断电, 把oreo R2167升级文件解压,得到Update.ZIP和xiaomi_update,把这两个文件存入FAT32格式U盘,插入MI BOX 3 的USB端口,接通电源,它会自动更新,更新过程大约5分钟,更新完成后,你将成功回退到 Android oreo r2167 。再一次进入Recovery模式,Wipe 双清,并重启,完成。
关于 recovery 恢复循环,请查看教程:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
此方法有可能会帮助到能进入Recovery模式变成砖的mi box恢复原始镜像 ,比如 Amlogic-USB_Burning_Tool 显示 1% Low_Power 错误,但不保证有效。
注意下载完整img文件,不能损坏img文件。使用高质量USB线缆、高质量U盘、使用电脑后置USB接口。
Thanks for your information, I'm tried to mibox downgrade ,too.
My mother language is chinese, too.
Thanks again. (再次感謝)
can you share the source link please
Can you share the original link of the source?
When I leave the male usb cable connected (pc to the mibox3) I cannot enter the recovery, first I have to disconnect the male usb cable, in this way if I can access the recovery, is this so ?. Another thing is that the usb cable connected to the pc at no time recognizes the mi box.
Wouldn't you have to open the mibox3 to cut short, as was done with the 16-AA version?
I am using windows 10 home and if I could install the driver, the male to male cable had already been used to flash other devices.
Hi
in the Status i have [ 1% : low_power ] - and nothing more
device not wake up anymore .... - in the sys when connect to PC - appear the "WorldCupDevice"
( i try diff. usb ports.... 3 and 2 and rear and front)
any help pls?
edit
I just tried another laptop that has windows 10 pro, and the downgrade has worked perfectly for me.
I'd like to try this on my device, however I cannot get into recovery mode. My Mi Box powers up, but does not seem to output anything via HDMI at all
[QUOTE =“ 372812,帖子:84011735,成员:8569207”]
你能分享源链接吗
您可以共享源的原始链接吗?
当我保持公USB电缆连接(pc到mibox3)时,我无法进入恢复,首先必须断开公USB电缆,这样才能访问恢复,是这样吗?另一件事是,连接到PC的USB电缆无法立即识别mi盒。
您是否不需要像16-AA版本那样打开mibox3来缩短时间?
我正在使用Windows 10 Home,并且如果可以安装驱动程序,则已经使用了公对公电缆来刷新其他设备。
[/引用]
You have successfully downgraded from pie to oreo, this post is the source link. There is no need to disassemble the mi box 3. Again: no need to disassemble the mibox 3. Steps 1 to 3, mibox3 is not displayed in amlogic_burning_tool as connected. This is to use the power-off bug to let the official bootloader perform secondary boot loading. When amlogic_burning_tool recognizes a bootloader that does not initially load the system ROM flash, it will activate the amlogic_burning_tool flashing process. Xiaomi may block this bootloader vulnerability in future system upgrades.
Talon said:
Hi
in the Status i have [ 1% : low_power ] - and nothing more
device not wake up anymore .... - in the sys when connect to PC - appear the "WorldCupDevice"
( i try diff. usb ports.... 3 and 2 and rear and front)
any help pls?
Click to expand...
Click to collapse
Your mibox3 must be able to enter recovery normally before you can use this method to downgrade. If your device's flash memory is damaged, you cannot do anything.
OcelotNo said:
I'd like to try this on my device, however I cannot get into recovery mode. My Mi Box powers up, but does not seem to output anything via HDMI at all
Click to expand...
Click to collapse
Press and hold the back + OK button of the Bluetooth remote control, and then turn on the power supply of mibox3, which will enter recovery. TV does not have HDMI image display, if your mibox is not faulty, you should check the TV input and HDMI cable
skyforcetw said:
Thanks for your information, I'm tried to mibox downgrade ,too.
My mother language is chinese, too.
Thanks again. (再次感謝)
Click to expand...
Click to collapse
Thanks
deep00007 said:
Your mibox3 must be able to enter recovery normally before you can use this method to downgrade. If your device's flash memory is damaged, you cannot do anything.
Click to expand...
Click to collapse
i was!... - i normally entered to the recovery but when i started in Burning_Tool - i got the error "low power" at 1% (
Talon said:
i was!... - i normally entered to the recovery but when i started in Burning_Tool - i got the error "low power" at 1% (
Click to expand...
Click to collapse
Please make sure that your mibox3 is running normally and there is no fault before it can be degraded! Do not need to open the circuit board, strictly follow my tutorial operation
deep00007 said:
Please make sure that your mibox3 is running normally and there is no fault before it can be degraded! Do not need to open the circuit board, strictly follow my tutorial operation
Click to expand...
Click to collapse
Hi, my Mi Box powers up, but does not seem to output anything via HDMI at all. Any advice on how to get it running again?
deep00007 said:
Please make sure that your mibox3 is running normally and there is no fault before it can be degraded! Do not need to open the circuit board, strictly follow my tutorial operation
Click to expand...
Click to collapse
that instruction good for future "romintruders"...
but i (without any claims or towards you or your tutorial) just need any help or suggestion, not a warning ... - because all this has already happened to me ;/
...and although I'm sure that on my mibox3 had everything running normally and there was is no faults !! -... for one reason or another ...- something went [email protected]#$%F$ wrong - during the operation process
... and I'm definitely not the only one with whom the same thing happened ...
This worked perfectly. Skipped the last recovery/wipe, after upgrade it was factory reset already.
Downgrade fixed the terrible ghosting for me. Picture is so much better in orea.
Didn't try DRM yet, but Netflix cert is there
Hello, I have also downgraded successfully to Oreo. But the process was slightly different.
2] within step 2 (after I pressed Start and connected box via USB cable) - I pressed these two keys on the remote, connected power supply, after MiBox logo appeared I released the keys on remote, and expected the box would go to recovery. Instead the flashing started immediately. Thus I skipped the part making the box to reboot to Bootloader.
PS: anyone knows how come please? Why is the phase with bootloader needed and what is the risk when this not happens?
Maybe it's needed to hold the keys until the box is really in recovery?
Anyway - flashing went to 100% => success.
5] in step I was expecting the box will go into recovery. But nope - it was showing me the 4 colored rotating logos (as when the box is booting regularly) but it had stacked in this state.
So I took the pen drive with the update files and inserted it into box's USB port - attached the power while having 2 buttons presed on the remote and box started doing update. After it's all finished I am a lucky owner of MiBox 3 with Oreo build 2562 again.
BTW - my reason to downgrade was to use Darken WakeLock which stopped working on Pie ROMs (on both MiBox 3 and MiBox S). This allows the box to be waken up from standby - either by TV CEC or by Chromecast which is ready to cast even in standby).
-------
Please make sure you have downloaded the image correctly. My downloads were corrupted when using Chrome on a Windows computer (twice). I used an Android tablet to download, then it was OK.
I used a package from a link I have found on the Russian forum (4pda).
https://yadi.sk/d/RnN2hz_IUEMOSg?w=1
Good luck to all who want to get box downgraded too.
Hello. I tried to downgrade, but with no succes, sadly.
After step 4, the Amlogic USB Burning Tool progress bar does not move and the flashing does not start. Actually there is no HUB and no progress bar like in your photo. After a short time the device boots to recovery. Where is the problem? Can you help?
The device is on PI.3175 release-keys build.
I'm using an ASUS X550 laptop with Windows 10.
I´m able to boot to recovery, the select reboot to bootloader but the computer/Amlogic USB burning tool does not detect the mi box
Any suggestions?
i downgraded to android 8 build 2167 successfully but i found 1 problem, i check for new update OS through OTA it give me result that there is no new update,
i'm wondering is that there is no new update at this moment or maybe it's because of downgrading to android 8 make it unable to update to new build versions of android 8 ?
is anyone have the same problem like me ?

[GUIDE] Lenovo Legion Y70 - Unbrick with QFIL

Since there's no Legion Y70 section, I'm posting this here in hopes of helping those who may have bricked their device (like I did).
Requirements:
1. Stock rom. I used L71091_CN_SECURE_USER_Q00041.0_S_ZUI_14.0.697_ST_221216_QPST.zip but any version will work.
2. QPST, QFIL, and Qualcomm drivers installed. I installed them from here: https://qpsttool.com/qpst-tool-v2-7-496
Steps:
1. Extract the stock rom zip to a folder with no spaces. For example I used C:\Stock\
2. Open QFIL, click on Configuration->Firehose configuration
3. Set the configuration settings as shown in attached file config.png (reset state machine should be checked, device type UFS)
{
"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"
}
4. Back in the main QFIL window, select:
Build type : Meta build
Programmer Path: Select the xbl_s_devprg_ns.melf file from where you extracted your stock rom .zip
Content XML: select contents.xml
Storage types: ufs (in the middle and in the bottom right corner too!)
RawProgram and Patch: Select all available files in the rom directory.
For RawProgram, there should be 9 files: rawprogram_unsparsed0, retain_userdata, unsparsed4, and rawprogram 0 to 5
For patch, there should be 6 files: patch0 to 5
5. With the phone off and unplugged, hold volume up + volume down at the same time
6. Plug the phone into a USB slot on your computer while still holding the volume up+down buttons. Wait for Qualcomm HS-USB QDLoader 9008 (COMx) to appear on top of the QFIL screen. You can now release the volume buttons.
7. Click Download Content.
Voila!
My phone was bricked/bootlooping giving me a QUALCOMM CRASHDUMP error on boot up for several days now after trying to load a custom rom and I kept getting SAHARA FAIL error in QFIL while trying to reflash stock in EDL mode. Finally the above settings worked!
sso003 said:
Since there's no Legion Y70 section, I'm posting this here in hopes of helping those who may have bricked their device (like I did).
Requirements:
1. Stock rom. I used L71091_CN_SECURE_USER_Q00041.0_S_ZUI_14.0.697_ST_221216_QPST.zip but any version will work.
2. QPST, QFIL, and Qualcomm drivers installed. I installed them from here: https://qpsttool.com/qpst-tool-v2-7-496
Steps:
1. Extract the stock rom zip to a folder with no spaces. For example I used C:\Stock\
2. Open QFIL, click on Configuration->Firehose configuration
3. Set the configuration settings as shown in attached file config.png (reset state machine should be checked, device type UFS)
View attachment 5866435
4. Back in the main QFIL window, select:
Build type : Meta build
Programmer Path: Select the xbl_s_devprg_ns.melf file from where you extracted your stock rom .zip
Content XML: select contents.xml
Storage types: ufs (in the middle and in the bottom right corner too!)
RawProgram and Patch: Select all available files in the rom directory.
For RawProgram, there should be 9 files: rawprogram_unsparsed0, retain_userdata, unsparsed4, and rawprogram 0 to 5
For patch, there should be 6 files: patch0 to 5
View attachment 5866437
5. With the phone off and unplugged, hold volume up + volume down at the same time
6. Plug the phone into a USB slot on your computer while still holding the volume up+down buttons. Wait for Qualcomm HS-USB QDLoader 9008 (COMx) to appear on top of the QFIL screen. You can now release the volume buttons.
7. Click Download Content.
Voila!
My phone was bricked/bootlooping giving me a QUALCOMM CRASHDUMP error on boot up for several days now after trying to load a custom rom and I kept getting SAHARA FAIL error in QFIL while trying to reflash stock in EDL mode. Finally the above settings worked!
Click to expand...
Click to collapse
(Solved)i keep getting SAHARA FAil error too in QFIL.. Can u tell me how did you solve this problem? and where did you find stock rom? i have only zui14 220914 rom and this rom has a SAHARA error
—— i chose the wrong stock rom. It is not working on QFIL
.
.
.
wjswnsgk0204 said:
(Solved)i keep getting SAHARA FAil error too in QFIL.. Can u tell me how did you solve this problem? and where did you find stock rom? i have only zui14 220914 rom and this rom has a SAHARA error
—— i chose the wrong stock rom. It is not working on QFIL
Click to expand...
Click to collapse
Hello, maybe it's late but for those who need it, I had the same problem as you, that always came up until I came across some advice on why it usually happens, in my case it was that the connection was made before time, We must configure everything long before placing and connecting the mobile in EDL mode, be careful it must be a 100% original USB cable of any brand for the data transmission to be successful... I hope it works for you...
credits: https://www.getdroidtips.com/sahara-fail-error-in-qfil/
where can we find the stock rom
kalid191 said:
donde podemos encontrar la stock rom
Click to expand...
Click to collapse
Hello, this link is https://drive.google.com/file/d/1bRKqkWb7RDcrnXZEnS701T87nfgHxUrk/view?usp=share_link
GustavoRj98 said:
Hello, this link is https://drive.google.com/file/d/1bRKqkWb7RDcrnXZEnS701T87nfgHxUrk/view?usp=share_link
Click to expand...
Click to collapse
thank you so much,
another file i want to ask for is vbmeta.img do you know where can i find it
kalid191 said:
thank you so much,
another file i want to ask for is vbmeta.img do you know where can i find it
Click to expand...
Click to collapse
Here we go
(Credits for the people on 4pda)
This is super helpful! I've linked your guide in my discord server (for Y70 owners) if you don't mind. If anyone is interested in joining, here is the invite: https://discord.gg/r5VMszTGVr
Please feel free to share the link around or invite others. There are help and support channels, and a resources one too. I'm hoping we can attract more people there and have more things shared amongst each other.
jimbi87 said:
Here we go
(Credits for the people on 4pda)
Click to expand...
Click to collapse
What is this??
A alguno le funciona las aplicaciones de streaming como Netflix, HBO, Crunchyroll, etc después de flashear???
Where can I find stock ROM for Legion Y70?
Something is wrong with the display. There is a bar in the middle of the screen that is displayed in a different shade. I have a factory protective film on my screen.
hello , why Programmer Path not work for me , cant click ?
G14R said:
A alguno le funciona las aplicaciones de streaming como Netflix, HBO, Crunchyroll, etc después de flashear???
Click to expand...
Click to collapse
I have the same doubt. You managed to find out.
Discord users have stated that it works using Magisk

Categories

Resources