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?
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.
Hey,
Tried as hard as I could not to have to ask, looked everywhere I could think of, searched through dozens of threads and found nothing in regards to my Trio Stealth G2 tablet.
My question is, what method of rooting should I use for my tablet, and once I do root would there be a custom ROM I could use?
I've seen people mention they messed up flashing a custom ROM to the Stealth Pro 7, but I'm not sure if any ROM made for a 7" Cortex A9 tablet would work. Don't want to brick this though so thought I wouldn't chance it.
Thanks
I got the other day an I am to wanting to root it I think bin4ry root method would work but adb won't work cause there's no fastboot on the thing it dose have a recovery but its 3e
Sent from my G2 using xda premium
I think I got some progress today while its pluged into ur computer press pwr+vol- to get off of battery charging screen then hold them till u here ur computer make the sound like something got pluged in an ur tablet will be under m3-chipset in device manager search the internet for aml flash tool I have got it to connect to my pc
Sent from my G2 using xda premium
Not gonna use aml flash tools cause I can't find any good info on it found a safe mode on the thing today an got root with bin4ry to finally pick up the device its using adb still no root cant get a backup made with it an adb in cmd won't pick it up I know the tab has it tho I found the adb file on it after looking forever View attachment 2107849
{
"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"
}
Sent from my G2 using xda premium
here is a method that might work for you
go to my thread: forum.xda-developers.com/showthread.php?p=44294370#post44294370
I would post it here but i would just take up alot of posting space writing it down..the way i did it worked for me and believe me i was going for hours trying to find someway to root my trio stealth g2 until i found out how lmao let me know how it goes
U really got root on it
Sent from my G2 using xda premium
Yeah I did i have it rooted now with the play store mod
Sent from my G2 using xda app-developers app
Trio Stealth G2
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.
slick97477 said:
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.
Click to expand...
Click to collapse
Hi, slick97477. Where did you get the One Click Root tool? I didn't see any forums for this (or any other Trio) device on here.
Thank you in advance.
http://forum.xda-developers.com/showthread.php?t=1734365
One click
I got it from here
just google oneclickroot
and just run it. Couldn't believe it worked but it did.
However today went to try and turn it on and nothing, Just hung and the Trio logo. Let it sit for about 10 minutes. Decided maybe battery was dead and plugged it in still nothing. No battery logo nothing. Hit reset button and plugged it in again and nothing. Screen doesnt come on now nothing but however weird thing is it shows up as winusb now under devices which is amlogic driver for flashing firmware which im not sure how this has happened but it has. I have took it apart and took pics of the mainboard and cpu. Would like to see if perhaps there is firmware out for this...Have done quite a bit of research and numerous different things so far..
I have downloaded the firmware installer from amlogic but so far no firmware seems to like my cpu....Hmmm well cannot upload pictures yet for some reason..If anybody is interested in trying to help me figure out which firmware will work on it I would greatly appreciate it. I used it the night before and it worked great. Have not installed anything new or anything so I am a bit baffled in how the firmware got torched but I am pretty sure that is what has happened any ideas I am willing to try. I have recently dived into really messing with the android devices but had not done anything with this tablet yet because I had not found a way to back up the current firmware on it...so was really being nice to it for now....
(Edit) Pics are included just didn't try hard enough
try this
Yea id like to help try turning it on while its pluged in ur computer then hold the power button till u here the sound like something got pluged in ur computer then then hit the power button to turn it on if this dosnt work try turning it on then after the @9 boot logo hold both volume keys that should put it in safe mode only the apps that came on the tab will work
Trio Stealth g2 tablet issues
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible
Stealth G2 9.7"
damncheaptablets said:
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible
Click to expand...
Click to collapse
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.
Issue
spurloc said:
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.
Click to expand...
Click to collapse
Hey I was able to flash the tabley with aml but I used novo 7 fire and now nothing comes up, no boot screen or anything, however when its plugged into my pc I can access the internal storage and Micro sd card storage, but I need to remove the rom and get one that works correctly for the tablet, unlike before It wont let me push the power and vol button to make it go to the m3 chip which then I could use the aml world cup driver so some how I have to flash it from the internal storage or by some means but I have no clue at this point. The driver is Portable media player MID Novo7 I changed the driver to android ADB which it installs but then I cant access the internal storage, is there anyway to re flash this? I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing
damncheaptablets said:
I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing
Click to expand...
Click to collapse
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440
Umm ur awesome
spurloc said:
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440
Click to expand...
Click to collapse
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed
damncheaptablets said:
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed
Click to expand...
Click to collapse
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar
Yeah im stuck now
spurloc said:
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar
Click to expand...
Click to collapse
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
\40D_resque.zip
W/ [P2][19:41:11]Loading spl ...
W/ [P2][19:41:12]Transfer Complete! total size is 18556 Bytes
E/ [P2][19:41:13]Spl code,identy(-1)
E/ [P2][19:41:13]Load uboot failed 1 times
E/ [P2][19:41:14]Spl code,identy(-1)
E/ [P2][19:41:14]Load uboot failed 2 times
E/ [P2][19:41:15]Spl code,identy(-1)
E/ [P2][19:41:15]Load uboot failed 3 times
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me
damncheaptablets said:
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me
Click to expand...
Click to collapse
It looks like there's an issue with that specific u-boot.bin (u-boot-orig.bin) within that package. Although the fact that it shows up in device manager as Portable device means that part of it was written by the flash utility. Have you tried force-ably replacing the drivers from portable device to android adb drivers. This might allow you to access the adb recovery mode.
Alternatively if ADB doesnt show any devices after replacing the drivers, you might want to uninstall the adb drivers that didnt work, once it appears as portable device again, the tablet might be looking for its new firmware on the sdcard. Check out the page in the link and follow the instructions for "Method One - SD Card Method for a "soft" brick". It involves restoring a factory image onto the sdcard using a handy tool "USB Image tool" and then rebooting. It might kick in an update from the sd.
link --
slatedroid(.)com/topic/41478-how-to-unbrick-your-amlogic-aml8726-mx-series-tablet-v20/
Also I could upload the aml flash files that are getting me into adb recovery mode every time
Hi my friends In this guide i will teach you how to root your Jiayu g5s+
{
"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"
}
Steps:
1.Drivers
2.Rooting
3.backup with mtkdroidtools
4.Install cwm through mtkdroid tools
1.DriversDownload the drivers and mtkdroidtools from here : https://mega.co.nz/#!z9oXgCpD!5Vil8gYSC3rwUdTIImt0PYKRObbZVc17i4GpVx7RKQw
extract the archive and connect your phone with debugging enabled
then go to start and type device manager you will see that adb driver arent installed double click on it locate usb folder you extracted and your done
or google how to install adb drivers
2.RootingThere are many tools to root this phone
the tools you can use to root your jiayu are
1.Cydia Impactor
2.Kingoroot <-i recommend this how to root go here -> http://androidxda.com/root-android-device-using-kingo-root
3.Vroot <-Becareful this one is backdoored run it via sandboxie http://sandboxie.com/
3.Backup with mtkdroidtoolsdownload scatter file https://mega.co.nz/#!KwpWURQC!8CGoDjsE-BsGwBOT08Ljzu9XsXlfIFo3uBKRYb-VvaU and put in mtkdroid tools directory
copy scatter also in backup directory of your phone
open mtk droid tools connect phone with usb debugging enabled then go to "root,backup,recovery" tab click on backup and wait till its funished
then click on "to prepare blocks for flash tool" then choose files.md5 and wait till its finished
4.cwm recoverythere are many tools you can use to install cwm recovery
but these two i used are good
1.open mtk droid tools go to "root,backup,recovery" tab click on "recovery and boot" button
Please check always your phone the tools ask you for revoke acces you have to allow them
2.Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY
http://forum.xda-developers.com/showthread.php?t=2748169
Download here my backup : https://mega.co.nz/#!DlhEGKJC!GJYxUBaJIaiEMuqnCMmctgO7XYnvcrlpo9aJ1S1wCac
Many thanks my friend, you have saved my phone, it works correctly now
We will keep alive this thread for any news for this phone.
Again, thank you very match.
Amazing timing, I just started looking for ROMs for this phone yesterday and today you post!
Subscribed for future updates
Have any one problemes with TitaniumBackup ?
I can not backup any thing, restore any things !
the sdcard contains already app backups (from an other phone) TB already see them but no way to restore.
bricked Jiayu G5S+ (Elephone P6i)
Hi!
I tried to change the ROM for a friend's fake Jiayu G5S+ phone (a have some previous experience with flashing ROMs but neither me and especially my friend didn't know about this being a fake) so I tried to flash a G5S ROM and the phone now is bricked. The SP_Flash stops after the red stripe, "DA Download 100%" and that is all. From time to time I hear the sound of a new connected device in my PC speakers and the MTK USB port reappears in Device Manager.
Any idea how could I revive this phone, even it is a fake ?
My friend is very sad as I ruined his phone. Anyway, he couldn't use it with the original ROM because the touchscreen keyboard wasn't calibrated, he could not type almost anything.
L.E.: I tried to flash the backup that Gr4nDT3R0R posted above, now I get this error BROM ERROR: S_CHIP_TYPE_NOT_MATCH. I guess the ROM is not for my chip(set):
In the picture, I see that you do not provide the preloader.bin, you must give it (it is a part of the backup).
Then you have also to provide android, cache and data images, even from other ROM (system.img is in the backup, and you can extract cache.img and userdata.img from an p6i ROM)
Use, as you do, "format all + download" and it must works (if your phone is JY-G5S+, otherwise, use an entire ROM from elephone p6i)
Sent from my ZOPO ZP990+ using XDA Free mobile app
Yes, it might be wrong what I showed in that picture, I guess I tried a dozen of times to flash different ROMs. Today I finally managed to flash the original ROM provided by the author of this topic. It seems that after plugging in the phone to the USB port, right after the "ding-dong" sound you have to insert the battery. So I could see the so long waited yellow bar. After this I used the MTK Droid Tools and which showed that in fact the phone is a Quad Core MTK i6, 4.4.2, ALPS.KK1.MP1.v2.13 phone (instead of Jiayu G5S+, full HD screen, octa core...). I don't know how but after repeated tries now the phone is showing the real specs in About phone section.
Anyway, the reason I tried to change the ROM is that the touchscreen is acting weirdly, it is not calibrated, it is impossible to tap a text using the virtual keyboard. Even the menu items are very hard to tap as they don't respond to touching but the ones from vicinity. I have found a few recent videos with the same problems on Youtube but none have the solution. The screen is 540x960 and I guess the LCD driver is not the proper one.
Right know I am glad I managed to revive my friend's phone but I am pretty sad of his loss (I recommended him to by another trusted phone but he wouldn't listen to me).
Maybe in time, some smart guys will find any workaround for these Jiayu G5S+ fakes.
Jiayu g5s+ fake
Hi I Jiayu G5S + fake. I downloaded the rom elephone P6I update. The sp falasha tool I put the firmware upgrade. All went well. But the phone is now dead. When I try to give my deposit so still lists the error. If you give the firmware upgrade takes place so blue about three times and then prints cheksum failed. If so I will just download again writes PMT changed for the rom, it must be downloaded. Please if anyone know help us some advice.
fake Jiayu G5s+
doldik611 said:
Hi I Jiayu G5S + fake. I downloaded the rom elephone P6I update. The sp falasha tool I put the firmware upgrade. All went well. But the phone is now dead. When I try to give my deposit so still lists the error. If you give the firmware upgrade takes place so blue about three times and then prints cheksum failed. If so I will just download again writes PMT changed for the rom, it must be downloaded. Please if anyone know help us some advice.
Click to expand...
Click to collapse
sorry for my english
I'd done so.
I used this version of SP.FlashTool v3.1320.0.174.
In addition to the files for flashtool is in this post, add the two missing (cache and userdata) of this rom.
http://www.needrom.com/download/elephone-p6i/
Then select all and give a firmaware upgrade and also mark "DA DL All whit check sum" and has to work.
luck:good:
:good::good::good::good::good::good:
Super. Already mobile lives. It is everything. Your procedure is a 100%. Had 24 hours of suffering.
I also do not know English. I am from Slovakia.
Once again many thanks.
doldik611 said:
:good::good::good::good::good::good:
Super. Already mobile lives. It is everything. Your procedure is a 100%. Had 24 hours of suffering.
I also do not know English. I am from Slovakia.
Once again many thanks.
Click to expand...
Click to collapse
Glad many, it is a pleasure to help
Just do not understand why he had killed the recording rom from elephone P6I.Everything passed smoothly until final confirmation.Everything passed smoothly until final confirmation. I used SP_Flash_Tool_v5.1352.01.A choice of upgrade.Through net download it would not let me on.Well, after reboot phone has not responded to anything.Then somehow after about 50 experiment has released a record at least preloader.The display has been seen batteries.Again, after several attempts we have recorded the entire archive.But the phone cycles through the android logo.They let me into the start menu via the minus button and start.No I did not find the file from the backup to SD card.Meanwhile told me the phone and I revived to full finery.I also tried older flash tool, but not load file scater.I wanted to remove the fake hardware information.Therefore, I recorded the rom elephone.And he made I have a lot of joy instead of worry.I did not know that the phone is fake when buying.But when I gave her ignorance was added resellers deceive my next concern.I do not know what a cell phone.What is hardware and what rom fit into it.I would be grateful if someone figured out how rom is good for this model.
fake
doldik611 said:
Just do not understand why he had killed the recording rom from elephone P6I.Everything passed smoothly until final confirmation.Everything passed smoothly until final confirmation. I used SP_Flash_Tool_v5.1352.01.A choice of upgrade.Through net download it would not let me on.Well, after reboot phone has not responded to anything.Then somehow after about 50 experiment has released a record at least preloader.The display has been seen batteries.Again, after several attempts we have recorded the entire archive.But the phone cycles through the android logo.They let me into the start menu via the minus button and start.No I did not find the file from the backup to SD card.Meanwhile told me the phone and I revived to full finery.I also tried older flash tool, but not load file scater.I wanted to remove the fake hardware information.Therefore, I recorded the rom elephone.And he made I have a lot of joy instead of worry.I did not know that the phone is fake when buying.But when I gave her ignorance was added resellers deceive my next concern.I do not know what a cell phone.What is hardware and what rom fit into it.I would be grateful if someone figured out how rom is good for this model.
Click to expand...
Click to collapse
http://service.elephone.hk/forum.php?mod=forumdisplay&fid=98#.VGzQbvmG8Zn
looking here
Thanks.You do not have to quote such a long post.
Original rom for ELPHONE not want to work. I run the risk of custom rom?
doldik611 said:
Thanks.You do not have to quote such a long post.
Original rom for ELPHONE not want to work. I run the risk of custom rom?
Click to expand...
Click to collapse
developments???io find nothing , the custom MIU , goes just as bad , I've tried, and locks the touch
You have Jiayu G5S +?Use the old rom how did you get it?You rom works by elephone P6I?
doldik611 said:
You have Jiayu G5S +?Use the old rom how did you get it?You rom works by elephone P6I?
Click to expand...
Click to collapse
Yes, I hold Jiayu G5S +, but I do not keep the rom originale.l'ho lost by putting a rom Jiayu G5S original (wrong) and I raised up with this post.
you have the original rom Jiayu G5S + ?????
Have a little different.Because I put the factory settings.And then I made a backup.When you try to load the rom elephone I had a brick.After recording my backup files from + 2 elephone I do not have computer and boot logo Jiayu, but android.Rom of elephone not want to work.I tried to put preloader.bin from my backup, but hangs at log elephone.
The information on phone type I: i6 and quad core.
Online test of CPU-Z as follows: http://valid.canardpc.com/a/2amvfb
doldik611 said:
Have a little different.Because I put the factory settings.And then I made a backup.When you try to load the rom elephone I had a brick.After recording my backup files from + 2 elephone I do not have computer and boot logo Jiayu, but android.Rom of elephone not want to work.I tried to put preloader.bin from my backup, but hangs at log elephone.
The information on phone type I: i6 and quad core.
Online test of CPU-Z as follows: http://valid.canardpc.com/a/2amvfb
Click to expand...
Click to collapse
we get closer to the truth.
try this (looks much better).
You'll say
http://www.needrom.com/download/zlr-i6/
I tried and the phone did not work - brick.I do not remember what rom would be good.To show the actual hardware.And there are still other data.We do not know what brand and model really is.While we remain in a false indication.Therefore, I would like to prefer the original rom.I did not have to look for information under the designation as a fake.So no elephone P6I.It just seems so outwardly.But (intestines) hardware is different.Perhaps better, but also can be worse.While this is a mystery.:laugh:
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).
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?