s805 m201(?) Read Only File System?

[blahblah]

Hi,

I picked up a WorldMax Quad TV Android box, with provider-locked-up functionality. https://fccid.io/2ADRS-QUAD After 42GB of image downloads, I found a KitKat MQx firmware that seems a reasonable starting point, yet no wifi or ir remote..

I have some aspirant remote.conf files for the IR remote controller, and instructions on where to put them. I also have some driver files for the wifi (RT8189), and instructions on where to rename and place them.

I installed Android Terminal Emulator app, and found that I could issue the su command to gain root # privileges. (Does that mean my box is pre-rooted?)

So I run su, then cd to /etc to copy the old remote.conf file, and replace it with some other candidates. Even as root, the os refuses with 'read only file system'. What does this mean, and what can I do to get around this?

I don't want to start installing super user apps just yet, not before I've backed-up the entire system as I have it now. Any hints on what I should be looking for, in terms of fully backing-up and restoring firmware images, would also be of much help. I have no clue what's the norm, or what to look for.

Thanks for reading, and for any help you can provide.

B. :-)

[blahblah]

Okay, I managed to get TWRP to boot off an sd card, and do a full backup.

Now for the wifi drivers and remote control installation. The info I have is plain wrong, so if anyone can help me install the requisite 8019es.ko file, and remote.config files...?

TIA.

[blahblah]

Okay, I have the files I need, I now know where they go, by in trying to copy them there, I still get the Read-only file system error.

Any thoughts?

TIA

[freddy]

This box is done
Get rid of it...

Kit Kat.....seriously????

Maybe look for rom that us at least Android 5
That matches your hardware
Ethernet
Wifi
Bluetooth
Remote config.

There are many roms compatible..

Or try something like EmuElec/libreelec
Armbian.

Below your post is
Linux for S805 bales 150

Also there is 42 pages of posts to read
Since Box is 9 years old approx.
Go to page 42
And read from there..

Happy Testing

[blahblah]

Thanks, Freddy. I don't actually need a TY Box, as I have an Ubuntu Celeron for that. It's about the challenge of cracking something difficult. Once I've done that, then I'll likely throw, or give it away.

B.

[blahblah]

Not sure I can find the extended thread you mentioned, Freddy. It sounds like something I should be looking at.

B.

[freddy]

I think I mean this.
If you back out of this Thread you created
Look down will see 1 to 42 pages of threads/posts

Since your box is 2015/2016 ish
Anything relative will be on the last page 42
Then will have to read forward in time..
To present day.

ExhaustIng for a box that is redundant...

I can't remember anythinanything Kit Kat except
Edit build prop to read as Android 5.0
Why that was done????
No idea.

Iam still working on/learning Slimbox Android 9

Mabe did not specify location
Or permissions
Should be able to just use file explorer n replace..
IDK to long ago.

ADB Remount
or Remount as read/write
then when finished
Remount as read only

If possible try to get a newer box to test on.
S905x or S912
Then cam be trying same as you are but with Slimbox Android 9

Happy Testing

[blahblah]

Thanks, Freddy.

I seem to be having the same difficulty that many have previously. They can get firmware for an RT8188 wifi controller working, but without wifi, as they have an RT8189 like mine. Copying, and renaming *.ko files and directories gets you very slow wifi, that doesn't understand DHCP, and can't be made to connect to hidden SSIDs. Done with that dead, or very costly end.

The remote control, on the other hand was a doddle, with excellent instructions about reading dmesg output.

Guess we start looking for alternative builds...linux, etc. There's plenty more fun to be had with this one before I lob it.

B. :-)

[blahblah]

Hi Gang, (Bricked Box, need file: S805_8189_MXQdatong_aml_upgrade_package_20160224.i mg)

Was just starting to get somewhere with LolliPop on my oddball s805 RTK8189, when the inevitable happened, and I bricked it. No Android recovery, no sd card .img execution...nothing.

Recovery seems a simple enough process, but the file I seem to need, S805_8189_MXQdatong_aml_upgrade_package_20160224.i mg, is rather hard to find.

The file was available on the MXQ Project site as: http://www.mxqproject.com/files/USB-...age_20160224.i mg. I guess you all know that site's been gone for some time.

Okay, so there's a cached version on the Internet WayBack Machine, as: https://web.archive.org/web/20211203...age_20160224.i mg, but I only get a small portion of the file before the download fails, siting a 'network error'.

Anyone able to somehow send me a copy of the file: S805_8189_MXQdatong_aml_upgrade_package_20160224.i mg, should they have it?

Otherwise, how might I deal with this partial download dilemma?

All other sources for the file online are dead links.

TIA,

B

[blahblah]

Hey, Guys.

Some luck with creating a boot burned sd card, with a u-boot.bin file that brings my tv box up, when I short NAND pins at power up. The sd card has a basic Android recovery.img, that has a few options, ADB, EXT, factory reset, clear cache, etc.

From what I can glean from it's output, my NAND is totally trashed, with no locatable folders or partitions.

How do I now somehow re-organise the NAND, and get it to store and run the u-boot.bin, and recovery.img files, like it had previously?

I'm still thinking that the elusive file: S805_8189_MXQdatong_aml_upgrade_package_20160224.i mg, may be my solution?

Thoughts?

B.

[blahblah]

Can possibly repartition and format eMMC flash using fdisk utility in TWRP recovery.

Just can't get boot process to deal with eMMC flash device:


dmesg | grep mmc

<4>[ 2.826432@2] mmc driver version: 1.07, 2014-06-30: eMMC add hw reset function
<6>[ 2.966271@0] sd: mmc_rescan_try_freq: trying to init card at 400000 Hz
<4>[ 3.045980@1] get property: pinname, str:emmc
<4>[ 3.064245@1] [is_emmc_exist] host->storage_flag=1, POR_BOOT_VALUE=7
<6>[ 3.097558@1] mmcblk0: sd:aaaa SC32G 29.7 GiB
<6>[ 3.105993@1] mmcblk0: p1
<4>[ 3.154887@1] device name=emmc_key open error
<4>[ 10.615359@0] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<7>[ 10.620105@0] SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts
<4>[ 45.767898@0] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<7>[ 45.772405@0] SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts


ls /dev

Includes nothing even similar to emmcxxxx, or mtd.


cat /proc/mtd

dev: size erasesize name
(nothing!)


How to I get a NAND-short-initiated u-boot.bin, on a boot-burned sd card, to recognise and include my eMMC flash?

M.

[blahblah]

Here's the initial portion of the output from a NAND-pin-short initiated u-boot.bin, residing on a bootburner sd card.

This seems to indicate that my emmc is trashed, and that the associated ntfl-dev device can't be brought up.

How to repartition, format, and populate the emmc, is the dilemma...I think?




QA5:B;SVN:B72;POC:3FF;STS:0;BOOT:0;INIT:0;READ:82; BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
no sdio debug board detected
TE : 278047
BT : 16:59:29 Sep 21 2015
PMU:NONE
##### VDDEE voltage = 0x044c

CPU clock is 792MHz

DDR mode: 32 bit mode
################################################## ####
DDR size: 1GB (auto)
DDR check: Pass!
DDR clock: 516MHz with 2T mode
DDR pll bypass: Disabled
DDR init use : 19805 us

HHH
SD_boot_type: 00000001
card_type: 00000001
0x0000009f
check SD_boot_type:0x1 card_type:0x1
ucl decompress...pass
0x12345678
Boot from external device
TE : 640028

System Started


U-boot-00000-gfbec207-dirty(m8b_m201_v1@) (Sep 21 2015 - 16:59:17)

clr h-ram
DRAM: 1 GiB
relocation Offset is: 2fec8000
show partition table:
part: 0, name : logo, size : 2000000
part: 1, name : recovery, size : 2000000
part: 2, name : misc, size : 2000000
part: 3, name : boot, size : 2000000
part: 4, name : system, size : 40000000
part: 5, name : cache, size : 20000000
part: 6, name : data, size : end
aml_card_type=0x100
MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6
[mmc_register] add mmc dev_num=1, port=2, if_type=6
SDIO Port B: 0, SDIO Port C: 1
power init
out reg=c110804c,value=dfffffff
IR init done!
register usb cfg[0][1] = 3ff738cc
register usb cfg[2][0] = 3ff76450
NAND: NAND BOOT: boot_device_flag 1
Nand PHY driver Version: 1.01.001.0004 (c) 2013 Amlogic Inc.
amlnf_phy_init : amlnf init flag 0
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
get_boot_device_flag: init_ret -1
get_boot_device_flag NAND BOOT:
NAND BOOT,nand_env_relocate_spec : env_relocate_spec 49
uboot env amlnf_env_read : ####
*** Warning - bad CRC, using default environment

NAND BOOT,nand_saveenv :saveenv 94
uboot env amlnf_env_save : ####
nand_saveenv : Successful!
set_storage_device_flag: store 0
set_storage_device_flag: set store to 1
NAND BOOT,nand_saveenv :saveenv 94
uboot env amlnf_env_save : ####
nand_saveenv : Successful!
nand get nftl dev boot failed
nftl_dev be NULL
nand cmd read failed
nand cmd store failed
Err imgread(L123):Fail to read 0x1000B from part[boot] at offset 0
check dts: FDT_ERR_BADMAGIC, load default vpu parameters
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
Net: Meson_Ethernet
msg:====>upgrade_step=0<=====
[mmc_init] SDIO Port B:0, if_type=7, initialized OK!
Device: SDIO Port B
Manufacturer ID: 0
OEM: 0
Name: Tran Speed: 20000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 31914983424
Boot Part Size: 0
Bus Width: 4-bit

** Unable to open "aml_sdc_burn.ini" from mmc 0:1 --- file not exist**
init suspend firmware done. (ret:0)
cvbs trimming.1.v5: 0xa0, 0x0
hdmi tx power init
mode = 8 vic = 16
set HDMI vic: 16
mode is: 8
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
nand get nftl dev logo failed
nftl_dev be NULL
nand cmd read failed
nand cmd store failed
Err imgread(L519):Fail to read 0x2000B from part[logo] at offset 0
There is no valid bmp file at the given address
reboot_mode=charging
Hit Enter key to stop autoboot -- : 0
exit abortboot: 0
Booting...
error: image data is not a fdt
key_unify_init:364,unify key config table parse fail
Err key(L47):fail in key_drv_init
error: image data is not a fdt
key_unify_init:364,unify key config table parse fail
Err key(L47):fail in key_drv_init
nand get nftl dev boot failed
nftl_dev be NULL
nand cmd read failed
nand cmd store failed
Err imgread(L323):Fail to read 0x100000B from part[boot] at offset 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
enter recovery

[blahblah]

eMMC NAND Flash pin shorting microswitch installed, uart to FTDI USB adapter cable all rigged-up. Do I look determined?

[blahblah]

Okay, I'm thinking that the copy of u-boot.bin in my board's flash has been overwritten, and unless I can find another one that understands how to talk to my unusual Toshiba eMMC flash device, then I'm out of luck. Does that sound sensible? That, or the device tree blobs I seem to be able to write to somewhere on the board, aren't appropriate either.




This is only round one.

M.

[blahblah]

Okay, after probing around with Amlogic's debug tools, I'm now 100% certain that my Toshiba THGBMBG5D1KBAIL 4GB e-MMC flash chip is dead.

Most likely I did this myself, whilst poking-about, looking for a pair of pins to short, to initiate the recovery modes.

"Just try every pair of pins, and eventually you will find them" appears to have been poor YouTube contributor advice.

Know EXACTLY which 2 pins to short, and leave the others alone. The pin pair details ARE documented, and it appears I only found this out after it was too late.

I'm now either in the market for another WORLDMAXTV QUAD Tv Box (SHENZHEN GIEC ELECTRONICS CO., LTD, GK-MP1515), or looking for someone who can rent me their hot air rework station. The former being the more likely, yet I have a boat load of donor pcb chip contenders.

Never mind, I can still use this box, only with firmware running via the pretty snappy sd card interface. Where's the fun in that?!?!

Done.

M.