Info about A500 ICS bootloader (and only ICS Bootloader, HC bootloader files don't have that - it was partly discussed in leak thread):
What we know so far:
- ICS bootloader has fastboot
- ICS bootloader is built as unlockable and relockable; however this right now doesn't work on A500/A100, it's confirmed to work on A200
Currently I don't know if the "unlock process" can be done "manually" - that is whether it's not forcibly disabled or just "not yet implemented" (It's just a leak, so keep that in mind). Lock command looks like to be fully in effect. On the other hand, old bootloader and itsmagic will do just fine, at least for now (for A500/A501).
Fastboot has these variables:
Code:
version-bootloader
version-baseband
version
secure
serialno
mid
product
(serialno will probably be your UID)
Fastboot OEM commands are:
Code:
fastboot oem debug on
fastboot oem debug off
fastboot oem lock
fastboot oem unlock
If you try to relock locked device, you'll get:
Code:
Fastboot: Device is already locked! Abort ...
Unlocked BL also supports these commands:
Code:
flash
boot
download
erase
(normal FB commands: so if you screw up your boot / recovery image, you can quite easily restore it).
PATCHED BOOTLOADER - !!!TO BE FLASHED WITH NVFLASH!!!
- overriden GetUnlockMode to return 1 (=Unlocked)
- overriden SetUnlockMode to return 0 (=Error)
- when booting to recovery it won't add the update command
- fastboot oem lock / fastboot oem unlock commands removed
DL: http://forum.xda-developers.com/attachment.php?attachmentid=919618&d=1330199867
In V2 there is additionally
- says "Custom Mode" instead of "Unlock Mode"
- fastboot variable secure: no
- boot command works (for some reason tight to secure variable)
- booting recovery manually with VOL_Down is like booting it via "adb reboot recovery": i.e won't erase cache etc.
DL: http://forum.xda-developers.com/attachment.php?attachmentid=922059&d=1330348851
Also fastboot is buggy (sometimes failed flashing recovery), but flashing boot.img works for instance. And yeah you won't have to use itsmagic for this one. Also, I flashed the stock ICS leak, and wasn't testing how it goes with HC.
CWM for ICS bootloader: http://forum.xda-developers.com/showpost.php?p=22978118&postcount=49
CLASSIC STUFF - YOU DO EVERYTHING AT YOUR OWN RISK!!!
This guy seems to have been around a very long time . I am not a DEV but this might be worth someone to take a look at . Here is the Link to his post.. He claims he if i read right repacked ics rom . guessing self signed and flashed with FAST BOOT.
or im lame and misread
http://www.acertabletforum.com/forum/acer-a200-general-discussions/3649-how-unlock-boot-loader.html
check the link
Hope this helps you.
erica_renee said:
This guy seems to have been around a very long time . I am not a DEV but this might be worth someone to take a look at . Here is the Link to his post.. He claims he if i read right repacked ics rom . guessing self signed and flashed with FAST BOOT.
or im lame and misread
http://www.acertabletforum.com/forum/acer-a200-general-discussions/3649-how-unlock-boot-loader.html
check the link
Hope this helps you.
Click to expand...
Click to collapse
Makes sense. I had to use fastboot to unlock the bootloader, flash recovery, and then flash a new system/boot/data img to my Galaxy Nexus for the first time. It seemed the unlock process wiped the operating system, so it was required to push the files from my computer to the phone manually in order to restore it.
Yeah, fastboot erases literally everything for security reasons IIRC.
Well reading that post on the other forum, it seems that they get the option to unlock like on the Google nexus devices, although it seems that screen doesn't appear on the a500 when trying this method.
Sent from my Desire HD using xda premium
heres a text file containing some more info. I ripped apart the bootloader update in a hex editor.
starts at 88640
Code:
AKBMSCLock switched
vendor/nvidia/tegra/prebuilt_t20/../core/system/fastboot/acer_funcs.cVOL_DOWN key pressed
VOL_UP key pressed
FastbootModeFOTAFactoryResetrecovery
--update_package=SDCARD:update.zip
Erasing Cache before SD update...
CACSD update cmd: %s
Error: Data not start yet!
whole-file signature verified against key %d
failed to verify whole-file signature
Error: Not enough buffer!!!
buffer & signature cannot be NULL!ANDROID!LNX%s: No boot image found!%s: Verify failed! Please redownload official image from Acer and try again!SOS%s: No recovery image found!Please flash official system.img and try againError: System.img is not official
Please flash official flexrom.img and try againError: flexrom.img is not official
%s: LockMode verified ok!
%s: LockMode verified failed
Magic value mismatch: %c%c%c%c%c%c%c%c
%s
Failed to setup warmboot args %x
Failed to set shmoo boot argument
Critical failure: Unable to start kernel.
Load OS now via JTAG backdoor....
Failed to initialize Aboot
Platform Pre Boot configuration...
Entering OS Download mode
LockUnlockFastboot: Device is now in %s mode
Bootloader Version %s (Unlock Mode)0.03.11-ICS
Bootloader version: %s
HW version 0x%x
NOYESIs Wifi Only? %s
EB2Unable to parse odmdata for wait input
Checking for android ota recovery
Erasing Userdata...
UDAErasing Cache...
Booting recovery kernel image
Recovery Verified!
Recovery verified failed ...(UnlockMode)Bootloader v%s%s: Starting Fastboot USB download protocol
No CAC partitions found
getvar:version-bootloaderOKAY%sversion-basebandOKAYversionOKAY0.4secureOKAYyesOKAYnoserialnoOKAYKal-El001midOKAY001productdownload:Fastboot: Not support the command in Lock modeDATA%08x
Insufficient memory
Staging partition size is not big enough
bootrebootRebooting the device ...continueflash:bootloaderrecoverysystemflexuserdataFastboot: Not support!No %s partition found
Not enough space in %s partitionFastboot: Official system image checked passed!
Fastboot: Official flex image checked passed!
Fastboot: Official system image checked failed!
Fastboot: Official flex image checked failed!
erase:StorMgr Formatting %s
Erasing %s
oem debug ondebug offlockFastboot: Device is already locked! Abort ...
Fastboot: Please use left key (VOL_DOWN) to choose, and use right key (VOL_UP) to select
Please wait ...Fastboot: Device locked!!!Please reboot the device to take affect!Fastboot: Failed to set lock modeFastboot: Cancelled by user or timeoutunlockFAIL(%08x)Failed to process command %s error(0x%x)
Boot Verified!
Boot verified failed ...Unrecoverable bootloader error (0x%08x).
vendor/nvidia/tegra/prebuilt_t20/../core/system/fastboot/main_acer.cmiscAPPcachestagingUSPbcttableBCTEBTubuntuUBNmbrMBRFLXUse scroll wheel or keyboard for movement and selection
Neither Scroll Wheel nor Keyboard are detected ...Booting OS
Checking for RCK.. press <Enter> in 5 sec to enter RCK
Press <Enter> to select, Arrow key (Left, Right) for selection move
Key driver not found.. Booting OS
Checking for RCK.. press key <Menu> in 5 sec to enter RCK
Press <Menu> to select, Home(Left) and Back(Right) for selection move
Picasso2Picasso_MPicasso_EPicassoVangoghMayaChecking for RCK.. press any key in 5 sec to enter RCK
Press scroll wheel to select, Scroll for selection move
Scroll wheel not found.. Booting OS
Press <Wake> to select, Home(Left) and Back(Right) for selection move
Checking for RCK.. press key <Volume Down> in 5 sec to enter RCK
Press <Volume Down> to select, <Volume Up> for selection move
tegraid=%x.%x.%x.%x.%x.%s mem=%[email protected]%uM vmalloc=%uM androidboot.serialno=%08x%08x video=tegrafb console=ttyS0,115200n8 debug_uartport=lsport console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=%[email protected]%x tegra_fbmem=%[email protected]%x brand=acer target_product=%s a500_ww_gen1max_cpu_cur_ma=%d core_edp_mv=%d pmuboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x displayboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x power_supply=Adapter power_supply=Battery audio_codec=%s cameraboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x upnosmp usbroot=/dev/nfs ip=:::::usb%c:on rw netdevwait ethroot=/dev/nfs ip=:::::eth%c:on rw netdevwait sdroot=/dev/sd%c%c rw rootwait mmchdroot=/dev/mmchd%c%c%c rw rootwait mtdblockroot=/dev/mtdblock%c rw rootwait mmcblkroot=/dev/mmcblk%c%c%c rw rootwait Unrecognized root device: %s
root=/dev/sda1 rw rootwait tegraboot=nand tegraboot=nor tegraboot=emmc tegraboot=sdmmc mtdparts=tegra_nand:mtdparts=tegra_nor:%[email protected]%uK(%s),tegrapart=gpt_sector=%d Unable to query partition %s
%s:%x:%x:%x%cmodem_id=%d androidboot.carrier=wifi-only bootloader_ver=%s gpt %s: Fail set unlock mode!
%s: Successfully %s the device!
%s: Error occured while %s the device ...
%s: Error e = 0x%x
Do not support in ACER T20 Projects
MSM-RADIO-UPDATE
Unsupported binary in blob
Start Updating %s
failed-update-%s
End Updating %s
failed-updateboot-recoverySignature length wrong!!!! %d
data length wrong!!!! %d
Clearing useless bytes ...
Not legal!!!!!!! abort
Warning: The blob package is not official ~ Abort!
blob update failed
vendor/nvidia/tegra/prebuilt_t20/../core/system/nvaboot/nvaboot.cPassedFailedClearSBKTest: %s
LockSSKTest: SSK = Zero
LockSSKTest: LockSSK %s
Jumping to kernel at:%d ms
EFI PARTFastboot: Unlock mode, Clear SSK!!!
SetPartitionToVerify failed. NvError %u NvStatus %u
GetSecondaryBootDevice failed. NvError %u NvStatus %u
LoadPartitionTable failed. NvError %u NvStatus %u
AllocateState failed. NvError %u NvStatus %u
nverror:0x%x (0x%x)
GetBct failed. NvError %u NvStatus %u
DownloadBct failed. NvError %u NvStatus %u
SetBlHash failed. NvError %u NvStatus %u
UpdateBct failed. NvError %u NvStatus %u
SetDevice failed. NvError %u NvStatus %u
StartPartitionConfiguration failed. NvError %u NvStatus %u
EndPartitionConfiguration failed. NvError %u NvStatus %u
FormatPartition failed. NvError %u NvStatus %u
Start Downloading %s
UpdateBlInfo failed. NvError %u NvStatus %u
End Downloading %s
QueryPartition failed. NvError %u NvStatus %u
CreatePartition failed. NvError %u NvStatus %u
ReadPartition failed. NvError %u NvStatus %u
RawReadPartition failed. NvError %u NvStatus %u
RawWritePartition failed. NvError %u NvStatus %u
SetBootPartition failed. NvError %u NvStatus %u
ReadPartitionTable failed. NvError %u NvStatus %u
DeleteAll failed. NvError %u NvStatus %u
Obliterate failed. NvError %u NvStatus %u
OdmOptions failed. NvError %u NvStatus %u
Error in memory allocation
FuelGaugeFwUpgrade failed. NvError %u NvStatus %u
sdram validation can not be done at bootloader level
OdmCommand failed. NvError %u NvStatus %u
Sync failed. NvError %u NvStatus %u
VerifySignature failed. NvError %u NvStatus %u
ReadVerifyData failed. NvError %u NvStatus %u
VerifyPartition failed. NvError %u NvStatus %u
SetTime failed. NvError %u NvStatus %u
DownloadPartition failed. NvError %u NvStatus %u
FormatAll failed. NvError %u NvStatus %u
LocatePartitionToVerify failed. NvError %u NvStatus %u
Error PT partition format sector start=%d, count=%d
Format partition %s PT%s: Error BCT handle!
%s: Version = %x
%s: Version = 0x%x
Bct read verify failed
Error Bct Verify: NO valid Bct found lost+foundNvDdkDispSetWindowSurface/ controller: %d window: %d count: %d
surface: 0
tiledpitchsurface width: %d height: %d Bpp: %d layout: %s
NvDdkDispSetMode/ controller: %d
width: %d height: %d bpp: %d refresh: %d frequency: %d flags: 0x%x
NvDdkDispSetMode/ null mode
NTSC/PAL1WIN3WIN_AC2WIN_A2WIN_Cdisplay %d isn't clocked
Error when writing data
Error on clock en!!! Set to Tx_only mode!!!
ByPassHdmiDll/sys/firmware/fuse/kfuse_rawlibnvodm_hdmiNvOdmDispHdmiI2cTransactionNvOdmDispHdmiI2cOpenNvOdmDispHdmiI2cCloseNvOdmDispHdcpIsRevokedKsvlibnvodm_tvoNvOdmDispTvoGetGlobNvOdmDispTvoReleaseGlobNo SmartDimmer activity has been recorded.
Constant Values:
SD_LUT = R_LUT G_LUT B_LUT
%d: 0x%02x 0x%02x 0x%02x
SD_BL_TF = PT_0 PT_1 PT_2 PT_3
%d: 0x%02x 0x%02x 0x%02x 0x%02x
Total SD3 activities count: %d
Entry(%d) Info:
SD_CONTROL = 0x%08X
SD_BL_CONTROL = 0x%08X
SD_CSC_COEFF = 0x%08X
SD_FLICKER_CONTROL = 0x%08X
SD_PIXEL_COUNT = 0x%08X
SD_BL_PARAMETERS = 0x%08X
SD_HW_K_VALUES = 0x%08x
SD_HISTOGRAM = BIN_0 BIN_1 BIN_2 BIN_3
Input Backlight Intensity = %d
Output Backlight Intensity = %d
PWM frequence = %4.2f, SD percentage = %4.2f
JEDEC
Calling simple log2 with value which is not power of 2
Failed Ddk Rd. Bad block
Failed Ddk Wr. Bad block
Failed Ddk Erase. Bad block
Failed Ddk Cpybk. Bad block
Failed Ddk unknown Operation. Bad block Error code=0x%x at chip=%d,block=%d
DDK_Ers:dev = %d, number of blks = %d
Chip: %d, Page = %d, blk = %d
NandRead Error: Number of Pages=%d < interleave count=%d
Ecc.Err pgoffset: %d, status: 0x%x
Ecc.Err in Tag pgoffset: %d, status: 0x%x
Chip: %d, Page = %d
-MAINTAG
DDK_Rd:dev = %d, %s + %s, number_of_pages = %d
DDK_Cpbk:Srcdev = %d, Dstdev = %d, number_of_pages = %d
SrcChip: %d, Page = %d, blk = %d
DstChip: %d, Page = %d, blk = %d
DDK_Write:device = %d, %s + %s, number_of_pages = %d
Factory Bad block: Chip%u Block=%u
Runtime Bad block: Chip%u Block=%u,RTB=0x%x
Scan for Region table blocks: Chip=%u, Block=%u Bad
Marking Runtime Bad block: Chip%u Block=%u
Block driver mark bad failed at Chip=%d, Block=%d
Erase Partition Error: failed to erase block chip=%d,blk=%d
Nand block driver: Write Error = 0x%x, PartId=%u, , Write: start=0x%x, sector count=0x%x
Nand block driver: Read Error = 0x%x, PartId=%u, Read: start=0x%x, sector count=0x%x
Possible forced region table load
Region Table copy at CurrBlockNum %u is probably corrupt
Device Bad block table:
{%u, %d},
Device has %d bad blocks
Error Nand block driver Load Region table call failed for part-id=%d, error code=%d
Global Nand Interleave count = %u
Error: NandUtilGetRegionEntry failed for part Id=%d
Partitions in region table: Id=%d
FTL open for partition=%d failed,code=%d
Nand Block dev open failed error 0x%x
Physical Rd/Wr on block error: req=%d,actual=%d
Bad block during Rd/Wr physical found at: Chip=%d, Block=%d
Block dev Physical Ioctl failed. Marking Chip=%d,Blk=%d
Unable to Erase Nand starting block 0x%x
Nand Block driver map logical2physical failed BlockNum=%d, DeviceNum=%d, CurrPhysBlk=%d
Error: Failed to map logical block=%d in entire Nand.
Error: As Region table is bigger than 1 sector size. Need to change Load Region table logic
Unable to Erase Nand chip=%d,block=%d
Partition %d - number of physical blocks = %d
Error: Unable to find requested blocks on Nand: req=%d,found=%d
Invalid value for PercentReserved = %d [should not exceed]%d, setting PercentReserved = %d
Insufficient space, cannot create partition
PartId %u: LB[%u %u] PB[%u %u] IL%u LS[%u %u]
Abs PartId %u: LB[%u %u] PB[%u %u] IL%u
Last Abs PartId %u: LS[%u %u] PartId %u: LB[%u %u] PB[%u %u] IL%u
Abs ** PartId %u: LS[%u %u]
Data mismatch in Copy of Region Table at BlockNum %d
Erase failed. Get Physical Sectors failed for logical start=%d,stop=%d
Erase Partition part-id=%d: Start=%d,End=%d NvDdkBlockDevIoctlType_DisableCacheNvDdkBlockDevIoctlType_EraseLogicalSectorsNvDdkBlockDevIoctlType_QueryFirstBootNvDdkBlockDevIoctlType_DefineSubRegionNvDdkBlockDevIoctlType_WriteVerifyModeSelectNvDdkBlockDevIoctlType_AllocatePartitionNvDdkBlockDevIoctlType_PartitionOperationNvDdkBlockDevIoctlType_ReadPhysicalSectorNvDdkBlockDevIoctlType_WritePhysicalSectorNvDdkBlockDevIoctlType_QueryPhysicalBlockStatusNvDdkBlockDevIoctlType_ErasePhysicalBlockNvDdkBlockDevIoctlType_LockRegionNvDdkBlockDevIoctlType_MapLogicalToPhysicalSectorNvDdkBlockDevIoctlType_FormatDeviceNvDdkBlockDevIoctlType_GetPartitionPhysicalSectorsNvDdkBlockDevIoctlType_IsGoodBlockNvDdkBlockDevIoctlType_UnprotectAllSectorsNvDdkBlockDevIoctlType_ProtectSectors
Nand Block dev ioctl opcode=%s error 0x%x
Save Region Table copy %u at CurrBlockNum %u
ftllite mark bad: chip=%d blk=%d
ftllite mark bad erase fail error=0x%x : chip=%d blk=%d
Ftl Lite bad block mark failed at Chip=%d, Block=%d
EraseAllBlocks: GetBlockInfo error=0x%x @ chip=%d,blk=%d
EraseAllBlocks: factory bad block @ chip=%d,blk=%d
EraseAllBlocks: runtime bad block @ chip=%d,blk=%d
Bad block in pba2lba ftlite map: chip=%d, blk=%d
Fatal error in pba2lba ftllite: line%d,lba=%d, startlba=%d chip=%d blk=%d
sparebuf[0]=0x%x, factory good=%d
Erasing block at chip=%d, blk=%d
continuing mapping erased blk
Erase partition error: start arg=%d, start log blk=%d
Erase partition error: count arg=%d, erase size=%d
Ftllite erase logical failed: blk start=%d,end=%d
Replace block=%d in chip=%d for read failure
New Block at: chip=%d,block=%d
Partition sequential read type: read failure at chip=%d, blk=%d
Error in FtlLitePrivCreatePba2LbaMapping: e=0x%x
Write called without PBA mapping info: chip=%d,lba=%d
Data area read verification failed in FTL Lite at Chip=%d,Blk=%d,Pg=%d
FTL Lite Read Verify error code=0x%x
Wr Error: 0x%x, Replace ftl lite bad block, PbaIndex=%d,Chip=%d,Block=%d,StartPg=%d,PgCount=%d
Rd verify error: 0x%x, Replace ftl lite bad block, PbaIndex=%d,Chip=%d,Block=%d,StartPg=%d,PgCount=%d
Replaced mapped block for lba=%d: old=%d new pba=%d
Factory bad block at chip=%d blk=%d:
Runtime bad block at chip=%d blk=%d:
Error: exhausted spare blocks toreplace lba=%d
finished remapping till index=%d out of total blocks=%d
used spare blocks=%d
Error: Unable to replace blocks with spare blocks for %d blocks
Error in FTL Lite write
RETURNING ERROR FROM NvNandWriteSector TL error=%u,Sector Start=0x%x,Count=0x%x
RETURNING ERROR FROM NvNandReadSector TL error=%u,Sector Start=0x%x,Count=0x%x
RETURNING ERROR FROM NvNandOpen
Error: trying cached read past page limits
512B Read: Page=%d, within page sector in page=%d, sector count=%d
Error: 512B buffer allocate failed earlier
Error: trying cached write past page limits
Error: failed to allocate buffer for 512B sector support
Alloc memory failed
TLvalidate FAIL1 sector offset=0x%x,count=0x%x,sectorsPerRow=%u
TLvalidate FAIL2, Interleave bank Pgs[ %d ]
TLvalidate FAIL3
TLvalidate FAIL4
TLvalidate FAIL5 page[0]=0x%x,Reqd rows=0x%x
TLEraseAll fail BtlGetPba: Chip=%d,Block=%d
GetBlock info failed: Chip=%d, Blk=%d
Marking Bad block failed forChip=%d Block=%d
Found Bad block Chip=%d Block=%d
Factory Bad: 0x%x, Run-time bad marker: 0x%x
Interleave2PhysicalPg fail1: illegal page
Interleave2PhysPg fail2: illegal device
Ddk Read error code=0x%x
In NandTLGetBlockInfo Error = 0x%x
NandTL_INVALID_ARGUMENT3
NandTL_INVALID_ARGUMENT4
NandTL_INVALID_ARGUMENT5
NandTL_INVALID_ARGUMENT6
Error: No free Blk, Region[%d]=%d
Strategy Handle Error failed in Wr Status:%d,
TL write error=%u,sector start=0x%x,count=0x%x
NandTL_INVALID_ARGUMENT1
NandTL_INVALID_ARGUMENT2
TlRead failed Status:%d,
TL read error=%u,sector start=0x%x,count=0x%x
Region=%d SD Erase start 512B-sector=%d,512B-sector-num=%d
LCM of %d and %d =%d
Part-id=%d size from %d sectors by %d sectors
SD Alloc Partid=%d, start sector=%d,num=%d NvDdkBlockDevIoctlType_ErasePartitionNvDdkBlockDevIoctlType_VerifyCriticalPartitionsUnknownIoctl
Inst=%d, SD ioctl %s failed: error code=0x%x SPIF ERROR: SpifOpen failed..
SPIF ERROR: Trying to read more than SPI flash device size..
SPIF ERROR: Trying to program more than SPI flash device size..
SPIF ERROR: Trying to erase more than chipsize NumberOfSectors[0x%x] TotalBlocks[0x%x]
SPIF ERROR: Trying to erase more than chipsize NumberOfBlocks[0x%x] TotalBlocks[0x%x]
SPIF ERROR: Illegal block driver Ioctl..
SPIF ERROR: SpifBlockDevIoctl failed error[0x%x]..
Inst=%d, SPI Flash ioctl %s failed: error code=0x%x Trying to close driver without open
SPIF ERROR: NvDdkSpifBlockDevInit failed error[0x%x]..
Error SD clear skip blocks - sector=%d
Skipping SD erase of prefix %d blocks from %d
Skipping SD erase of suffix %d blocks from %d
Hsmmc Erase start sector=%d,num=%d
Hsmmc Alloc Partid=%d, start sector=%d,num=%d
NvNandHandle: FtlStartLba=%d, FtlEndLba=%d FtlStartPba=%d, FtlEndPba=%d pBlocks[%d ] prevBlocks[]
TrackLba[%d]: lba=%d, %s
Misc start
NumOfBanksOnBoard = %d
NoOfILBanks = %d
PhysBlksPerBank = %d
ZonesPerBank = %d
PhysBlksPerZone = %d
PhysBlksPerLogicalBlock = %d
TotalLogicalBlocks = %d
TotEraseBlks = %d
NumOfBlksForTT = %d
PgsRegForTT = %d
TtPagesRequiredPerZone = %d
NumOfBlksForTAT = %d
BlksRequiredForTT = %d
PgsAlloctdForTT = %d
ExtraPagesForTTMgmt = %d
LastTTPageUsed = %d
CurrentTatLBInUse = %d
bsc4PgsPerBlk = %d
Misc end
TAT Handler start
tatBlocks[%d] bank = %d, block = %d
ttBlocks[%d] bank = %d, block = %d
tat Block bank = %d, block = %d
TtAllocBlk[%d] bank = %d, block = %d
lastUsedTTBlock bank = %d, block = %d
TAT Handler end
++++++++++++++++++
TT 32-bit entry format in dump :
=============
Region: b31-b30
BlockNotUsed: b29
BlockGood: b28
DataReserved: b27
SystemReserved: b26
TatReserved: b25
TtReserved: b24
PhysBlkNum: b23-b0
============
Dumping page %d
**SuperBlock %d
*0x%08X [%d] [SYS-RSVD]
*0x%08X [%d] [ ^^^ FREE BLK ] Region%d
*0x%08X [%d] [ USED BLK ] Region%d
*0x%08X [%d] [*** BAD BLK ***]
Total=%u,Free=%u,Bad=%u,Reserve Data=%u,System=%u,Tat=%u,Tt=%u,Illegal=%u,Region0=%u,Region1=%u,Region2=%u,Region3=%u
No free blocks Available- find out the reason, bank = %d
[Strategy] Erase Failed
Bad Block found at LBA %d
Marked blk bad bank = %d, block = %d Rev = %d lba = %d
TAT write failed page = %d, bank = %d, block = %d Rev = %d lba = %d WriteOnlyHeader = %d
NO FREE TAT BLOCKS AVAILABLE
writing to TAT blocks failedInvalid percent reserved value = %d, should not exceed%d, setting it to %d
[Nand_Strategy] Failed to mark PBAs BAD
**** Fail: Invalid Case ****
Not Expected to come here
NvError_NandNoFreeBlock1
Error: NandStrategyGetSectorPageToWrite InTracking case, No Page
Error: NandStrategyGetSectorPageToWrite GetPBA case, No Page
NvError_NandNoFreeBlock2
GetNewPBA failed Sts: 0x%x in GetSectorPage2Write #2
Error: NandStrategyGetSectorPageToWrite PBA assigned already case, No Page Crypto Engine Disabled, Returning IOCTL
AES DDK Unsupported IOCTL COMMAND
Invalidate-only cache maint not supported in NvOs
NVRM Initialized shmoo database
NVRM Got shmoo boot argument (at 0x%x)
ActiveIdleAutoHwRM power state before suspend: %s (%d)
Active Module: 0x%x*** Wakeup from LP0 ***
*** Wakeup from LP1 ***
*** Wakeup after Skipped LP0 ***
DTT: TMON initialization failed
DTT: T = %d, Range = %d (%d : %d)
DVFS set core at %dmV
Clock control balance failed for module %d, instance %d
ADJUSTED CLOCKS:
MC clock is set to %6d KHz
EMC clock is set to %6d KHz (DDR clock is at %6d KHz)
PLLX0 clock is set to %6d KHz
PLLC0 clock is set to %6d KHz
CPU clock is set to %6d KHz
System and AVP clock is set to %6d KHz
GraphicsHost clock is set to %6d KHz
3D clock is set to %6d KHz
2D clock is set to %6d KHz
Epp clock is set to %6d KHz
Mpe clock is set to %6d KHz
Vde clock is set to %6d KHz
NVRM CLOCKS: PLLX0: %d Khz
NVRM CLOCKS: PLLM0: %d Khz
NVRM CLOCKS: PLLC0: %d Khz
NVRM CLOCKS: PLLP0: %d Khz
NVRM CLOCKS: PLLA0: %d Khz
NVRM CLOCKS: CPU: %d Khz
NVRM CLOCKS: AVP: %d Khz
NVRM CLOCKS: System Bus: %d Khz
NVRM CLOCKS: Memory Controller: %d
NVRM CLOCKS: External Memory Controller: %d
ODM CPU freq request beyond SOC limit
GPUHandheldBrChipsCrushMCPCkVaioHandheld SOCSimulation Chip: 0x%x
FPGAQuickTurnEmulation (%s) Chip: 0x%x Netlist: 0x%x Patch: 0x%x
Chip Id: 0x%x (%s) Major: 0x%x Minor: 0x%x SKU: 0x%x
pNV_CFG_RMC_FILENV_CFG_CHIPLIBNV_CFG_CHIPLIB_ARGSSECURITY_VIOLATION DecErrAddress=0x%x SECURITY_VIOLATION DecErrStatus=0x%x EMEM DecErrAddress=0x%x EMEM DecErrStatus=0x%x GART DecErrAddress=0x%x GART DecErrStatus=0x%x DTT: Invalid Range = %d
Err in I2c transfer: Controller Status 0x%08x
AP20 Master I2c Isr got unwanted interrupt IntStatus 0x%08x
I2c slave rx buffer filled
%s(): Slave is not started
%s(): No space in Tx fifo
%s(): Slave is already started
I2cSlaveIsr(): Illegal transfer at this point
AP20 Slave I2c Isr got unwanted interrupt IntStatus 0x%08x
ARB EMEM Interrupt occurredSMMU DecErrAddress=0x%x SMMU DecErrStatus=0x%x QueryIface_CQueryIfacebogusOBS bus modID 0x%x index 0x%x = value 0x%xLLC Client %d Count: 0x%.8X, %u
LLC Client %d Clocks: 0x%.8X, %u
Client %.3d Count: 0x%.8X, %u
Total MC Clocks: 0x%.8X, %u
AXI DecErrAddress=0x%x AXI DecErrStatus=0x%x NvRmChannelSubmit failed (err = %d, SyncPointValue = %d)
Output FIFO does not refill, context read is stuck.Error> DSI Panel Initialization Failed
Error> DSI Panel Suspend Failed
ERROR: GPIO_PCF50626_I2cWrite8() failed.
Thanks gh123man.
Can you also try to extract the strings in the original bootloader that itsmagic works on for comparison?
namely the cmdline part which is this from the ics one
Code:
tegraid=%x.%x.%x.%x.%x.%s mem=%[email protected]%uM vmalloc=%uM androidboot.serialno=%08x%08x video=tegrafb console=ttyS0,115200n8 debug_uartport=lsport console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=%[email protected]%x tegra_fbmem=%[email protected]%x brand=acer target_product=%s a500_ww_gen1max_cpu_cur_ma=%d core_edp_mv=%d pmuboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x displayboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x power_supply=Adapter power_supply=Battery audio_codec=%s cameraboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x upnosmp usbroot=/dev/nfs ip=:::::usb%c:on rw netdevwait ethroot=/dev/nfs ip=:::::eth%c:on rw netdevwait sdroot=/dev/sd%c%c rw rootwait mmchdroot=/dev/mmchd%c%c%c rw rootwait mtdblockroot=/dev/mtdblock%c rw rootwait mmcblkroot=/dev/mmcblk%c%c%c rw rootwait Unrecognized root device: %s
root=/dev/sda1 rw rootwait tegraboot=nand tegraboot=nor tegraboot=emmc tegraboot=sdmmc mtdparts=tegra_nand:mtdparts=tegra_nor:%[email protected]%uK(%s),tegrapart=gpt_sector=%d Unable to query partition %s
%s:%x:%x:%x%cmodem_id=%d androidboot.carrier=wifi-only bootloader_ver=%s gpt %s: Fail
drellisdee said:
Thanks gh123man.
Can you also try to extract the strings in the original bootloader that itsmagic works on for comparison?
namely the cmdline part which is this from the ics one
Code:
tegraid=%x.%x.%x.%x.%x.%s mem=%[email protected]%uM vmalloc=%uM androidboot.serialno=%08x%08x video=tegrafb console=ttyS0,115200n8 debug_uartport=lsport console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=%[email protected]%x tegra_fbmem=%[email protected]%x brand=acer target_product=%s a500_ww_gen1max_cpu_cur_ma=%d core_edp_mv=%d pmuboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x displayboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x power_supply=Adapter power_supply=Battery audio_codec=%s cameraboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x upnosmp usbroot=/dev/nfs ip=:::::usb%c:on rw netdevwait ethroot=/dev/nfs ip=:::::eth%c:on rw netdevwait sdroot=/dev/sd%c%c rw rootwait mmchdroot=/dev/mmchd%c%c%c rw rootwait mtdblockroot=/dev/mtdblock%c rw rootwait mmcblkroot=/dev/mmcblk%c%c%c rw rootwait Unrecognized root device: %s
root=/dev/sda1 rw rootwait tegraboot=nand tegraboot=nor tegraboot=emmc tegraboot=sdmmc mtdparts=tegra_nand:mtdparts=tegra_nor:%[email protected]%uK(%s),tegrapart=gpt_sector=%d Unable to query partition %s
%s:%x:%x:%x%cmodem_id=%d androidboot.carrier=wifi-only bootloader_ver=%s gpt %s: Fail
Click to expand...
Click to collapse
sure ill have it up asap
Edit:
up. see next post
I have uploaded the archive with nvflash and some instructions on using it with A500. This is only intended for hardcore geeks who know how ARM boots. Be careful - while you can't really brick tegra2 (since it has a minimal usb-capable bootloader in the OTP area), you can screw up things and it will be quite hard to force the tablet to boot in some cases due to stupid security checks.
You can use this to download any bootloader/recovery/linux you want. That will help us with porting uboot. Someone may even write an automated tool for reflashing bootloaders and unbricking tablets..
http://www.mediafire.com/?pp97x9aahs58hzp
Let me just copy-paste the README from the archive here.
1. First, generate your sbk with http://vache-android.com/v1/index.php?site=sbk
2. Then, get a hold of mmcblk0 start sectors (at least 4KB) and copy it to mmcblk0_start
3. run the ./rip_bct.sh script and supply it with your SBK to rip BCT (boot config table. contains ram timings among other things)
4. run ./download.sh to connect nvflash to iconia (do it in APX mode). Note that you also need to supply your SBK here, but not as a long single number, but as it is displayed on the website
5. You can now play with nvflash - for example, read partitions, partition table and write your own flash_ic.cfg with partition layout
6. If you flash linux/recovery, make sure to update the magic values (like itsmagic does).
To do it, first download the 12th partition (AKB)
then, in the akb.bin, at address 0x84, replace 4 16-byte entries with the same pattern
"00 FB 30 94 99 01 4F 97 2E 4C 2B A5 18 6B DD 06"
ok, you need to patch the file once and can use it in further flashing. Just upload it to the device (like sign.sh does)
POTENTIAL PITFALLS. Listen up, I ain't gonna help you if you eff up here.
1. You must use BCT from your device. Otherwise, the bootloader will not boot.
You will still be able to use NVFLASH, but until you dump your own BCT and use it
with NVFLASH, the device will not be booting again
2. If you use the ./iconia_boot.bin that differs from the bootloader on your
device, the device will get stuck in the APX mode after a reboot. If you do it,
flash the new ./iconia_boot.bin to the device (to the partition 4).
The archive contains several bootloaders to play with - ./iconia_boot.bin is from
Honeycomb, iirc, ./ics_boot.bin is from ICS, obviously and ./tf101_boot.bin is
from transformer tf101
---------- Post added at 11:56 PM ---------- Previous post was at 11:42 PM ----------
Sorry for another off-topic post. If any of the devs is interested
Here is the uboot binary http://www.mediafire.com/?1zb2zc163tla8cj
And here is the linux kernel version 3.0 in the uboot image format http://www.mediafire.com/?j8fddkbm5fdsuu4
You can create vfat partition on the micro sd (/dev/mmcblk1p1) and copy the uImage there
The bootloader only supports booting from microsd now. The precompiled kernel tries to mount ubuntu rootfs on /dev/mmcblk1p2 and boot it.
drellisdee said:
Thanks gh123man.
Can you also try to extract the strings in the original bootloader that itsmagic works on for comparison?
namely the cmdline part which is this from the ics one
Code:
tegraid=%x.%x.%x.%x.%x.%s mem=%[email protected]%uM vmalloc=%uM androidboot.serialno=%08x%08x video=tegrafb console=ttyS0,115200n8 debug_uartport=lsport console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=%[email protected]%x tegra_fbmem=%[email protected]%x brand=acer target_product=%s a500_ww_gen1max_cpu_cur_ma=%d core_edp_mv=%d pmuboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x displayboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x power_supply=Adapter power_supply=Battery audio_codec=%s cameraboard=0x%04x:0x%04x:0x%02x:0x%02x:0x%02x upnosmp usbroot=/dev/nfs ip=:::::usb%c:on rw netdevwait ethroot=/dev/nfs ip=:::::eth%c:on rw netdevwait sdroot=/dev/sd%c%c rw rootwait mmchdroot=/dev/mmchd%c%c%c rw rootwait mtdblockroot=/dev/mtdblock%c rw rootwait mmcblkroot=/dev/mmcblk%c%c%c rw rootwait Unrecognized root device: %s
root=/dev/sda1 rw rootwait tegraboot=nand tegraboot=nor tegraboot=emmc tegraboot=sdmmc mtdparts=tegra_nand:mtdparts=tegra_nor:%[email protected]%uK(%s),tegrapart=gpt_sector=%d Unable to query partition %s
%s:%x:%x:%x%cmodem_id=%d androidboot.carrier=wifi-only bootloader_ver=%s gpt %s: Fail
Click to expand...
Click to collapse
here is the string section of the original bootloader. puled from the tar.gz thanks to sp3dev
Code:
UnknownChecking for RCK.. press any key in 5 sec
HarmonyTangoWhistlerVentana
Assert on %s:%d: %s
Assert on %s:%d
Signal %d raised!
vendor/nvidia/proprietary_src/prebuilt/../core/utils/nvos/aos/nvap/nvos_aos_gcc.cvendor/nvidia/proprietary_src/prebuilt/../core/utils/nvos/aos/nvap/nvos_aos_libc.c0123456789abcdefghijklmnopqrstuvwxyz**********Aos DebugSemiHosting Initialized*******
GetSkuId ************ * ************* ************* * * * * * * * * * * ** ** * * * * ** ** ************ * * * * *********** *********** ************ ************ * ************* ************ ************ * * * * * * * * * * * * * * * * * * ************** **************recovery
--update_package=SDCARD:update.zip
Erasing Cache before SD update...
CACMSCSD update cmd:%s
[%s] read gpio OK, a6=%d b5=%d a3=%d
[%s] read gpio FAIL, a6=%d b5=%d a3=%d
AKBANDROID!vendor/nvidia/proprietary_src/prebuilt/../core/system/fastboot/main.cMagic value mismatch: %c%c%c%c%c%c%c%c
%s
Failed to setup warmboot args %x
Failed to set shmoo boot argument
HarmonyVentanaCritical failure: Unable to start kernel.
Load OS now via JTAG backdoor....
TEGRA_PMC_BASE::PMC_CNTRL_0 = 0x%x
FIX TEGRA_PMC_BASE::PMC_CNTRL_0 = 0x%x
Entering Acer Download Mode
LNXFactoryResetErasing Userdata...
UDAErasing Cache...
FOTAVolume up pressed.
Volume down pressed.
SOSBooting recovery kernel image
Unrecoverable bootloader error (0x%08x).
miscrecoverybootsystemAPPcachestagingUSPuserdatabcttableBCTbootloaderEBTubuntuUBNmbrMBRUse scroll wheel or keyboard for movement and selection
Neither Scroll Wheel nor Keyboard are detected ...Booting OS
Checking for RCK.. press <Enter> in 5 sec to enter RCK
Press <Enter> to select, Arrow key (Left, Right) for selection move
Key driver not found.. Booting OS
Checking for RCK.. press key <Menu> in 5 sec to enter RCK
Press <Menu> to select, Home(Left) and Back(Right) for selection move
Checking for RCK.. press any key in 5 sec to enter RCK
Press scroll wheel to select, Scroll for selection move
Scroll wheel not found.. Booting OS
Press <Wake> to select, Home(Left) and Back(Right) for selection move
nvmem=%[email protected]%uM mem=%[email protected] vmalloc=%uM video=tegrafb console=ttyS0,115200n8 console=none usbcore.old_scheme_first=1 lp0_vec=%[email protected]%x upnosmp usbroot=/dev/nfs ip=:::::usb%c:on rw ethroot=/dev/nfs ip=:::::eth%c:on rw sdroot=/dev/sd%c%c rw rootdelay=15 mmchdroot=/dev/mmchd%c%c%c rw rootdelay=1 mtdblockroot=/dev/mtdblock%c rw rootdelay=15 mmcblkroot=/dev/mmcblk%c%c%c rw rootdelay=15 Unrecognized root device: %s
root=/dev/sda1 rw rootdelay=15 tegraboot=nand tegraboot=emmc tegraboot=sdmmc board_info=%x:%x:%x:%x:%x mtdparts=tegra_nand:%[email protected]%uK(%s),tegrapart=%s:%x:%x:%x%cUnable to query partition %s
gpt MSM-RADIO-UPDATEboot-recoveryupdatefailed-updateinvalid-updatefailed-update-%sokayWQ02824SATMA1278vendor/nvidia/proprietary_src/prebuilt/../core/system/nvaboot/nvaboot.cEFI PARTakb4820110311jeqNULLSecure boot: image %s checksum fail!nverror:0x%x (0x%x)
Error PT partition format sector start=%d, count=%d
Format partition %s PT
Bct read verify failed
Error Bct Verify: NO valid Bct found lost+foundNvDdkDispSetWindowSurface/ controller: %d window: %d count: %d
surface: 0
tiledpitchsurface width: %d height: %d Bpp: %d layout: %s
NvDdkDispSetMode/ controller: %d
width: %d height: %d bpp: %d refresh: %d frequency: %d flags: 0x%x
NvDdkDispSetMode/ null mode
NTSC/PAL1WIN3WIN_AC2WIN_A2WIN_Cdisplay %d isn't clocked
ByPassHdmiDlllibnvodm_hdmiNvOdmDispHdmiI2cTransactionNvOdmDispHdmiI2cOpenNvOdmDispHdmiI2cCloseNvOdmDispHdcpIsRevokedKsvlibnvodm_tvoNvOdmDispTvoGetGlobNvOdmDispTvoReleaseGlob====== Register Dump Start =========
Start command count=0x%x
NAND_COMMAND = 0x%8.8x
NAND_STATUS = 0x%8.8x
NAND_ISR = 0x%8.8x
NAND_IER = 0x%8.8x
NAND_CONFIG = 0x%8.8x
NAND_TIMING = 0x%8.8x
NAND_RESP = 0x%8.8x
NAND_TIMING2 = 0x%8.8x
NAND_CMD_REG1 = 0x%8.8x
NAND_CMD_REG2 = 0x%8.8x
NAND_ADDR_REG1 = 0x%8.8x
NAND_ADDR_REG2 = 0x%8.8x
NAND_DMA_MST_CTRL = 0x%8.8x
NAND_DMA_CFG.A = 0x%8.8x
NAND_DMA_CFG.B = 0x%8.8x
NAND_FIFO_CTRL = 0x%8.8x
NAND_DATA_BLOCK_PTR = 0x%8.8x
NAND_TAG_PTR = 0x%8.8x
NAND_ECC_PTR = 0x%8.8x
NAND_DEC_STATUS = 0x%8.8x
NAND_HWSTATUS_CMD = 0x%8.8x
NAND_HWSTATUS_MASK = 0x%8.8x
NAND_LL_CONFIG = 0x%8.8x
NAND_LL_PTR = 0x%8.8x
NAND_LL_STATUS = 0x%8.8x
====== Register Dump End ===========
Calling simple log2 with value which is not power of 2
Failed Ddk Rd. Bad block
Failed Ddk Wr. Bad block
Failed Ddk Erase. Bad block
Failed Ddk Cpybk. Bad block
Failed Ddk unknown Operation. Bad block Error code=0x%x at chip=%d,block=%d
NandRead Error: Number of Pages=%d < interleave count=%d
Ecc.Err pgoffset: %d, status: 0x%x
Ecc.Err in Tag pgoffset: %d, status: 0x%x
Chip: %d, Page = %d
-MAINTAG
DDK_Rd:dev = %d, %s + %s, number_of_pages = %d
Chip: %d, Page = %d, blk = %d
DDK_Cpbk:Srcdev = %d, Dstdev = %d, number_of_pages = %d
SrcChip: %d, Page = %d, blk = %d
DstChip: %d, Page = %d, blk = %d
DDK_Write:device = %d, %s + %s, number_of_pages = %d
DDK_Ers:dev = %d, number of blks = %d
Factory Bad block: Chip%u Block=%u
Runtime Bad block: Chip%u Block=%u,RTB=0x%x
Scan for Region table blocks: Chip=%u, Block=%u Bad
Marking Runtime Bad block: Chip%u Block=%u
Block driver mark bad failed at Chip=%d, Block=%d
Erase Partition Error: failed to erase block chip=%d,blk=%d
Nand block driver: Write Error = 0x%x, PartId=%u, , Write: start=0x%x, sector count=0x%x
Nand block driver: Read Error = 0x%x, PartId=%u, Read: start=0x%x, sector count=0x%x
Possible forced region table load
Region Table copy at CurrBlockNum %u is probably corrupt
Device Bad block table:
{%u, %d},
Device has %d bad blocks
Error Nand block driver Load Region table call failed for part-id=%d, error code=%d
Global Nand Interleave count = %u
Error: NandUtilGetRegionEntry failed for part Id=%d
Partitions in region table: Id=%d
FTL open for partition=%d failed,code=%d
Nand Block dev open failed error 0x%x
Physical Rd/Wr on block error: req=%d,actual=%d
Bad block during Rd/Wr physical found at: Chip=%d, Block=%d
Block dev Physical Ioctl failed. Marking Chip=%d,Blk=%d
Unable to Erase Nand starting block 0x%x
Nand Block driver map logical2physical failed BlockNum=%d, DeviceNum=%d, CurrPhysBlk=%d
Error: Failed to map logical block=%d in entire Nand.
Error: As Region table is bigger than 1 sector size. Need to change Load Region table logic
Unable to Erase Nand chip=%d,block=%d
Partition %d - number of physical blocks = %d
Chip%d Block=%d bad
Error: Unable to find requested blocks on Nand: req=%d,found=%d
Invalid value for PercentReserved = %d [should not exceed]%d, setting PercentReserved = %d
Insufficient space, cannot create partition
PartId %u: LB[%u %u] PB[%u %u] IL%u LS[%u %u]
Abs PartId %u: LB[%u %u] PB[%u %u] IL%u
Last Abs PartId %u: LS[%u %u] PartId %u: LB[%u %u] PB[%u %u] IL%u
Abs ** PartId %u: LS[%u %u]
Data mismatch in Copy of Region Table at BlockNum %d
Erase failed. Get Physical Sectors failed for logical start=%d,stop=%d
Erase Partition part-id=%d: Start=%d,End=%d NvDdkBlockDevIoctlType_DisableCacheNvDdkBlockDevIoctlType_EraseLogicalSectorsNvDdkBlockDevIoctlType_QueryFirstBootNvDdkBlockDevIoctlType_DefineSubRegionNvDdkBlockDevIoctlType_WriteVerifyModeSelectNvDdkBlockDevIoctlType_AllocatePartitionNvDdkBlockDevIoctlType_PartitionOperationNvDdkBlockDevIoctlType_ReadPhysicalSectorNvDdkBlockDevIoctlType_WritePhysicalSectorNvDdkBlockDevIoctlType_QueryPhysicalBlockStatusNvDdkBlockDevIoctlType_ErasePhysicalBlockNvDdkBlockDevIoctlType_LockRegionNvDdkBlockDevIoctlType_MapLogicalToPhysicalSectorNvDdkBlockDevIoctlType_FormatDeviceNvDdkBlockDevIoctlType_GetPartitionPhysicalSectorsNvDdkBlockDevIoctlType_IsGoodBlock
Nand Block dev ioctl opcode=%s error 0x%x
Save Region Table copy %u at CurrBlockNum %u
Ftl Lite bad block mark failed at Chip=%d, Block=%d
New Block at: chip=%d,block=%d
Replace block=%d in chip=%d for read failure
Data area read verification failed in FTL Lite at Chip=%d,Blk=%d,Pg=%d
FTL Lite Read Verify error code=0x%x
Wr Error: 0x%x, Replace ftl lite bad block, PbaIndex=%d,Chip=%d,Block=%d,StartPg=%d,PgCount=%d
Rd verify error: 0x%x, Replace ftl lite bad block, PbaIndex=%d,Chip=%d,Block=%d,StartPg=%d,PgCount=%d
Error in FTL Lite write
RETURNING ERROR FROM NvNandWriteSector TL error=%u,Sector Start=0x%x,Count=0x%x
RETURNING ERROR FROM NvNandReadSector TL error=%u,Sector Start=0x%x,Count=0x%x
RETURNING ERROR FROM NvNandOpen
Error: trying cached read past page limits
512B Read: Page=%d, within page sector in page=%d, sector count=%d
Error: 512B buffer allocate failed earlier
Error: trying cached write past page limits
Error: failed to allocate buffer for 512B sector support
Alloc memory failed
TLvalidate FAIL1 sector offset=0x%x,count=0x%x,sectorsPerRow=%u
TLvalidate FAIL2, Interleave bank Pgs[ %d ]
TLvalidate FAIL3
TLvalidate FAIL4
TLvalidate FAIL5 page[0]=0x%x,Reqd rows=0x%x
TLEraseAll fail BtlGetPba: Chip=%d,Block=%d
GetBlock info failed: Chip=%d, Blk=%d
Marking Bad block failed forChip=%d Block=%d
Found Bad block Chip=%d Block=%d
Factory Bad: 0x%x, Run-time bad marker: 0x%x
Interleave2PhysicalPg fail1: illegal page
Interleave2PhysPg fail2: illegal device
Ddk Read error code=0x%x
In NandTLGetBlockInfo Error = 0x%x
NandTL_INVALID_ARGUMENT3
NandTL_INVALID_ARGUMENT4
NandTL_INVALID_ARGUMENT5
NandTL_INVALID_ARGUMENT6
Error: No free Blk, Region[%d]=%d
Strategy Handle Error failed in Wr Status:%d,
TL write error=%u,sector start=0x%x,count=0x%x
NandTL_INVALID_ARGUMENT1
NandTL_INVALID_ARGUMENT2
TlRead failed Status:%d,
TL read error=%u,sector start=0x%x,count=0x%x
Region=%d SD Erase start 512B-sector=%d,512B-sector-num=%d
LCM of %d and %d =%d
Part-id=%d size from %d sectors by %d sectors
SD Alloc Partid=%d, start sector=%d,num=%d NvDdkBlockDevIoctlType_ErasePartitionNvDdkBlockDevIoctlType_VerifyCriticalPartitionsUnknownIoctl
Inst=%d, SD ioctl %s failed: error code=0x%x SPIF ERROR: SpifOpen failed..
SPIF ERROR: Trying to read more than SPI flash device size..
SPIF ERROR: Trying to program more than SPI flash device size..
SPIF ERROR: Trying to erase more than chipsize NumberOfSectors[0x%x] TotalBlocks[0x%x]
SPIF ERROR: Trying to erase more than chipsize NumberOfBlocks[0x%x] TotalBlocks[0x%x]
SPIF ERROR: Illegal block driver Ioctl..
SPIF ERROR: SpifBlockDevIoctl failed error[0x%x]..
Inst=%d, SPI Flash ioctl %s failed: error code=0x%x Trying to close driver without open
SPIF ERROR: NvDdkSpifBlockDevInit failed error[0x%x]..
Error SD clear skip blocks - sector=%d
Skipping SD erase of prefix %d blocks from %d
Skipping SD erase of suffix %d blocks from %d
Hsmmc Erase start sector=%d,num=%d
Hsmmc Alloc Partid=%d, start sector=%d,num=%d
NvNandHandle: FtlStartLba=%d, FtlEndLba=%d FtlStartPba=%d, FtlEndPba=%d pBlocks[%d ] prevBlocks[]
TrackLba[%d]: lba=%d, %s
Misc start
NumOfBanksOnBoard = %d
NoOfILBanks = %d
PhysBlksPerBank = %d
ZonesPerBank = %d
PhysBlksPerZone = %d
PhysBlksPerLogicalBlock = %d
TotalLogicalBlocks = %d
TotEraseBlks = %d
NumOfBlksForTT = %d
PgsRegForTT = %d
TtPagesRequiredPerZone = %d
NumOfBlksForTAT = %d
BlksRequiredForTT = %d
PgsAlloctdForTT = %d
ExtraPagesForTTMgmt = %d
LastTTPageUsed = %d
CurrentTatLBInUse = %d
bsc4PgsPerBlk = %d
Misc end
TAT Handler start
tatBlocks[%d] bank = %d, block = %d
ttBlocks[%d] bank = %d, block = %d
tat Block bank = %d, block = %d
TtAllocBlk[%d] bank = %d, block = %d
lastUsedTTBlock bank = %d, block = %d
TAT Handler end
++++++++++++++++++
TT 32-bit entry format in dump :
=============
Region: b31-b30
BlockNotUsed: b29
BlockGood: b28
DataReserved: b27
SystemReserved: b26
TatReserved: b25
TtReserved: b24
PhysBlkNum: b23-b0
============
Dumping page %d
**SuperBlock %d
*0x%08X [%d] [SYS-RSVD]
*0x%08X [%d] [ ^^^ FREE BLK ] Region%d
*0x%08X [%d] [ USED BLK ] Region%d
*0x%08X [%d] [*** BAD BLK ***]
Total=%u,Free=%u,Bad=%u,Reserve Data=%u,System=%u,Tat=%u,Tt=%u,Illegal=%u,Region0=%u,Region1=%u,Region2=%u,Region3=%u
No free blocks Available- find out the reason, bank = %d
[Strategy] Erase Failed
Bad Block found at LBA %d
Marked blk bad bank = %d, block = %d Rev = %d lba = %d
TAT write failed page = %d, bank = %d, block = %d Rev = %d lba = %d WriteOnlyHeader = %d
NO FREE TAT BLOCKS AVAILABLE
writing to TAT blocks failedInvalid percent reserved value = %d, should not exceed%d, setting it to %d
[Nand_Strategy] Failed to mark PBAs BAD
**** Fail: Invalid Case ****
Not Expected to come here
NvError_NandNoFreeBlock1
Error: NandStrategyGetSectorPageToWrite InTracking case, No Page
Error: NandStrategyGetSectorPageToWrite GetPBA case, No Page
NvError_NandNoFreeBlock2
GetNewPBA failed Sts: 0x%x in GetSectorPage2Write #2
Error: NandStrategyGetSectorPageToWrite PBA assigned already case, No Page Crypto Engine Disabled, Returning IOCTL
AES DDK Unsupported IOCTL COMMAND
AES Engine[%d] Disabled - EngineStatus[%d]
MemMap failed.
.NVRM Initialized shmoo database
NVRM Got shmoo boot argument (at 0x%x)
ActiveIdleAutoHwRM power state before suspend: %s (%d)
Active Module: 0x%x*** Wakeup from LP0 ***
*** Wakeup from LP1 ***
*** Wakeup after Skipped LP0 ***
DTT: TMON initialization failed
DTT: T = %d, Range = %d (%d : %d)
DVFS set core at %dmV
Clock control balance failed for module %d, instance %d
ADJUSTED CLOCKS:
MC clock is set to %6d KHz
EMC clock is set to %6d KHz (DDR clock is at %6d KHz)
PLLX0 clock is set to %6d KHz
PLLC0 clock is set to %6d KHz
CPU clock is set to %6d KHz
System and AVP clock is set to %6d KHz
GraphicsHost clock is set to %6d KHz
3D clock is set to %6d KHz
2D clock is set to %6d KHz
Epp clock is set to %6d KHz
Mpe clock is set to %6d KHz
Vde clock is set to %6d KHz
NVRM CLOCKS: PLLX0: %d Khz
NVRM CLOCKS: PLLM0: %d Khz
NVRM CLOCKS: PLLC0: %d Khz
NVRM CLOCKS: PLLP0: %d Khz
NVRM CLOCKS: PLLA0: %d Khz
NVRM CLOCKS: CPU: %d Khz
NVRM CLOCKS: AVP: %d Khz
NVRM CLOCKS: System Bus: %d Khz
NVRM CLOCKS: Memory Controller: %d
NVRM CLOCKS: External Memory Controller: %d
GPUHandheldBrChipsCrushMCPCkVaioHandheld SOCSimulation Chip: 0x%x
FPGAQuickTurnEmulation (%s) Chip: 0x%x Netlist: 0x%x Patch: 0x%x
Chip Id: 0x%x (%s) Major: 0x%x Minor: 0x%x SKU: 0x%x
NV_CFG_RMC_FILENV_CFG_CHIPLIBNV_CFG_CHIPLIB_ARGSSECURITY_VIOLATION DecErrAddress=0x%x SECURITY_VIOLATION DecErrStatus=0x%x EMEM DecErrAddress=0x%x EMEM DecErrStatus=0x%x GART DecErrAddress=0x%x GART DecErrStatus=0x%x DTT: Invalid Range = %d
Err in I2c transfer: Controller Status 0x%08x
AP20 I2c Isr got unwanted interrupt IntStatus 0x%08x
QueryIface_CQueryIfacebogusOBS bus modID 0x%x index 0x%x = value 0x%xLLC Client %d Count: 0x%.8X, %u
LLC Client %d Clocks: 0x%.8X, %u
Client %.3d Count: 0x%.8X, %u
Total MC Clocks: 0x%.8X, %u
AXI DecErrAddress=0x%x AXI DecErrStatus=0x%x Output FIFO does not refill, context read is stuck.Error> DSI Panel Initialization Failed
Error> DSI Panel Suspend Failed
Max8907bRtcCountWrite() error. Max8907bRtcCountRead() error. ERROR: GPIO_PCF50626_I2cWrite8() failed.
Sorry for spamming this thread, just wanted to show off some cool pics and vids
http://img404.imageshack.us/img404/4427/20120224235839.jpg
http://www.youtube.com/watch?v=moflp1BDCpA
sp3dev said:
Sorry for spamming this thread, just wanted to show off some cool pics and vids
http://img404.imageshack.us/img404/4427/20120224235839.jpg
http://www.youtube.com/watch?v=moflp1BDCpA
Click to expand...
Click to collapse
I would not call that spam. Thats AMAZING. cant wait to see more!
edit:
so did you completely replace acers bootloader on the tab with uboot?
gh123man said:
I would not call that spam. Thats AMAZING. cant wait to see more!
edit:
so did you completely replace the bootloader on the tab with uboot?
Click to expand...
Click to collapse
Yes, but..
1. Right now it does not support the tegra's partition layout - no luck with reading emmc partitions. Probably need to port tegrapart to uboot or figure out how to use EFI partition table (possibly needs hacking GPT offset)
2. Uboot doesn't support Android's boot images. The support can be added, but it may be easier to just repack kernel and initrd to uImage.
3. There's no USB client driver, so one will need to use microsd or usb stick to flash kernel/recovery for the first time.
So. I didn't have much time to play with it, but I'll look into it further
sp3dev said:
Yes, but..
1. Right now it does not support the tegra's partition layout - no luck with reading emmc partitions. Probably need to port tegrapart to uboot or figure out how to use EFI partition table (possibly needs hacking GPT offset)
2. Uboot doesn't support Android's boot images. The support can be added, but it may be easier to just repack kernel and initrd to uImage.
3. There's no USB client driver, so one will need to use microsd or usb stick to flash kernel/recovery for the first time.
So. I didn't have much time to play with it, but I'll look into it further
Click to expand...
Click to collapse
thanks... extremely interesting... keep us updated with progress, im sure im not the only one interested in this.
sp3dev said:
I have uploaded the archive with nvflash and some instructions on using it with A500. This is only intended for hardcore geeks who know how ARM boots. Be careful - while you can't really brick tegra2 (since it has a minimal usb-capable bootloader in the OTP area), you can screw up things and it will be quite hard to force the tablet to boot in some cases due to stupid security checks.
Click to expand...
Click to collapse
Just curious, you are using 0x300d8011 as odmdata, when EUU's are using 0xb00d8011.
My understanding is that LPSTATE=LP0 with yours (instead of LP1).
Any reason/consequences ?
wlk0 said:
Just curious, you are using 0x300d8011 as odmdata, when EUU's are using 0xb00d8011.
My understanding is that LPSTATE=LP0 with yours (instead of LP1).
Any reason/consequences ?
Click to expand...
Click to collapse
Actually you should use the value from the BCT (it's around the end of it). As far as I understand, there are several SoC revisions, and one of them is iirc A03p, which supports LP0, and the other one is A03, which does not. I think I had a file somewhere describing ODM value
In tegra devkit here
145 /// Soc low power state
146 #define TEGRA_DEVKIT_BCT_CUSTOPT_0_LPSTATE_RANGE 31:31
147 #define TEGRA_DEVKIT_BCT_CUSTOPT_0_LPSTATE_LP0 0x0UL
148 #define TEGRA_DEVKIT_BCT_CUSTOPT_0_LPSTATE_LP1 0x1UL
Other than mmcblk0 p1-8 what other hidden partitions are there? I can write the detection for mmc as I have it for recovery just haven't set the debugging to find the dtypes for iconia as I've been lazy and defined them. Can you list any partitions after p8 or hidden ones related to nvflash etc I have the usual boot, data, cache, misc, recovery, system etc please id any new ones as well.
sp3dev said:
I have uploaded the archive with nvflash and some instructions on using it with A500 ...
Click to expand...
Click to collapse
Oh, so the bootloader is actually unsigned - or I missed something? So what prevents me to patch the ICS BL and force unlock mode? I see I am a bit desoriented on Acer scene.
Back to the stock ICS BL, the unlock info is stored to BCT.
Skrilax_CZ said:
Oh, so the bootloader is actually unsigned - or I missed something? So what prevents me to patch the ICS BL and force unlock mode (so ppl can use fastboot)? I see I am a bit desoriented on Acer scene.
Back to the stock ICS BL, the unlock info is stored to BCT.
Click to expand...
Click to collapse
correct me if im wrong. now since we can generate the sbk we have full access to nvflash which gives us direct access to flash anything we want. including a new bootloader (weather its signed or not). its like a layer above the bootloader. sp3dev could explain it better...
Anyway, I was using Miui V3 2.4.20 [2.6.35], and Google maps wasn't very happy with it. So I decided it was time to move on to the .32 kernal version, since the developer was going that way too. Downloaded a stock rom with .32 kernal, went to the pink screen and flashed, and then boot loop.
Luckily, I'm awesome, so my phone won't die on me. Tried flashing some roms through clockwork, no bootloop, just stuck at huawei logo. Tried flashing some stock roms, and at about 98% done flashing it goes error. Some parts get flashed causing my recovery reverts to stock, but I'm still stuck at the huawei logo.
Also, in clockworkmod I get errors mounting data and emmc, so that might be a problem. Other partitions mount fine.
I'm sure I'll find a solution eventually, so there's no rush. I've been in similar situations before. Just wanted to see what other people had used for similar situations. So if you know of something that would help, please let me know.
Found these through search (I'll do a better search again later), i will try them tomorrow:
http://forum.xda-developers.com/showpost.php?p=18944228&postcount=4
http://forum.xda-developers.com/showthread.php?t=1683249
http://forum.xda-developers.com/showthread.php?t=1689469
http://forum.xda-developers.com/showthread.php?t=1682501
http://forum.xda-developers.com/showthread.php?t=1011527
After reading a lot of threads, attempting to flash a lot of roms (stock and others), replacing all kinds of images, and offering a sacrifice to the cellphone gods, still at the same problem:
To reiterate problem:
1) Stuck/reboots at Huawei logo
2) Flashing stock roms via pink screen never finish installing, get error message at ~95% finished (During install, unpacks fine)
3) Flashing roms via recovery say they installed, but still boot problem
4) This problem occurred while trying to downgrade from .35 to .32
My next step is to try using Linux to put the Dload folder on the internal SD card and try installing from there. I have a feeling it is related to the partitions having problems. I used both the "get back pink screen" and "data partition resize," maybe something went wrong with them that only appeared when I tried to go back to stock. I'll find out more when I install linux and can see if the partitions are OK or not.
I've always wanted to try linux, and now that my phone is broke I have found the motivation to do so. So a word of advice for people for people wanting to try linux but are too lazy to download the linux file: Soft-brick your phone, it gives you motivation.
UPDATE: I'm pretty sure my partition table is broke pretty bad. In adb shell, df gives me:
Filesystem Size Used Free
/dev 173M 64K 172M
/system 203M 200M 2M
/cache 127M 4M 123M
and that's it. No /HWUserData, /.cust_backup, /mnt/asec, /mnt/obb, or /data.
Would someone be as kind as to tell me how to fix the partition table? I've got a soldering iron, duct tape and super glue. Also, I'm not afraid to buy a "box" to do some Jtag stuff.
Anybody know what Blefish uses to format the phone memory? I read on his tumbler page and his github that he has altered the partition table (he split the /hwuserdata into three sections, which means he has the ability to create partitions) If I can get that tool, then I have a plan:
0) If my understanding is correct, the updates don't install because the needed partitions are missing, which causes an error. I guess the updates won't create partitions, just alter them.
1) Use the tool blefish used to setup the partition table as described in this thread: http://forum.xda-developers.com/showthread.php?t=1504488
2) Once the partitions are back, i should at least be able to get the blue screen, if I'm good, then I can put all right files in /dev/sdb1, which will get me the pink screen.
3) Using the blue/pink screen, I can install stock firmware, which should correct any problems that the partition table has. Maybe even install android.
4) Do the happy dance
5) ???
6) Profit
I've done my homework, searched the forums, made a plan, and cleaned my room. Someone please give me some feedback and at least let me know if I'm heading in the right direction.
typci said:
Anybody know what Blefish uses to format the phone memory?
Click to expand...
Click to collapse
I am using fdisk, the main partitioning tool for MBR table. You can check the table by doing fdisk /dev/block/mmcblk0 and then "p" which should print the current partition table. From there, you can also modify the partitions.
Sent from my U8800 using Tapatalk 2
Blefish said:
I am using fdisk, the main partitioning tool for MBR table. You can check the table by doing fdisk /dev/block/mmcblk0 and then "p" which should print the current partition table. From there, you can also modify the partitions.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
Awesome. I used to use fdisk back in the dos days, so I just need to brush up on my skills and learn the adb specifics. I really need to take the time to go learn all the commands associated with adb.
INTERESTING UPDATE: If I flash a rom with locked boot loader, I still get the pink screen but it doesn't work, i.e. I can't access the image folder via windows. If I flash a rom without a locked boot loader, pink screen works. Granted none of these roms actually fully flash, I still get the error near the end.
Fdisk = Permission denied, su = permission denied. Rooted boot image prevents me from getting into recovery, which means adb won't work. Any other way to get root? I'll try flashing a custom rom when I can get clockworkmod working again. For some reason I can't get recovery to load via vol+ & power.
Also something weird is going on. When it boots, it reboots once, then goes to stock recovery, tries to do a factory reset, gets errors on formating. Also in windows two removable disks appear, but I can access them. I take it that they represent the internal SD card and maybe the pink screen image folder partition. Tomorrow I'll try linux and see what happens.
UPDATE:
1) I can't use FDISK because SU won't work. I'm not sure how SU/root works on a software/partition bricked phone.
2) Rooted boot.img won't boot into recovery. SuperOneClick won't work because it can't find the data partition (probably because I don't have one).
3) I was going to try flashing a custom rom but for some reason I can't get clockworkmod working again. The phone will boot into stock recovery on it's own, after a couple of reboots. However, if I change the boot.img or recovery.img to anything else, it gets stuck at huawei logo or boot loop.
4) Unbuntu LiveCD won't work (says it can't find the kernal) even though I used the installer from the website and tried it both via cd and flash drive. Working on installing a dual-boot system now.
I'm really striking out here. Couple of questions if anyone would care to answer.
1) Besides recovery, how else can I establish an adb connection? Pink screen and huawei logo give me device not found.
2) Is there a root exploit available that doesn't require a data partition or is there a root exploit I can modify so it doesn't require a data partition? It's OK if it's a manual exploit, while I'm new with android/adb, I got plenty of experience with command prompt input from back in the dos days.
Also learned there is a HuaWei office in my town. Don't know what they do there, but if I don't make any progress after I couple more days, I'll go find out.
typci said:
UPDATE:
1) I can't use FDISK because SU won't work. I'm not sure how SU/root works on a software/partition bricked phone.
2) Rooted boot.img won't boot into recovery. SuperOneClick won't work because it can't find the data partition (probably because I don't have one).
3) I was going to try flashing a custom rom but for some reason I can't get clockworkmod working again. The phone will boot into stock recovery on it's own, after a couple of reboots. However, if I change the boot.img or recovery.img to anything else, it gets stuck at huawei logo or boot loop.
4) Unbuntu LiveCD won't work (says it can't find the kernal) even though I used the installer from the website and tried it both via cd and flash drive. Working on installing a dual-boot system now.
I'm really striking out here. Couple of questions if anyone would care to answer.
1) Besides recovery, how else can I establish an adb connection? Pink screen and huawei logo give me device not found.
2) Is there a root exploit available that doesn't require a data partition or is there a root exploit I can modify so it doesn't require a data partition? It's OK if it's a manual exploit, while I'm new with android/adb, I got plenty of experience with command prompt input from back in the dos days.
Also learned there is a HuaWei office in my town. Don't know what they do there, but if I don't make any progress after I couple more days, I'll go find out.
Click to expand...
Click to collapse
On pink screen, your device is just like any other mass storage device. So you can still use fdisk on ubuntu with the correct /dev/sdX path. You can also format the data/system/cache using other tools if you need to.
Sent from my U8800 using Tapatalk 2
Sweet, so I just need to get Unbuntu working. I still can't figure out why the live CD/flash drive didn't work. Oh, well. When I get off of work I'll get to installing the dual-boot system. Thanks for your help.
typci said:
Sweet, so I just need to get Unbuntu working. I still can't figure out why the live CD/flash drive didn't work. Oh, well. When I get off of work I'll get to installing the dual-boot system. Thanks for your help.
Click to expand...
Click to collapse
i actually understood nothing from your posts but i would like to congratulate you for being a user who does research before asking ppl something
and I gladly give you a bump
JaymzBond said:
i actually understood nothing from your posts but i would like to congratulate you for being a user who does research before asking ppl something
and I gladly give you a bump
Click to expand...
Click to collapse
Thanks. Unfortunately the project is on hold for a couple of days. My electric motorcycle has been having some problems and I've been repairing it. Also, I think I found out why linux wasn't working. Apparently the "alternative" downloads aren't useable as a live CD, which is why the kernal wasn't there. Anyway, it's been a great learning experience. Maybe after I "break" my phone enough times I'll learn enough to become a developer.
Doing some research before getting back to working on the phone.
Looks like Blefish is talking about using linux's fdisk, when I was trying to use adb's fdisk. That would certainly allow me to bypass the su problem with adb. I think I got all the correct files for my linux livecd, so that shouldn't be a problem. After I'm done with my workout, I'll try it out and see how it goes. It's time to learn how to use linux.
Update: Got unbuntu working. Storage devices are all /media instead of /dev like I was expecting. But I think I'm not looking in the right place.
Plugged in phone via pink screen and 3 drives came up:
System - has system stupp (app, bin, etc, fonts, ...) - sdb12
256 MB File system - image folder with all the .img and .mbn files - sdb1
136 MB File system - has fotapkg, lost+found, recovery folders- filesystem type ext3/ext4 - I'm not sure what this is, maybe sdb6? If it was data (sdb13) then I wouldn't get the error in recovery, If it was the internal SD card the filesystem should be vfat. If someone knows better, please let me know.
For some reason I don't have permission to access the lost+found folder, or so Unbuntu tells me.
Tried to used fdisk with system, got error: I don't know how to handle files with mode 40755
Also found some recovery log files in the fotapkg and recovery folders. I'll post it here incase someone can get some more useful information out of it. Does anyone know what all these (null) mean?
Tomorrow I'll get to work on learning how to use unbuntu and fdisk.
Starting recovery on Sun Jan 6 00:03:50 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot vfat /dev/block/mmcblk0p1 (null)
2 /fat vfat /dev/block/mmcblk0p1 (null)
3 /cache ext4 /dev/block/mmcblk0p6 (null)
4 /data_pseudo ext4 /dev/block/mmcblk0p13 (null)
5 /misc emmc /dev/block/mmcblk0p7 (null)
6 /recovery vfat /dev/block/mmcblk0p1 (null)
7 /HWUserData vfat /dev/block/mmcblk0p14 (null)
8 /system ext4 /dev/block/mmcblk0p12 (null)
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
I:cmdline: console=ttyDCC0 androidboot.hardware=huawei androidboot.localproppath=hw/default androidboot.emmc=true androidboot.image=recovery androidboot.mode=user androidboot.baseband=msm
Ita_move_command_file
I:Got arguments from boot message
Command: "recovery" "--wipe_data" "--wipe_cache"
Formatting /cache...
Creating filesystem with parameters:
Size: 136314880
Block size: 4096
Blocks per group: 32768
Inodes per group: 4160
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 33280
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/8320 inodes and 1585/33280 blocks
E:failed to mount /data_pseudo (No such file or directory)
E:failed to mount /data_pseudo (No such file or directory)
Formatting /data...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
E:failed to mount /data_pseudo (No such file or directory)
E:failed to mount /data_pseudo (No such file or directory)
Formatting /cache...
Creating filesystem with parameters:
Size: 136314880
Block size: 4096
Blocks per group: 32768
Inodes per group: 4160
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 33280
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/8320 inodes and 1585/33280 blocks
Data wipe failed.
wipe internal sdcard fail.
It could be that the data partition (originally mmcblk0p13) got wiped out and now mmcblk0p13 is internal sd card. Here's the original partition table:
Code:
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
1 heads, 16 sectors/track, 483328 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 30721 245760 b Win95 FAT32 CUST
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 30721 30783 500 4d Unknown SBL1
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 30783 31158 3000 46 Unknown TZ
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 31158 483328 3617363+ 5 Extended EBR
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 32769 34304 12288 59 Unknown OEMINFO/BOOTLOADER IMAGES
/dev/block/mmcblk0p6 40961 57600 133120 4c Unknown CACHE
/dev/block/mmcblk0p7 65537 65599 500 5a Unknown MISC
/dev/block/mmcblk0p8 73729 74112 3072 58 Unknown FSG?
/dev/block/mmcblk0p9 81921 82795 7000 50 Unknown ADSP
/dev/block/mmcblk0p10 90113 90496 3072 4a Unknown MODEM_ST1
/dev/block/mmcblk0p11 98305 98688 3072 4b Unknown MODEM_ST2
/dev/block/mmcblk0p12 106497 134656 225280 83 Linux SYSTEM
/dev/block/mmcblk0p13 139265 216064 614400 83 Linux USERDATA
/dev/block/mmcblk0p14 221185 483328 2097152 69 Unknown INTERNAL_SD
The sdb6 is indeed cache, and it is used for recovery communication between Android.
If everything would be ok, it would mount sdb1, sdb6, sdb12, sdb13 and sdb14 inside Ubuntu, so it seems that something is wrong at the end.
If you have 14 partitions, use disk utility from Ubuntu and try manually formatting the 13 for ext4 and 14 for vfat. Taking ownership is not needed, it should work either way.
Blefish, thanks for the help. Got unbuntu up and working along with fdisk and identified the phone.
I have 13 partitions (including one empty one) , not 14. Here's the print out:
[email protected]:~$ sudo fdisk /dev/sde
omitting empty partition (13)
Command (m for help): p
Disk /dev/sde: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 491520 245760 b W95 FAT32
/dev/sde2 * 491521 492520 500 4d QNX4.x
/dev/sde3 492521 498520 3000 46 Unknown
/dev/sde4 498521 7733247 3617363+ 5 Extended
/dev/sde5 524288 548863 12288 59 Unknown
/dev/sde6 655360 921599 133120 4c Unknown
/dev/sde7 1048576 1049575 500 5a Unknown
/dev/sde8 1179648 1185791 3072 58 Unknown
/dev/sde9 1310720 1324719 7000 50 OnTrack DM
/dev/sde10 1441792 1447935 3072 4a Unknown
/dev/sde11 1572864 1579007 3072 4b Unknown
/dev/sde12 1703936 2154495 225280 83 Linux
Comparing with your partition table I see two differences:
1) the ending block of sde1 is 491520 on mine and on the original it is 30721, however the blocks are the same, so that is probably not a problem
2) sde13 is empty, and sde14 is missing.
This actually makes sense. When I was using MIUI, I reduced the size of the internal sd to near zero, since MIUI could only either the internal or external sd, not both. After trying to downgrade, I had a problem, so I tried to restore the internal sd card back to stock size, just to bring my phone back to stock. Something must have gone when I did that.
So if I understand the problem correctly, to fix this I need to:
1) Split sde13 into 2 partitions
2) Format sde13 to ext4 and sde14 to vfat
3) Try installing adroid again
Do I need to name the partitions a certain name or do anything else?
In the mean time I'll be looking into how to use disk utility and fdisk to deal with sde13 and sde14.
Had an idea that I only need sde13 (data) to get things working again, the system shouldn't need sde14 (internal sd) to work.
So I went to disk utility, found Qualcomm MMC storage and tried to format the free 2.9GB at the end. Got an error:
Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/sde, start=1103101952, size=2856000000, type=0x83
Entering MS-DOS parser (offset=0, size=3959422976)
MSDOS_MAGIC found
looking at part 0 (offset 512, size 251658240, type 0x0b)
new part entry
looking at part 1 (offset 251658752, size 512000, type 0x4d)
new part entry
looking at part 2 (offset 252170752, size 3072000, type 0x46)
new part entry
looking at part 3 (offset 255242752, size 3704180224, type 0x05)
Entering MS-DOS extended parser (offset=255242752, size=3704180224)
readfrom = 255242752
MSDOS_MAGIC found
readfrom = 255243264
MSDOS_MAGIC found
readfrom = 255243776
MSDOS_MAGIC found
readfrom = 255244288
MSDOS_MAGIC found
readfrom = 255244800
MSDOS_MAGIC found
readfrom = 255245312
MSDOS_MAGIC found
readfrom = 255245824
MSDOS_MAGIC found
readfrom = 255246336
MSDOS_MAGIC found
readfrom = 1140842496
No MSDOS_MAGIC found
Exiting MS-DOS extended parser
Exiting MS-DOS parser
MSDOS partition table detected
containing partition table scheme = 1
got it
Error: Invalid partition table on /dev/sde -- wrong signature 0.
ped_disk_new() failed
So, my partition table is corrupt? I'll need to figure out how to fix this.
Here's some options I've found:
http://forum.xda-developers.com/showpost.php?p=21572216&postcount=12
ksatta mentions a couple of ideas:
1) If someone backed up their phone using dd, I could use that to restore my phone.
Here's a link on how to do it: http://linuxpoison.blogspot.com/2009/04/creating-backuprestore-images-using-dd.html
dd if=/dev/sdX | gzip > /home/sdX.bin.gz
where sdX is the U8800
2) I could clone someone's partition table. If someone could give me a copy of their MBR that should work.
Here's a link on how to do it: http://embraceubuntu.com/2005/10/20/backing-up-the-mbr/
Create a backup of your MBR by doing a:
dd if=/dev/sdX of=MBR-backup bs=512 count=1
That should read “create a disk dump of the input file, which is /dev/sdx (change to hda, or hdb or sda, depending on where the MBR is on your computer), and save it in the output-file MBR-backup in the directory from where the command is issued. Backup the first sector only, while you are at it”.
3) gparted - it's some kind of partition tool. Might be able to use it to fix the error. Not sure how to use it though.
For now I'm going to look into gparted for Ubuntu. If someone can help me out with a dd backup or cloning the partition table that would be awesome.
UPDATE: For people following this thread, and to keep me more organized, I'll start adding more of the important resources I find. They may one day help you fix your phone.
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/434463
Seems a guy fixed his the same error with gparted. However it wasn't on a phone. Also I'm seem a lot of people refer to sfdisk. I'll need to learn more about it.
https://answers.launchpad.net/ubuntu/+question/113539
"I got an answer in a forum, which looks easy.
Do a
sudo fdisk /dev/sda
then type
w
to write partition table, without any modification of it.
The signature should be fixed."
Is this safe to do to my phone? I know I'll have to write the MBR eventually, but I have to get it right the first time. If I screw up, I may not be able to connect to ubuntu anymore. Anyway, the guy said it fixed the error with his harddrive, so it's worth a try.
http://www.thegeekstuff.com/2010/09/linux-fdisk/
How to use fdisk, in case anyone needs to know
So my new plan is to:
1) dd Backup and MBR backup - in case I break it worse than it is
2) try to fix with fdisk w or gparted
I think the change in start and end is caused by Ubuntu using cylinders/sectors/blocks. Should not too much difference though.
Using MBR restore would not work here, as it restores the main 4 partitions list. MBR uses EBR aswell, which is located at the beginning of every extended partition. So we would have to copy the EBR of every partition.
I'd suggest deleting sde13, adding sde13 and sde14.
When adding sde13, note that starting block should be at the end of sde12, so simply insert last block of sde12 there. If it gives error, simply press enter as it automatically finds free block after the last one. End block could be for example +500M so fdisk automatically finds the correct end block. Do the same for sde14, but note the start block again. sde14 end block should be the last block there is on the card.
After you've done that, do w to write and if it tells you to restart or something, unplug the phone, take out the battery and restart to pink screen again. Then try to use disk utility again or gparted (have not tested this) to reformat sde13 and sde14 to ext4 and vfat.
You should be safe until you don't mess with the primary partitions, especially the mmcblk0p2 and mmcblk0p3.
Thanks again for the reply, Blefish. I may have just fixed it. I'll know soon enough.
I did two things:
1) sudo fdisk /dev/sde12 followed by w
2) sudo fdisk /dev/sde followed by w
After that it enabled me to add the 13 and 14 partition. I used disk utility so I didn't have to worry about the blocks. Afterwards they mounted in ubuntu like they should.
UPDATE: Not quite fixed, but the rom installed without error. So I think the partition problem is fixed.
Now I just have a boot loop. I'll go back to ubuntu, clear the cache, and try installing from the internal sdcard
2nd UPDATE: Stock recovery gives and error about mounting the cache partition. However CWM mounts it fine. My partition problems may not be over.
3rd UPDATE: genokolar's "Custom you partition" file to return to stock file deletes my partition 13 and 14. Had 13 and 14 back working, used the file as per instructions, afterwards ubuntu drive utililty shows 13 and 14 as "free." So that is where part of my problem comes from.
4th UPDATE: Fixed the problem with stock recovery. Turns out froyo doesn't like ext4 partitions. Changed cache partition to ext3, no more error.
Here are some exerts from the CMW log when I tried to flash cyanongen. Can anyone tell me if any of these errors are problems, and if they are what they mean?
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/CM7-070512.zip
Finding update package...
I:Update location: /sdcard/CM7-070512.zip
Opening update package...
Installing update...
unmount of /system failed; no such volume
package_extract_file: no backup_initd.sh in package
set_perm: chown of /tmp/backup_initd.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backup_initd.sh to 777 failed: No such file or directory
about to run program [/tmp/backup_initd.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: 11/56448 files (0.0% non-contiguous), 7142/225280 blocks
mount: failed to mount /dev/block/mmcblk0p12 at /system: Invalid argument
set_perm: chown of 0750 to 0 2000 failed: No such file or directory
set_perm: chmod of 0750 to 755 failed: No such file or directory
set_perm: chown of /system/etc/init.qcom.post_boot.sh to 0 2000 failed: No such file or directory
set_perm: chmod of /system/etc/init.qcom.post_boot.sh to 555 failed: No such file or directory
set_perm: chown of /system/xbin/apply_firewall to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/apply_firewall to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/apply_theme to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/apply_theme to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/dumplog to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/dumplog to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/mv2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/mv2sd to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/ota to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/ota to 6755 failed: No such file or directory
Updating BOOT Image...
about to run program [/tmp/backup_initd.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Installation complete!script result was [Installation complete!]
Install from sdcard complete.
failed to open /sys/class/android_usb/android0/state: No such file or directory
My phone is fixed. I have no idea how it became fixed, but it is fixed.
I placed b518 on the internal sd card, and installed it. Then bootloop. So I held both volume keys+power to try another rom. It installed again. Went to recovery, it did a factory reset. Bootloop. Went back to recovery to see if I could wipe the sd card. No option for it, so I did another factory reset and rebooted my phone. I left my phone bootlooping for a minute while I looked online for a Huawei service center, and then my phone booted. I gues it got scared and didn't want to go to a service center.
This been a great learning experience, although at times a major headaches. I want to thank blefish for all his help. Thanks to this, i've bee reading his blog and other stuff, and now will follow some of his other projects.
Now to downgrade back to 2.2!!!!
UPDATE: All official roms are working correctly (b136, b138, b518, b528), recovery (5.0.2.6) works. However I haven't been able to get a single custom rom to work. Tried a couple .32 MIUI and CM, but they all stick at the huawei logo. Did factory reset and dalvik wipe, get error can't mount /sd-ext during dalvik wipe, and still doesn't boot.
Maybe I need to try a newer verison of CWM? I tried the newer versions before, and I didn't like them. Buggy and often wouldn't find my sd card.
This thread must be made sticky because it consists of pure information about dealing with soft-bricks. Thanks a lot for your curiosity, you're my hero.