I have replaced new empty eMMC flash memory in change of previous dead one.
Reason: bootloop, google logo, no boot, no fastboot (no LED blinking), device detected only in Intel DNX fastboot (MOOREFIELD):
Code:
New USB device found, idVendor=8086, idProduct=0a2c, bcdDevice= 0.a0
New USB device strings: Mfr=2, Product=1, SerialNumber=3
Product: MOOREFIELD
Manufacturer: INTEL
Instead of android fastboot mode:
Code:
New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice=ff.ff
New USB device strings: Mfr=2, Product=3, SerialNumber=4
Product: fugu
Manufacturer: Android
xFSTK Downloader (used files from ZenFone) doesn't work. Player disconnecting during flashing.
Actually I need partitions dumps or full RAW dump.
Code:
Setting interface to EasyJtag2/E-Socket
Setting bus width to 8 Bit
Setting frequence to 42 MHz
EMMC Device Information :
EMMC CID: 110100303038474530006625C95B71F1
EMMC CSD: D05E00320F5903FFFFFFFFEF924000D3
EMMC Manufacture : TOSHIBA , EMMC NAME: 008GE0 , HEX: 303038474530 , S/N: 6625C95B , rev. 0x00
EMMC Manufacture ID: 0x11 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 7/2014
EMMC ROM 1 (Main User Data) Capacity: 7456 MB (0001D2000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000) Counter: 716 , Response: Not Clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
Boot configuration [PARTITION_CONFIG]: 0x00 , Boot from: no boot
Boot Bus Config: 0x00 , width 1bit
H/W Reset Function [RST_N_FUNCTION]: 0x00, RST_n signal is temporarily disabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: 008GE0_6625C95B_20191117_171608.extcsd
EMMC Init completed.
Warning: Health report is very BAD
Device Life Time Estimation (MLC) [269]: 0x00 Not defined
Device Life Time Estimation (SLC) [268]: 0x0B Exceeded its maximum estimated device life time
Pre EOL information [267]: 0x01 Normal
Scanning soft partitions
GPT header is found and is valid
Partition: boot, [000000005000 - 000001005000], size: 000001000000 (16,0 MB)
Partition: recovery, [000001005000 - 000002005000], size: 000001000000 (16,0 MB)
Partition: fastboot, [000002005000 - 000003005000], size: 000001000000 (16,0 MB)
Partition: factory, [000003005000 - 000003605000], size: 000000600000 (6,00 MB)
Partition: splashscreen, [000003605000 - 000003A05000], size: 000000400000 (4,00 MB)
Partition: panic, [000003A05000 - 000003E05000], size: 000000400000 (4,00 MB)
Partition: misc, [000003E05000 - 000003F05000], size: 000000100000 (1,00 MB)
Partition: temp, [000003F05000 - 000004F05000], size: 000001000000 (16,0 MB)
Partition: cache, [000004F05000 - 000014F05000], size: 000010000000 (256 MB)
Partition: system, [000014F05000 - 000054F05000], size: 000040000000 (1,00 GB)
Partition: userdata, [000054F05000 - 0001D1FFBE00], size: 00017D0F6E00 (5,95 GB)
GPT header successfully parsed
Dump status:
ROM1 - failed !
ROM2/3 (bootloader = ifwi - 164 bytes ?) - ok
RPMB - ok
Partially I can get boot, recovery, fastboot (droidboot), splashscreen, system from official google firmwares.
But more important is factory partition.
Anyway it would be nice to have full RAW dump.
Thanks.
Related
It seems that there is about 100 MB Missing... I just guess is EXTROM
It could very easy to test that - different EXTROM but same Flash.bin.
The total free ROM space unchanged, even your EXTROM just used a few MB
If the EXTROM could be used, then it could be great help for cooking
The files may relate to FLASH.Header and partition.mbn. could anyone have a good try?
But...
pdocread.exe -l
411.25M (0x19b40000) DSK1:
| 1.87M (0x1df000) Part00 BOOT SECTION image
| 5.00M (0x500000) Part01 XIP RAM Image
| 84.25M (0x5440000) Part02 IMGFS file system
| 320.13M (0x14020000) Part03 legit DOS partition
handle#1 ef638fc6 320.13M (0x14020000)
handle#2 ef6adea6 84.25M (0x5440000)
handle#3 2f6ade82 5.00M (0x500000)
handle#4 4f6ade3a 1.87M (0x1df000)
Total is just 411.25, about 100MB (0x064C0000) seems missing....
For Part02, I could know is imgfs, and Part00 seems EXTROM, but where is disappear 100M?
partition table:
Code:
Partition-Info :
------------------
MIBIB
---------------------------------------------------------
Page: 0x6
Size: 0x4
Address: 0x000C0000 - 0x00140000
Block: 0x00000180 - 0x00000280
Flash: 0xFEFFFFFF
SIM_SECURE
---------------------------------------------------------
Page: 0x4
Size: 0x2
Address: 0x00080000 - 0x000C0000
Block: 0x00000100 - 0x00000180
Flash: 0xFEFFFFFF
FSBL
---------------------------------------------------------
Page: 0x180
Size: 0x1E
Address: 0x03000000 - 0x033C0000
Block: 0x00006000 - 0x00006780
Flash: 0xFFFFFFFF
OSBL
---------------------------------------------------------
Page: 0x180
Size: 0x1E
Address: 0x03000000 - 0x033C0000
Block: 0x00006000 - 0x00006780
Flash: 0xFFFFFFFF
AMSS
---------------------------------------------------------
Page: 0x4650
Size: 0x708
Address: 0x8CA00000 - 0x9AB00000
Block: 0x00119400 - 0x00135600
Flash: 0xFFFFFFFF
EFS2
---------------------------------------------------------
Page: 0x1F40
Size: 0xC8
Address: 0x3E800000 - 0x40100000
Block: 0x0007D000 - 0x00080200
Flash: 0xFFFFFF01
DSP1
---------------------------------------------------------
Page: 0x3E80
Size: 0x258
Address: 0x7D000000 - 0x81B00000
Block: 0x000FA000 - 0x00103600
Flash: 0xFFFFFFFF
FOTA
---------------------------------------------------------
Page: 0x80
Size: 0x64
Address: 0x01000000 - 0x01C80000
Block: 0x00002000 - 0x00003900
Flash: 0xFFFFFFFF
EXTROM
---------------------------------------------------------
Page: 0xC350
Size: 0x7D0
Address: 0x86A00000 - 0x96400000
Block: 0x0010D400 - 0x0012C800
Flash: 0xFFFFFFFF
APPSBL
---------------------------------------------------------
Page: 0x300
Size: 0x32
Address: 0x06000000 - 0x06640000
Block: 0x0000C000 - 0x0000CC80
Flash: 0xFFFFFFFF
APPS
---------------------------------------------------------
Page: 0x80
Size: 0xC
Address: 0x01000000 - 0x01180000
Block: 0x00002000 - 0x00002300
Flash: 0xFFFFFFFF
EFS2APPS
---------------------------------------------------------
Page: 0xFFFFFFFF
Size: 0xFFFF
Address: 0xFFFE0000 - 0xFFFC0000
Block: 0x001FFFC0 - 0x001FFF80
Flash: 0xFFFF02FF
good investigation ! I hope you can find a Way to reduce the allocated space, sadly I can't help you with this...keep the research !
Arto said:
good investigation ! I hope you can find a Way to reduce the allocated space, sadly I can't help you with this...keep the research !
Click to expand...
Click to collapse
Thank you also
The difficult problem is that, I'm not much understanding NAND Flash...
But, it seems that, after flashing ROM with new partition.mbn, the size of ExtRom could be changed.
At this moment, I'm not sure that the Hex files should be also changed or not ...
Code:
EXTROM
---------------------------------------------------------
[COLOR="Red"] Page: 0xC350
Size: 0x7D0[/COLOR]
Address: 0x86A00000 - 0x96400000
Block: 0x0010D400 - 0x0012C800
[COLOR="Red"] Flash: 0xFFFFFFFF[/COLOR]
Form Page (seems like format pagepool), the maximum ExtROM could be 50MB, that's the limit for a cook to modify ExtROM.
Of cause, if we could modify ExtROM size, then we could include more module in to Image
Moreover, including ExtROM, the boot system could used up to 93.674MB
my extrom take 7mb...so if the extrom allocated space can be changed it would be reallocated to application space? Qazer found a way to change page pool size, maybe it can help you on this !
edit, what is NAND flash?
Arto said:
my extrom take 7mb...so if the extrom allocated space can be changed it would be reallocated to application space? Qazer found a way to change page pool size, maybe it can help you on this !
edit, what is NAND flash?
Click to expand...
Click to collapse
After rearranged the partition table, it could be like this:
Code:
offset size
SIM_SECURE 0x4 0x2
MIBIB 0x6 0x4
FOTA 0x80 0x64
APPS 0x80 0xC
FSBL 0x180 0x1E
OSBL 0x180 0x1E
APPSBL 0x300 0x32
EFS2 0x1F40 0xC8
DSP1 0x3E80 0x258
AMSS 0x4650 0x708
EXTROM 0xC350 0x7D0
EFS2APPS 0xFFFFFFFF 0xFFFF
It could be much strange that some 'partitions' are overlapping!
Emmm, I forgot the order flashing these programs (.mbn), however, the ExtROM could be the last one to flash in the phone...
If somebody could tell me the order, then it could be much clear the process
Seems changed size could be OK, but I just wonder that what about ImageFS...
BTW, for term 'NAND flash', just wikipedia it
the best thing we can do is to reallocate this space in a virtual ram driver, and dont use the extrom space anymore. I noticed that the extrom files (cabs,tsk..) are in the windows folder of the device when you explore the windows folder.
So Is there a virtual ram driver or is there a way to do that, we don't need space, we need ram alternative.
anyway, don't know if it is possible to do such a thing on winmo devices...
( a kind of swap space....)
ocman said:
the best thing we can do is to reallocate this space in a virtual ram driver, and dont use the extrom space anymore. I noticed that the extrom files (cabs,tsk..) are in the windows folder of the device when you explore the windows folder.
So Is there a virtual ram driver or is there a way to do that, we don't need space, we need ram alternative.
anyway, don't know if it is possible to do such a thing on winmo devices...
( a kind of swap space....)
Click to expand...
Click to collapse
I think we should hardmod to add more RAM instead of using NAND flash, to avoid damaging it faster
Emmm, at this time I could not be sooooooo brave to flash my only phone
I just only change 0x7D0 (D0 07 00 00) to 0x3E8 (E8 03 00 00)....
If I try to flash with new partition.mbn,the phone turn into FTM Mode
But I just put partition.mbn, extrom.bin and two hex files only to the flash tool...
It sounds like I should put all files in that...
Then, finally these two hex files ENPRG8650.hex and NPRG8650.hex should be also modified.
Hi i was looking for help on my iconia tab a500 everywhere, i've tried everything and don't get it to work, i try afterota, the blackthund3r, the timmy's help i try flashin bootloader, recovery, with babsector i ran the a502A Bat and give me this:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x7AAB1E00 0xB8CCE601 0x57850203 0x59042103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c6243416121d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Presione una tecla para continuar . . .
then I ran the a501B and get this at the end
Formatting partition 2 BTC please wait.. FAILED¿
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7)
message: nverror:0x42008 (0x6042008) flags: 0
Presiones una tecla para continuar...
If someone can help me I appreciate it very much.
Thank you
I have reached the exact same point...for what I could found the issue is the internal SD damaged... only a MB change would be the solution...
sucks
My Odroid won't boot to CWM recovery with CM10.1 installed on the emmc.
I extracted the three files from here: http://cyanogenmod.org/rc/odroidu2-recovery.zip and placed them on the root of the emmc but every time I boot up I get this
Code:
U-Boot 2010.12-svn (Jan 28 2013 - 14:10:19) for Exynox4412
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
APLL = 1000MHz, MPLL = 880MHz
DRAM: 2047 MiB
PMIC VERSION : 0x00, CHIP REV : 2
TrustZone Enabled BSP
BL1 version: 20121128
Checking Boot Mode ... EMMC4.41
REVISION: 2.0
Manufacturer TOSHIBA [ 15028MB ]
NAME: S5P_MSHC4
MMC Device 0: 15028 MB
MMC Device 1: 0 MB
MMC Device 2 not found
*** Warning - using default environment
ModeKey Check... run normal_boot
Net: No ethernet found.
Hit any key to stop autoboot: 0
NAME: S5P_MSHC4
NAME: S5P_MSHC4
>>> Load Boot Script from mmc 0:1 <<<
NAME: S5P_MSHC4
Partition1: Start Address(0x520000), Size(0x181a000)
reading boot.scr
Warning : Reads a file that is smaller than the cluster size.
623 bytes read
## Executing script at 40008000
Wrong image format for "source" command
Exynos4412 #
how can i get past this?
deleted
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
]
Enter your SBK:0x9180C201 0x7B22F106 0x7B4D1504 0x62512103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x04280003433fd217
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Sorry chap u got faulty memory chip error. Can try acer support, someone else had tab out of warranty last week. Acer repairing for free. Worth a shot!
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Sorry chap u got faulty memory chip error. Can try acer support, someone else had tab out of warranty last week. Acer repairing for free. Worth a shot!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Could you give a link or something?
In germany there is a warranty of 24 months if the producer have given a faulty device.
But I've only time until tommorow xD, so some stuff would help me to get a functionally device .
Fiedler5895 said:
Could you give a link or something?
In germany there is a warranty of 24 months if the producer have given a faulty device.
But I've only time until tommorow xD, so some stuff would help me to get a functionally device .
Click to expand...
Click to collapse
As far as I know you just go to the acer website. Choose "support" from the menu. I've never had to do it myself, so can't help much. The other thing is that it doesn't matter if your tab is out of warranty or not, acer seems to honour it anyway, according to the last few users who've done this.
babsector download no longer available Russian site
Please help can somebody provide me with the babsector.rar (Needed for my Acer Iconia a500) seem like Russian site is no longer available, please somebody help me. Thanks in advance!:cyclops:
Root guide in my Sig 2nd post
Sent from my HTC_PN071 using Tapatalk
BCT create error... Help!!!
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Same problem
Hello, I have the same problem. can anyone help?
[email protected] said:
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Click to expand...
Click to collapse
TRY THIS!!!
Worked for me. try this
http://forum.xda-developers.com/showthread.php?t=2617196
[email protected] said:
Hi, All!
First of all sorry for my English...
I have a problem with my Acer Iconia Tab A501.
History:
- once upon a time, when i turn on my tablet, i have a logo ACER...and booting not continued
- i had not SD card and decide recover my A501 from my PC.
- i look at tons of posts about this, and i use EUUS method (EUUs_SBK_Acer_A501_0.017.01_PA_ATT)
- i tried to run this EUUS many times, but obtain Error when tablet turn on from APX mode to "Entering Acer Downloader Mode"
- i tried many different FastUnbric & SlowUnbrick packages - nothing happened. (stuck on creating BCT, or lower formatting BCT)
- one of the days i use EUUS again? and it works! And i have HC 3.0.1
- then i put on SD card image.dat with HC 3.2.1 - OK!
- then i take upgrades from ACER with WiFi - OK!
- then i take upgrade ti ICS 4.0.3 from ACER with WiFi - download success, but when tab rebooted - logo ACER...and booting not continued
- from SD card put 3.2.1 over 4.0.3 - OK! AND I HAVE FUN ABOUT MONTH!!!
- but i want 4.0.3!!!
- insalling this version have one result - logo ACER (installing wia WiFi, or from SD card)
- ok many manipulation with others unbrickers (icluding BabSector) have one result - my Tab Bricked in APX mode and turned on with NVFLASH to "Entering Acer Downloader Mode".
Lower "screenshot" of BabSector, i have this now!
I don't think the eMMC chip is dead - this error was early, but 3.2.1 worked fine about the month until i decided upgrade it to ICS 4.0.3
CPUID and SBK - correct!!!
Here is EROOR:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Enter your SBK:0xC3A11E00 0x9743C501 0xD7092103 0x302C2103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061c7428041d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Для продолжения нажмите любую клавишу . . .
Thanks to All...
Serg.
Click to expand...
Click to collapse
TechShui said:
****************************************************************
...command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Click to expand...
Click to collapse
Sound like a EMMC/ROM problem...Just send it to RMA if you could.
But what if it's out of warranty?
I took out the Mother Board to a local electronics repairman, he blew heat gun over the sandiskNAND memory chip. I put it back together and turned on. To my surprise it worked.
You can find a thread link in my post above for further help.
androidvillage said:
Sound like a EMMC/ROM problem...Just send it to RMA if you could.
Click to expand...
Click to collapse
farhanalisyed said:
But what if it's out of warranty?
I took out the Mother Board to a local electronics repairman, he blew heat gun over the sandiskNAND memory chip. I put it back together and turned on. To my surprise it worked.
You can find a thread link in my post above for further help.
Click to expand...
Click to collapse
Pretty much all 500 and 501 tablets are out of warranty. I believe maybe some few places may have them new, and sell them. But I wouldnt buy one. (hence the RMA post). But technically, if you buy it, it starts the warranty, so indeed you should be able to RMA the purchase.
HI, I have been working on the PB Liberty Tab G100 for over a week.. I just want it back to stock.. no custom boot loaders or roms etc.. just so they can use it..
the story so far... I was asked to repair a PB liberty tab that was supposedly just freezing.. I think it had a custom boot V8..
Recovery was not working just getting the android dube with red triangle.. so installed thor recovery via fastboot..
tried the update method.. did not work.. tried everything.. but was having an issue with the wiping and formating...
I managed to finally get the cpuid by using a 64 bit version of ubuntu and have managed to get the SBK.. tried the recommended flashs A500 apx etc
but now i'm stuck in apx mode.. when i try to use V8-UNL-ICS-HC-bootloader-MULTI-cwm method I get the failed to format..
info found from this thread http://forum.xda-developers.com/showthread.php?t=1751978
**********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .
Flashing HC-Bootloader...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
I think I have an internal storage issue, or bad sectors.. or I am just not using the right apx.. and help would be awesome..
i have read so many forum sections and pieced together which has finally got me into the device.. but now I seem to have hit a brick wall..
so help i have tried to track down the bad sectors software to run in apx mode but cant seem to find it al all the link i have found are dead..
quick update
**********************************************************
* Make your choise: *
*(1) ICS bootloader V8 with TWRP-2.1.3-ICS cwm(touch cwm)*
*(2) ICS bootloader V8 with PubRecovery-v0.2 (BareBones) *
*(3) ICS bootloader V8 with Thor-1.7cwm (touch cwm) *
*(4) ICS bootloader V8 with Thor-1.7.3 NEW cwm(touch cwm)*
* with its compatible recoveries. *
**********************************************************
(1 2 3 4):4
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c62484260****
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x60420
08) flags: 0
*****************************************************************
* Press any key when your A500/501/G100W is in bootloader mode *
*****************************************************************
Press any key to continue . . .
UPDATE
I have tried running Badsector but all i get it this.. I have checked the correct drivers are installed.. but just seem to be stuck..
I am thinking my internal storage is fried..
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x****1E00 0x0**51700 0xEB*****2 0x682*****
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624842601397
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .