Database Users

Factory values in BT AudioGateway

Hi..
I have been instalaling some BTroute and Jetaware aplications in my touch Dual- so now my \HKEY_LOCAL_MACHINE\software\microsoft\Bluetooth\audioGateway does not have the factory settins
Can someone send me the default settins?
Just check on the registry and write down here the Keys and Values
Thank you

Default setting from my Touch Dual 20keys
\HKEY_LOCAL_MACHINE\software\microsoft\Bluetooth\AudioGateway
BTAGExtModule = OEMAGW.dll
BTAGPBModule = \Windows\BthAGPhonebook.dll
Capability = 0x65(101)
ConnectHFOnCall = 0x0(0)
NoRoleSwitch = 0x1(1)
SupportCLI = 0x0(0)
Hope this can help you.

My was
BTAGextmodule=BthagPhoneBook.dll
BTAGPBModule=OEMAGW.DLL
Capability 0x65
ConnectHFOnCall 0x0
MicVolume 0x8
NoRoleSwitch 0x1
PowerSave 0x0
SpkVolume 0x8
SupportCli 0x0
I'm going to try yours
Thanks!

[GUIDE] USB Uart on Galaxy S devices [2012/09/25]

== General Info ==
Hello, and welcome to my usb uart guide - aka, how to totally f' your phone up, if you don't think first!
Really though, read everything before attempting anything!
USB Uart is not new news. There are many great people whom have come before me to make what I am documenting here possible. But I am putting this here because I keep getting PM'd about getting help with USB Uart, and figured it would be good to start a thread that documents what you need and how to get going.
So up front, I need to list some credits.
I gained a lot of knowledge from these people:
TheBeano - Fun with resistors (home/car dock mode + more)
UberPenguin - Galaxy S UART JIG & Debugging Connector
AdamOutler - UART Output / Bootloader Hacking / Kernel Debuging
E:V:A - The Samsung Anyway Jig
I'm sure there is more... let me know if you think you need to be in this list. I'll be happy to update it!
== WARNING ==
I am not responsible for anything you do to your device! If you follow my guide and it results from anything like your phone not working or ending the world, I cannot be held accountable for what you do!
This guide will show you how to use the usb uart on most galaxy s phones (with the FSA9480 USB port accessory detector and switch)
It helps to have Unbrickable Mod. There are some commands you can run from the SBL that will wipe your bootloaders!
You must be VERY CAREFUL!
== Requirements ==
First off, you will need some hardware to connect to your computer. It helps. Below is a list of things I use and they are common and cheap. The links to the items below are what I have. Its what works for me.
mini-usb cable - http://www.sparkfun.com/products/598
bus pirate or arduino (I only cover bus pirate here... for now.) - http://www.seeedstudio.com/depot/bus-pirate-v3-assembled-p-609.html?cPath=174
In my guide i use the bus pirate probe kit - http://www.seeedstudio.com/depot/bus-pirate-probe-kit-p-526.html?cPath=178_180
I used a tape printer to label the test clips.
breadboard (optional, if you rather just solder the resistor to the micro-usb break-out board. more later...) - http://www.sparkfun.com/products/112
USB MicroB Plug Breakout Board - http://www.sparkfun.com/products/10031
some jumper wire - http://www.sparkfun.com/products/124
150k, 523k, 619k resistor (ymmv. AdamOutler and others told me to try 523k or 619k, but I was able to get all the output I need with 150k)
guts - priceless
Also, I use minicom on Linux and Mac OS X (use homebrew to install minicom), but you should be able to use any serial console program you like (i.e. kermit, cu, etc...)
I highly suggest getting to know your bus pirate, but this guide assumes you have read manuals and updated firmware. Any of the other uart modes should also work this way, but I currently don't cover that here... yet.
== Getting Started ==
When we connect to the usb port on the bus pirate(bp), you can find the version info by typing i at the high impedance mode (HiZ>) prompt. Change to this mode when your modifying connections or cable argments.
Code:
HiZ>i
Bus Pirate v3b
Firmware v6.0 r1625 Bootloader v4.4
DEVID:0x0447 REVID:0x3043 (24FJ64GA002 B5)
http://dangerousprototypes.com
Disconnect the bp and lets connect everything from the micro usb port connecting to your phone backwards to the bp. I use a breadboard for things that I might work on later or things I'll re-arrange a lot. You may also decide to solder the resistor directly to the GND/ID pins, but you will need a little lead on the GND. Connect MOSI to D+ and MISO to D-.
Another warning!
You can also fry the ftdi on the bus pirate, if you mess with the connections while the bus pirate is in any mode besides HiZ (Hi Impedance) or unplugged. Usually, I'm in uart bridge mode, so you can't go back to HiZ. You just have to unplug the usb cable.
{
"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"
}
Solder some jumper wire to the micro usb breakout board. I use about an inch.
I usually start at a1 on the breadboard with vcc and a4 and a5 for ID and GND (respectively). In these images, I'm at the opposite end of the board to make it easier to have the phone next to and above my mouse so it is easy for me to work with the phone.
Put the resistor on b4 and b5 - which is where I connect GND on the bp.
Now that you have the bp connected to the circut, lets move forward and plug in the micro usb cable into the bp and then into your computer.
To change into UART mode on the buspirate, type 'm' at the HiZ> prompt:
Code:
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
x. exit(without change)
(1)>3
Set serial port speed: (bps)
1. 300
2. 1200
3. 2400
4. 4800
5. 9600
6. 19200
7. 38400
8. 57600
9. 115200
10. BRG raw value
(1)>9
Data bits and parity:
1. 8, NONE *default
2. 8, EVEN
3. 8, ODD
4. 9, NONE
(1)>1
Stop bits:
1. 1 *default
2. 2
(1)>1
Receive polarity:
1. Idle 1 *default
2. Idle 0
(1)>1
Select output type:
1. Open drain (H=Hi-Z, L=GND)
2. Normal (H=3.3V, L=GND)
(1)>2
Ready
UART>(3)
UART bridge
Reset to exit
Are you sure? y
After you get into UART Bridge mode, you will have to unplug the usb port from your computer to reset the bus pirate.
This is where experimenting with different resistors on the GND/ID pins make a difference. Using 619k resistance, I just plug the phone in and it boots up. During boot up, I can see the PBL output like the output you will see in the rest of this document. Using 150k resistance, the phone doesn't automatically turn on.
Also, you may have different usability of the console depending on if you set the output type to Open drain or Normal drain.
With Open drain, I am able to see the uart output, but I am not able to break into the SBL prompt like I am with Normal drain.
Interestingly, with 619k on my SGH-T959V, I don't see all of the kernel console output. I still haven't figured out exactly why yet. With 150k resistance, I don't see the PBL output, but I can still break into the SBL prompt (with normal drain) and get full kernel console output.
When you get to this point, the mode light should now be green. When you plug your phone into the micro usb adapter (again 619k in these examples), you should see everything from the pbl in to the kernel starting:
Code:
1
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
+n1stVPN 3008
+nPgsPerBlk 64
PBL found bootable SBL: Partition(4).
Set cpu clk. from 400MHz to 800MHz.
OM=0x29, device=OnenandMux(Audi)
IROM e-fused - Non Secure Boot Version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: ARIES REV 03
Build On: Oct 28 2011 15:45:50
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x60
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1540
===============================
ID : DATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1672
NO_UNITS : 2120
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 3792
NO_UNITS : 160
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 3952
NO_UNITS : 60
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
reading nps status file is successfully!.
nps status=0x504d4f43
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 4013mV, soc = 86
check_quick_start_condition- Voltage: 4013.75000, Linearized[74/89/100], Capacity: 89
init_fuel_gauge: vcell = 4013mV, soc = 86, rcomp = d000
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0x20
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x40
PMIC_STATUS2 = 0x0
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x0
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
check_download: micorusb_status1 = 400, key_value = 0
aries_process_platform: final s1 booting mode = 0
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
Autoboot (0 seconds) in progress, press any key to stop
get_debug_level current debug level is 0x574f4c44.
get_debug_level current debug level is 0x574f4c44.
boot_kernel: Debug Level Low
FOTA Check Bit
Read BML page=, NumPgs=
FOTA Check Bit (0xffffffff)
Load Partion idx = (6)
..............................done
Kernel read success from kernel partition no.6, idx.6.
setting param.serialnr=0x3733b898 0x1ffc00ec
setting param.board_rev=0x30
setting param.cmdline=console=ttySAC2,115200 loglevel=4
Starting kernel at 0x32000000...
== The SBL (Secondary BootLoader) ==
The most interesting line out of all of that was:
Code:
Autoboot (0 seconds) in progress, press any key to stop
If you happen to hold down the Enter/Return key while booting the phone you will get into the "SBL>" prompt.
The Secondary BootLoader is essentially like u-boot.
Code:
...
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
Autoboot (0 seconds) in progress, press any key to stop Autoboot aborted..
SBL>
If we type help, we will get some commands you can run. Some of these commands are affected by what is set in the environment.
Code:
SBL> help
Following commands are supported:
* setenv
* saveenv
* printenv
* help
* reset
* boot
* kernel
* format
* open
* close
* erasepart
* eraseall
* loadkernel
* showpart
* addpart
* delpart
* savepart
* nkernel
* nramdisk
* nandread
* nandwrite
* usb
* mmctest
* keyread
* readadc
* usb_read
* usb_write
* fuelgauge
* pmic_read
* pmic_write
To get commands help, Type "help <command>"
SBL>
You can get some minimal help for each command:
Code:
SBL> help loadkernel
* Help : loadkernel
* Usage : loadkernel
load kernel image
- loadkernel 0x80A00000 from kernel partition
Another set of intersting commands here are the ones that manipulate the environment:
setenv
saveenv
printenv
Code:
SBL> help setenv
* Help : setenv
* Usage : setenv [name] [value] . .
Modify current environment info on ram
SBL> help saveenv
* Help : saveenv
* Usage : saveenv
Save cuurent environment info to flash
SBL> help printenv
* Help : printenv
* Usage : printenv
Print current environment info on ram
printenv is probably the safest of them to run, so lets try this first.
Code:
SBL> printenv
PARAM Rev 1.3
SERIAL_SPEED : 7
LOAD_RAMDISK : 0
BOOT_DELAY : 0
LCD_LEVEL : 97
SWITCH_SEL : 1
PHONE_DEBUG_ON : 0
LCD_DIM_LEVEL : 0
LCD_DIM_TIME : 6
MELODY_MODE : 1
REBOOT_MODE : 0
NATION_SEL : 0
LANGUAGE_SEL : 0
SET_DEFAULT_PARAM : 0
CUST_KERNEL_DL_COUNT : 0
KERNEL_BINARY_TYPE : 0
VERSION : I9000XXIL
CMDLINE : console=ttySAC2,115200 loglevel=4
DELTA_LOCATION : /mnt/rsv
PARAM_STR_3 :
PARAM_STR_4 :
I'm not fully sure what all of these options are, but the ones I know about are SWITCH_SEL and PHONE_DEBUG_ON.
I usually turn SWITCH_SEL to 765431. If I turn 2 on, I don't get anything. It would be worthy to test each number in SWITCH_SEL to figure out what number changes what. That maybe specific to the device I have.
Setting at least 6543 in SWITCH_SEL will give you kernel log output:
Code:
setenv SWITCH_SEL 6543
saveenv
I also set PHONE_DEBUG_ON to 1:
Code:
setenv PHONE_DEBUG_ON 1
saveenv
When I set this, I get some extended battery statistics like:
Code:
[BAT] CHR(0) CAS(0) CHS(3) DCR(0) ACP(2) BAT(81,0,0) TE(31) HE(1) VO(3926) ED(1000) RC(0) CC(0) VF(591) LO(0)
You must remember that after running setenv, you must then run saveenv at least once at the end to save the environment. I believe this environment info is saved to either an offset on the sbl partition or on the param.lfs. It would be useful to find this out, because u-boot has a userspace utility (that you can use from within linux userspace) to modify the u-boot environment. It may be handy to use a tool like that to modify the CMDLINE option during rom flashing time.
Also, instead of powering your phone off then on again to put the new settings in place, just run reset from the sbl prompt to reboot the phone with the new settings.
Anyways, This is what I have so far. I will be adding more to this as time goes on.
Enjoy!
-Bryan

Very nice and clear guide!
Also check out my Anyway thread on more details about JIG resistances etc. Soon I hope there will be more added to that about building your own Samsung Test Jig...

Setenv switch sel 1234567
Phone debug on 1
This gives you some kernel debugging.

bhundven said:
I usually turn SWITCH_SEL to 765431. If I turn 2 on, I don't get anything. It would be worthy to test each number in SWITCH_SEL to figure out what number changes what.
Click to expand...
Click to collapse
AdamOutler said:
Setenv switch sel 1234567
Phone debug on 1
This gives you some kernel debugging.
Click to expand...
Click to collapse
Yup. I've got that in there.
It's interesting to note that not all bootloaders are created equal. My results are on SGH-T959V.

Any chance that it will work witch Galaxy Ace too?

dragonnn said:
Any chance that it will work witch Galaxy Ace too?
Click to expand...
Click to collapse
I'm not sure. The GT-i9001 and the SGH-i717 (at&t galaxy note) also both have the FSA9480 chip, but use Qualcomm chips. I can only get some bootloader output from the SGH-i717:
Code:
Android Bootloader - UART_DM Initialized!!!
[VIBETONZ] ENABLE
[VIBETONZ] DISABLE
HW_REV = 12
mipi_init : status = 1
HW_REV = 12
start init_charger
smb328a_init_charger : is_reboot_mode = 0, vcell = 3975
check valid dcin (0x33) = 0x0
no dcin, skip init_charger
fuelguage : soc = 80%, vcell = 3975mV
fuelguage : rcomp(0xd01f) ==?? 0xd0d0
HW_REV = 12
VReset : 0x8c
Hibernation mode : 0x0
8340 = ( 397500 - 334350 ) * 13207 / 100000
HW_REV = 12
reboot_mode = 0xb6cef249
do key check
enter normal booting mode
AST_POWERON
usable ddi data.
HW_REV = 12
HW_REV = 12
E.V.A. said that it might be some debugging setting in the kernel that might have disabled the kernel log output.
It would be helpful to get some MSM developers here to help us out with that!

bhundven said:
I'm not sure. The GT-i9001 and the SGH-i717 (at&t galaxy note) also both have the FSA9480 chip, but use Qualcomm chips. I can only get some bootloader output from the SGH-i717:
Click to expand...
Click to collapse
I looked in the kernel source and it have ./drivers/i2c/chips/fsa9280.c and the driver is included in the build kernel:good:. As far I understand we can using this method recovery the phone from hard brick? That will be really nice, my friend bricked his Ace, maybe he can use this method.

dragonnn said:
I looked in the kernel source and it have ./drivers/i2c/chips/fsa9280.c and the driver is included in the build kernel:good:. As far I understand we can using this method recovery the phone from hard brick? That will be really nice, my friend bricked his Ace, maybe he can use this method.
Click to expand...
Click to collapse
Currently, I only know this method to work on SGS( not sgs2 or sgs3 ) phones with the FSA9480.

bhundven said:
Yup. I've got that in there.
It's interesting to note that not all bootloaders are created equal. My results are on SGH-T959V.
Click to expand...
Click to collapse
The switches are messages from levels 1-7. Turn on more to get more messages.

AdamOutler said:
The switches are messages from levels 1-7. Turn on more to get more messages.
Click to expand...
Click to collapse
That makes sense, but what doesn't is if I set SWITCH_SEL to 1234567 or any combination with 2, I get no output. As long as I don't have 2 in there, it works fine. Must just be this device.

Memory Architecture
Of course each device will have a different Memory Map. Each carrier designs their varient based on what they want and need to function. The MM is sectioned off in the ROM. Any user or modifiable area is stored in RAM so remember we are working in an area that is not supposed to touched (ROM).
Bootloaders are tricky beasts, have never developed a flashing algorithm so I don't know. Usually BLs are not updated after release ( atleast in my field) only sw/fw is.
Either way, excellent ideas, but there is always a way in!

Fly-n-High said:
Of course each device will have a different Memory Map. Each carrier designs their varient based on what they want and need to function. The MM is sectioned off in the ROM. Any user or modifiable area is stored in RAM so remember we are working in an area that is not supposed to touched (ROM).
Bootloaders are tricky beasts, have never developed a flashing algorithm so I don't know. Usually BLs are not updated after release ( atleast in my field) only sw/fw is.
Either way, excellent ideas, but there is always a way in!
Click to expand...
Click to collapse
huh?

Good post
Nice...!!
Thanks you~

can't get SBL or PBL logs on uart in galaxy-y (GT-S5360)
Hello sir,
Thanks for your great tutorial .
I Tried to get uart on galaxy-y (GT-S5360) . I got a working uart but can't see any PBL or SBL logs during the boot. The only log I see during the booting is
Code:
AST_POWERON..
BOOTING COMPLETED
After booting, uart works fine and i can use a shell via serial using command
(on phone)
Code:
busybox sh</dev/ttyS0 >/dev/ttyS0
and on PC
Code:
microcom -s 115200 -p /dev/ttyS0
ttyS0 settings of the phone is
Code:
speed 115200 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke
And that of PC is
Code:
speed 115200 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig -icanon iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
-echoctl echoke
cat /proc/cmdline of phone is
Code:
console=ttyS0,115200n8 mem=362M kmemleak=off root=/dev/ram0 rw androidboot.console=ttyS0 mtdparts=bcm_umi-nand:[email protected](bcm_boot)ro,[email protected](loke)ro,[email protected](loke_bk)ro,[email protected](systemdata)ro,[email protected](modem)ro,[email protected](param_lfs)rw,[email protected](boot)ro,[email protected](boot_backup)ro,[email protected](system)rw,[email protected](cache)rw,[email protected](userdata)rw,[email protected](efs)rw,[email protected](sysparm_dep)ro,[email protected](umts_cal)ro,[email protected](cal)r BOOT_MODE=0 loglevel=0 BOOT_FOTA=0 DEBUG_LEVEL=LOW
Circuit diagram is attached below
any one please help

harish2704 said:
I Tried to get uart on galaxy-y (GT-S5360) . I got a working uart but can't see any PBL or SBL logs during the boot. The only log I see during the booting is
Code:
AST_POWERON..
BOOTING COMPLETED
Click to expand...
Click to collapse
I get something similar on a Samsung Rugby Smart (SGH-I847). I think they have tweaked the UART stuff on the newer devices that post date the Galaxy S devices. They might share the UART chip, but it seems as if they changed the loader implementation which is causing the newer devices to not see the PBL and SBL information during boot.
harish2704 said:
Circuit diagram is attached below
Click to expand...
Click to collapse
Have you tried a 150k or 619k resistor instead of the 523k? I was able to get output with both a 150k and 619k, but the output was very similar to what you have posted. Likely a long shot, but worth a try.
harish2704 said:
cat /proc/cmdline of phone is
Code:
console=ttyS0,115200n8 mem=362M kmemleak=off root=/dev/ram0 rw androidboot.console=ttyS0 mtdparts=bcm_umi-nand:[email protected](bcm_boot)ro,[email protected](loke)ro,[email protected](loke_bk)ro,[email protected](systemdata)ro,[email protected](modem)ro,[email protected](param_lfs)rw,[email protected](boot)ro,[email protected](boot_backup)ro,[email protected](system)rw,[email protected](cache)rw,[email protected](userdata)rw,[email protected](efs)rw,[email protected](sysparm_dep)ro,[email protected](umts_cal)ro,[email protected](cal)r BOOT_MODE=0 loglevel=0 BOOT_FOTA=0 DEBUG_LEVEL=LOW
Click to expand...
Click to collapse
Do you have any control over this? It might be the case that ttyS0 isn't setup during early-boot and you need to use a different tty to get it to output over the FSA chip.

Have you tried a 150k or 619k resistor instead of the 523k?
Click to expand...
Click to collapse
yes I tried I didn't feel any difference b/w 619k & 523k when tried. And with 150k, I couldn't get uart active ()
Do you have any control over this? It might be the case that ttyS0 isn't setup during early-boot and you need to use a different tty to get it to output over the FSA chip
Click to expand...
Click to collapse
.
What you mean by control? You mean, can i change this parameters? yes its possible by reflashing (update.zip methode)
Or
you mean do i have control on ttyS0 device? yes I could change that by
Code:
busybox stty -F /dev/ttyS0 ..........
command
Sorry for my language

harish2704 said:
What you mean by control? You mean, can i change this parameters? yes its possible by reflashing (update.zip methode)
Click to expand...
Click to collapse
This is the method I was referring to. If you tweak the parameters you might be able to get the kernel log over serial.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2

Can you please describe about the tweaks i have to do...
in my knowledge, kernel param
Code:
console=ttyS0,115200n8
is enough for that....
So please specify the tweaks...

harish2704 said:
Can you please describe about the tweaks i have to do...
in my knowledge, kernel param
Code:
console=ttyS0,115200n8
is enough for that....
So please specify the tweaks...
Click to expand...
Click to collapse
If you can interact with ttyS0 post-boot I'd expect it to work. Is there maybe anther serial device such as ttyHS0 or similar that you can interact with? If so, that might be something to try.

You need to change that ttyS0 to ttySAC2 in the boot parameters. Use the abootimg tool on Ubuntu. Apt-get install abootimg.

Flash Counter not resetting itself!?

Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app

Help anyone?
Sent from my GT-P3100 using XDA Premium HD app

Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2

Aditya16 said:
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
have you tried "Triangule Away" ?
you can installed it from google play
but you need to root your device first

sapiterbang said:
have you tried "Triangle Away" ?
you can installed it from google play
but you need to root your device first
Click to expand...
Click to collapse
I resetted it with that only. Is it some bug in jb?
Sent from my GT-P3100 using XDA Premium HD app

Alvin Lai said:
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Will try that.
Sent from my GT-P3100 using XDA Premium HD app

May be try installing supersu ( not superuser) from google play and give permissions to triangle away
Install latest version 1.95 of triangle away
Sent from Galaxy S2 or Galaxy Tab2

I confirm Triangle Away and SuperSU combination still work in JB.

So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app

Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone can help you...
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone could help you

Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!

ketut.kumajaya said:
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
Click to expand...
Click to collapse
How will i get this sbl.bin file from?

Aditya16 said:
How will i get this sbl.bin file from?
Click to expand...
Click to collapse
From /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3. Be careful, this is a critical part of boot process.

I really do not not know how to do it advice please?
Sent from my GT-P3100 using XDA Premium HD app

News update guy's. Chainfire pm'ed me saying that he will look into the matter. Now all we can do is cross our finger and wait.
Oh and also this download mode does not show +1 when I replaced CWM with stock recovery. I wonder why?
Sent from my GT-P3100 using XDA Premium HD app

UPDATE:
No warning when boot to stock JB XXCLI5 recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x135b4d bytes)
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
More investigation needed, when boot to unofficial recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x39a7b0 bytes)
Ramdisk @ 82800000 (0x1e4fc6 bytes)
[WARNING] Current kernel is NOT official binary!!!
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
Normal boot to stock JB XXCLI5 kernel:
Code:
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Parsed above value from /proc/last_kmsg. From last_kmsg value (second boot loader message?), I can confirm my boot logo hack is safe. Sbl successfuly mount param.lfs:
Code:
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.

[Discussion] Check flash memory UFS version (rooting needed)

Hi there,
After rooting your phone, lowlevel information is available e.g. UFS memory version. Use Code (Superuser): "cat /sys/kernel/debug/ufs/dump_device_desc" (a space needed after "cat").
Then you will get *:
Code:
Device Descriptor[Byte offset 0x0]: bLength = 0x40
Device Descriptor[Byte offset 0x1]: bDescriptorType = 0x0
Device Descriptor[Byte offset 0x2]: bDevice = 0x0
Device Descriptor[Byte offset 0x3]: bDeviceClass = 0x0
Device Descriptor[Byte offset 0x4]: bDeviceSubClass = 0x0
Device Descriptor[Byte offset 0x5]: bProtocol = 0x0
Device Descriptor[Byte offset 0x6]: bNumberLU = 0x4
Device Descriptor[Byte offset 0x7]: bNumberWLU = 0x4
Device Descriptor[Byte offset 0x8]: bBootEnable = 0x1
Device Descriptor[Byte offset 0x9]: bDescrAccessEn = 0x0
Device Descriptor[Byte offset 0xa]: bInitPowerMode = 0x1
Device Descriptor[Byte offset 0xb]: bHighPriorityLUN = 0x7f
Device Descriptor[Byte offset 0xc]: bSecureRemovalType = 0x0
Device Descriptor[Byte offset 0xd]: bSecurityLU = 0x1
Device Descriptor[Byte offset 0xe]: Reserved = 0x4
Device Descriptor[Byte offset 0xf]: bInitActiveICCLevel = 0x0
[B]Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2[/B]
Device Descriptor[Byte offset 0x12]: wManufactureDate = 0x1610
Device Descriptor[Byte offset 0x14]: iManufactureName = 0x0
Device Descriptor[Byte offset 0x15]: iProductName = 0x1
Device Descriptor[Byte offset 0x16]: iSerialNumber = 0x2
Device Descriptor[Byte offset 0x17]: iOemID = 0x3
Device Descriptor[Byte offset 0x18]: wManufactureID = 0xce01
Device Descriptor[Byte offset 0x1a]: bUD0BaseOffset = 0x10
Device Descriptor[Byte offset 0x1b]: bUDConfigPLength = 0x10
Device Descriptor[Byte offset 0x1c]: bDeviceRTTCap = 0x2
Device Descriptor[Byte offset 0x1d]: wPeriodicRTCUpdate = 0x0
(* From Mate 9 with KLUCG4J1EB-B0B1 Samsung UFS2.0 flash memory)
'Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2' is a parameter in Device Descriptor defined in JESD220 to indicate the version of UFS flash memory. It is readable from the flash memory IC, but it is not configurable by user. wSpecVersion = 0200h represents UFS2.0, and wSpecVersion = 0210h represents UFS2.1.
JESD220C (UFS2.1 Standard) has also added/changed the following parameters to Device Descriptor, which not defined in JESD220B (UFS2.0 Standard):
Code:
(offset 0x1f) bUFSFeaturesSupport
(offset 0x20) bFFUTimeout
(offset 0x21) bQueueDepth
(offset 0x22) wDeviceVersion
(offset 0x24) bNumSecureWPArea
(offset 0x25) dPSAMaxDataSize
(offset 0x29) bPSAStateTimeout
(offset 0x2A) iProductRevisionLevel
If you get 'wSpecVersion = 0x21', then the flash memory in your phone is definitely UFS2.1!
Reference:
'B.1.3 Changes in features already defined in UFS 2.0' Page-360 of JESD220C
'Table 14-4 — Device Descriptor' Page-319 of JESD220C
'Table 14.4 — Device Descriptor' Page-306 of JESD220B

xlgssss said:
Hi there,
After rooting your phone, lowlevel information is available e.g. UFS memory version. Use Code (Superuser): "cat /sys/kernel/debug/ufs/dump_device_desc" (a space needed after "cat").
Then you will get *:
Code:
Device Descriptor[Byte offset 0x0]: bLength = 0x40
Device Descriptor[Byte offset 0x1]: bDescriptorType = 0x0
Device Descriptor[Byte offset 0x2]: bDevice = 0x0
Device Descriptor[Byte offset 0x3]: bDeviceClass = 0x0
Device Descriptor[Byte offset 0x4]: bDeviceSubClass = 0x0
Device Descriptor[Byte offset 0x5]: bProtocol = 0x0
Device Descriptor[Byte offset 0x6]: bNumberLU = 0x4
Device Descriptor[Byte offset 0x7]: bNumberWLU = 0x4
Device Descriptor[Byte offset 0x8]: bBootEnable = 0x1
Device Descriptor[Byte offset 0x9]: bDescrAccessEn = 0x0
Device Descriptor[Byte offset 0xa]: bInitPowerMode = 0x1
Device Descriptor[Byte offset 0xb]: bHighPriorityLUN = 0x7f
Device Descriptor[Byte offset 0xc]: bSecureRemovalType = 0x0
Device Descriptor[Byte offset 0xd]: bSecurityLU = 0x1
Device Descriptor[Byte offset 0xe]: Reserved = 0x4
Device Descriptor[Byte offset 0xf]: bInitActiveICCLevel = 0x0
[B]Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2[/B]
Device Descriptor[Byte offset 0x12]: wManufactureDate = 0x1610
Device Descriptor[Byte offset 0x14]: iManufactureName = 0x0
Device Descriptor[Byte offset 0x15]: iProductName = 0x1
Device Descriptor[Byte offset 0x16]: iSerialNumber = 0x2
Device Descriptor[Byte offset 0x17]: iOemID = 0x3
Device Descriptor[Byte offset 0x18]: wManufactureID = 0xce01
Device Descriptor[Byte offset 0x1a]: bUD0BaseOffset = 0x10
Device Descriptor[Byte offset 0x1b]: bUDConfigPLength = 0x10
Device Descriptor[Byte offset 0x1c]: bDeviceRTTCap = 0x2
Device Descriptor[Byte offset 0x1d]: wPeriodicRTCUpdate = 0x0
(* From Mate 9 with KLUCG4J1EB-B0B1 Samsung UFS2.0 flash memory)
'Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2' is a parameter in Device Descriptor defined in JESD220 to indicate the version of UFS flash memory. It is readable from the flash memory IC, but it is not configurable by user. wSpecVersion = 0200h represents UFS2.0, and wSpecVersion = 0210h represents UFS2.1.
JESD220C (UFS2.1 Standard) has also added/changed the following parameters to Device Descriptor, which not defined in JESD220B (UFS2.0 Standard):
Code:
(offset 0x1f) bUFSFeaturesSupport
(offset 0x20) bFFUTimeout
(offset 0x21) bQueueDepth
(offset 0x22) wDeviceVersion
(offset 0x24) bNumSecureWPArea
(offset 0x25) dPSAMaxDataSize
(offset 0x29) bPSAStateTimeout
(offset 0x2A) iProductRevisionLevel
If you get 'wSpecVersion = 0x21', then the flash memory in your phone is definitely UFS2.1!
Reference:
'B.1.3 Changes in features already defined in UFS 2.0' Page-360 of JESD220C
'Table 14-4 — Device Descriptor' Page-319 of JESD220C
'Table 14.4 — Device Descriptor' Page-306 of JESD220B
Click to expand...
Click to collapse
Samsung UFS 2.0?
Thanks!
{
"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"
}
Enviado desde mi MHA-L09 mediante Tapatalk

add grep to make it even easier:
cat /sys/kernel/debug/ufs/dump_device_desc | grep wSpecVersion
Mines 2.0.
Although Toshiba, but I guess it's the same result.

Thank you for the code! :good:
Actually, I am now very curious about how the whole "device descriptor" looks like with an UFS2.1 flash memory when typing "cat /sys/kernel/debug/ufs/dump_device_desc".
ante0 said:
add grep to make it even easier:
cat /sys/kernel/debug/ufs/dump_device_desc | grep wSpecVersion
Mines 2.0.
Although Toshiba, but I guess it's the same result.
Click to expand...
Click to collapse

The public television of Thailand opens its informative with the false publicity of the flash memories in the Huawei Mate 9. Surprising but true.
https://youtu.be/1J50o7HEdPM
Enviado desde mi MHA-L09 mediante Tapatalk

XoanCarlos said:
The public television of Thailand opens its informative with the false publicity of the flash memories in the Huawei Mate 9. Surprising but true.
https://youtu.be/1J50o7HEdPM
Enviado desde mi MHA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Thanks for the information. Do you think it was a good indication or not?

xlgssss said:
Thanks for the information Do you think it was a good indication or not?
Click to expand...
Click to collapse
It's a small step ... Here, in Spain, the sellers have reimbursed three Mate 9 for the false memories. Even so, to date, most sellers are reluctant to return, especially the telephone operators that sold Mate 9.
Enviado desde mi MHA-L09 mediante Tapatalk

Spain:
All Mate 9 tested bring UFS 2.0 memories from Samsung and Toshiba brands. Consumers claim to Huawei, the manufacturer offers as an official response that Mate 9 "support UFS 2.1." Consumers file official claims with consumer authorities against Huawei and sellers without ruling out the court.
[https://d3nevzfk7ii3be]
Excellent report:http://www.dappsandphones.com/2017/05/as...
Twitter people affected:https://twitter.com/AsiNoHuawei?s=09
Channel Telegram of people affected.https://t.me/joinchat/AAAAAER5ehLbg2WX8k...
Not that way, Huawei!
A greeting.
Enviado desde mi MHA-L09 mediante Tapatalk

XoanCarlos said:
Spain:
All Mate 9 tested bring UFS 2.0 memories from Samsung and Toshiba brands. Consumers claim to Huawei, the manufacturer offers as an official response that Mate 9 "support UFS 2.1." Consumers file official claims with consumer authorities against Huawei and sellers without ruling out the court.
[https://d3nevzfk7ii3be]
Excellent report:http://www.dappsandphones.com/2017/05/as...
Twitter people affected:https://twitter.com/AsiNoHuawei?s=09
Channel Telegram of people affected.https://t.me/joinchat/AAAAAER5ehLbg2WX8k...
Not that way, Huawei!
A greeting.
Enviado desde mi MHA-L09 mediante Tapatalk
Click to expand...
Click to collapse
You are publishing same post on four differents threads ( copy paste) .
Please choose one. Its the best way to follow the information. 4/4

I neeed BIG Help for Wisdom Customize Android 9 tv OS go back AOSP Android tv OS

I neeed BIG Help for Wisdom Customize Android 9 tv OS go back AOSP Android tv OS
China 55" 4K Led TV I want AOSP Android TV OS Software
My tv :
-No Android Settings, -No Android Tv Launcher and no many AOSP apps
Product Details
1. Market: P150-2851V6.2 combines the power supply,the backlight drive,TV board as whole.
2. TV System: ATV and DVB-C/T/T2/S2.
3. P150-2851V6.2SupportsRJ45networksignal,USB2.0,AVIN,YPBPR,HDMI1.4,HDMI2.0andTVincludingATVandDTV.In the mean time, it can sustain WIFI access VGA+PC AUDIO Input and Coaxial/Optical Fiber and Earphone output.
4. Chipset: RTD2851SSZ
5. OSD Language: English,French,Spanish,Danish,Swedish,Finnish,Dutch
6. Audio Output: 2*[email protected]Ω
7. Resolution:UP to 2840*2160
8. CKD and SKD available---HARDWARE CONFIGURATION AND FUNCTIONOS Android 9.0CPU ARM Cortex A55 quad coreGPU Mali 470MP2DDR size 1.5GbyteEMMC Flash 8Gbyte
4K Android Smart TV SoC with Advanced Picture/Audio Quality (RTD2851/RTD2873)The RTD2851/RTD2873 Smart TV SoC (System on a Chip) supports Android Pie and Google Assistant TV voice control. It also supports all HDR formats, including Dolby Vision™, HDR10, Technicolor Prime, HLG, and HDR10+. It provides theater-like sound effects using the built-in TV speakers through decoding Dolby ATMOS™, and offers advanced picture and video processing for internet streaming contents
{
"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"
}
<<< Aida64 Sysinfo Summary (English) >>>
DB Device Model: < unknown >
Manufacturer: MediaTek
Model: SMART TV
Brand: MediaTek
Board: m7332_eu
Device: m7332_eu
Hardware: m7332
Platform: m7332
Product: m7332_eu
SoC Model: < unknown >
RO SoC Model: < unknown >
Core Architecture: 4x ARM Cortex-A53 @ 1450 MHz
CPU Cores: 4
CPUInfo HW: m7332
CPUInfo ChipName: < empty >
CPUInfo MSM HW: < empty >
Screen Resolution: 1920 x 1080
Display Mode #1: 1920 x 1080
vendor.display-size: 3840x2160
OGLES Vendor: ARM
OGLES Renderer: Mali-G52
OGLES Version: OpenGL ES 3.2 v1.r16p0-01rel0-a319455b5-20190827.a188048ecd49603991a490e38a4a1861
Current GPU Clock: < unknown >
GPU Clock Range: < unknown >
GPU Utilization: < unknown >
Power Source: A/C Charger
Level: 100 %
Status: Charging
Charge Rate: 1.6 mA
Charge Rate (Raw): 1.6 mA
Android Version: 9 (Pie)
API Level: 28
Rooted Device: No
Bootloader: 123456789
Build ID: m7332_eu-userdebug 9 PPR2.180905.006.A1 TVOS-04.16.031.01.12 dev-keys
Codename: REL
Fingerprint: MediaTek/m7332_eu/m7332_eu:9/PPR2.180905.006.A1/builder06120124:userdebug/dev-keys
ID: PPR2.180905.006.A1
Incremental: TVOS-04.16.031.01.12
ro.boot.fpsensor: < empty >
Total RAM (ActMgr): 1328 MB
Total RAM (MemInfo): 1328 MB
Avail RAM (ActMgr): 540 MB
Avail RAM (MemInfo): 492 MB
Fake Dev (Android Rel): No
Fake Dev (Total RAM): No
Fake Dev (Avail RAM): No
getThisAppInstallerPackageName: com.android.packageinstaller
isThisAppSideLoaded: true
getAppInstallerPackageName(com.android.chrome): null
getAppInstallerPackageName(com.google.android.youtube): null
getAppInstallerPackageName(com.cpuid.cpu_z): null
getAppInstallerPackageName(com.eg.android.AlipayGphone): null
getAppInstallerPackageName(com.baidu.searchbox): null
getAppInstallerPackageName(com.huawei.global): null
<<< System >>>
Device Type: TV
Manufacturer: MediaTek
Model: SMART TV
Brand: MediaTek
Board: m7332_eu
Device: m7332_eu
Hardware: m7332
Platform: m7332
Product: m7332_eu
Installed RAM: 1.5 GB
Total Memory: 1328 MB
Available Memory: 539 MB
Internal Storage Total Space: 3016 MB
Internal Storage Free Space: 1597 MB
Bluetooth Version: 4+
Device Features: android.hardware.audio.output
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera.any
android.hardware.camera.external
android.hardware.ethernet
android.hardware.gamepad
android.hardware.hdmi.cec
android.hardware.opengles.aep
android.hardware.ram.low
android.hardware.screen.landscape
android.hardware.type.television
android.hardware.usb.host
android.hardware.vulkan.compute
android.hardware.vulkan.level
android.hardware.vulkan.version
android.hardware.wifi
android.hardware.wifi.direct
android.software.adoptable_storage
android.software.app_widgets
android.software.autofill
android.software.backup
android.software.cant_save_state
android.software.companion_device_setup
android.software.cts
android.software.home_screen
android.software.input_methods
android.software.leanback
android.software.leanback_only
android.software.live_tv
android.software.verified_boot
android.software.voice_recognizers
android.software.webview
com.google.android.tv.installed
nrdp.modelgroup
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A53 @ 1450 MHz
Instruction Set: 64-bit ARMv8-A (32-bit Mode)
CPU Revision: r0p4
CPU Cores: 4
CPU Clock Range: 1150 - 1450 MHz
Core 1 Clock: 1449 MHz
Core 2 Clock: 1449 MHz
Core 3 Clock: 1449 MHz
Core 4 Clock: 1449 MHz
Scaling Governor: interactive
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Supported
NEON: Supported
PMULL: Supported
SHA1: Supported
SHA2: Supported
<<< Display >>>
Screen Resolution: 1920 × 1080
xdpi / ydpi: 77 / 77 dpi
GPU Vendor: ARM
GPU Renderer: Mali-G52
GPU Cores: 1
Refresh Rate: 60 Hz
Default Orientation: Landscape
OpenGL ES Version: 3.2
GPU Version: OpenGL ES 3.2 v1.r16p0-01rel0-a319455b5-20190827.a188048ecd49603991a490e38a4a1861
OpenGL ES Extensions: GL_EXT_debug_marker
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth24
GL_OES_depth_texture
GL_OES_depth_texture_cube_map
GL_OES_packed_depth_stencil
GL_OES_rgb8_rgba8
GL_EXT_read_format_bgra
GL_OES_compressed_paletted_texture
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_EGL_image_external_essl3
GL_OES_EGL_sync
GL_OES_texture_npot
GL_OES_vertex_half_float
GL_OES_required_internalformat
GL_OES_vertex_array_object
GL_OES_mapbuffer
GL_EXT_texture_format_BGRA8888
GL_EXT_texture_rg
GL_EXT_texture_type_2_10_10_10_REV
GL_OES_fbo_render_mipmap
GL_OES_element_index_uint
GL_EXT_shadow_samplers
GL_OES_texture_compression_astc
GL_KHR_texture_compression_astc_ldr
GL_KHR_texture_compression_astc_hdr
GL_KHR_texture_compression_astc_sliced_3d
GL_EXT_texture_compression_astc_decode_mode
GL_EXT_texture_compression_astc_decode_mode_rgb9e5
GL_KHR_debug
GL_EXT_occlusion_query_boolean
GL_EXT_disjoint_timer_query
GL_EXT_blend_minmax
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_OES_texture_3D
GL_EXT_texture_storage
GL_EXT_multisampled_render_to_texture
GL_EXT_multisampled_render_to_texture2
GL_OES_surfaceless_context
GL_OES_texture_stencil8
GL_EXT_shader_pixel_local_storage
GL_ARM_shader_framebuffer_fetch
GL_ARM_shader_framebuffer_fetch_depth_stencil
GL_ARM_mali_program_binary
GL_EXT_sRGB
GL_EXT_sRGB_write_control
GL_EXT_texture_sRGB_decode
GL_EXT_texture_sRGB_R8
GL_EXT_texture_sRGB_RG8
GL_KHR_blend_equation_advanced
GL_KHR_blend_equation_advanced_coherent
GL_OES_texture_storage_multisample_2d_array
GL_OES_shader_image_atomic
GL_EXT_robustness
GL_EXT_draw_buffers_indexed
GL_OES_draw_buffers_indexed
GL_EXT_texture_border_clamp
GL_OES_texture_border_clamp
GL_EXT_texture_cube_map_array
GL_OES_texture_cube_map_array
GL_OES_sample_variables
GL_OES_sample_shading
GL_OES_shader_multisample_interpolation
GL_EXT_shader_io_blocks
GL_OES_shader_io_blocks
GL_EXT_tessellation_shader
GL_OES_tessellation_shader
GL_EXT_primitive_bounding_box
GL_OES_primitive_bounding_box
GL_EXT_geometry_shader
GL_OES_geometry_shader
GL_ANDROID_extension_pack_es31a
GL_EXT_gpu_shader5
GL_OES_gpu_shader5
GL_EXT_texture_buffer
GL_OES_texture_buffer
GL_EXT_copy_image
GL_OES_copy_image
GL_EXT_shader_non_constant_global_initializers
GL_EXT_color_buffer_half_float
GL_EXT_color_buffer_float
GL_EXT_YUV_target
GL_OVR_multiview
GL_OVR_multiview2
GL_OVR_multiview_multisampled_render_to_texture
GL_KHR_robustness
GL_KHR_robust_buffer_access_behavior
GL_EXT_draw_elements_base_vertex
GL_OES_draw_elements_base_vertex
GL_EXT_protected_textures
GL_EXT_buffer_storage
GL_EXT_external_buffer
GL_EXT_EGL_image_array
<<< Network >>>
<< Telephony >>
Phone Type: None
<< Wi-Fi >>
State: Enabled
SSID: < private >
BSSID: < private >
Hidden SSID: Yes
IPv4 Address: < private >
IPv6 Address: < private >
Signal Strength: -35 dBm (Excellent)
Link Speed: 135 Mbps
Frequency: 2412 MHz
Network ID: 0
Gateway: < private >
Netmask: 255.255.255.0
DNS1: < private >
DHCP Lease Duration: 24 hours
5 GHz Band: Not Supported
Wi-Fi Aware: Not Supported
Wi-Fi Direct: Supported
<<< Battery >>>
Power Source: A/C Charger
Level: 100 %
Status: Charging
Health: Good
Technology: Li-ion
Temperature: 42.4°C
Voltage: 45.000 V
Charge Counter: 0 mAh
Charge Rate: 1.60 mA
<<< Android >>>
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-06-01
Rooted Device: No
Android ID: 00c6e6eeb37e4da8
Bootloader: 123456789
Build ID: m7332_eu-userdebug 9 PPR2.180905.006.A1 TVOS-04.16.031.01.12 dev-keys
Codename: REL
Fingerprint: MediaTek/m7332_eu/m7332_eu:9/PPR2.180905.006.A1/builder06120124:userdebug/dev-keys
ID: PPR2.180905.006.A1
Incremental: TVOS-04.16.031.01.12
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 192 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118+
Tags: dev-keys
Type: userdebug
Google Play Services Version: 16.0.89 (100300-239467275)
Huawei Mobile Services Version: < Not Present >
OpenSSL Version: OpenSSL 1.1.0 (compatible; BoringSSL)
ZLib Version: 1.2.11
ICU CLDR Version: 32.0.1
ICU Library Version: 60.2
ICU Unicode Version: 10.0
Android Language: Turkish (Turkey)
Configured Time Zone: Arabian Standard Time (UTC+03:00)
UpTime: 05:44:22
<<< Devices >>>
<< External Camera >>
Resolution: 2.1 MP (1920 × 1080)
Focus Modes: fixed, infinity
Video Stabilization: Not Supported
Zoom: Supported
Auto Exposure Locking: Not Supported
Auto White Balance Locking: Not Supported
Flash: Not Supported
<< Vulkan Device - Mali-G52 >>
Device Name: Mali-G52
Device Type: Integrated GPU
Device UUID: 20-E7-92-C6-F5-DE-89-0B-F7-A8-CC-CA-9D-DE-66-B8
Device ID: 000013B5-74021000
Memory Size: 1360744 KB
Max 1D Image Size: 16384
Max 2D Image Size: 8192 x 8192
Max 3D Image Size: 4096 x 4096 x 4096
Max Cube Image Size: 8192 x 8192
Max Image Layers: 256
Max Texel Buffer Elements: 65536
Max Uniform Buffer Range: 65536
Max Storage Buffer Range: 268435456
Max Push Constants Size: 256 bytes
Buffer Image Granularity: 4 KB
Max Bound Descriptor Sets: 4
Max Per-Stage Descriptor Samplers: 128
Max Per-Stage Descriptor Uniform Buffers: 12
Max Per-Stage Descriptor Storage Buffers: 35
Max Per-Stage Descriptor Sampled Images: 16
Max Per-Stage Descriptor Storage Images: 8
Max Per-Stage Descriptor Input Attachments: 4
Max Per-Stage Resources: 83
Max Descriptor Set Samplers: 768
Max Descriptor Set Uniform Buffers: 72
Max Descriptor Set Dynamic Uniform Buffers: 8
Max Descriptor Set Storage Buffers: 210
Max Descriptor Set Dynamic Storage Buffers: 4
Max Descriptor Set Sampled Images: 96
Max Descriptor Set Storage Images: 48
Max Descriptor Set Input Attachments: 4
Max Vertex Input Attributes: 16
Max Vertex Input Bindings: 16
MaxVertex Input Attribute Offset: 2047
Max Vertex Input Binding Stride: 2048
Max Vertex Output Components: 128
Max Tesselation Generation Level: 64
Max Tesselation Patch Size: 32
Max Tesselation Control Per-Vertex Input Components: 128
Max Tesselation Control Per-Vertex Output Components: 128
Max Tesselation Control Per-Patch Output Components: 120
Max Tesselation Control Total Output Components: 4096
Max Tesselation Evaluation Input Components: 128
Max Tesselation Evaluation Output Components: 128
Max Geometry Shader Invocations: 32
Max Geometry Input Components: 64
Max Geometry Output Components: 128
Max Geometry Output Vertices: 256
Max Geometry Total Output Components: 1024
Max Fragment Input Components: 128
Max Fragment Output Attachments: 8
Max Fragment Combined Output Resources: 51
Max Compute Shared Memory Size: 32 KB
Max Compute Work Group Invocations: 384
Max Compute Work Group Size: X: 384, Y: 384, Z: 384
Subpixel Precision Bits: 8
Subtexel Precision Bits: 8
Mipmap Precision Bits: 8
Max Draw Indexed Index Value: 4294967295
Max Draw Indirect Count: 1
Max Sampler LOD Bias: 255.000000
Max Sampler Anisotropy: 16.000000
Max Viewports: 1
Max Viewport Size: 8192 x 8192
Viewport Bounds Range: -16384.000000 ... 16383.000000
Min Memory Map Alignment: 64 bytes
Min Texel Buffer Offset Alignment: 256 bytes
Min Uniform Buffer Offset Alignment: 16 bytes
Min Storage Buffer Offset Alignment: 256 bytes
Min / Max Texel Offset: -8 / 7
Min / Max Texel Gather Offset: -8 / 7
Min / Max Interpolation Offset: -0.500000 / 0.500000
Subpixel Interpolation Offset Bits: 4
Max Framebuffer Size: 8192 x 8192
Max Framebuffer Layers: 256
Framebuffer Color Sample Counts: 0x00000005
Framebuffer Depth Sample Counts: 0x00000005
Framebuffer Stencil Sample Counts: 0x00000005
Framebuffer No Attachments Sample Counts: 0x0000001D
Max Color Attachments: 8
Sampled Image Color Sample Counts: 0x00000005
Sampled Image Integer Sample Counts: 0x00000001
Sampled Image Depth Sample Counts: 0x00000005
Sampled Image Stencil Sample Counts: 0x00000005
Storage Image Sample Counts: 0x00000001
Max Sample Mask Words: 1
Discrete Queue Priorities: 2
Point Size Range: 1.000000 ... 1024.000000
Line Width Range: 1.000000 ... 1.000000
Point Size Granularity: 0.062500
Optimal Buffer Copy Offset Alignment: 64 bytes
Optimal Buffer Copy Row Pitch Alignment: 64 bytes
Non-Coherent Atom Size: 64 bytes
Driver Version: 16.0.0
API Version: 1.1.82
Vulkan Library: /system/lib/libvulkan.so
Alpha To One: Not Supported
Anisotropic Filtering: Supported
ASTC LDR Texture Compression: Supported
BC Texture Compression: Not Supported
Depth Bias Clamping: Supported
Depth Bounds Tests: Not Supported
Depth Clamping: Not Supported
Draw Indirect First Instance: Supported
Dual Source Blend Operations: Not Supported
ETC2 and EAC Texture Compression: Supported
Fragment Stores and Atomics: Supported
Full Draw Index Uint32: Supported
Geometry Shader: Supported
Image Cube Array: Supported
Independent Blend: Supported
Inherited Queries: Not Supported
Large Points: Supported
Logic Operations: Not Supported
Multi-Draw Indirect: Not Supported
Multi Viewport: Not Supported
Occlusion Query Precise: Supported
Pipeline Statistics Query: Not Supported
Point and Wireframe Fill Modes: Not Supported
Robust Buffer Access: Supported
Sample Rate Shading: Supported
Shader Clip Distance: Not Supported
Shader Cull Distance: Not Supported
Shader Float64: Not Supported
Shader Image Gather Extended: Supported
Shader Int16: Supported
Shader Int64: Not Supported
Shader Resource Min LOD: Not Supported
Shader Resource Residency: Not Supported
Shader Sampled Image Array Dynamic Indexing: Supported
Shader Storage Buffer Array Dynamic Indexing: Supported
Shader Storage Image Array Dynamic Indexing: Supported
Shader Storage Image Extended Formats: Supported
Shader Storage Image Multisample: Not Supported
Shader Storage Image Read Without Format: Supported
Shader Storage Image Write Without Format: Supported
Shader Tesselation and Geometry Point Size: Not Supported
Shader Uniform Buffer Array Dynamic Indexing: Supported
Sparse Binding: Not Supported
Sparse Residency 2 Samples: Not Supported
Sparse Residency 4 Samples: Not Supported
Sparse Residency 8 Samples: Not Supported
Sparse Residency 16 Samples: Not Supported
Sparse Residency Aliased: Not Supported
Sparse Residency Aligned Mip Size: No
Sparse Residency Buffer: Not Supported
Sparse Residency Image 2D: Not Supported
Sparse Residency Image 3D: Not Supported
Sparse Residency Non-Resident Strict: No
Sparse Residency Standard 2D Block Shape: No
Sparse Residency Standard 2D Multisample Block Shape: No
Sparse Residency Standard 3D Block Shape: No
Standard Sample Locations: Yes
Strict Line Rasterization: Yes
Tesselation Shader: Supported
Timestamps on All Graphics and Compute Queues: Not Supported
Variable Multisample Rate: Not Supported
Vertex Pipeline Stores and Atomics: Not Supported
Wide Lines: Not Supported
Device Extensions: VK_KHR_incremental_present
VK_KHR_shared_presentable_image
VK_GOOGLE_display_timing
VK_KHR_16bit_storage
VK_KHR_bind_memory2
VK_KHR_dedicated_allocation
VK_KHR_descriptor_update_template
VK_KHR_external_fence
VK_KHR_external_fence_fd
VK_KHR_external_memory
VK_KHR_external_semaphore
VK_KHR_external_semaphore_fd
VK_KHR_get_memory_requirements2
VK_KHR_image_format_list
VK_KHR_maintenance1
VK_KHR_maintenance2
VK_KHR_sampler_ycbcr_conversion
VK_KHR_shader_draw_parameters
VK_KHR_storage_buffer_storage_class
VK_KHR_variable_pointers
VK_KHR_create_renderpass2
VK_KHR_maintenance3
VK_KHR_relaxed_block_layout
VK_KHR_device_group
VK_KHR_multiview
VK_EXT_queue_family_foreign
VK_KHR_swapchain
Instance Extensions: VK_KHR_surface
VK_KHR_android_surface
VK_EXT_swapchain_colorspace
VK_KHR_get_surface_capabilities2
VK_EXT_debug_report
VK_KHR_external_fence_capabilities
VK_KHR_external_memory_capabilities
VK_KHR_external_semaphore_capabilities
VK_KHR_get_physical_device_properties2
VK_KHR_device_group_creation
No USB devices found.
No OpenCL devices found.
No CUDA devices found.
No PCI devices found.
<<< Thermal >>>
Battery: 42.4°C
<<< Sensors >>>
No sensors found.
<<< Directories >>>
Data: /data
Root: /system
Java Home: /system
Download/Cache Content: /data/cache
<< External Storage >>
Primary External Storage: /storage/emulated/0
External Files #1: /storage/emulated/0/Android/data/com.finalwire.aida64/files
Alarms: /storage/emulated/0/Alarms
Downloads: /storage/emulated/0/Download
Music: /storage/emulated/0/Music
Notifications: /storage/emulated/0/Notifications
Pictures: /storage/emulated/0/Pictures
<< Mount Points >>
/: Device: /dev/root
File System: ext4
Read-Only
/dev: Device: devtmpfs
File System: devtmpfs
Read-Write
/dev: Device: tmpfs
File System: tmpfs
Read-Write
/dev/pts: Device: devpts
File System: devpts
Read-Write
/dev/cpuctl: Device: none
File System: cgroup
Read-Write
/dev/cpuset: Device: none
File System: cgroup
Read-Write
/dev/cg2_bpf: Device: cg2_bpf
File System: cgroup2
Read-Write
/dev/usb-ffs/adb: Device: adb
File System: functionfs
Read-Write
/proc: Device: proc
File System: proc
Read-Write
/sys: Device: sysfs
File System: sysfs
Read-Write
/sys/fs/selinux: Device: selinuxfs
File System: selinuxfs
Read-Write
/sys/kernel/debug: Device: debugfs
File System: debugfs
Read-Write
/sys/kernel/debug/tracing: Device: tracefs
File System: tracefs
Read-Write
/sys/fs/bpf: Device: bpf
File System: bpf
Read-Write
/mnt: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/vendor/tvservice: Device: /dev/block/platform/mstar_mci.0/by-name/tvservice
File System: ext4
Read-Only
/mnt/vendor/linux_rootfs: Device: /dev/block/platform/mstar_mci.0/by-name/linux_rootfs_a
File System: squashfs
Read-Only
/mnt/vendor/3rd: Device: /dev/block/platform/mstar_mci.0/by-name/3rd_a
File System: squashfs
Read-Only
/mnt/runtime/default/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/read/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/write/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/vendor: Device: /dev/block/platform/mstar_mci.0/by-name/vendor
File System: ext4
Read-Only
/vendor/tvconfig: Device: /dev/block/platform/mstar_mci.0/by-name/tvconfig
File System: ext4
Read-Write
/vendor/tvcertificate: Device: /dev/block/platform/mstar_mci.0/by-name/tvcertificate
File System: ext4
Read-Write
/acct: Device: none
File System: cgroup
Read-Write
/config: Device: none
File System: configfs
Read-Write
/data: Device: /dev/block/platform/mstar_mci.0/by-name/userdata
File System: ext4
Read-Write
/data/vendor/tmp: Device: tmpfs
File System: tmpfs
Read-Write
/data/vendor/tmp: Device: tmpfs
File System: tmpfs
Read-Write
/data/vendor/3rd_rw: Device: /dev/block/platform/mstar_mci.0/by-name/3rd_rw
File System: ext4
Read-Write
/cache: Device: /dev/block/platform/mstar_mci.0/by-name/cache
File System: ext4
Read-Write
/factory: Device: /dev/block/platform/mstar_mci.0/by-name/factory_a
File System: ext4
Read-Write
/storage: Device: tmpfs
File System: tmpfs
Read-Write
/storage/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/storage/self: Device: tmpfs
File System: tmpfs
Read-Write
<<< External Dirs >>>
ExternalStorageDir = /storage/emulated/0
ExternalFilesDirs[0] = /storage/emulated/0/Android/data/com.finalwire.aida64/files
SDCardMountPoint[0] = /mnt/sdcard
<<< /proc/cpuinfo >>>
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 2884.97
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 2884.97
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 2884.97
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 2884.97
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : m7332
Revision : 0020
Serial : 0000000000000000
Hardware : m7332
<<< /proc/meminfo >>>
MemTotal: 1360744 kB
MemFree: 68052 kB
MemAvailable: 494524 kB
Buffers: 7088 kB
Cached: 475488 kB
SwapCached: 6560 kB
Active: 478848 kB
Inactive: 258360 kB
Active(anon): 153796 kB
Inactive(anon): 103916 kB
Active(file): 325052 kB
Inactive(file): 154444 kB
Unevictable: 2548 kB
Mlocked: 2548 kB
HighTotal: 913408 kB
HighFree: 18600 kB
LowTotal: 447336 kB
LowFree: 49452 kB
SwapTotal: 511996 kB
SwapFree: 227632 kB
Dirty: 68 kB
Writeback: 0 kB
AnonPages: 255772 kB
Mapped: 340752 kB
Shmem: 980 kB
Slab: 58880 kB
SReclaimable: 20080 kB
SUnreclaim: 38800 kB
KernelStack: 14864 kB
PageTables: 40324 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1192368 kB
Committed_AS: 32467388 kB
VmallocTotal: 557056 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
CmaTotal: 69632 kB
CmaFree: 31580 kB
<<< Directory /system/lib >>>
libLLVM_android.so
libaudioclient.so
libvulkan.so
<<< Directory /system/vendor/lib >>>
libOpenCL.so
<<< Directory /system/vendor/lib/egl >>>
libGLES_mali.so
<<< GpuSysFs Files >>>
/sys/devices/platform/gpusysfs/gpu_clock: < Failed >
/sys/devices/platform/gpusysfs/gpu_cores_config: < Failed >
/sys/devices/platform/gpusysfs/gpu_freq_table: < Failed >
/sys/devices/platform/gpusysfs/gpu_governor: < Failed >
/sys/devices/platform/gpusysfs/gpu_max_clock: < Failed >
/sys/devices/platform/gpusysfs/gpu_mem: < Failed >
/sys/devices/platform/gpusysfs/gpu_min_clock: < Failed >
/sys/devices/platform/gpusysfs/gpu_model: < Failed >
/sys/devices/platform/gpusysfs/gpu_tmu: < Failed >
/sys/devices/platform/gpusysfs/gpu_version: < Failed >
/sys/devices/platform/gpusysfs/gpu_voltage: < Failed >
<<< Mali Files >>>
/sys/devices/platform/mali.0/clock: < Failed >
/sys/class/misc/mali0/device/asv_table: < Failed >
/sys/class/misc/mali0/device/available_frequencies: < Failed >
/sys/class/misc/mali0/device/clock: < Failed >
/sys/class/misc/mali0/device/core_mask: *** Current core mask (JS0) : 0x1
Current core mask (JS1) : 0x1
Current core mask (JS2) : 0x1
Available core mask : 0x1
***
/sys/class/misc/mali0/device/dvfs_governor: < Failed >
/sys/class/misc/mali0/device/dvfs_table: < Failed >
/sys/class/misc/mali0/device/norm_utilization: < Failed >
/sys/class/misc/mali0/device/utilization: < Failed >
/sys/class/misc/mali0/device/utilization_stats: < Failed >
/sys/class/misc/mali0/device/vol: < Failed >
<<< OMAP Files >>>
/sys/kernel/debug/clock/virt_38400000_ck/sys_clkin_ck/dpll_per_ck/dpll_per_x2_ck/dpll_per_m7x2_ck/gpu_fck/rate: < Failed >
/sys/kernel/debug/clock/virt_38400000_ck/sys_clkin_ck/dpll_per_ck/dpll_per_x2_ck/dpll_per_m7x2_ck/gpu_fck/flags: < Failed >
<<< PXA Files >>>
/sys/kernel/debug/pxa/cp15: < Failed >
/sys/devices/platform/pxa-ion/modalias: < Failed >
/sys/devices/platform/pxa-ion/subsystem/devices/pxa1088-thermal/modalias: < Failed >
<<< Tegra Files >>>
/sys/devices/soc0/family: < Failed >
/sys/devices/soc0/revision: < Failed >
/sys/devices/soc0/soc_id: < Failed >
<<< CPUFreq >>>
CPU0: < Failed > / 1150000 / 1450000 // 1150000 / 1150000 / < Failed >
CPU1: < Failed > / 1150000 / 1450000 // 1350000 / 1150000 / 1450000
CPU2: < Failed > / 1150000 / 1450000 // 1350000 / 1150000 / 1450000
CPU3: < Failed > / 1150000 / 1450000 // 1350000 / 1150000 / 1450000
<<< Battery Files >>>
/sys/class/power_supply/battery/batt_attr_text: < Failed >
/sys/class/power_supply/battery/batt_current: < Failed >
/sys/class/power_supply/battery/batt_current_now: < Failed >
/sys/class/power_supply/battery/batt_current_ua_avg: < Failed >
/sys/class/power_supply/battery/batt_current_ua_now: < Failed >
/sys/class/power_supply/battery/batt_power_meter: < Failed >
/sys/class/power_supply/battery/BatteryAverageCurrent: < Failed >
/sys/class/power_supply/battery/charge_counter: < Failed >
/sys/class/power_supply/battery/charge_counter_ext: < Failed >
/sys/class/power_supply/battery/charge_now: < Failed >
/sys/class/power_supply/battery/chg_current_adc: < Failed >
/sys/class/power_supply/battery/chg_temp: < Failed >
/sys/class/power_supply/battery/current_avg: < Failed >
/sys/class/power_supply/battery/current_now: < Failed >
/sys/class/power_supply/battery/energy_now: < Failed >
/sys/class/power_supply/battery/time_to_empty_now: < Failed >
/sys/class/power_supply/battery/time_to_full_now: < Failed >
/sys/class/power_supply/battery/usb_temp: < Failed >
/sys/class/power_supply/battery/voltage_now: < Failed >
/sys/devices/platform/battery/power_supply/battery/BatteryAverageCurrent: < Failed >
<<< Misc Files >>>
<<< TelephonyManager Method Names >>>
public int android.telephony.TelephonyManager.getDataActivity() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getDataNetworkType() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getDataNetworkType(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getDataState() declared by class android.telephony.TelephonyManager
public static android.telephony.TelephonyManager android.telephony.TelephonyManager.getDefault() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkCountryIso() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkCountryIso(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkCountryIsoForPhone(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkOperator() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkOperator(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkOperatorForPhone(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkOperatorName() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkOperatorName(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getNetworkType() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getNetworkType(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getNetworkTypeName() declared by class android.telephony.TelephonyManager
public static java.lang.String android.telephony.TelephonyManager.getNetworkTypeName(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getPhoneCount() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getPhoneType() declared by class android.telephony.TelephonyManager
public static int android.telephony.TelephonyManager.getPhoneType(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getSimCount() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimCountryIso() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimCountryIso(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimCountryIsoForPhone(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperator() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperator(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorName() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorName(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorNameForPhone(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorNumeric() declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorNumeric(int) declared by class android.telephony.TelephonyManager
public java.lang.String android.telephony.TelephonyManager.getSimOperatorNumericForPhone(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getSimState() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getSimState(int) declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getVoiceMessageCount() declared by class android.telephony.TelephonyManager
public int android.telephony.TelephonyManager.getVoiceMessageCount(int) declared by class android.telephony.TelephonyManager
public boolean android.telephony.TelephonyManager.hasIccCard() declared by class android.telephony.TelephonyManager
public boolean android.telephony.TelephonyManager.hasIccCard(int) declared by class android.telephony.TelephonyManager
public boolean android.telephony.TelephonyManager.isNetworkRoaming() declared by class android.telephony.TelephonyManager
public boolean android.telephony.TelephonyManager.isNetworkRoaming(int) declared by class android.telephony.TelephonyManager
public void android.telephony.TelephonyManager.setNetworkCountryIso(java.lang.String) declared by class android.telephony.TelephonyManager
public void android.telephony.TelephonyManager.setNetworkCountryIsoForPhone(int,java.lang.String) declared by class android.telephony.TelephonyManager
public void android.telephony.TelephonyManager.setSimCountryIsoForPhone(int,java.lang.String) declared by class android.telephony.TelephonyManager
<<< Comment >>>
Enter your comment here:
Click to expand...
Click to collapse

I want Orginal (non touch) no customization Android tv OS
this file Distributor update customization Android9 https://drive.google.com/drive/u/0/folders/1TNq91duEnXrfUpzjH0DMr9Ln_XQwkUiH

i have a different tv name with the same motherboard and features.... i am very interested in having a stock firmware too (mine looks exactly like yours). I have flashed yours on my tv, so I am sure it works. The only difference is that now my tv says dijitsu instead of akai and the remote controller does not work....

your firmware is much better than mine by the way... it has apple play, play store and an app to control the device with the phone. it is a shame that the remote does not work, otherwise i would have kept it!
EnzoErrichiello said:
i have a different tv name with the same motherboard and features.... i am very interested in having a stock firmware too (mine looks exactly like yours). I have flashed yours on my tv, so I am sure it works. The only difference is that now my tv says dijitsu instead of akai and the remote controller does not work....
Click to expand...
Click to collapse

Hi
I have similar TV on different name. the customized Android OS have none of Google Apps and I even if I install google play by my self it didn't run.
Do you find any good firmware?
and how do you manage to upgrade above firmware?

yaser.k said:
Hi
I have similar TV on different name. the customized Android OS have none of Google Apps and I even if I install google play by my self it didn't run.
Do you find any good firmware?
and how do you manage to upgrade above firmware?
Click to expand...
Click to collapse
Hey,
In the end I used the firmware the author attached here. To have my remote working again, I then flashed a minor update released by AKAI, which is my tv.
I haven't found a stock firmware yet, but I'll let you know if I do.

EnzoErrichiello said:
Hey,
In the end I used the firmware the author attached here. To have my remote working again, I then flashed a minor update released by AKAI, which is my tv.
I haven't found a stock firmware yet, but I'll let you know if I do.
Click to expand...
Click to collapse
Hey Enzo
could you tell me how update with this firmware?
I extract rar file and there was 3 bin file. I copy all on usb drive attach to tv.
I go to system upgrade > local upgrade. but it didn't detect file on flash.
also I try hold power bottom and plug in but it also dont work.

yaser.k said:
Hey Enzo
could you tell me how update with this firmware?
I extract rar file and there was 3 bin file. I copy all on usb drive attach to tv.
I go to system upgrade > local upgrade. but it didn't detect file on flash.
also I try hold power bottom and plug in but it also dont work.
Click to expand...
Click to collapse
Hey sorry for the late reply!
I renamed that firmware with the name of my firmware. If you need to switch back, you need to do the opposite

Do have a TV set with Mediatek m7332 chip, Android 9.
You have an app to control TV via phone? Maybe that can be copied to other TVs too?
I am new to SmartTV but would be curious to learn.

i found that the remote control configuration is saved in a file in the system folder of tv "/vendor/tvconfig/config/ir_config.ini'.
Because tv isnt rooted yet, you need to access to this file via adb, allowing access to system files by adb and make copy of your oryginal config file, then replace it after flashing another firmware.
It worked on akai, nordmende, manta, and dijitsu firmwares on my Manta tv with TP.SK706S.PC822 board and with Mediatek m7332 chip.
● To enable ADB you have to go to hidden 'service menu' by pressing buttons (MENU) + (1) + (1) + (4) + (7).
If the service menu will appear, then you need to go to the ''debug'' option and then switch ''adb enable'' to 'on'.
[In other brands than Akai, Dijitsu, Manta, Nordmende, the service code may be different.]
You can try to enable ADB via AndroidHiddenSettings app, getting acces thru 'Developer Settings'.
Screenshots in: post-87570305
● Then you can explore your tv file system from your android phone by the Bugjaeger Mobile ADB app after connecting it thru wifi by ip of your tv.
Press button 'connect to' where you can 'search' for adb device or you can type tvs ip manually.
Now You can view system folders, copy files, install apps thru adb wifi, reboot system to recovery etc etc.
Files inside the system are still read only, so you cant delete/replace nothing yet, and some of the system folders are hidden at this time.
To make file system read and write enabled You have to use ADB command thru your PC/laptop.
● So you need to download some Minimal Adb Tool or ADBappControl for windows.
• Minimal ADB Tool (ADB.exe) run in 'windows command prompt' (cmd.exe) by typing:
adb connect 192.168.**.*** (-type your tvs ip, you can find tvs ip in main 'service menu')
adb root
adb remount
• ADBappControl with bulid-in ADB also allows you type those commands, has a pretty nice interface that allows you to install/uninstall disable apps.
It just don't have file manager, so 'bugjaeger' is still needed for the next step.
● Now file system is read and write enabled and you can backup your oryginal 'ir_config.ini', thru 'bugjaeger' app in section "files'.
The same way replace it after flashing another firmware.
At this time You can modify, replace/remove system apps as youtube, netflix, etc.
Read/write file system is enabled only till reboot. after reboot you need to redo pc ADB commands to get acces to r/w file system.
btw.
Section 'packages' in 'bugjaeger' app let you send and install apps downloaded/installed on your phone to your tv thru wifi. You can also run apps or disable/enable apps thru this section, instead of removing them from the system.
Section 'command' let you grant some special permision of some app if you need it.
Section 'fastboot' let you quick reboot your device, or reboot to recovery.
EDIT.: Added in attachment a remote config file working with my stock (manta) tv remote.
Anyway, better make Your own backup if You can.

yaser.k said:
Hey Enzo
could you tell me how update with this firmware?
I extract rar file and there was 3 bin file. I copy all on usb drive attach to tv.
I go to system upgrade > local upgrade. but it didn't detect file on flash.
also I try hold power bottom and plug in but it also dont work.
Click to expand...
Click to collapse
The best way to to flash firmware to your TV (with TP.SK706S.PC822 board) is:
-Rename your firmware file, for example from 'allupgrade706_8GB_1P5GB_ref71.bin' to 'allupgrade706_8GB_1P5GB_sos.bin.
-copy firmware file to your pendrive, formatted to the 'FAT32' filesystem, (probably the best working is up to 8Gb capicity pendrive.)
Unplug your Tv from the power supply, wait till the standby LED turn off.
-Then plug your pendrive to Tvs usb slot.
Plug Your Tv to power supply and wait for firmware upgrade blue screen.
-Wait till 100%, Unplug your Tv from the power supply, unplug pendrive then connect to power supply again, and power it on by tv 'power button'.

In Case of any issues with Android Tv system like Boot Loop etc, i found file MstarUpgrade Android Recovery Software by @KazmiElecom, that boots up Tv to 'Recovery Mode', so you can do wipe data/factory reset or anything from recovery mode.
Same process as upgrade firmware:
just rename file, in this case "MstarUpgrade.bin" to "allupgrade706_8GB_1P5GB_sos.bin" and plug to tv's usb slot.
Connect Tv to power supply, and when you'll see the completed 100% "Upgrade firmware" on a blue screen,
- Reconnect Tv again and it will boot up in Recovery Mode for once.
It works probably with many others Mstar / Mediatek chip boards.

Emilson said:
In Case of any issues with Android Tv system like Boot Loop etc, i found file MstarUpgrade Android Recovery Software by @KazmiElecom, that boots up Tv to 'Recovery Mode', so you can do wipe data/factory reset or anything from recovery mode.
Same process as upgrade firmware:
just rename file, in this case "MstarUpgrade.bin" to "allupgrade706_8GB_1P5GB_sos.bin" and plug to tv's usb slot.
Connect Tv to power supply, and when you'll see the completed 100% "Upgrade firmware" on a blue screen,
- Reconnect Tv again and it will boot up in Recovery Mode for once.
It works probably with many others Mstar / Mediatek chip boards.
Click to expand...
Click to collapse
I tried doing this but i am stuck at "no command". tried randomly pushing buttons on the tv but nothing is happening. sad, my OS is Android 11 Wisdom Share. I think it is stuck at boot because I messed with the build.prop

I am new to SmartTV but would be curious to learn.

لدي تلفاز nordmende ماهو الحل علاق tv nordmende nd 46 ks 4000 j

Emilson said:
i found that the remote control configuration is saved in a file in the system folder of tv "/vendor/tvconfig/config/ir_config.ini'.
Because tv isnt rooted yet, you need to access to this file via adb, allowing access to system files by adb and make copy of your oryginal config file, then replace it after flashing another firmware.
it worked for my on akai, nordmende, manta, and dijitsu firmwares on my Manta tv with TP.SK706S.PC822 board and with Mediatek m7332 chip.
To enable ADB you have to go to hidden 'service menu' by pressing buttons (MENU) + (1) + (1) + (4) + (7). and the service menu will appear, then you need to go to the ''debug'' option and then switch ''adb enable'' to 'on'.
Then you can explore your tv file system from your android phone by the app Bugjaeger Mobile ADB app after connecting thru wifi by ip of your tv.
If ADB is enabled and tv is connected to wifi, app should find your tv, by pressing button 'connect to' and 'search' for adb devices. or you can type tvs ip manually.
Now You can view system folders, copy files, install apps thru adb wifi, add special permisions to apps, rebot system to recovery etc etc.
But 'files' inide the system are still read only, so you cant delete/replace it nothing yet.
To make file system read and write enabled You have to use ADB command thru your PC
So you need to download some mini ADB tool (adb.exe) for windows, run it in windows 'command prompt' by typing:
adb connect 192.168.**.*** (-type your tvs ip, also you can find tvs ip in main 'service menu')
adb root
adb remount
adb shell chmod 0777 /system
Now file system is read and write enabled and you can backup your oryginal 'ir_config.ini', thru 'bugjaeger' app in section "files'. The same way replace it after changing with another firmware.
At this time You can replace/remove system apps as youtube, netflix, etc.
Read file system is enabled only till reboot. after reboot you need to redo pc ADB commands to get acces to r/w filesystem.
btw.
Section 'packages' in 'bugjaeger' app let you send and install apps downloaded/installed on your phone to your tv thru wifi. You can also run or disable/enable system apps thru this section, instead of removing it from the system.
Section 'command' let you reboot your device, or grant some special permision of some app if you need it,
Click to expand...
Click to collapse
Have you found out a way to change bootanimation?

I have found a firmware that claims it is AOSP, can anybody try? https://remont-aud.net/dump/lcd_pdp...06s_pc822_b19457/248-1-0-110135?l3BuY2?lb0zah
EnzoErrichiello said:
your firmware is much better than mine by the way... it has apple play, play store and an app to control the device with the phone. it is a shame that the remote does not work, otherwise i would have kept it!
Click to expand...
Click to collapse

kaitokid1412 said:
I tried doing this but i am stuck at "no command". tried randomly pushing buttons on the tv but nothing is happening. sad, my OS is Android 11 Wisdom Share. I think it is stuck at boot because I messed with the build.prop
Click to expand...
Click to collapse
Whoa, android 11? Whats your tv model?
By the way, bootanimation is placed at /system/media/bootanimation.zip
You just need to download any bootanimation.zip from web and replace it, when system folders are read/write enabled.
I already changed it in mine
There is one bootanimation link for example:
atv11_bootanimation/Working and Tested/bootanimation.zip at master · khurramrizvi/atv11_bootanimation
A brand new boot animation coming straight from Google's Android TV 11 build. - atv11_bootanimation/Working and Tested/bootanimation.zip at master · khurramrizvi/atv11_bootanimation
github.com
Probably newest original google androidTV bootanimation

Emilson said:
Whoa, android 11? Whats your tv model?
By the way, bootanimation is placed at /system/media/bootanimation.zip
You just need to download any bootanimation.zip from web and replace it, when system folders are read/write enabled.
I already changed it in mine
There is one bootanimation link for example:
atv11_bootanimation/Working and Tested/bootanimation.zip at master · khurramrizvi/atv11_bootanimation
A brand new boot animation coming straight from Google's Android TV 11 build. - atv11_bootanimation/Working and Tested/bootanimation.zip at master · khurramrizvi/atv11_bootanimation
github.com
Probably newest original google androidTV bootanimation
Click to expand...
Click to collapse
Mine, I think, is a rebranded Chinese TV. N-Vision S900-65S1NV. It is Android 11 yet still with a Wisdom Share UI. That's the thing, I have located the bootanimation folder in mine, it's in vendor/tvconfig folder, however, when I tried to replace it using bugjaeger, the system does not read the new boot animation.

Oh ok, in a vendor/tvconfing folder you can find a branded bootlogo etc, but i couldnt change it that way too.
To change it you have to use tvs 'service menu' and go to 'general settings' -> 'import/export' and then you can use 'logo export/logo import' to download original bootlogo and upload new one, but you need to plug some usb pendrive for it.
Then to change 'wisdomshare logo' you have to replace bootanimation.zip in system/media folder.
Btw, Do you have any links with firmware to your tv? Mine is still on android 9.0 cant find any upgrades.
do you know whats your tv motherboard name? Mine is 'tpsk706s.pc822'