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:
Related
Hello,
I used Sp Flash Tool to get my ZTE Blade L3 back to Stock (after a self ported rom failed -.-').
Because I was a little sleepy, I didn't unchek all boxes and everything got flashed.
(Preloader, MBR, EBR1, BOOTMG, Recovery, SEC_RO, LOGO, Android (/System))
Afterwars I wanted to restart the phone, but the display stayed black....
As it seems, my L3 only starts the bootloader, but doesn't realy boot ( Device-Manager doesn't detect the phone).
After many tries, I wasn't able to acomplish something.
Tried:
-reflash everything
-only flash bootloader, MBR, EBR1, BOOT, LOGO & SEC_RO
-flash bootloader & format flash
-(wasn't able to get meta-mode http://forum.xda-developers.com/showthread.php?t=1943442)
Sometimes the phone loopes the bootloader and changes between Mediatek Preloader & Mediatek USB Port (strangely the COMs switch between 6 and 7).
SP Flashtool Memory Test also says:
Error: NAND Flash not detected!
Error: UFS not detected!
{
"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 to expand...
Click to collapse
I don't know what I can do anymore, I hope that someone can help me.
Just for someone else who comes here the ROM (at least the stock ROM)... Go to 4PDA. I went 6 days trying to learn how to fix the phone without knowing anything about any of this, and luckly I found 4PDA... It has ROMs of the phone. Stock ROMs (which was what I wanted) and modified ROMs. Nowhere else I found stock ROMs for it... I REALLY recommend that website for ANYONE who mods the phone... At least if it's not that known, like Blade L3. It's in russian, but if you need, use Google Translate or any other translator and it will work well enough. This phone can't be bricked. I've done many stupid things to it. It's ALWAYS recoverable. I can do whatever I want. It will never be bricked. As long as a phone with a MediaTek chipset has a scatter file and correct files to flash, it can't be bricked. At least from my experience... Cheers!
using SPFlash you need to click on download or if not working click on firmware upgrade, not on format and download!
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
OTT TV BOX, GooBang Doo M8S-II, M8S-II, AMlogic s905_v3
{
"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"
}
External:
OTT TV BOX Action 4K AS-14 64bit
4x CPU Cortex A53 5X GPU Mali-450
2GB RAM
16GB ROM
Internal:
S905_V03 2016.04.15
M8_IO V3_0_20150110
AP6330
I have two of these... wonderful /s devices. both ended up in a bad way. One was OTA update that nuked it and the other was me playing with it. :crying:
Years go by and every so often I see if they can be salvaged, but to no avail. Recovery is working, holding the reset button does nothing; just a blaack screen and then the tv turns off due to no signal. Finally a break through, the USB Burning Tool provided by Amlogic. After a ton of trial and error and the destruction of two many usb cables; i was able to find the combo to restore the both systems.
WARNING
This is not an upgrade guide. This is a use at your own risk, get this thing working, hail mary kinda thing. I cant help or guarantee anything, just after countless hours of seeing unanswered forum posts and scattered info, i had to do something. Again, AT YOUR OWN RISK!
Reqs:
USB MALE A to MALE A
Havit 2-Feet USB 2.0 Type A Male to Type A Male Cable, Black (1pack)
https://www.amazon.com/gp/product/B00UF8SEA0/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
(attempted making my own, but neither functioned properly)
Amlogic USB Burning Tool v2.1.6.8
update_minim8s_rv104L03.img
http://www.mediafire.com/file/clodv5h2c8c5y9c/oct_M8S-II_RecoveryPack.7z/file
(both are 7zipped in this location)
extract the .img file and burning tool to the desktop.
Install the burning tool, the driver should also install.
import .img into tool, leave all settings default.
connect usb, in my case i had to connect the power cord as well.
press start
install takes about 8 minutes. after it finishes let it sit for another 3-5 minutes, (why not!)
click stop, disconnect usb and then power if needed.
connect to hdmi and plug back in - should be about 10 to be back in the os
REMOTE MAY OR MAY NOT WORK! one did one didnt, idk, im not a doctor.
Hopefully this helps someone else with a bricked device.
I tried a ton of other images floating around out there, but none did the trick. this got me back into the os and operational.
FOLLOW UP
Was able to get Batocera 5.10 running.
burn image to sd card or usb.
Copy dtb.img into boot folder
profit.
LINK
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?
Hi guys.
Have X96 Max 3, had Slimbox ROM, rooted, and TWRP installed.
Wanted to go back to stock because didn't manage to get Netfilx in FHD.
First I installed official recovery, then, official ROM X96Max_Plus2_20200901-1005 ROM
That went without any errors, but after reboot, it stucked there.
Tried to short pin it, nothing. (already done this few times before, every time worked, till now)
But, if I leave it connected via USB A-A cable to my computer, after 10 mins it boots, but UBT won't recognize it.
Tried few versions of UBT, but no luck.
{
"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"
}
Anyone tried to unbrick via modded HDMI dongle?
I guess I need clean image for microsd card.
Anyone know where to get one?
Amlogic HDMI Boot Dongle
@superna9999's Linux kernel source fork for upstream development - superna9999/linux
github.com
Is this ROM X96Max_Plus2_20200901-1005 latest version? You must find original firmware, first version when trying to recover box after bricking.
It`s not necessary to install official recovery when install new firmware with UBT, it will be installed with firmware.
Salacue said:
Is this ROM X96Max_Plus2_20200901-1005 latest version? You must find original firmware, first version when trying to recover box after bricking.
It`s not necessary to install official recovery when install new firmware with UBT, it will be installed with firmware.
Click to expand...
Click to collapse
My Box is not recognised by UBT. That's was the problem in first place.
First that is not a plus2 board that is a plus board. It don't have the second radio and the chip is not on the board it's on the other side. The original firmware would be the 1449.
Yea. I believe I've got scammed.
I bought it here in Croatia in big electronic store. Very reputed one.
Even on receipt it says it have 1000mbit, BT, which has not for sure, 4/32.
But when I opened, critical writings on the chip was marked out with black pencil.
However, I tried to remove that black pencil markings, but I ruined the whole sticker.
This one the very same like mine, and it's clearly written on stickers 2/16
That's way I bricked my second X96 from same store.
First pic, mine with blacked out writings,
And second one I found on pda4.
Anyway, I managed to partly unbrick by it via self modified, and programmed HDMI emulator dongle, and it's now recognised by UBT. It was really fun method, will describe in thread I opened before.
I will flash 1449 fw, that is intended for 2/16
Anyway, how to count how many memory modules I have?
Well if you have a 2/16 model. Then you have to verify that you don't have the modified version of the plus. That takes the JAW firmware only. I suggest you identify each chip and write down the numbers on the chip and then compare it to all the data at the information link for the slim box firmware for the x96 Max Plus. To truly determine which box you have. That's key to know which box you have before you ever load firmware and you skip that to begin with and you still aren't certain which box you have.