> Important!

We strongly recommend to familiarize withRules section "Android - devices"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Bliss Pad A9730 - Discussion | 9.7 "tablet



Rep: (933)
DiscussionBliss Pad A9730
PictureBliss Pad A9730
Discussion пїЅ
  • Before asking a question, look Android OS FAQandGlossary. Respect your and other people's time.
  • To discuss and search for third-party programs / games, use the following sections: Programs and Games .
  • To compare the device with competitors and on the choice of devices, please contact: Selection and Comparison .
  • The available amount of RAM and memory for installing applications is discussed in the topic: How much memory is in your machine?
  • The results of performance tests of Android devices, see the topic: Benchmark
  • Before posting photos, read the topic Working with Images on the forum
  • Messages that are not related to the topic of discussion (offtopic) are deleted without warning.

Specifications and photos of the device
Attached Image

Processor, model: Dual Core ARM Cortex-A9, CPU 1.5 GHz
CPU, core: Cortex A9
Operating system: Android 4.0
RAM: 1Gb DDR3
Internal storage: 16GB
Display: 9.7 '' LCD Touch Panel (4: 3; Resolution 1024 * 768), IPS
Microphone, speaker: Built-in, 1V x 2, stereo
Power Supply: Li-Polymer 6000mAh / 3.7V
Charger: DC Output 5V / 2A
G-Sensor: 3-axis
Wi-Fi: 802.11 b / g
Camera: Front 0.3M rear 2M
Bluetooth: V4.0 of 1.2.3 Mbps
GPS: built-in
3G: built-in
MicroSD: up to 32GB
HDMI: Support 1.4 A
USB OTG: USB OTG 2.0 x 1
I / 0: USB2.0, Mini USB, DC In, 3.5mm headphone jack, HDMI, TF Card slot, SIM slot
Video format: (1080p / FullHD 3D): AVI, 3GP, MP4, RMVB, MOV, MKV, TS, M2TS, MPG, VOB, M4V, FLV
Image Format: JPG / BMP / PNG / GIF
Audio format: MP3, WAV, OGG, FLAC, APE, AAC, AMR, M4A, M4R
Office Suite: Word, Excel, Powerpoint, PDF Reader
Email: Gmail, Email, optional
Games: G-sensor games / Touch games / Classic games
Surfing: Youtube, Facebook, Google Browser
E-Book: PDF / Epub / TXT / FB2
Applications: Over 20,000 applications from the Google Market
Weight, g: 610
Dimensions, mm: 189.5 x 242.5 x 11


How to enable developer mode in the settings on Android 4.2: Settings - in-info about the system - tap 7 times on the version of the assembly (the bottom line).
How to get into the service menu (recovery): We simultaneously hold the volume up and the power button.


Firmware

Instructions

Real photo device

Programs


Post has been editedAlexanderL - 14.11.16, 15:40
Reason for editing: If it does not load further than the inscription BLISS



Rep: (27)
Updated little forum. As it is written in the datasheet in the NAND 29F64G08CBAAA, up to 10,000 write cycles per cell before the first failure. Enough. Although there is a note manufacturer.
Google free translation
This NAND Flash device has a minimum number of valid blocks (NVB).
the total number of blocks available in the matrix shown in Table 21 on page 92. This means that
devices may have units that are not valid at the factory. Invalid unit
this is the page that contains at least one page with a large number of bit errors than can be corrected
minimum required ECC. Additional bad blocks may develop with use. However, the total
The number of available blocks drops below NVB during the life of the product.
Although NAND flash memory device may include bad blocks, they can be used safely
in systems that provide bad block management algorithms and error correction for
ensure data integrity.
Domestic circuit isolates each block from the other blocks, so the presence of the bad block
It does not affect the rest of the NAND Flash array.
NAND Flash devices are available from the factory. Factory identifies invalid
blocks before sending in an attempt to program the tag of bad blocks in each place
on the first page of each invalid block. It may not be able to program in each location
invalid block with a bad block mark. However, the first spare area in each
bad block tag is guaranteed to contain the bad block. This method corresponds to
Mapping Requirements to manufacturing defects ONFI. See. Table 17 for the marking of bad blocks.
System software should first check the location of the first spare area on the first page
each block before execution of any program or erase operations in the NAND Flash
device. Then the bad block table can be created that allows the system software to display
these areas. Factory tests are carried out under the worst conditions. Because invalid
units may be marginal, it may be impossible to restore the marking of bad blocks, if
block is erased.
Over time, some memory can not be programmed or erased properly. that
make sure that data is stored properly over the life of the Flash NAND device service,
Required precautions:
• Check the condition after each PROGRAM and ERASE.
• Under typical conditions, using the minimum required ECC, given in Table 17.
• Use the control algorithms for bad blocks and wear leveling.
The first block (physical block address 00h) for each CE # is guaranteed to be valid from
ECC is shipped from the factory.

Those. ON tablet should also be able to properly develop bad blocks and mark them.



Rep: (1019)
who needs a spare, give, because the problem with memory befell me



Rep: (27)
1ferrari @ 02.03.19, 08:49*
who needs a spare, give, because the problem with memory befell me

You have no desire poesperimentirovat memory?
I found the info, how to fix bad-blocks, but in UART ....
Pick something nahalyavu th willing, of course. But still I want to get to the truth ...

Post has been editedsoneks - 02.03.19, 10:56



Rep: (1019)
* soneks,
yes you can



Rep: (27)
I finally soldered nand-memory, some "patch" contacts affected. But it looks like the best of my nand-memory was even more inferior quality - bad-blocks there is still more. Fill the loader body is possible only through the USB-Burning-Tool, as other methods are not available. And it can not spill out of the huge number of bad-blocks. To nothing come. Or look for another memory and the normal hand for the installation of chips, or ...
Log for those interested (Silke shortened in part found bad-blocks)
EEEE I3000000032940xf100100203: 77510EEEE I400000004294_M6_BL1_3003>2137333в–’в–’в–’в–’L &, в–’Hв–’
wait pll-0x03 target is 0204 now it is 0x00000203
set ddr clock ok!

DX0DLLCR: 40000000
DX0DQTR: ffffffff
DX0DQSTR: 3db05001
DX1DLLCR: 40000000
DX1DQTR: ffffffff
DX1DQSTR: 3db05001
DX2DLLCR: 40000000
DX2DQTR: ffffffff
DX2DQSTR: 3db05001
DX3DLLCR: 40000000
DX3DQTR: ffffffff
DX3DQSTR: 3db05001
00000000 00 Stage Result
Stage 01 Result 00000000
Stage 02 Result 00000000
Stage 03 Result 00000000
USB boot Start
w_length = 00000040cmd: crc 0x8f800000 519,876 b2925b3f
buf = 8f800000len = 0007eec4fake_len = 0007eec4crc_value = b2925b3fw_length = 00000040w_length = 00000040w_length = 00000040cmd: crc 0x8f800000 519,876 b2925b3f
buf = 8f800000len = 0007eec4fake_len = 0007eec4crc_value = b2925b3fw_length = 00000040


U-Boot 2011.03-00000-g7a239f8-dirty (m6_anda_g12m1005a_v1 @ next) (Dec 28, 2012 - 13:55:03)

aml_rtc_init
aml rtc init first time!
DRAM: 1 GiB
relocation Offset is: 10614000
NAND: Amlogic nand flash uboot driver, Version U1.01.005 (c) 2010 Amlogic Inc.
No NAND device found !!!
NAND device id: 2c d7 94 84 3e 0
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron A revision NAND 4GiB MT29F32G-A)
aml_nand_init auto detect RB pin here and por_cfg: 3fe
aml_nand_init detect with RB pin here
##### aml_nand_init, with RB pins and chip->chip_delay: 20
bus_cycle = 5, bus_timing = 6, start_cycle = 6, end_cycle = 7, system = 5.0ns
oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mode: NAND_BCH24_1K_MODE
Creating 1 MTD partitions on "nandboot":
0x000000000000-0x000000400000: "nandboot"
nandboot initialized ok
No NAND device found !!!
NAND device id: 2c d7 94 84 3e 0
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron A revision NAND 4GiB MT29F32G-A)
4 NAND chips detected
dect valid_chip_num: 4 over 2, using NO RB mode
bus_cycle = 5, bus_timing = 6, start_cycle = 6, end_cycle = 7, system = 5.0ns
oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mode: NAND_BCH24_1K_MODE
detect valid_chip_num: 4 over 2, and aml_chip->internal_chipnr: 1, disable NAND_TWO_PLANE_MODE here
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1024, blk: 8 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1024, blk: 8 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1024, blk: 8 chip [3]
1 NAND detect Bad block at 1000000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1536, blk: 12 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1536, blk: 12 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1536, blk: 12 chip [3]
1 NAND detect Bad block at 1800000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1664, blk: 13 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1664, blk: 13 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 1664, blk: 13 chip [3]
1 NAND detect Bad block at 1a00000
...............................
..........................
1 NAND detect Bad block at 200000000
1 too much bad block !!
2 too much bad block !!
2 too much bad block !!
2 too much bad block !!
2 too much bad block !!
Creating 5 MTD partitions on "nandnormal":
0x000200400000-0x000200c00000: "mtd1"
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,544, blk: 4098 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,544, blk: 4098 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,544, blk: 4098 chip [3]
1 NAND detect Bad block at 200 400 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,672, blk: 4099 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,672, blk: 4099 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,672, blk: 4099 chip [3]
1 NAND detect Bad block at 200 600 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,800, blk: 4100 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,800, blk: 4100 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,800, blk: 4100 chip [3]
1 NAND detect Bad block at 200 800 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,928, blk: 4101 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,928, blk: 4101 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 524,928, blk: 4101 chip [3]
1 NAND detect Bad block at 200a00000
0x000200c00000-0x000201400000: "mtd2"
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,056, blk: 4102 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,056, blk: 4102 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,056, blk: 4102 chip [3]
1 NAND detect Bad block at 200c00000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,184, blk: 4103 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,184, blk: 4103 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,184, blk: 4103 chip [3]
1 NAND detect Bad block at 200e00000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,312, blk: 4104 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,312, blk: 4104 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,312, blk: 4104 chip [3]
1 NAND detect Bad block at 201 million
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,440, blk: 4105 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,440, blk: 4105 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,440, blk: 4105 chip [3]
1 NAND detect Bad block at 201 200 000
0x000201400000-0x000201c00000: "mtd3"
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,568, blk: 4106 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,568, blk: 4106 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,568, blk: 4106 chip [3]
1 NAND detect Bad block at 201 400 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,696, blk: 4107 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,696, blk: 4107 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,696, blk: 4107 chip [3]
1 NAND detect Bad block at 201 600 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,824, blk: 4108 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,824, blk: 4108 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525,824, blk: 4108 chip [3]
1 NAND detect Bad block at 201 800 000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525952, blk: 4109 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525952, blk: 4109 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 525952, blk: 4109 chip [3]
1 NAND detect Bad block at 201a00000
0x000201c00000-0x000202400000: "mtd4"
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,080, blk: 4110 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,080, blk: 4110 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,080, blk: 4110 chip [3]
1 NAND detect Bad block at 201c00000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,208, blk: 4111 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,208, blk: 4111 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,208, blk: 4111 chip [3]
1 NAND detect Bad block at 201e00000
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,336, blk: 4112 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,336, blk: 4112 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,336, blk: 4112 chip [3]
1 NAND detect Bad block at 202 million
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,464, blk: 4113 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,464, blk: 4113 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 526,464, blk: 4113 chip [3]
1 NAND detect Bad block at 202 200 000
0x000202400000-0x000222400000: "mtd5"
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 559232, blk: 4369 chip [1]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 559232, blk: 4369 chip [2]
######## aml_nand_read_page_hwecc 2956 read ecc failed here at at page: 559232, blk: 4369 chip [3]
1 NAND detect Bad block at 222 200 000
nandnormal initialized ok
MMC: SDIO Port B: 0
*** Warning - readenv () failed, using default environment

Writing to Nand ... 0x1200000
Successful!
In: serial
Out: serial
Err: serial
aml_i2c_init
register usb cfg [0] = 9fe8e79c
register usb cfg [2] = 9fe8e79c
LCD Initialize:

Init LCD type: LVDS.
lcd frame rate = 598/10.
video pl1 clk = 0
video pll2 clk = 77
cts_enct clk = 0
cts_encl clk = 77
lvds fifo clk = 77

Init LCD type: LVDS.
lcd frame rate = 598/10.
video pl1 clk = 0
video pll2 clk = 77
cts_enct clk = 0
cts_encl clk = 77
lvds fifo clk = 77
LCD: 1024x768 16bbp
init suspend firmware done. (Ret: 0)
nand - NAND sub-system

Usage:
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off | partition size
nand write - addr off | partition size
read / write 'size' bytes starting at offset 'off'
to / from memory address 'addr', skipping bad blocks.
nand erase [clean | whole] [off size] - erase 'size' bytes from
offset 'off' (entire device if not specified)
nand bad - show bad blocks
nand dump [.oob] off - dump page
nand scrub_detect - detect bad blk again
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off [...] - mark bad block (s) at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
nand rom_protect on / off
nand wr_rd_cmp src dst off | partition size
nand rom_write addr off | partition size
nand factory_info addr block_offset block_count part | all

wrong pack img!
Check all regulator
Use constant PWM for DC-DC2 & DC-DC3. But the register is 0xe0 before
Set DCDC2 (DDR3_1.5V) to 1500mV (0x20). But the register is 0x22 before
reboot_mode = usb_burning
Enter USB burning.


Post has been editedsoneks - 06.03.19, 22:29



Rep: (27)
Maybe someone knows where to buy the trail to the matrix of the board? With his experiments broke trail. Well, it removable and bad that you know where the figure is to look for and what number :-(



Rep: (9)
soneks @ 07.03.19, 12:37*
Maybe someone knows where to buy the trail to the matrix of the board? With his experiments broke trail. Well, it removable and bad that you know where the figure is to look for and what number

And in the loop there are no inscriptions? If not, you can search for twins of this device, if there of course. And seek to spare him.

Post has been editedmrALmazini - 11.03.19, 08:35



Rep: (27)
What's the point? Still need nand-memory no contact noses I strongly damaged. Follow desoldering - guaranteed by opening the remaining snout. I've lowered my hands.



Rep: (0)
Help me please. There are technical things work of art, which is divided touchscreen (with a display like everything is normal). In the online store glass is not available, in which case it will not work from their home? The topic did not find the answer, maybe bad looking ..



Rep: (0)
freespy @ 14.11.16, 15:24*
So, the same situation, only the logo and hanging (holding 3 hours). Immediately used kuztom method turned out everything as he described, worked fine without any showdown device.

kuztom,
I had a problem with the machine, do not ship on BLISS inscriptions. What I've done:
of this manual! Create a bootable USB flash drive, please do it here in the standard mode (hold Vol + and Power to the unit is turned off) and the screen was black, but it is clear that the backlight is on. After a while there was a robot with a boot band, then he crashes. It worked !!!


Post edited freespy - 16.11.16, 21:38


I just do not understand how to select the Fail bin ??? it does not see the program in the folder and offers only img


Full version    

Help     rules

Time is now: 14/10/19, 7:11