Try at your own risk
https://youtu.be/YHRQrO3ZwoE
or use simply update
https://yadi.sk/d/sljofb2s3GzLCa
Good job thank you.
I have successfull update it.
Has onyone try this SCV2-ATV image? http://freaktab.com/forum/tv-player...b2-pro-ddr4-vorke-z1-ddr4-scv2-atv-android-tv
mecool bb2 pro
algdu83 said:
or use simply update
do you have a newer version of mecool bb2 pro thank you
Click to expand...
Click to collapse
Thats great but
Yes I would love to update my firmware. The problem is the only thing that runs anything that resembles windows in my house is the mecool. I use an Imac and the wifey uses a Macbook pro. I live in the sticks so getting my hands on a PC is next to impossible. Any idea's ? I also have another question how many GB's does the card need to be and, could I use a flash drive instead of card. I think my biggest sd card is 4 or 6 Gigs. Any suggestions would be wonderful. Thanks Yall
MECOOL BB2 PRO up date 7.1
Thanks to the friends the links and explanations posted, but these 2 ways to upgrade would already be for android 7.1 mentioned above?
Thank you and a great day.
Installing through TWRP
algdu83 said:
or use simply update
https://yadi.sk/d/sljofb2s3GzLCa
Click to expand...
Click to collapse
Hi,
Apologies for resuscitating this old thread, but have this problem maybe someone can help me.
I'm trying to install the zip suggested by you through TWRP and an error tells me that "This package is for bb2_pro devices - this is a q200". Now when I bought the box I'm quite sure that it was advertised as a BB2 PRO - I can still see it in my order history on Aliexpress. Even when I go in the About section in the box - it says Model BB2 PRO.
Does anyone know what this q200 mean? And can someone suggest a zip or img to install for it since I would like to upgrade from my Android 6 to at least Android 7.
Also, when I tried to install decalman's img, TWRP is telling me that the img size is bigger than the target. Any help please?
Many thanks!
thealley said:
Hi,
Apologies for resuscitating this old thread, but have this problem maybe someone can help me.
I'm trying to install the zip suggested by you through TWRP and an error tells me that "This package is for bb2_pro devices - this is a q200". Now when I bought the box I'm quite sure that it was advertised as a BB2 PRO - I can still see it in my order history on Aliexpress. Even when I go in the About section in the box - it says Model BB2 PRO.
Does anyone know what this q200 mean? And can someone suggest a zip or img to install for it since I would like to upgrade from my Android 6 to at least Android 7.
Also, when I tried to install decalman's img, TWRP is telling me that the img size is bigger than the target. Any help please?
Many thanks!
Click to expand...
Click to collapse
Test it
https://forum.xda-developers.com/showthread.php?t=3840103
you can install with USB_Burning_Tool and cable usb-usb
Rom https://mega.nz/#F!GEpQmQhZ!ezNEXQdnyNIhm2axjnfTIg?6EBAUIoZ choose normal
Usb burning http://www.exodux-box.com/download_files/(Exodux-Box.com)_USB_Burning_Tool_v2.1.7.1.zip
failed
algdu83 said:
Test it
https://forum.xda-developers.com/showthread.php?t=3840103
you can install with USB_Burning_Tool and cable usb-usb
Rom https://mega.nz/#F!GEpQmQhZ!ezNEXQdnyNIhm2axjnfTIg?6EBAUIoZ choose normal
Usb burning http://www.exodux-box.com/download_files/(Exodux-Box.com)_USB_Burning_Tool_v2.1.7.1.zip
Click to expand...
Click to collapse
Hi, many thanks for the links and info!!
To my shame, I couldn't find a usb to usb cable at home
I tried again with TWRP via USB stick but again it's telling me that "Size of image is larger than target device". This is very strange since the box should have at least 12GB of ROM.
I downloaded the zip file and extracted both images s912_atvXperience_v2FF and s912_LPDDR_atvXperience_v2FF and tried them both separately. Is that the right way, or should I leave both images as zip and install the rom as zip rather than as image (cause TWRP has the option to choose between zip and image)?
Do you think if I try with usb to usb, the same will happen?
Thanks!
thealley said:
Hi, many thanks for the links and info!!
To my shame, I couldn't find a usb to usb cable at home
I tried again with TWRP via USB stick but again it's telling me that "Size of image is larger than target device". This is very strange since the box should have at least 12GB of ROM.
I downloaded the zip file and extracted both images s912_atvXperience_v2FF and s912_LPDDR_atvXperience_v2FF and tried them both separately. Is that the right way, or should I leave both images as zip and install the rom as zip rather than as image (cause TWRP has the option to choose between zip and image)?
Do you think if I try with usb to usb, the same will happen?
Thanks!
Click to expand...
Click to collapse
you can not install an img with twrp
You can try this method
https://www.youtube.com/watch?v=CUfKNNgxb9E
You need a sdcard
And this software
https://chinagadgetsreviews.com/download-amlogic-burn_card_maker-v2-0-2.html
To make a USB USB cable
It's simple
You take two cables that you do not need and you cut them
And you reconnect them by keeping the same color of the queues
{
"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"
}
algdu83 said:
you can not install an img with twrp
You can try this method
https://www.youtube.com/watch?v=CUfKNNgxb9E
You need a sdcard
And this software
https://chinagadgetsreviews.com/download-amlogic-burn_card_maker-v2-0-2.html
To make a USB USB cable
It's simple
You take two cables that you do not need and you cut them
And you reconnect them by keeping the same color of the queues
Click to expand...
Click to collapse
Thanks again for your help algdu, tomorrow I'll try it out!
box not recognised
algdu83 said:
you can not install an img with twrp
You can try this method
https://www.youtube.com/watch?v=CUfKNNgxb9E
You need a sdcard
And this software
https://chinagadgetsreviews.com/download-amlogic-burn_card_maker-v2-0-2.html
To make a USB USB cable
It's simple
You take two cables that you do not need and you cut them
And you reconnect them by keeping the same color of the queues
Click to expand...
Click to collapse
Hi again,
I have bought a USB/USB cable, but the device is not being recognised by the burning tool. Do you know what could be the reason?
I have downloaded the Amlogic drivers and installed them.
Before connecting the device, I insert a needle in the small hole of the box so that it starts in Recovery mode. Then I open the burning tool, and connect the device to the pc via the USB/USB, but to no avail. It is not being recognised.
Thanks for any suggestions you might have.
thealley said:
Hi again,
I have bought a USB/USB cable, but the device is not being recognised by the burning tool. Do you know what could be the reason?
I have downloaded the Amlogic drivers and installed them.
Before connecting the device, I insert a needle in the small hole of the box so that it starts in Recovery mode. Then I open the burning tool, and connect the device to the pc via the USB/USB, but to no avail. It is not being recognised.
Thanks for any suggestions you might have.
Click to expand...
Click to collapse
1-open the burning tool
2-choos the firmware img
3-connecting the usb cable to pc
4-Stay on the power button of the bb2 (front button)
And connect the usb cable in the usb port on the power supply side. always stay pressed until you see the message connect
https://www.youtube.com/watch?v=DuPyVdEKQdQ
algdu83 said:
1-open the burning tool
2-choos the firmware img
3-connecting the usb cable to pc
4-Stay on the power button of the bb2 (front button)
And connect the usb cable in the usb port on the power supply side. always stay pressed until you see the message connect
https://www.youtube.com/watch?v=DuPyVdEKQdQ
Click to expand...
Click to collapse
Hi,
Unfortunately I cannot get the box recognised by the burning tool. I've done as per your latest instructions, and the video you linked, but to no avail. I've also uninstalled the burning tool and downloaded a more recent version, but still it wouldn't connect.
Anyway, don't want to waste you anymore time, but thanks for your help
thealley said:
Hi,
Unfortunately I cannot get the box recognised by the burning tool. I've done as per your latest instructions, and the video you linked, but to no avail. I've also uninstalled the burning tool and downloaded a more recent version, but still it wouldn't connect.
Anyway, don't want to waste you anymore time, but thanks for your help
Click to expand...
Click to collapse
Sorry
When connecting the USB cable, connect the power source and do not let go of the button
algdu83 said:
Sorry
When connecting the USB cable, connect the power source and do not let go of the button
Click to expand...
Click to collapse
Hello,
I finally managed to connect the device after various attempts! Many thanks for your help
May I just ask you one last question, if you know the difference between images s912_atvXperience_v2FF and s912_LPDDR_atvXperience_v2FF found in the zip file you suggested? I installed the first one but was wondering what is the difference between the one I installed and the other one? Thanks.
thealley said:
Hello,
I finally managed to connect the device after various attempts! Many thanks for your help
May I just ask you one last question, if you know the difference between images s912_atvXperience_v2FF and s912_LPDDR_atvXperience_v2FF found in the zip file you suggested? I installed the first one but was wondering what is the difference between the one I installed and the other one? Thanks.
Click to expand...
Click to collapse
Because in my memory I think I have tried this version
if you have problems, try the second one
The subject of origin
https://forum.xda-developers.com/showthread.php?t=3840103
Sorry, for reviving such an old thread but as usual I'm late to the game. I'm used to flashing custom roms to Android phones but this was a bit of a learning experience and I wanted to share what worked for me and what didn't. I'm a new member so I can't share links yet.
Love my Mecool BB2 and BB2 Pro boxes, they're still great quality, bought them both for around $79 (pro) and $59 (no-pro) and their value is still holding up. My wifi stopped working on both of them around the same time, not sure why? Luckily these boxes came with gigabit ethernet which is extremely rare in the mid-range android tv boxes, most come with 10/100, even the ones that say 10/1000m will often say in the fine print "max ethernet speed 100mbps", so be careful, most of the boxes on eBay are drop shipped from China/Hong Kong and claim to be shipping from a US address, there is often poor communication with these sellers and misrepresentation of the specs.
I updated both boxes to ATV style (Android TV) firmwares with a windows computer and AmlogicBurnTool. I also installed the ATV Launcher from Playstore and disabled the pre-installed Launchers. I really like the ATV Launcher, worth the $2.99 pro upgrade for all the customization options.
The BB2 (non pro), Android Pie, full official play store, can turn Root on/off with a switch, can disable system apps etc..., wifi started working again. Only hickup is the Blue power light is now off, and the red light is now on... (Mecool_BB2_2_16_GB_DDR3_Android_7.1.2_from_Tanix_TX9S-20200401.img)
For the BB2 Pro I used (SCV2-ATV-BB2Pro-VorkeZ1.img), sadly this is Android Marshmallow and no full Playstore app, just some dumbed down app that looks and feels more like Aptoide. Can turn Root on/off with a switch, can disable system apps etc..., wifi started working again.
I've soft bricked my device by installing OTA firmware via Recovery and also with the Burn Card Maker, so I prefer the Amologic Burning Tool, it either flashes successfully or it doesn't. Either way I've never soft Bricked the boxes with the Burning Tool, (just make sure you load the .img file first, click start, then connect a male to male USB cord to the USB port that's closest to the corner of the box. No power supply needed).
Related
[update 2013/04/10]
And it is back to life! :victory:
I still cannot believe it! I decided to have another go using the Haier W718 USB cable and guess what? The cable supplied with the Zhou Xing i9300 is basically a big piece of s****.
I can confirm that the test point which worked for me are also GND + KCOL0
I have flashed the ROM wich link yuweng supplied. Thanks, again, bro :good:
Most things work except:
1) The ribbon cable running from the volume keys to the upper board is detached and I am not sure of how to fix this. Is it crazy to "superglue" it?
2) The IMEIs are not recognised. I have tried setting them up manually (following a video from Colonel Zap and taking the digits printed underneath the battery slot). No joy, no matter what SIM card slot I try, I get "IMEI invalid". In engineer mode, under bandmode, I have actually noticed that no band is selected. I check those applicable in Spain and click on "Set", but it basically ignores it.
So I am trying to get now a new ROM, hopefully closer to our settings in Spain. I have contacted a fellow member from a Spanish forum. Fingers crossed.
Oh, I almost forgot. Since the volume keys are not working because of the detached ribbon cable, I have ported TWRP recovery for the Zhou Xing. I thought a touch screen recovery would come in particularly handy now! Here it is.
BACKGROUND STORY BELOW:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
khankll said:
so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
Click to expand...
Click to collapse
Thanks, khankll So here is the update on the 1st post. Sorry, but I am leaving in an hour and will be away for the whole week, so this is as much I can tell at this point.
khankll said:
the first thing is that you make it recognizable by pc .
Click to expand...
Click to collapse
At first I still got it recognised as MTK device, but right now the best I get is an "Unknown device" under USB devices (not under COM ports). This is with the phone completely assembled and battery inserted. When I dismantle the phone to try to trigger test point, no sign of life whatsoever. If I try to update the drivers, I get something like "Windows determined the best drivers are already present". I guess Windows is only detecting the device as some kind of USB memory and that is it.
{
"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"
}
khankll said:
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
Click to expand...
Click to collapse
I already found a ROM thanks to dragonevo's pointer here. The problem is, I guess, this ROM is in a format to be used when you can boot into Recovery mode. I say "I guess" because I have never got to see Recovery mode on this phone. I am not even sure of the key combination (tried Power & Volume + and Power & Volume -). I am using SP Flash Tool and it looks first for a scatter text file, and several other files that are not in that ROM zip, (only the boot.img is there). And from what I gather all these files also are specific to the phone model.
This is why I raised my original question in this post, so that I could use the ROM found in Flash Tool.
khankll said:
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
Click to expand...
Click to collapse
I am not sure I get this, but I will try when I get back in one week
khankll said:
also what is the battery voltage ? is it charged ?
Click to expand...
Click to collapse
2.9 v (I have a spare one which reading is 4.1 v)
Reminder: when I try the test point, the battery is not present (it cannot be since the board has to be completely dismantled on this phone to access KCOL and GND points. commonwarrior has another phone model but exactly the same board and it has worked for him this way. If I got this right, the battery is not required and Flash Tool (since yesterday I am using the latest supplied by commonwarrior) actually has an option called "Autodetect", which is supposed to work either way, with and without battery). file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
[update 2013/02/14]
Sorry about vanishing, guys. I actually bumped into a bigger problem. My PC hard disk crashed. Anyway, I recovered my older (and smaller capacity) hard disk and installed it. As to the OS, I have just installed Ubuntu 12.04 + Windows XP as a virtual machine. I am a novice to Ubuntu, so please forgive me if the ending of this story is still delayed as I have other priorities to take care of right now.
Thanks a bunch again to yuweng for the correction for the test point and finally the files to flash from SP Flash Tools. I have downloaded the files and will have another go when I get the chance.
To be continued...
[update 2013/02/18]
I am afraid I am giving up on the Zhou Xing. No matter what test point I try, I never get any response in Flash Tool (I have also tried different versions including the latest one uploaded by commonwarrior).
With all the handling, the flat small cable that runs from the Volume up and down keys is detached from the contacts on the main board and I cannot see how I could weld these back.
So I am closing this chapter on my end. I hope it has been helpful to other people. At least now we have the files to flash from Flash Tools for this phone model. I wish we had found them before I screwed it completely.
Thanks again for all your help, particularly to yuweng and commonwarrior
Zhou xing bricked.
2x1 said:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
Sorry, pigu36, I actually never got into Recovery mode. I flashed mine (and softbricked it) with SP Flash Tool.
Regarding the stock ROM, you will find the link in Dragonevo's post.
Maybe in that same thread, somebody will be able to tell you how to get into Recovery mode. As far as I am concerned, I have tried pressing "Power + Volume up" keys, but it has never worked.
Whatever I find out, I will share it here and in the other thread.
Good luck!
so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..
khankll said:
so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..
Click to expand...
Click to collapse
Sorry about the confusion, khankll.
This was before I tried to flash something else because I thought it could not get worse and maybe I could flash some kind of Recovery which would allow me to update from the SD card (where I have a copy of the stock ROM in a zip file).
However... things could get worse and they did. The phone is not detected any more even in SP Flash Tool, not charging... well you know the symptoms. So I found the test point thread and fingers crossed with all the advice you guys are helping with
If I am lucky with the test point method, I will still need the type of files SP Flash Tool looks for. Unless you know a way of getting them (converting repacking, I don't know what the right word would be) from the stock ROM zip file.
Model: ZhouXing I9300 MTK6577 Dual Core Android 4.0 3G GPS 4.7 Inch 8.0 MP Camera Smart Phone
Some pics
so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
the first thing is that you make it recognizable by pc .
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
also what is the battery voltage ? is it charged ?
2x1 said:
Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
Sent you pm previously & notice that you haven't been online since 8th February 2013 08:20 AM...
Good news, found your Stock ROM here, credits to Анатолий... :laugh:
it turns out the testpoint KCOL0 & GND is wrong, credits to orx65...
Hopefully, this infos here will be useful for Zhou Xing users to unbrick their device too... :fingers-crossed:
Cheers...
Many, many, thanks for this rare rom. So I was able to unbrick my phone without any hardware experiments. I searched several Weeks!
My only problem is, that there is no touchscreen-response.
Any Idea to solve this problem?
Thanks and regards
Herby53
Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM
yuweng said:
Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM
Click to expand...
Click to collapse
Thanks for the fast response, Yuweng
I have installed back the Ribbon Cable, but not correct and without complete contacts. Now the TouchScreen works, but the touches lands not there where they should. Especially noticeable when using the phone keypad #1-3 = #4-6. I think I have to calibrate the touchscreen, but don't know how.
Second problem: the hardware- (volume up / down) - and sensor buttons (menu, home and back) are without function. I hope I did not damaged the flat cable searching the testpoint.
Your question about the testpoint:
See thread ..... / / forum.xda-developers.com/showthread.php? p = 36908056
# 240
The first image shows the backsite of the board. Testpoint for me wars KCOLO & GND to start flashtool download => there is no Point DM.
Greetings
Herby
Hmm, according to orx65 photo on previous page, its definitely not KCOL0 & GND ( the two red dots )....
Big problem ! To calibrate Touch Screen, you need to boot into Factory mode....
Shut down the phone then hold Volume Down, don't let go & press power button until you see that it boots into Factory mode then only let go... :fingers-crossed:
Then it will display all the keys that you need to press once then only you can proceed with the Factory mode calibration...
ESC, BACK, MENU, VOLUME UP, VOLUME DOWN, POWER
Thanks once more!
I first have to repair the definitly broken flat cable for the hardware buttons. It already looked a bit cracked out of delivery.
But my fingers and my soldering iron are to big. :laugh: I must look even if there's a trick!?
Testpoint:
The combination on first picture (with phone 9 ContactPoints) ist KCOLO (2nd row/ center) & GND (first row/ center) worked for me.
It's shown in the picture thereunder.
There is no Contact with DM. 3rd Row right Contact is named DP, but I don't know if this ist what you are looking for.
There is one crazy idea on repairing the Flex Ribbon Cable here with a staple... :laugh:
Can't see it clearly on those photos, so what i meant was : does KCOL0 with DP works, if not then i'll remove the photo on previous page...
... for me only KCOLO & GND works ...
Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!
commonwarrior said:
Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!
Click to expand...
Click to collapse
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!
2x1 said:
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!
Click to expand...
Click to collapse
This is a capture for the flash tool settings. In option, leave just the usb flag and disable the RID flags. Just copy all the options you see in this picture and start the flashing in all the ports to be sure.
Sent from my lt29i modded phone!
I solved the problem
pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
If you don´t have solved the problem I have the original Zhou xing android 4.1.1 rom flash usb cable intallation
USB problem?
Hi guys. I few weeks ago I received my Zhou Xing i9300 and everything work great, but now, some days ago it start to no be recognized by my PC.
It simply dont do nothing.
I already try a new USB cable and even try to connect to another PC here i my home, and stay won't working.
Any idea about what possibly happens?
Any help will be veeeeeery appreciated.
Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful
Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
chrismast said:
Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
Click to expand...
Click to collapse
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
brigantti said:
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
Click to expand...
Click to collapse
tried that as well with my new mibox power supply, same result though.
bigtalker said:
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
Click to expand...
Click to collapse
tried that, did not help
Found a guy with a similar issue on Reddit but he had also no luck...
I went thru 4 different flash drives until it relented to flash
If you cannot resolve this issue PM me and if your happy to send your device for testing/recovery purposes you can send it to me, if i recover you can have it back, i simply need it for debugging as the one someone already sent had a wipes emmc
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
sergeyouknw said:
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
Click to expand...
Click to collapse
Sounds like you have a flaky USB thumb drive. Try formatting on a different pc and keep trying different usb drives. Current world record holder tried 8 different drives until succeeding with #9!!
Concur with bigtalker. Or a bad download. I followed a procedure that was a cross between https://www.reddit.com/r/AndroidTV/comments/9fo34b/xiaomi_mdz16ab_solution_to_downgrade_from_flaky/ and https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/:
Extracted the 2167 7zip file to a clean 2GB thumb drive (FAT32)
Booted MiBox into recovery and did a data wipe/reset
Shut down the MiBox and inserted thumb drive
Booted MiBox into recovery, again, where it automatically picked up and installed the 2167 update
Shut down the MiBox
Cleared the thumb drive, copied the 2179 .zip over to it as update.zip and restored the xiaomi_update file (from the 2167 7zip file)
Rebooted the MiBox into recovery again. It picked-up and installed the 2179 update
Booted the MiBox into Android and did a Factory Reset
Did minimal new setup configuration on boot and installed the 2396 OTA update
Done!
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
{
"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"
}
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
jseymour said:
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
Click to expand...
Click to collapse
Sorry to hear of your travail...
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
bigtalker said:
Sorry to hear of your travail...
Click to expand...
Click to collapse
Thanks. I'm not as annoyed as I might otherwise have been, being as I was more-or-less expecting it'd happen eventually. *shrug*
bigtalker said:
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
Click to expand...
Click to collapse
Each of the two boxes bricked themselves, or Xiaomi bricked them for me, with absolutely no intervention from me whatsoever. Box #1 was bricked to its splash screen. That one I recovered with the aforementioned procedure. Box #2 was bricked to completely dead except its front-panel indicator.
They had both been on the same versions. I don't recall which that was at the time they were bricked. The 1st or 2nd update Xiaomi pushed out for Oreo. IIRC: 2179 created as many problems as it solved, so I didn't apply that OTA when it was available. So perhaps the one before that?
There are reports of Xiaomi MiBox 3's "bricking themselves" on every on-line forum in which I participate, BT. Some to their splash screens. Some to just dead. Just like I experienced. These all started appearing about the time 2396 became available.
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
Click to expand...
Click to collapse
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://4pda.ru/pages/go/?u=https:/...c055db0b4f8dee8d49e4b04ecf9100.zip&e=65311772
What is the AndroidTV version of the img file you posted
What is the AndroidTV version of the update.zip file you posted
Curious as to the origin of the img file. Normally such things come from the hardware vendor. Xiaomi has not been forthcoming with img files, mainly staying with flashable zip format updates
hum..
I Use USB_Burning_Tool 2.0.7 and it say Low-Power after 1' ... :'( after, crash burn...
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://android.googleapis.com/pack.../2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
Click to expand...
Click to collapse
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Edit: Download for latest USB Burning Tool v2.2.0:
https://mega.nz/file/Hd0CmACT#OPws8xFAPOGR6SmFJKfkVQ4SXjXpetJHmZZZ7nqkRHc
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Hitchar said:
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Click to expand...
Click to collapse
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
criscodecookies said:
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
Click to expand...
Click to collapse
Yeah that seems to work. The USB Burning Tool sees the device and I can start the flash. But after a minute I get the error 'low_voltage'. I've tried all my USB ports (USB2 and USB3) and also tried to use my laptop. So now I'm wondering whether my cable is good (I've soldered it myself). I've tested for continuity so the connections are good. How are the cables inside your USB cable wired?
criscodecookies said:
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
Click to expand...
Click to collapse
i've tryed to flash this oero img16-ab on my bricked mi box 3 mdz 16-ab and the usb burning tool all the time showing me error
low power with this img but when i try to flash any other rom dont showing this error only with this rom, whats the problem?
Hi, I'm having these issues with this box. It was intended to be a small media server, but in trying different things I'm stuck and I'd appreciate it if anyone could help me. These AmLogic boxes are quite similar so any idea is more than welcome.
This is an S905X3 based box with 4GB RAM.
CoreELEC has been installed onto eMMC using their "ceemmc" tool. CoreELEC runs just fine.
Device is now unable to boot Armbian from either SD card nor USB.
Can't restore stock firmware: Burn Card Maker throws an error when writing SD card. Also, manually created SD card gives a black screen.
Can't access recovery. Almost sure RESET button isn't doing anything.
Windows can't detect when connected via male-to-male USB cable: do I need to short pins?
Any way to force recovery mode by shorting pins?
Thanks
Hi, I found this thread while looking for some info on how I could unbrick my X96 Max+.
It has bricked because of the Bl301 injection on CoreELEC and just like you, I can't access recovery and I don't know on which pins I should apply a short-circuit.
If someone knows which pins are the ones to short circuit, that would be much appreciated. Here are two pics of the X96 Max+ PCB:
{
"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"
}
I have higher resolution versions if necessary but I cannot post outside links at the moment.
Cheers.
After bottles my device is the same, nothing works anymore you have found a solution please write thank you
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
ludotaku said:
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
Click to expand...
Click to collapse
Is there a pattern for connection before you short the pins. I'm using USB burning tool, holding button in av port with USB connected then shorting the pins. Still no connection
leefreeman said:
Is there a pattern for connection before you short the pins. I'm using USB burning tool, holding button in av port with USB connected then shorting the pins. Still no connection
Click to expand...
Click to collapse
I didn't manage to make it work with USB Burning Tool. I burned a card with Burn Card Maker then I plugged the AC and HDMI cables with the SD card in the slot, did the short, waited for a few minutes (the screen was black during sometime) and then, the device was as new.
It was the bootloader that was broken on my device so it allowed me to restore it to its initial state.
My solution
ludotaku said:
I didn't manage to make it work with USB Burning Tool...
Click to expand...
Click to collapse
leefreeman said:
Is there a pattern for connection...n
Click to expand...
Click to collapse
ergun37 said:
After bottles my device is the same...
Click to expand...
Click to collapse
I should have posted an update here as soon as I got it resolved but I completely forgot and for that I apologise. :fingers-crossed:
Anyway, I went online and downloaded as many ROM images (aka "firmwares", .img files) for this box as I could find. I then wrote each onto MicroSDs as normal and booted the box with the card in. Eventually one of them worked and after a few minutes I was looking at the original box's AndroidTV skin.
HOWEVER... Although USB Image Tool copies data from these .img files onto cards I don't think it actually formats the card before it does, but just erases all the files instead. It seemed to only work for me after I formatted the card first with a small tool called SD Card Formatter from Tuxera and then used USB Image Tool. I hope this helps anyone.
On a side note: I went to CoreELEC's forum to ask for help and there were a couple of people who were more interested in ranting and giving me lectures than actually helping me. One guy did try and help me but now I'm not sure his suggestions actually helped. You can read the whole exchange here.
with my x96 max plus nothing goes no display allas dark with tv no life picture
ergun37 said:
with my x96 max plus nothing goes no display allas dark with tv no life picture
Click to expand...
Click to collapse
me too. nothing happen when i did short pin, there is no sign that my box would be restored again
iSlaker said:
I should have posted an update here as soon as I got it resolved but I completely forgot and for that I apologise. :fingers-crossed:
Anyway, I went online and downloaded as many ROM images (aka "firmwares", .img files) for this box as I could find. I then wrote each onto MicroSDs as normal and booted the box with the card in. Eventually one of them worked and after a few minutes I was looking at the original box's AndroidTV skin.
HOWEVER... Although USB Image Tool copies data from these .img files onto cards I don't think it actually formats the card before it does, but just erases all the files instead. It seemed to only work for me after I formatted the card first with a small tool called SD Card Formatter from Tuxera and then used USB Image Tool. I hope this helps anyone.
On a side note: I went to CoreELEC's forum to ask for help and there were a couple of people who were more interested in ranting and giving me lectures than actually helping me. One guy did try and help me but now I'm not sure his suggestions actually helped. You can read the whole exchange here.[/URL]
Click to expand...
Click to collapse
did you have 3 files in the card after burned ? or more files ? because i already burned my card, only 3 files there. and there is no response from my box, already short the pin to the ground. nothing happened
Hi ISlakar
having some odd issues with my x96max+ also. i have been unable to get CE on it at all. the box simply will not boot from the SD, infact it wouldn't even boot in to stock rom with the SD inserted, just got stuck at the x96 splash screen (but if i insert after stock is booted i see the SD and CE partition) my reset button appeared to be either broken, or disabled as it has no effect, does not even restart the box. i figured it may be disabled by firmware intentionaly or due to a bug so i tried some custom roms. non worked initially and no longer (or so i thought) was recognised by the AMlogic burning tool. the box appeared bricked however i noticed by chance that after around 4 minutes, it would suddenly ' connect' in the flash tool on my PC and teh clock would light up, and the box would stay connected in the flash tool. i tried same as you - many ROMS, none of the generic s905x3 roms will boot the box, and niether will the 'stock' x96 Max + roms i downloaded (various releases from last year and this). I found i can get the box to boot using slimbox ROMS for x96 AIR p1, p2 and V2. It does not run well with them though and hangs oftern for a few seconds, and still no way to get CE on with re-set button still seemingly broken or disabled. i treid 'reboot update' from terminal emulator but still no CE, it just seems to boot in to the boot loader, i dont get any CE splash screen. ive had loads of cheap boxes before and always have been able to get a decent ROM in them, and then get CE going from SD, but this one has me perplexed...
what ROM did you find that worked on you X96 Max+ ?
Thanks!!
thecubasekid said:
Hi ISlakar
having some odd issues with my x96max+ also. i have been unable to get CE on it at all. the box simply will not boot from the SD, infact it wouldn't even boot in to stock rom with the SD inserted, just got stuck at the x96 splash screen (but if i insert after stock is booted i see the SD and CE partition) my reset button appeared to be either broken, or disabled as it has no effect, does not even restart the box. i figured it may be disabled by firmware intentionaly or due to a bug so i tried some custom roms. non worked initially and no longer (or so i thought) was recognised by the AMlogic burning tool. the box appeared bricked however i noticed by chance that after around 4 minutes, it would suddenly ' connect' in the flash tool on my PC and teh clock would light up, and the box would stay connected in the flash tool. i tried same as you - many ROMS, none of the generic s905x3 roms will boot the box, and niether will the 'stock' x96 Max + roms i downloaded (various releases from last year and this). I found i can get the box to boot using slimbox ROMS for x96 AIR p1, p2 and V2. It does not run well with them though and hangs oftern for a few seconds, and still no way to get CE on with re-set button still seemingly broken or disabled. i treid 'reboot update' from terminal emulator but still no CE, it just seems to boot in to the boot loader, i dont get any CE splash screen. ive had loads of cheap boxes before and always have been able to get a decent ROM in them, and then get CE going from SD, but this one has me perplexed...
what ROM did you find that worked on you X96 Max+ ?
Thanks!!
Click to expand...
Click to collapse
Hey,
It's been a while since I touched this box. Once I got it back working on the original firmware I just threw it in a drawer and decided to wait until some linux based ROM came along as I knew I did not want to use CoreELEC. Their forum is not a very welcoming place.
Did you read my last post above? I think there's something about the way the card is formatted. It only worked once I used this specific tool to format the card BEFORE using USB ImageTool. I don't remember how many files ended up in the card but I still have the .img file. See if it helps.
If you do go down the CoreELEC route and pop in their forums DO NOT mention you installed or even tried to install anything on it other than CoreELEC. They can be a bit nazi-ish about their beloved software.
aml_upgrade_package.img
drive.google.com
[/QUOTE]
[/QUOTE]
Hi,
I have this box too, /q5x3_141 v4.0 20112/
I tried to update the android on it, and got trouble.
The box not starting if I plug in the power.
I have to plug in, and wait about 5 minutes and automatic turn it on, without I touch anything.
But it freeze on the boot loader pic. /clock working/
I tried reinstall rom with pc, same, it not turning on, I have to wait and turn it on itself.
Not help reset, not help that 2 small pin short circuit connect.
Only start itself.
But I can install different rom /I tried 3 different -original 20200901 , nexon x8 q 10 aosp v222, some x96max plus which is not the original/
All of them problem is the same, I have to wait about 5 minutes to start the device, and the boot picture freeze, but clock working /clock first show booting, after clock start as a clock/
I tried different power adapter, different hdmi, different tv, same problem.
Do you have any idea?
----SOLVED-----
This rom fix all the problems.
Now I see, what was the problem.
I bought 4/32 , and it shows on the roriginal system 4/32 version /in the storage I see 25Gb free space/
But in real it is a 2/16 version. And when I updated it updated with 4/32 and crashed the system.
Now with this rom I see the real storage which is 11Gb free, and 2Gb ram
I hope it helps, if somebody walking in my shoes.
hello, I have the same problem, but my box is 2gb / 16gb X96Max + Q5X3_141, I even found their original firmware, which I'm leaving here for you, but I need someone to help me, where can I find the pins for short circuit of the 2gb / 16gb version. below I leave the links to download for both versions:
x96max+ 2gb/16gb: https://mega.nz/file/jlg32KgA#7dVg-5EI9t37YzC4IzDfHiO5bR7tPVzA62c3IRXfohk
x96max+ 4gb/32/64 https://mega.nz/file/P0hzBaiS#8K3DJmhU8OwP8mSCxhW7TcsnCHwDwXFixZVxWjo1G5w
rogerioca said:
hello, I have the same problem, but my box is 2gb / 16gb X96Max + Q5X3_141, I even found their original firmware, which I'm leaving here for you, but I need someone to help me, where can I find the pins for short circuit of the 2gb / 16gb version. below I leave the links to download for both versions:
x96max+ 2gb/16gb: https://mega.nz/file/jlg32KgA#7dVg-5EI9t37YzC4IzDfHiO5bR7tPVzA62c3IRXfohk
x96max+ 4gb/32/64 https://mega.nz/file/P0hzBaiS#8K3DJmhU8OwP8mSCxhW7TcsnCHwDwXFixZVxWjo1G5w
Click to expand...
Click to collapse
I discovered the secret, patience is everything, no need to short circuit, just open the USB BURNING TOOL choose the firmware file and START, then put the hdmi cable, hold the boot recovery pin and connect the usb cable to the pc, release the pin and wait about 5 minutes and it will start to update, mine I discovered by accident, due to the fact that I forgot the cable connected in this way. I hope it helps,
sorry for the english, i'm using google translator
Guys, I strongly discourage opening the box and shorting pins unless 1) you know what you're doing; and 2) you have tried ALL other avenues. Before you go opening the box, please try as many ROMs as possible (there have been two ROMs posted in this thread so far, afaik), also try special formatting tools (like the one I mentioned from Tuxera), and make sure you use MicroSD cards only and if you can, pick a 4GB one.
Best of luck to all having trouble with this godforsaken box and please report back so other people who WILL ALSO have problems can find help in the future.
I have x96 max plus 4gb/64gb board v4.0.Who installed armbian ubuntu on s905x3?
I1V1A1N said:
I have x96 max plus 4gb/64gb board v4.0.Who installed armbian ubuntu on s905x3?
Click to expand...
Click to collapse
This is for H96 max X3 https://forum.armbian.com/topic/13992-h96-max-x3-specifics-only/
ludotaku said:
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
Click to expand...
Click to collapse
its different version the first pic is v4.0 the second pic is v3.0 the short pin location is different.. anyone know where the short pin loaction for the first pic?
Good news for the guys with this new affordable TVBox.
Android TV
Based on the official firmware X98mini_20211027-2130
Root is working via magisk
The video codec AV1 is OK on YouTube, but not on Kodi, nor VLC
Firmware found on the Russian forum 4PDA.
https://drive.google.com/file/d/1iig5gYBz_RrjD4mEtGAJBm3OzX8NV6dE/view
Not perfect yet, but it's much better than the official firmware with its ugly launcher. Hope that Slimbox will soon support this model.
V4
Anyone tried this on the new Tanix TX3mini+ ?
hojnikb said:
Anyone tried this on the new Tanix TX3mini+ ?
Click to expand...
Click to collapse
DaivietPDA has made an ATV version for that model, but it doesn't seem available to download yet.
ATV_X98mini_20211124-2005
I have the x98 mini s905w2 with atv xperience rom. The rom runs pretty good. But can anyone help me get working twrp recovery for this box please..
[email protected]&droid said:
I have the x98 mini s905w2 with atv xperience rom. The rom runs pretty good. But can anyone help me get working twrp recovery for this box please..
Click to expand...
Click to collapse
You installed the 4pda version? or another one?
Mercu7io said:
You installed the 4pda version? or another one?
Click to expand...
Click to collapse
The 4pda version. I scoured the site and others and came up with nothing.
[email protected]&droid said:
I have the x98 mini s905w2 with atv xperience rom...
Click to expand...
Click to collapse
Hi, i am not aware that atvX team released firmware for S905W2 cpu, please, can you provide link to mentioned ROM ?
mAtvXk said:
Hi, i am not aware that atvX team released firmware for S905W2 cpu, please, can you provide link to mentioned ROM ?
Click to expand...
Click to collapse
It's the 4pda version.
link above
LITUATUI said:
ATV_X98mini_20211124-2005
Click to expand...
Click to collapse
i downloaded this ,, but as i dnt have the stock img file i am really worried to give it a go.. can u give me stock img or any other img for x98 mini?
scormaxx said:
i downloaded this ,, but as i dnt have the stock img file i am really worried to give it a go.. can u give me stock img or any other img for x98 mini?
Click to expand...
Click to collapse
Stock: https://dropmefiles.com/iKBV7
LITUATUI said:
Stock: https://dropmefiles.com/iKBV7
Click to expand...
Click to collapse
Do you have a twrp .zip or img that works with S905W2 ? or S905X4 ?
I would like to backup stock partitions (boot,recovery,system,vendor,???), replace kernel splash image, replace launcher with my app only.
Have you had any luck connecting box to PC with a USB cable?
Thank you.
https://www.amazon.com/dp/B09SLRW5SD/ref=emc_b_5_t
https://www.amazon.com/dp/B07PX11SCX/ref=emc_b_5_t?th=1
{
"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"
}
Gantori said:
Do you have a twrp .zip or img that works with S905W2 ? or S905X4 ?
I would like to backup stock partitions (boot,recovery,system,vendor,???), replace kernel splash image, replace launcher with my app only.
Have you had any luck connecting box to PC with a USB cable?
Thank you.
https://www.amazon.com/dp/B09SLRW5SD/ref=emc_b_5_t
https://www.amazon.com/dp/B07PX11SCX/ref=emc_b_5_t?th=1
Click to expand...
Click to collapse
No. I was myself waiting for a twrp img. I sold my box so i am no longer waiting for it. Maybe someone will come up with something.
As far as I know TWRP isn't available yet for these new SoCs.
LITUATUI said:
As far as I know TWRP isn't available yet for these new SoCs.
Click to expand...
Click to collapse
Good to know because I am new at this and I have been wasting quite some time doing guess work.
Is there a way I can have these boxes connect via a USB cable to a PC, I bought the following cable A to A (I call it rectangle to rectangle) however nothing shows in Windows 11 when I connect it. Is there some driver I am missing on the PC side or an app that needs to run on the android box. It would simplify my adb interaction and I think fastboot does not support iport connectivity.
https://www.amazon.com/gp/product/B00P0E394U/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
This picture sold me on bying to the cable
Thank you for your time and insights on this.
Yes, you can use USB Burning Tool.
Download Amlogic USB Burning Tool (Latest Version) - Amlogic Flash Tool
Download the Latest verison of Amlogic USB Burning Tool which helps you to flash the Stock Firmware on Mobile devices powered by Amlogic Chipset.
androidmtk.com
While connecting the tvbox to the computer you have to press the reset button that is inside the AV output. Check the video below.
LITUATUI said:
Yes, you can use USB Burning Tool.
Download Amlogic USB Burning Tool (Latest Version) - Amlogic Flash Tool
Download the Latest verison of Amlogic USB Burning Tool which helps you to flash the Stock Firmware on Mobile devices powered by Amlogic Chipset.
androidmtk.com
While connecting the tvbox to the computer you have to press the reset button that is inside the AV output. Check the video below.
Click to expand...
Click to collapse
So I went ahead and installed the latest "Amlogic_USB_Burning_Tool_v3.2.0" also installed a driver
The "USB Burning Tool" seems to be a one way tool for writing a firmware image to the device, it does NOT provide a function to read existing firmware from the device and create an .img file. Without a valid .img I cannot really follow the steps in the video you shared. I am equating "firmware" with all the code that's in the device and that's probably wrong. More likely I don't need to touch the firmware (code controlling the low level hardware) but instead I need *help* on how to read/backup things like vendor, user installed APKs, my custom bootanimation.zip, ... Such content is more likely located in things like /system /userdata /boot ...??? This is in order for me to replicate it onto another identical device.
See this link for details on my goals/attempts/guess work...
https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/post-86771801
I was hoping the device driver installed by "USB Burning Tool" would cause the classic audible beep in Windows11 like all other USB devices when connected to the PC, however it does NOT. The video shows holding the reset button before connecting the USB cable then releasing the reset button with no power supply or hdmi connected, does that mean power will be delivered to the PCB board via USB power. This did not cause the device to be detected by Windows11.
I have also tried the same sequence with the reset-inAV button depressed prior to connecting the cable, and the power supply connected to the TV box (normal boot).
I am familiar with the reset button for booting into the stock recovery screen however the video seems to be more about custom software "USB Burning Tool" connecting silently/privately to box PCB board.
To iterate my goal with the USB cable is to have Windows recognize the box so I can see it with "adb devices" instead of connecting over WiFi.
Thank you for your guidance.
LITUATUI said:
ATV_X98mini_20211124-2005
Click to expand...
Click to collapse
LITUATUI said:
ATV_X98mini_20211124-2005
Click to expand...
Click to collapse
can i flash it to tx3 mini 2.4g running android 11
Very disappointed why Slimbox had no custom ROMs for X98 mini s905w2 and I could not find any compatible AOSP rom til now.
I would appreciate if someone could help to recommend a compatible AOSP rom for me to test .... or the way to migrate the factory bluetooth/wifi/remote files to other adjustable s905w2 AOSP rom.
Many thanks!