Debricking an Amlogic M8S Android TV Box - Android Stick & Console AMLogic based Computers

I have scoured the internet for material on how to do the above and I have found two ways to do this:
1: The matchstick/toothpick method
2: The Male-to-male USB cable method.
I have also downloaded numerous versions of M8S firmware, only two of which seem to give some hope. The problem is that I am stuck in the boot loop with these two and one of them shows the M8S+ logo. I have tried to get the TV box to install TWRP in the recovery partition to no avail. I have studied both the aml_autoscript file (looks like a promising solution, but I do not know if the addresses that I have are correct) and the *.ml file which is more straightforward, but I do not seem to have a working .ZIP firmware file to flash. I am also not sure whether any of the recovery IMG files are meant for my device since they never work.
I am at wits end and I need to bring this box back to life. Is there any other way I can flush the recovery partition? Do the many versions of firmware (all purported to be for the M8S) imply that we have different versions of the M8s?
The motherboard on my device has the text "M8 V8_*" on it and 20150923 below that as shown in the attached image. Someone please advise.
{
"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"
}

Here's a photo of the board: https://pasteboard.co/HsbIlbB.jpg
Saichovsky said:
I have scoured the internet for material on how to do the above and I have found two ways to do this:
1: The matchstick/toothpick method
2: The Male-to-male USB cable method.
I have also downloaded numerous versions of M8S firmware, only two of which seem to give some hope. The problem is that I am stuck in the boot loop with these two and one of them shows the M8S+ logo. I have tried to get the TV box to install TWRP in the recovery partition to no avail. I have studied both the aml_autoscript file (looks like a promising solution, but I do not know if the addresses that I have are correct) and the *.ml file which is more straightforward, but I do not seem to have a working .ZIP firmware file to flash. I am also not sure whether any of the recovery IMG files are meant for my device since they never work.
I am at wits end and I need to bring this box back to life. Is there any other way I can flush the recovery partition? Do the many versions of firmware (all purported to be for the M8S) imply that we have different versions of the M8s?
The motherboard on my device has the text "M8 V8_*" on it and 20150923 below that as shown in the attached image. Someone please advise.
Click to expand...
Click to collapse

Spoke to soon... I found this post just minutes after starting this thread. Sharing here for the benefit of anyone else who might find himself or herself in a situation similar to mine: http://freaktab.com/forum/tv-player...ng-tool-fails-at-2-solved?p=537504#post537504
Just boot up using your SD card after following the given steps and leave it. The recovery screen should come up after a while.
I'm installing apps as I type this

Related

[Q] Chinese Android TV Box Not Booting

Hey Guys!
I purchased two android TV boxes few months back. and one box got stuck at the android logo and i flashed it using MATRICOM_MX2_115_FULL_AUG_09_2013.imgc image file, and now it works fine.
The other box just shows a blank screen nothing displays. When i power it on the LED flashed and then nothing else. I tried to flash it but it ddnt work just the black screen.
i took it apart to flash it and this is how it looks.
{
"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"
}
Any help appreciated guys....
Thanks.
same problem but cant flash
I have the same box, i took it apart to find the reset botton, i couldn't find any. It is stuck on the android logo, how did u manage to flash it. Plz provide ur steps.
afshandc said:
Hey Guys!
I purchased two android TV boxes few months back. and one box got stuck at the android logo and i flashed it using MATRICOM_MX2_115_FULL_AUG_09_2013.imgc image file, and now it works fine.
The other box just shows a blank screen nothing displays. When i power it on the LED flashed and then nothing else. I tried to flash it but it ddnt work just the black screen.
i took it apart to flash it and this is how it looks.
View attachment 2778028 View attachment 2778044
Any help appreciated guys....
Thanks.
Click to expand...
Click to collapse
I also have the same problem with my device. it doesn't have any reset or volume button on it. I posted about my problem here:
http://forum.xda-developers.com/general/xda-assist/android-box-stuck-boot-logo-t3127923
could you please provide the steps you took.
I found a part on PCB board which said recovery so I connected the two pin and I got it into recovery but there is no option there. there is also three holes which says debug but I don't know how to connect it to pc.
I had a same device and using Online Nandroid backup I made a backup of the ROM which gave me boot.img recovery.img and some other files I put them in the SD card and put the device on recovery but nothing starts and there is only an android guy resting with no option and since there is no volume or power button I can't get into any option
thanks
This is also a picture of the board

Help: LG L70 D325; Blackscreen, no fastboot, no recovery, no download mode

To begin with, my device is LG L70 D325.
I accidentally deleted the swap file in my sdcard. Now my phone does not boot. (No fastboot, no recovery, blackscreen), but it is detected by my computer as a storage device containing "verinfo" and "image" folders.
I found this YouTube Video [youtube com/watch?v=ps6HYc7QWmg]
and this link [androidforums com/threads/guide-unbrick-lg-l70-no-download-mode-no-recovery-mode-no-fastboot.893311] which happens to be the same case of mine, and managed to do the instructions successfully (without errors) but it doesn't boot or solve my issue.
I also tried this guide [www lg-phones org/how-to-flash-unbrick-lg-l70-back-to-stock.html] but since it doesn't recognize my device as LG/Android device, it does not work.
Before posting this question, I saw this link which is similar to the YouTube video mentioned above but I don't have other .img files (laf.img & boot.img) for my device.
Since that thread is for LG G2, I assume I am not allowed to ask for the .img files for my device.
In addition to the YouTube guide, everytime I plug my device on Linux, it shows this error.
{
"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"
}
pvzkch said:
To begin with, my device is LG L70 D325.
I accidentally deleted the swap file in my sdcard. Now my phone does not boot. (No fastboot, no recovery, blackscreen), but it is detected by my computer as a storage device containing "verinfo" and "image" folders.
I found this YouTube Video [youtube com/watch?v=ps6HYc7QWmg]
and this link [androidforums com/threads/guide-unbrick-lg-l70-no-download-mode-no-recovery-mode-no-fastboot.893311] which happens to be the same case of mine, and managed to do the instructions successfully (without errors) but it doesn't boot or solve my issue.
I also tried this guide [www lg-phones org/how-to-flash-unbrick-lg-l70-back-to-stock.html] but since it doesn't recognize my device as LG/Android device, it does not work.
Before posting this question, I saw this link which is similar to the YouTube video mentioned above but I don't have other .img files (laf.img & boot.img) for my device.
Since that thread is for LG G2, I assume I am not allowed to ask for the .img files for my device.
In addition to the YouTube guide, everytime I plug my device on Linux, it shows this error.
Click to expand...
Click to collapse
You might want to look into this:
https://youtu.be/RpvvAeD08b4
Can someone help me?
Can someone help me?
I have an LG L70 D325f, had this problem but I formatted it and no longer appears the two folders "Image" and "verinfo".You have any solutions?
Pardon my English
LeandroDa7 said:
Can someone help me?
Can someone help me?
I have an LG L70 D325f, had this problem but I formatted it and no longer appears the two folders "Image" and "verinfo".You have any solutions?
Pardon my English
Click to expand...
Click to collapse
It fix?

Q-Box Issues

I have multiple issues, so figured I just start a new thread and attack each as they occur.
Ok, I have a heap of these Qbox, I'm trying to get a new custom ROM going on them, but I'm having dramas as nothing is consistent. Turns out I have TWO different types. I was struggling to get TWRP going as it would work on one, not the other. Was taking backups from one to try and fix the other, etc...
Anyway. I have the following boxes
- QBox s905 2/8GB
- QBox s905x 2/8GB
The main focus here is the s905x box (I have more of them). After getting TWRP working, I tried to flash a "stock" zip file to the box only to get an error saying it was incompatible as my box was a Nexbox a95x.
This is how I found the newer firmwares for the unit. They flash the img with USB Burning Tool fine and operate correctly, however the remotes dont work. I have tried three different a95x images (6.0, 6.0.1 and 7.1). I have copied over every remote config I can possibly find to the /etc folder with no results
Heres the remote in question.
{
"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 root and can copy/edit/delete from the root folder.
Any help appreciated
simonchunk said:
I have multiple issues, so figured I just start a new thread and attack each as they occur.
Ok, I have a heap of these Qbox, I'm trying to get a new custom ROM going on them, but I'm having dramas as nothing is consistent. Turns out I have TWO different types. I was struggling to get TWRP going as it would work on one, not the other. Was taking backups from one to try and fix the other, etc...
Anyway. I have the following boxes
- QBox s905 2/8GB
- QBox s905x 2/8GB
The main focus here is the s905x box (I have more of them). After getting TWRP working, I tried to flash a "stock" zip file to the box only to get an error saying it was incompatible as my box was a Nexbox a95x.
This is how I found the newer firmwares for the unit. They flash the img with USB Burning Tool fine and operate correctly, however the remotes dont work. I have tried three different a95x images (6.0, 6.0.1 and 7.1). I have copied over every remote config I can possibly find to the /etc folder with no results
Heres the remote in question.
I have root and can copy/edit/delete from the root folder.
Any help appreciated
Click to expand...
Click to collapse
if your 100% sure, remove the assert lines from updater script, do it at your own risk :good::good:

Creating Tablet image to transfer to others

Hi,
Newbie here so go easy!
Ive been changing the settings on an imported chinese tablet such as boot image, remove bloatware, download apps required, etc and it works great. However, I want to be able to create a full image of one tablet and transfer that to other tablets I buy so I dont have to manually do this every time. Basically a full backup and restore of everything on the tablet.
Can anyone assist on the best process to do this.
Thanks
If device's Android got rooted then you can perform a full NANDroid backup by means of either TWRP or FlashFire. FYI: ROOT is required for mounting all partitions as RW.
TWRP:
{
"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"
}
Flashfire:
Full article here:
How to Backup Android Device Completely 2023 (Updated)
If you plan to unlock bootloader or want to flash custom ROM, this guide is for you. In today's article, I will show you how to Backup Android Device
www.rootingsteps.com
Hi,
Thanks for the help.
The device is rooted but im struggling to get a TWRP recovery image for this tablet as its a chinese import. However, its a Rockchip RK3288 tablet. Any help with where to find correct version?
Also when I down loaded flash fire its starts up but crashes after a few seconds?
duckett100 said:
Also when I down loaded flash fire its starts up but crashes after a few seconds?
Click to expand...
Click to collapse
Do a LOGCAT to get the reason why.
[Tutorial] How To Logcat
Here's how to use logcat: There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app: Here are two good examples are either: aLogcat or Catlog I prefer...
forum.xda-developers.com
Hi, I worked out why flash fire was crashing, but some of the items in the app are greyed out so it doesn't allow a back up. I think its because I still have the standard recovery that came with the tablet instead of something like TWRP. And I cant find one online that will work.
Are there any other ways to do a full back up programmatically?

Bricked Vodafone Smart Tab 4G stuck at Android logo.

Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.

Categories

Resources