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?
Related
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
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
kebakkaran said:
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
Click to expand...
Click to collapse
I have same problem
Sent from my SM-J320FN using Tapatalk
imrandewana said:
I have same problem
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Same issue here as well, nothing I try works on this phone, it's driving me insane.
EDIT: It's android 6, so you can't root the phone without a custom recovery.
WELP. So I just spent the past 2 days wasting my time on this god awful phone. I can't even access fastboot on this piece of crap, it comes up for 2 seconds and then disappears and no amount of "properly" installing usb drivers for it has helped. I even tried disabling driver signing and installing the drivers through adding legacy hardware. Nothing worked at all. So I thought I'd just install a custom recovery with sp flash tool. So I downloaded a stock rom for the vfd300 (my phone) from here: https://androidmtk.com/download-vodafone-stock-rom-models and ported TWRP using an ASUS Zenfone GO's TWRP.img.
Custom Recovery works fine, the phone does not. It is now stuck in a bootloop. Tried formatting everything (from TWRP) doesn't work. Tried flashing the rom again (even with the stock recovery) still stuck at bootloop, tried about 3 other vfd300 stock roms that people have uploaded to http://forum.gsmhosting.com and none of them have worked either. Currently downloading yet ANOTHER one and tbh I don't have high hopes. (EDIT: It didn't work)
Any help at this point would be appreciated.
Holy crispy crap it started............................. So I managed to find a working rom from (what appeared to be) some Vietnamese file hosting website .
You follow the instructions below at your own risk. No one is responsible for any damage done to your device but you.
I officially have root working on this device.
Now that I've done it, it's a surprisingly simple procedure. As I stated in the edit in my reply above, the VFD300 has Android 6 on it, which requires (afaik) a systemless root to be installed from recovery.
I ported the custom recovery from this thread (since the Z00VD has the same chip as the VFD) which you can download here.
Download the latest version of Chainfires beta SuperSU installer from this thread and transfer it to either your phones internal storage or SD card.
Also download a copy of SP Flash tool (if your fastboot works, use that instead). Finally, you will need this scatter file.
Unplug your phone from the computer and shut it down. Open SP Flash tool and click the download tab at the top.
{
"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"
}
Click "choose" next to the Scatter-loading file box and select the path to the scatter file you downloaded. IMPORTANT Make sure all boxes below except recovery are unchecked and select Download Only in the drop-down box. Double click on recovery in the Location column and point it to the custom recovery image you downloaded.
Click the Download button at the top and then plug your phone back in. The bottom bar will turn red, then purple, then yellow and once it is fully done flashing you will get a pop-up box with a green tick as confirmation.
Unplug your phone and reboot into recovery (Power+Vol-Up). In the custom recovery, select install, go to the directory you transferred Chainfires beta SuperSU.zip to, install it and reboot. TWRP will ask you if you want it to install root, DO NOT LET IT INSTALL ROOT. Your phone may loop a few times and can take up to 10 minutes to boot the first time, but it will be successfully rooted.
If you need a copy of the stock rom, download this one. If you want to flash this rom, make sure you use the scatter file in the roms archive and select firmware upgrade from the Download Only box on SP Flash Tool.
EDIT: I'm so sorry I borked the hyperlink order. Instead of linking to the scatter file I linked to the entire rom and vice versa with the stock rom link
Vikeyev
vikeyev please contact me at [email protected]
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
InevitableDefeat276 said:
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
Click to expand...
Click to collapse
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
kathy9911 said:
vikeyev please contact me at [email protected]
Click to expand...
Click to collapse
....why?
stuck on loading
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
putzwon said:
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
Click to expand...
Click to collapse
Sounds like a boot loop. You need to download the stock rom (it should be about 700mb or so and in rar format). Once you've downloaded the stock rom, extract the archive to a folder somewhere (you will need something like 7zip or Winrar). Open SP Flash tool, load the scatter file from the extracted folder and make sure you select every box. There should be a check mark in each box. Change SP Flash tools dropdown box to firmware upgrade (by default it is on Download Only) and then flash it similar to how you did with the recovery (make sure you change the recovery to the custom one from above).
If my instructions aren't clear enough, I can do it again to my phone and take pictures of the entire process to make it easier to follow.
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Same problem
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
huggies15 said:
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
Click to expand...
Click to collapse
My brother, you're a genius . Thanks for helping out! It was worked. God bless!
stuck with a white circle runs
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
frepeak said:
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
Click to expand...
Click to collapse
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
successfully got a rooted vfd 300
InevitableDefeat276 said:
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
Click to expand...
Click to collapse
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
frepeak said:
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
Click to expand...
Click to collapse
can you provide link please google z not giving results for me
Vodafon VFD300 Firmware + TWRP + ROOT
As recommended above, Vodafon vfd 300 as a result of the phone turned on until the endless download -TWRP was not requested, sr1-SuperSU-v2.82 - sr120170608224931 and flash driver SP Flash Tool 3.1352.01 (5.1352.01) did not fit. I decided to solve the problem - the vfd 300 flashed through the firmware MT6580_S00_EMMC_MRA58K__6.0_VFD 300_Vodafone_356774071726533_08_19_2016_09_02_53 (1) (2), the flash driver SP_Flash_Tool_v5.1648_vin - the next way (remove the battery, hold the volume (-) until the end of the firmware, Download, connect the cable to the phone (the firmware will go to Emergency port about 8 minutes)
****************Next, we flash the TWRP - the flash driver SP_Flash_Tool_v5.1648_ the scatter and the TWRP are recommended - (MT6580_Android_scatter.Tht and
*Recovery-TWRP-VFD300.img) flashing.
**********We check TWRP (we clamp simultaneously ON-volume (+) release ON-opens TWRP.
**********Get Root rights ---- copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to the phone folder, turn off the phone, go to TWRP find Install - SuperSu - Swaipe to instal - Dj not Install. All made happy, good luck. There will be questions [email protected]
InevitableDefeat276 said:
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Click to expand...
Click to collapse
you need to make sure you click download on flash tool then plug the usb in to phone and pc (also remember the battery has to be out of the phone for it to flash)
then you should see the red,yellow, green colours.
Hi all. I will be attempting to root my Vodafone VFD-300 tomorrow,after reading through the entire thread there seems to have been many issues with getting it done successfully. I also saw that it was suggested to provide step by step screenshots of the entire process. If anyone who managed to do the whole rooting with no problems could please do so again and provide us with the step by step screenshots,it would be greatly appreciated. Thanks in advance.
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).
Hello guys, I was one the unfortunate guys who tried to downgrade from an updated XLOADER version FW to an older and failed to do so, resulting a hard brick. I managed to get my phone up and running again with free tools without DC-Phoenix, I include everything detailed in my post, even a preconfigured virtualbox linux system for the initial steps. I also included an UPDATE.app splitter too.
So, this is not an XLOADER downgrade tutorial, with this you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
What you need for this whole thing:
This archive, it contains the firmware, the tools, the preconfigured linux, and the drivers.
VirtualBox downloaded and installed, just google it.
A physically opened phone, unscrewed motherboard, as the testpoint is on the other side, and something to short your testpoint.
First steps:
After you downloaded the archive, just unzip the whole thing to a folder where you have enough space ( the archive is ~7.8GB unzipped)
Now you need to download and install VirtualBox, and import the HIKEY.ova virtual system I included in the zip.
Here's how you can do it
Step one, The HIKEY.ova file is located in the virtual machine folder
{
"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"
}
Step two, Leave the settings at default and import it
Setting up your phone and computer:
You need to open up your phone physically, here is a good video of the disassembly https://www.youtube.com/watch?v=Zkj7YVeSzS4
Now, if you got your motherboard unscrewed, you must leave the cable with the big arrow connected to it.
Plug your usb cable into your phone and into your computer, now you must short your testpoint, I included an image about where the testpoint is. https://i.imgur.com/q9ZNGgx.jpg
Just use metal tweezers or a bent metal paperclip, one end on the test point, and the other end to something you can ground it with, the metal shields next to it are good to use.
If you did everything right, your computer should recognize a new device named USB SER, if this is the case, you now must install the huawei android phone drivers. Now the USB SER is now recognized as HUAWEI USB COM 1.0 in the device manager.
Starting the revive process:
After you got the HUAWEI USB COM 1.0 set up, you need to start the virtual linux machine.
The first thing it will ask for is hw login, just type this with lowercase letters.
Code:
hw
hw (again)
Now, you need to add your HUAWEI USB COM 1.0 to the virtual machine.
To do this you need to click the USB icon in the lower right corner and select HUAWEI USB COM 1.0.
.
.
It should have connected as ttyUSB0, you can check it with the command
Code:
dmesg
Now you need to type
Code:
cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0
(if it asks for sudo password its hw again, also if your device is connected as other ttyUSB number, then you should use that number)
You should see this written from the console if it succeded
With this, you now have a special fastboot booted in your phone.
Flashing the system:
You can now exit the virtual machine, and run first batch, named 1. revive flasher.bat.
It will give you two options after it finished flashing the system, check the one you need, VTR-L29 or VTR-L09.
After the batch is done and you felt that the phone rebooted from the fastboot mode, you can now disconnect the phone from the computer.
You now need to connect the LCD cable, the battery cable, and buttons cable back to your motherboard, no need to re screw the mobo yet, just leave everything hanging in case you need to do the process again with the testpoint.
Now manually boot back into fastboot, Hold volume down while connecting your usb to your computer.
Now you need to flash a TWRP with 2. TWRP recovery.bat.
After that, boot into TWRP, wait for it to completely boot up, and flash an oeminfo with one of the oeminfo batches 3a or 3b.
With this, you should now be able to boot into the system, if there are still problems like bootlooping, do a factory reset from recovery.
Big thanks to:
@goodwin_c for the special fastboot/hikey_idt combo.
@Pretoriano80 for the TWRP recovery
@ante0 for the splitupdate.exe
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
NowLearn said:
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
Click to expand...
Click to collapse
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
yoghurt13 said:
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
Click to expand...
Click to collapse
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
NowLearn said:
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
Click to expand...
Click to collapse
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
yoghurt13 said:
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
Click to expand...
Click to collapse
bro, u didnt have to do that, but I appreciate it. Let me pm u. Thank you again
Would it be possible to rebrand VTR-L09 to VTR-L29 using this method?
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
volpula said:
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
Click to expand...
Click to collapse
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Ekenfo said:
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Click to expand...
Click to collapse
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
I can give you only my instagram.beacause I dont have a backup phone rightnow just waiting to fix my phone.if I can fix that buy a new phone but never huawei again.
yoghurt13 said:
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
Click to expand...
Click to collapse
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
volpula said:
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
Click to expand...
Click to collapse
Then there is the problem, try to install HiSuite, or my android driverpack, and try to see if the phone shows up in device manager.
Ekenfo said:
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
Click to expand...
Click to collapse
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
yoghurt13 said:
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
Click to expand...
Click to collapse
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Ekenfo said:
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Click to expand...
Click to collapse
There is currently no way to downgrade from XLOADER2, huawei did some black magic with it, and there is a checker built in the phone that checks if its a loader1 or 2.
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Ekenfo said:
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Click to expand...
Click to collapse
I literally have no ideai yet how to fix our IMEI, since the NVME partition does not contain the information we need, I just tested one from a working phone, and it was the same as before, zeroed out IMEI.
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?