apx mode brick - HTC One X

apx mode brick - HTC One X

the phone will not turn on.
apx mode entered.
nvflash code
C:\Users\ibrahim\Desktop\RD_release(with_sbk)without sis>nvflash --blob blob.bin
--bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --
create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813nation┐à^ª☼C
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d29948960200f
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
I sorry for my bad english

Related

[Q] How to unbrick Dropad A8x?

Hello
I accidentally brick my device with firmware upgrade
First: it was Boot logo. and after that black screen. Using DNW tool i got this information
===== USB DEVICE STATUS =====
USB_CONFIGURATION_DESCRIPTOR
bLength = 0x9, decimal 9
bDescriptorType = 0x2 ( USB_CONFIGURATION_DESCRIPTOR_TYPE )
wTotalLength = 0x20, decimal 32
bNumInterfaces = 0x1, decimal 1
bConfigurationValue = 0x1, decimal 1
iConfiguration = 0x0, decimal 0
bmAttributes = 0xc0 ( ??? UNKNOWN!! )
MaxPower = 0x19, decimal 25
-----------------------------
USB_INTERFACE_DESCRIPTOR #0
bLength = 0x9
bDescriptorType = 0x4 ( USB_INTERFACE_DESCRIPTOR_TYPE )
bInterfaceNumber = 0x0
bAlternateSetting = 0x0
bNumEndpoints = 0x2
bInterfaceClass = 0xff
bInterfaceSubClass = 0x0
bInterfaceProtocol = 0x0
bInterface = 0x0
-----------------------------
USB_ENDPOINT_DESCRIPTOR for Pipe00
bLength = 0x7
bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )
bEndpointAddress= 0x81 ( INPUT )
bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )
wMaxPacketSize= 0x200, decimal 512
bInterval = 0x0, decimal 0
-----------------------------
USB_ENDPOINT_DESCRIPTOR for Pipe01
bLength = 0x7
bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )
bEndpointAddress= 0x2 ( OUTPUT )
bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )
wMaxPacketSize= 0x200, decimal 512
bInterval = 0x0, decimal 0
-----------------------------
Second: device in system appears as SEC S5PC110 Test B/D. and asks for driver.
I used drivers for samsung dev board.
The device build on samsung s5pc110 with 512mb nand memory
some shots of board inside.
Add some log from rs232
Rid images mywes below 0x0.
?lengthsdistance symbolsdynamic bit lengths tree{tance codent memoryINVAL
Error:Neither High_Speed esize:0x0
[s3c_usb_print_pkt:tcoov ...
?kernel entry point!
rom environment
o current device
(null)
(s)
not valid on device 26476424 **
ize(0x0)
_J?Under 128M
ME u¬??t erase FAT region~~!!!
ormat complete.
qoe>img4 buffer~~!!
uffer~~!!
er?~a???*I?for jounaling : 0
dr : 0x0
Descriptor Table(0)~~~!!!
?t<erase inode table(0)~~~!!!
Can't write rootdata~~~!!!
't write 7th inode~~~!!!
ta~?youg to mount ext2 filesystem...
(indir 1) malloc failed. **
1) failed. **
fsyz?U2gs read block (indir 2 2) malloc failed. **
2) failed. **
fs doesn't support tripple indirecv8au?9?zYXzONI?‘•?partition sector 0
alid Block Device Descriptor (NULL)
**
(e8rc8?{yZev: (null)
s Firm: (null) Ser#: ”y“libuP^?Oy“o7wP^?j{?v
s available
movable i?ion Map for UNKNOWN Partition Type: (null)
own partition table
partition table on 0:ad .5µt 0 26476424 1835e50s
rtition Start Sector Num Sectors Type
- list files from 'dev' on 'interface' in a 'direaooy[filename] [bytes]
- load binary file 'filename' from 'dev' on 'interface'
to address 'addr' from ext2 filesystem
o–‹?address not on sector boundary
precedes start sector
r boundary
sN…EN?and/or end address not on sector boundary
or: end address (0xx) not in flash!
tect Flash Bank # 0
Bad sectoo?|EN•‘) type
address format
0 sectors
Bank # 0
ash Sectors 0-0 in e?on for all FLASH memory banks
flinfo N
- print information for FLASH memory bank # N
ase - erase FLASH memory
|–?'start' to the end of sect w/addr 'start'+'len'-1
erase N:SF[-SL]
- erase sectors SF-SL in FLASH bank # N
erase bank N
?yuaFLASH write protection
tart end
- protect FLASH from addr 'start' to addr 'end'
protect on start +len
- protect FLqO?,?KI?SF-SL in FLASH bank # N
protect on bank N
- protect FLASH bank # N
protect on all
- protect all FLASH banks
proteaoyi> - make FLASH from addr 'start' to end of sect w/addr 'start'+'len'-1 wrtable
protect off N:SF[-SL]
- make sectors SF-SL wreuajj…*•?all FLASH banks writable
s'
-lt=?®EOµA•UMNEO?N?returning error when dumping path: , (null)
0 times to (null)...
wSUI?...
to 0x00000000 at 0 bps...
for binary (kermit) download to 0x00000000 auya0vo 0 bps and press ESC ...
ad Addr = 0x00000000
## Last Load Addr = 0x00000000
## Total Size = 0x00000000 = 0 BytesSi?0S-Record file over serial line
- load S-Record file over serial line with offset 'off'
adb - load binary ??offset 'off' and baudrate 'baud'
- load binary file over serial line (ymodem mode)
Address: 0x00000000
:?O?‘?00000000, expected 00000000
???
word at 0x00000000 (0x00000000) != word at 0x00000000 (0x00000000)
alfwordayA•02x)
ordwere the same
0000y
[# of oa?y{j•µ?Ea?modify, auto increment address
m(constant address)
ddress
- memory modify, readaory
opy
e target count
- copy memory
cmpre
addr2 co~CRC32 checksum [save at addr]
set address offset
- print address offset for memory commands
base offi??ue
.w, .l] address number_of_objects
- loop on a set of addresses
mtestRAM test
tart [end [pattern]_]yagxecution for N seconds (N is _decimal_ !!!)
turer ID: 0
cSpeed: tZ<0-bit
C read: dev # 0, block # 0, count 0 ...: (null)
write: dev # 0, blyuw,saIN•µread <device num> addr blk# cnt
mmc write <device num> addr blk# cnt
mmc rescan <device num>
mmc list - list available davoENyesoot of image at addr 0x00000000 ...
- boot image via network using BootP/TFTP protocol
stIPaddr:]bootfilename]
ootRP/TFTP protocol
dhcp - invoke DHCP clientato ob|O8=}IEUMQ?to network host
Saving Environment to (null)...
or: illegal character '=' in variable name "(null)"
uuI?not supported
tenvonment size: 0/0 bytes
onment variables
- print8?…µ•?
t environment variables
e ...
- set environment variable 'name' to 'value ...'
setenv name
- ay|?K…?•)vironment variable
- run the commands in the environment variable(s) 'var'o8oot a block start address
th is not block aligned
write (0 blocks):
ad blocks 0 at 0x0 is skipped.e80x0, 0
---ofs=0x0,len=0x0,retlen=0x0,addr=0x0,oob=0x0
(0 blocks):
k8(0) reading page 00000000
:
00 00 00 00 04 00 2x 00 00 00 00 00
zess
ffs2 write:
ata -- 0%.0x0, 0vice 0 bad blocks:
0000 at 0x00000000
ND (null): Q®I•?failed 0x0, 0
iled 0x0, 0
rite test failed at 0xx
b: (null)
—?…?‘OneNAND sub-systemable OneNAND devices
onenand bad - show bad blocks
onenand read[.oob] addr off size
oneny?uy?Ea?address 'addr', skipping bad blocks.
onenand write.yaffs addr off size - read/write `size' bytes starting
at offset `off'?uytest [off size] - test 'size' bytes from
offset 'off' (entire device if not specified)
onenand dump[.oob] off - dump page
onena?oEµ…N???)to transmit data
nw - initialize USB device and ready to receive for Windows server (speaigy?A•?for (null) command
art
for imxtract
tractt a part of a multi-image
qble.
known command '(null)' - try 'help' without arguments for list of all known commands
ynewline
like /bin/sh
]
- test functionality
t script
§help' prints online help for the monitor commands.
Without arguments, it prints a short usage message for all commands.
To get guys as arguments.
- alias for 'help'
devices available!
utput devices available!
_env---default_environment=0x0,ENV_SIZE=0x0
ror - default environment is too large
arning - bad CRC, using defaultui/Flash
t and/or end address not on sector boundary
Unknown Vendor of Flash
pe of Flash
E)t allocated
There is a global environment variable with the same name.
I?µ?main input shell.
iftil) reached
ERROR, too many US~ F?U?E?AN?E± error 0
config descriptor too short (expected 0, got 0)
t reset port 0!?
USB device not responding, gi?Wk•?descriptor (error=0)
device descriptor short read (expected 0, got 0)
d to set default configuration len 0, staooyel part
Unknown errorCd(SOH)/0(STX)/0(CAN) packets, 0 retries
ock sequence error/checksu}??II?file1 .. 0, ld x 0x0ld loader.. 0, 0 ernel..>7y?mmc r/w sub system for SMDK board
Initialize moviNAND and show card info
movi read {u-boot | kernel} {addr} - Read data0g?‘‘Eo?[bytes(hex)] - Read rootfs data from sd/mmc by size
movi write rootfs {addr} [bytes(hex)] - Write rootfs data to sd/mmc by sia {sector#} {bytes(hex)} {addr} - instead of this, you can use "mmc write"
for Android image downloading.
8cyte) installation.
tem image installation.
d system image(0 byte) installation.
ge instalua?±•N•‘?kernel image (0 byte) installation.
installation.
ed uboot image (0 byte) installation.
vor Android
insdroid zimage - Install zimage image for Android
insdroid ramdisk - Install ramdisk image for Android
insdroid syu?eE??write u-boot {address} - Make bootable SD card with uboot
Partition table on OneNAND]
-…™™IWarning can not do hw and sw ecc for partition '(null)'
ng these flags
boot: Adding partitions from envy?Error:FASTBOOT no partition name for '(null)'
Error:FASTBOOT no closing on name
ror:FASTBOOT partitii?Y[±?a?default partition information
rtition informations!dding: (null), offset 0x8x, size 0x00000000, flags 0x00000000
•?N•‘)ted
ables setading of 0 bytes finished
load buffer
yN????does not exist
rtition '(null)' erased
ownloadad of 0 bytes
y?•±?.
mage..
ng failed
eset the board
alid boot image?…ENaN???partition '(null)' flashed
'(null)' failed : (null)
'(null)' saveenv-ed
NFOunknown OEM comma?rytes read
sing Image from SD Card.]
ill read images from the followy???A?oot- use USB Fastboot protocol
out]
- Run as a fastboot usb device.
?oy?!sdfuse - read images from FAT partition of SD card and write them to booting device.
- print0yz0 erase userdata, cache, and reboot.
sdfuse flash <partition> [ <filename> ] - write a file to>yy"•U??•?is NOT founded.
device's initialization is failed.
block start # block count paoti|*A"? 0x00
0 0 0x00
0 0 0*yysd/mmc.
e_num> - create partition.
fdisk -p <device_num> - print partition information
- using default u~yE«99?..
riables
bootable device data
oyyIThe input address don't need a virtual-to-physical translation : 00000000
DKC110
dowi syo?aON?down system now!
s 0!
!
s 1 already!
{KKKVE‹}µµ?}‘•U??•?error!
le to use mmc 0 for fatload **
-------------Download_addr--=0xi–‘…N…?image Error!
nd!
ea00000 0ge installation.
aDya‚‚‚?
A0000 write.yaffs2 40000000 e00000 6a00000age installation.
imgonenand write 30008000 b00000 300000k image installation.
nload kernel image Error!
ernel imq000l image installation.
logo.binnload logo image Error!
yo’‚‚‚‚‚onenand write 30008000 80000 200000.
d.bin‚A‚‚‚‚Completed uboot image installation.
update software!
d!
a|e Android zImage images Fail!
id Ramdisk images Fail!
droid System images Fail!
Android userdata imayyy‹?Uboot images Fail!
mages Fail!
images Fail!
;########################################
Completed Write Android all images From SD to Onenand!
ndroid images include:uboot/zim??0123456789abcdefghijklmnopqrstuvwxyz?literal/length code enderrorry?}IO‰µ?N}©?‰e ENOMEM
Full_SpYuZ«‘?
0, Download Filesize:0x0
sb_print_pkt:able Connected!
a OTG cauynjJ?N??fastboot ...
SId Fastbootbytes: (null)
ate_success--shut doy+E‹…
ironment
AT32 nt device
Interface: y=Invalid FAT entry
(null) file(s), 0 dir(s)
get_dentfromdir: (null)
atname: |(null)|
== NULLu=t>valid on device 0 **
on0: Start Address(0xx), Size(0x0)
is broken **
r~~!!
?•E?256M
16G~
NO NAME ite PBR~~~!!!
ke img buffer~~(reserved)!!
ggion~~!!!
ite FAT~~~!!!
n0 format complete.
* Partition0 is not ext2 file-system 0 **
mg2 buf?y?y?
make zero buffer~~!!
an't make img5 buffer~~!!
ake rootdata buffer~~!!
buffer~~!!
aling : 0
te addr : 0x0
lock(0)~~~!!!
ptor Table(d)~~~!!!
an't write reserve.~oe(0)~~~!!!
ta~~~!!!
an't write root+1~~~!!!
te 7th inode~~~!!!
't write 8th inode~~~!!!
A:?±•IaIN•µ?..
lock (indir 1) malloc failed. **
ead block (indir 1) failed. **
ext2fs read block*(?indir 2 2) malloc failed. **
d block (indir 2 2) failed. **
ext2fs doesn't support tripple indirect blocks. **
ay|ition sector 0
* Invalid Block Device Descriptor (NULL)
ext2fs_devread() read error **
* ext2fs_devread() read error8E> (null) Firm: (null) Ser#: s
Type: evice# 00 # Capacity:<y|yNition Type: (null)
?T?NA?9a&g§?`?IGyiy?y?Io?yyy??a::‚Aba? r4 : 00000000
?|VE«n?instruction
y??}?’?I2ay?*AIaI?= 0MHz, PclkPsys = ‹5!e
?yu?…?‘?erase ea00000 1160000onenanaa~oyyada/¬??•yaffs_unlink returning error:ay??yY.EEEEEEEEE *")nPageReads........... 0unAiiyyyycyceaTrying to add an object to a null pointY>u??aoa?N?valids_guts.h 0
?you•?N?values pagesInUse 0 counted chunk bits 0
?o}Yyr mismtch parentId 0 obj->parent is NULL
y??‡~ou•?0 0 0
?y?,uk*I)|oIbn 0 has chunkId 0 (null) (null)
?ea??W?I?(0:0)
yyy«N§???invalid chunk 0
x?aa!
±±??…N?E?out !!!!!!!!!!!!!!!!!
y—Y?I…ffs_FindObjectByName: non-directory
oyy<{*| obj addr 0
d
nyyauo ON?data chunk into a non-file
y: exis|uuoyuz?E??*?0,
that has no chunksau?yyyawN•?0 after gc, should be erased
yy?ya)yYx?point device
y=;E‹?checksum |
heckpointed 0
y+iEe?or wrong
~?cw|d not allocate block index!
yxy?from 0 0
rit|en block 0 being set for iyy???ound.
rds ends
yycuyyaffs: yaffs_GutsInitialise() done.
a??e yaffs_nand.c 0
?y±?nate
ext checkpt block: start: blocks 0 next au??yx…?±?0 next 0
ut of c??yy?yµt|i–i±v 1.19 2007/02/14 01:09:06 wookey Exp $y?x?*]ithTagsToNAND chunk 0 data 00000000 tags 00000000
failureay?y™? acc error fix performed on chunk 0:0
yaffs ayyy??ojNY?ecc error unfixed on chunk 0:0
ecc errooay~?—?ad del 0 ser 0 seq I$Id: yaffs_ecc.c,v 1.9 2007i?o?E•?N?to ded; i_?yyau?~o.—oBytes transferred = 0 (0x0)
esizexyyyg—Y…a? ?~:"??*** WARNING: (null) is too long (0 - max: 0) - try~yyyOyuoi INVALID STATE
OTP broadcast 0
??‡i~ot umount
p fail
yy—o??receive the ext_csd.
yoYsyA?EN?any high-speed modes.
8x??y.never released inhibit bit(s).
y?u??has 0 eraseregions
[offset: 0x00000000, erasesize:a?—?yyuu)- 0MB y>y?ayya~|~™?device
yyy?~gXo•a??‘?end of device
ck: Atteo?y?yoy‘}??‰}??±??*e Attempted to read beyond end of device
?~zttempted to write past end of de~uy??+i?•‘?data
d
yynot erased.
onenand?set_boundary: Please erase blocks ~goEyy?OK?Die 0
e for Di} EI«‘?for oobsize 0
can_bbt: Out of memory
?? EE?Ee status check fail: 0x0
rc error
?’]E+Ee?in 32 bit mode
de
uy?ax onknown: 0 . 0) **
i?>yBad magic number
header crc
yziyOaddr - A valid autoscr header must be present
<y—)*??Y??OSnown Image?>‚??/s:
age 0:ay?ainit Ramdisk from multi component Legacy Image at y?yues-Nµ…?•scriptogramyuyer5ppc~oyy?aa|ionaterminated, rc = 0x0
yxa=08lX:
Image at 00000000 ...
a~yye?aA•e yuyEIUnsupported Archotecture 0x0
gg U?y>?uuuncompress or overwrite error - must Ryyyu?~O?U•E)?oyAA±??…N????image stored in memory
passing argumeiuoyyc?e‹?µ‘?
ation ?u?a?a~µ…?•?contents (magic number, header and payload che:?s-RROFFugh) Cache is (null)
yuu?]
- enable or disable data (writethrough) cacho>Yyu‘u~ess 0xlx
yu??uyEa)artiny?y?yyya)‹Ua??u?Yyaio|"•U??•± use `dev[art]' **
uo?Yapartitio?aA•?"(null)" (expect "U-Boot")
y?±•I?in a directory (default /)
ayaY§igname] [bytes]
- load binary file 'filename'a?~?y®e??by ext2 on 'interface'
at^cy<|ev[art]>
ition 0-----
?zayN±?‡‘?<interface> <dev[art]> <addr> <filename> [byuyyyu~?•Iu) - load binary file 'filename' from 'dev' on ?uy?uI™…?oya<dev[art]>
- print information about filesyoy?yiay‘?ad|ress not on sector boundary
??>??…rt and/or end address not on sector boundary
yyy?•|?ASH type
y?i~ for all FLASH memory banks
flinfo N
- print info~iyu?yxyI?sN…EN? to the end of sect w/addr 'start'+'len'-1
eryy?YyySx write protection
start end
- protect FLA?|y?uoI?OF-SL in FLASH bank # N
protect on bank N
-a?yyy?y~…*•?FLASH from addr 'start' to end of sect w/a|o?y?iyyyke all FLASH banks writable
r ''i’YI?yµA•UMNEO?N?returning error when dumping path: , '.ay:rrOr binary (ymodem) download ?yu>>a~ps and press ESC ...
y????E‘?file over serial line
o/—yyuYI•t 'off' and baudrate 'baud'
bi~yyyy???a?08lX, expected 00000000
y toa?yyo?AauWhalfword sao??Ia?modify, auto increment address
???<a - memory copy
.w, .l] source target ¬«iy?ya>??•?*IOµ?[save at addr]
or oau??yy—u .w, .l] address number_of_objects
- loop oao?????for N seconds (N is _decimal_ !!!)
yiy??‹)
yyyoutemaddr blk# cnt
mmc write <dc~?—o|yNgsmage at addr 0x00000000 ...
?INyAy‘‘Ee]bootfilename]
rpboot?eeuirEQUEST to network host
?y< not supported
* Abort
yzyµ•?
nment variables
|{…?•)mands in an environment varia~yyay~?N?a block start address
ERROR: 0 length is not biiai?y~yy0xax, 0
x0,len=0x0,retlen=0x0,addr?yyIB*"? ~eading page 00000000
age 00000000 dump:
y?yI)–OE write:
y?Iy?failed 0x0, 0
failed 0x0, 0
~?‡?yI«99?sub-system?y·~?address 'addr', skipping bad blocks.
onenand writ}.ua~yyyyWst [off size] - test 'size' bytes from
offset 'offo??~Eµation
NW to transmit data
?auy•afor (null) command
e Part
~u|?±oyoUnknown command '(null)' - try 'help' without argume~t>??y«Y±??•)..]
aa?y~^coU? prints online help for the monitor commands.
Wiy?yay·•oaX.
u?Oµ•?NI?
alias for 'help'
o}y•?Uµ--default_environment=0x0,ENV_SIZE=0x0
?EI9Outside available Flash
s not Eyy?oo~!ERROR : memory not allocated
|#yyzyµ?main input shell.
?Iyu?AN?E± error 0
escriptor ooo short (expecte| ~ua—???•?descriptor (error=0)
ort raayyy?y—±apart
error, 0(SOyyyx??II?filewriting(null) 0 0xyy?o?mmc r/w sub system for SMDK board
ze mo_Ey~?{adar} [bytes(hex)] - Read rootfs data from sd/mmc by sizy??yyy?—?{oector#} {bytes(hex)} {addr} - instead of this, you cana?yo?yy¬te/ installation.
on.
o»±•N•‘?kernel image (0 byte) installation.
t ube‹??xoy—?for Android
insdroid zimage - Install zimage image for
?uuyiudmovi write u-boot {address} - Make bootable SD card with ??yuoyy•.a–OWarning can not do hw and sw ecc for partition '(null)'
O?Y??ame for '(null)'
??yagmploy default partition information
yyy^??N•‘)tected
y?a~W‹????does not existyya?–?•±?.
/yx?…EN?N???partition '(null)' flashed
??uayNoI?®V‘)yy?yY‘?Chip)fastbooty·es
sdfuse - read images from FAT partition of SD card an| yyy?aa  erse userdata, ¬<?y^u??• is NOT founded.
/sd device's initializationayya.Ay 0x00
3 0 a?*Au?y??i
create partition.
fdZ?=?y?A~oEEWriting to OneNAND...
®yu?>?y• input address don't need a virtual-to-physicau??u??Na|e??system now!
y~u?©I§?‘}µµ?}‘•U??•?error!
rd OK!?yaI—?dXW?image Error!
yyay00a6a00000affs2 40000000 e00000 6a00????00 300000???‚?Completed kernel image installation.
EyY???o?0000rite 30008000 80000 200000ed licy?00?‚‚‚‚Completed uboot image installation.
y?}?‘E?a‘?zImage images Fail!
I??yWboot images Fail!
Android Log images Fail!
y#####################################
?uyY??123456789abcdefghijklmnopqrstuvwxyzCDEFCoyyyyiany length or distance symbolsxy?lite®±?length codey??ai_submit_job: ENOMEM
need 0 TDs, only have 0
>xz«n?
loada?y|y??yy?©)?N??fastboot ...
LSI0n?oyyy?oint!
d 0x0 from environment
younvalid FAT entry
(null)??y±§‘?on device 0 **
0xax?y???Yy?’??j)x
Au????uu…!!
ataaoo»yyOt make zero buffer~~!!
.u…?y~±§u??: 0
write addr : 0x0
yy~«e=d)~~~!!!
't write rootdata~~~!!!
te ~u?uyyay?>?±esystem...
* ext2fs read block (indir 1) malloc faeyyy~Nnuira2 2) malloc failed. **
read block (invIa?uy>_‹????sector 0
ce Descriptor u®u?u?a TKµe (null) Ser#: (null)
y?aua?yy?Keea device 0 -- Partition Type: (null)
_26?UK14_32lkMsys = 0MHz, PclkMsys = 52494216MHz
A Uyz, PclkPsys = 0MHz
yy?YX‚‚‚‚SS?‚‚‚‚‚onenand read 40000000 8600000 1400000a}ffs_unlink returning error: 0
returning error: 0
??•I•…‘I?.......... 0
nBlockErasures....... 52494216
nGCCopies............ 0
garbageCollections... 52494216
passiveGarbageColl'ns 4087376
u??|d an object to a null pointer directory
g to add an object to a non-directory
€*yaffs bug: yaffs_guts.h 0
undefined state 0
gsInUse 0 counted chunk bits 52494216
suspect sequence number of 0
tags 0 obj 320ff88 oh 3e5e50
yntId 0 obj->parent is NULL
0 header mismatch parentId 52494216 parentObjectId 0
?ft delete chunk 0
struck out
li•yynt block count wrong dev 0 count 0
0 count 52494216
blocks 0 (max is 1)
oz*"?(null) ”y libuP^>
parent pointer 00000000 which does not look like an object
nt is not a directory (type 0)
bj cuaNj 0 has illegaltype 0
etiringmeDirty block 0 state 0 ”y libuP^>
iled 0
a{ounk 0
ine 0 delete of chunk 0
ore eraased blocks
ocated block 0, seq 52494216, 4087376 left
ya!!!!!!!!!!!!!!!!
unk 0 was not erased
d needs retiring
yaffs write required d attempts
yuy9…µ•e non-directory
isCheckpointed 0
ipping checkpoint write
kpoint validity
checkpoint devicyyave exit: isCheckpointed 0
daft chunkId 0 for 52494216
ocate Tnodes
uld not add tnodes to managyyno?a non-file
ting chunk < 0 in scan
alid
lected block 0 with 52494216 free, prioritioyy?a,WEe?block 0 that has no chunks in use
0
d 0 52494216
has no?e«±‘?be erased
unks before 0 after 52494216
im!!! erasedBlocks 0 after try 0 blaiy'0_[Na?file 0
mediate deletion of file 0
space during cache write
Could not allocatycNa)checkpoint objects
ruct size 0 instead of 0 ok 52494216
ead object 0 parent 52494216 ty?}ayoytore exit: isCheckpointed 0
fs: yaffs_GutsInitialise()
ice
ry problems: chunk size 0,a|: device already mounted
chunk group too large
checkpoint
only for YAFFS2!n{k index!
Block scanning block 0 state 0 seq 52494216
canning block 0 has bad sequence number?|i?written block 0 being set for retirement
ot make object for object 0 at chunk 52494216 during scan
?Y…rds ends
ntstartblk 0 intendblk 0...
on block 0 was not highest sequence id: block seq yuotialise() done.
s.c,v 1.52 2007/10/16 00:45:05 charles Exp $nknowncanningty?iting chunk 0 tags 52494216 4087376
g with no tags
affs_nand.c,v 1.7 2007/02/14 01:09:06 wookey Exp $ilableot block: start: blocks 0 next 0
h: block 0 oid 52494216 seq 0 eccr 52494216
pt block 0
…N????checkpt block 0
s
fer nand 0(52494216:4087376) objid 0 chId 52494216
t byte count 0
~E?‚SO‚EO‚????*•a?Exp $_MarkNANDBlockBad 0
nandmtd2_ReadChunkWithTagsFromNAND chunk 0 data 00000000 tags 0320FF88
_QueruIAyy 0 data 0320FF88 tags 00000000
at (null):52494216/4()!
G!/02/14 01:09:06 wookey Exp $?oyofor[Yz??chunk 0:0
ixed on chunk 0:0
error fix performed on chunk 0:1
~gd on chunk 0:0
mtd ecc error fix performed on chunk 0:1
>mtd ecc error unfixed on chunk 0:1
chunkaau?g<0
,v 1.9 2007/02/14 01:09:06 wookey Exp $needed but not set
u•
ARP Retry count exceeded; starting again
ss not given
yyn?= 0 (0x320ff88)
tluoo largeagicoot filya®’ Size is 0x0 Bytes = lx
ed; starting again
MB received
is too long (0 - max: 0) - truncated
Nameng vendor optional boot file
nBOOTP broadcast 0
ARP broadcast 0
2lX00320FF88.imga NFS from server ename '(null)/”y libuP^>'.i.'2?±•?lookup fail
MMC Device 0 not found
bl len failed
mmc r}y_y‘?
XT_CSD on a possible high capacity card. Card will be ignored.
le to read EXT_CSD, performance might su?n modes.
r 00000000init fail!
HSMMC0nnel 0
k neve?y?N?bit(s).
iting for status update.
during transfer: 0xx
mc: ^as}{asesize: 0x00000, numblocks: 0000]
Attempting to recover from uncorrectable read
L 2.65/3.3ND(null) 52494216MB 4V 16-bit (0x00)
n = 0x0000
timeout!ctrl=0x0000 intr=0x'?yynUE…I•e Unaligned address
ngth not block aligned
ase: Failed erase, block 0
nd_bbt_read_oob:0A|u?cg
olock: Attempt read beyond end of device
le_read_ops_nolock: Attempt read beyond end of devic}YY?to read beyond end of device
_oob_nolock: read failed = 0x0
e_oob_nolock: Attempted to start write outsy>>Attempted to write past end of device
ob_nolock: write failed 0
d_write_ops_nolock: Attempt write to past<UuyAI}??±??*e write filaed 0
tatus = 0x0
ma_transfer: DMA error!
nd_set_boundary: Invalid bound?uydset_boundary: Please erase blocks before boundary change
nd_set_boundary: boundary locked
flexonenand_set_boundary: Cxang^yy}‰?O?‘…Eae Failed PI write for Die 0
WN DEVICE ID!!!
rning - OneNAND read mode: async.
an(): Can't allocate?onyy?n_scan_bbt: Out of memory
or bad blocks
t 0x00000000
bbt: Can't scan flash and builduyA•x
rx crc error
error
big
ut
m9000 novooN‚‚O’O??????in 8 bit mode
00: Undefined IO-mode:0x0
02x:00:320ff88:3e5e50:x:00
lish link
…?a args (max. 0) **
efined
wn command '(null)' - try 'help'
yA«µ‰•E)Empty Script
ge format for autoscript
ting script at Aao®,.B•…‘•E?must be present
= 0x00000000
_paramsartethaddr =ip_addryi??N•?NOE•Unknown Imageget_format
x --------
bootm_low:
o)et = 0x00000000
g init Ramdisk from Legacy Image at 00000000 ...
i component Legacy Image at lx ...
ip2ippressedilesystem.W?‘…±??•Standalone Programat_dthaIntel x86kuperHarcckfinR32NetBSDotoO0x0
start application at address 'addr'
- start application at address 'addr'
passing ?yyy?Jµ…?•?at 00000000 ...
Bad Magic Number
Bad Header Checksum
CRC
rmt!
wycompressionData Size: 0 Bytes = 8x
Entry Point: x
xotgcture 0x0
Image Type for (null) command
t for (null) command
kernel image!
unknown yor overwrite error - must RESET board to recover
ompression type 0
RNING: legacy format multi component imagc?iE…?I™•EE????control to NetBSD stage-2 loader (at address 00000000) ...
sferring control to RTEMS (at address 00000000e ...
?•‘?in memory
passing arguments 'arg ...'; when booting a Linux kernel,
'arg' can be the address of an initrd image
yyi - print header information for application image
..]
- print header information for application image startincoa?anwmber, header and payload checksums)
sages found in flash
information about all imageo w|u?O??? Cache is (null)
Cache is (null)
le or disable instruction cache
on, off]
- enable or disqbuyuy~a‰±•?data (writethrough) cache
ilable devices:
le devices and inf?year (null) @ 0x0320ff88 (4087376 bytes)
ot of VxWorks image at address 0x08lx ...
MAC address not cooyoyne (@ 0x0): ”y libuP^>
Starting vxWorks at 0x00000000 ...
terminated
n at 0x00000000 ...
?X–•II?of ELF image.
vxWorks from an ELF image
ess] - load address of vxWorks ELF image.
u…ENu? **
4 **
0 ....
boot file definedua?o2.$B*aA•?N?"U-Boot")
s 0:52494216 **
or disk - (null) 52494216:4087376 **
** Unable to read "(null)" from ao?y?~efault /)
art]> [directory]
- list files from 'dev' on 'interface' in a 'directory'
2load-uynye+‘?binary file 'filename' from 'dev' on 'interface'
to address 'addr' from ext2 filesystem
?boundary
sector precedes start sector
ddress not on sector boundary
r: cannot span across banks whayi~?N?on sector boundary
nd address (0x00000000) not in flash!
# 0
ification
—*M!?type
Erased 0 sectors
e Flash Bank # 0
rase Flash Sectors 0-d in Bank # zu # 0:a?~ks
flinfo N
- print information for FLASH memory bank # N
- erase FLASH memory
FLASH froio?N?w/addr 'start'+'len'-1
erase N:SF[-SL]
- erase sectors SF-SL in FLASH bank # N
erase bank N
- erase FLASH bank # N
eyoouusN…EN?end
- protect FLASH from addr 'start' to addr 'end'
protect on start +len
- protect FLASH from addr 'start' to eiu??r)protect on bank N
- protect FLASH bank # N
protect on all
- protect all FLASH banks
protect off start end
- maogyy? 'start' to end of sect w/addr 'start'+'len'-1 wrtable
protect off N:SF[-SL]
- make sectors SF-SL writable in FLASH bank # Nuu|?itable
nknown operator '(null)'
Invalid data width specifier
=<= true/f}y?grror when dumping path: , (null)
Writing value (0) 320ff88 times to (null)... file (null)
lsotal Siuy?E?binary (ymodem) download to 0x00000000 at 52494216 bps...
# Ready for binary (kermit) download to 0xX at 0 bps...
ary (k}o}?^X
## Last Load Addr = 0x00000000
## Total Size = 0xlX = 0 Bytes
echoxuc??•) load S-Record file over serial line with offset 'off'
oadbnary file over serial line (kary?n'aaud'
file over serial line (ymodem mode)
ress: 0x00000000
r 00000000 ... 0320ff88 ==> 003e5e50
X
ength ???
sh... (0x00000000) != word at 0x00000000 (0x8lx)
8lx (0x0000) != ha|yyal of d (null)”y libuP^> were the same
08lx:d - memory display
.b, .w, .l] address [# of objects]
- memory displament address
- memory modify (constant address)
s
- memory modify, read and keep address
yy?, .w, .l] source target count
- copy memory
[.b, .w, .l] addr1 addr2 count
- compare memory
yIu)address offset
ss offset for memory commands
base off
- set address offsat ow[¬–}?™}?‰©•?NI) - loop on a set of addresses
t [end [pattern]]]
- simple RAM read/~y?os _decimal_ !!!)
Device: (null)
r ID: 0
0
: 0
MMC read: dev # d, block # 0, count 52494216 ...
e: dev # 0, block # d, count 0 ... A52494216u???X–?blk# cnt
mmc write <device num> addr blk# cnt
mmc rescan <device num>
mmc list - list available devices
ping failed; host aiae…?•?at addr 0x00000000 ...
pa network using BootP/TFTP protocol
ilename]
yarpbootrarpboot- boot image via network using RARP/TFTP protocol
CP client to obtain IP/boot params
ypingAddress
nt to (null)...
illegal character '=' in variable name "(null)"
_R
‰?EN)0 bytes
t environment variables
of all environmenta~Xonment variables
me value ...
- set environment variable 'name' to 'value ...'
setenv name
- delete environment variableozymmands in an environment variable
the commands in the environment variable(s) 'var'
lock a ?*II=Ie 0 length is not block aligned
te (0 blocks):
0x0 is skipped.
ne----ofs=0x0,len=xyIx0,len=0x0,retlen=0x320ff88,addr=0x0,oob=0x320ff88
a read (0 blocks):

s' is not a number
e (0x0) exceede|yy…?•?00000000 dump:
02x 00 320ff88 3e5e50 x 00 320ff88 3e5e50 01 00 320ff88 3e5e50 01 x 00 320ff88
x 00 320ff88 &?ua"…N…?-- 0%.ROR: Write failed 0x0, 0 at 0x00000000
s: y failed 0x0, 52494216
Read/Write test failed at 0x0
ittenNOT ma?yyu?y - show available OneNAND devices
onenand bad - show bad blocks
onenand read[.oob] addr off size
onenand write[.oob] addr off om?ung bad blocks.
onenand write.yaffs addr off size - read/write `size' bytes starting
at offset `off' to/from memory address `aday??' bytes from
offset 'off' (entire device if not specified)
onenand dump[.oob] off - dump page
onenand markbad off [...] - maryur<dNW to transmit data
lize USB device and ready to receive for Windows server (specific)
dress]
uqv‚…EN)8lx extract a part of a multi-image
addr part [dest]
- extract uxy?y ?Ea?'help' without arguments for list of all known commands
o monitor version
?test like /bin/sh
- test functionality
- exit script
onality
or<the monitor commands.
Without arguments, it prints a short usage message for all commands.
To get detailed help information vK
±?…I?for 'help'
In: ces available!
vailable!
rr: ces avaeix?oA•x,ENV_SIZE=0x0
default environment is too large
ng - bad CRC, using default environment
out writuuy?*WEN?and/or end address not on sector boundary
f Flash
f Flash
Programming Error
osyyqted
IFS"e is a global environment variable with the same name.
variablenknown cyyuyUEaRhiledoHUB (0) reached
USB Devices, max=0
RROR: ~ua}yc>•I?E?AN?E?too short (expected 0, got 52494216)
et port 0!?
SB device not responding, giving up (status=X)
yW"•U??•?descriptor short read (expected 0, got 52494216)
set default configuration len 0, status 320FF88
mu(?(xyzModem - (null) mode, 52494216(SOH)/0(STX)/52494216(CAN) packets, 0 retries
ksum errormingi?•1A .. 0, 52494216 lx 0x0 0x320ff88 0, 52494216 er.. 0, 52494216 l.. 0, 52494216 0, ||???…E‘)ialize moviNAND and show card info
movi read {u-boot | kernel} {addr} - Read data from sd/mmc
movi write {fw?iy??N™I?data from sd/mmc by size
movi write rootfs {addr} [bytes(hex)] - Write rootfs data to sd/mmc by size
movi read {sector#} {ry|yur} - instead of this, you can use "mmc write"
Android image downloading.
ad' buttiiytzaIN•µ?image installation.
stem image(0 byte) installation.
nstallation.
y|e) installation.
Start uboot image installation.
0 byte) installation.
age}0> - Install zimage image for Android
insdroid ramdisk - Install ramdisk image for Android
insdroid system - Install system imay}<y?a- Make bootable SD card with uboot
ition table on OneNAND]
me='(null)' art=N/A ) and sw ecc for partition '(null)'
ese flags
Adding partitions from environment
STBOOT syyuns…µ•?for '(null)'
r:FASTBOOT no closing c found in partition name
FASTBOOT partition name is too long
y?Eµ…N???)ions!t 0x00000000, size 0xx, flags 0x00000000
ty timeout 0 seconyet}cted
s set of 0 bytes finished
noring
ot?g:.s?
erase partitionion '(null)' erased
adf 0 bytes
FAILdata ?yRyErROR : bootting failed
hould reset the board
FAILinvalid boot imagewnloadedILimage too large foryI?•‘) failed : (null)
rtition '(null)' saveenv-ed
nknown OEM commandition: (null), File: ”y libuP^>/yyyay?e

People, help me somebody unbrick Dropad A8X, please !!!

Helter2 said:
People, help me somebody unbrick Dropad A8X, please !!!
Click to expand...
Click to collapse
I had exactly the same (Dropad A8X) - and many with us as I read on the DX forum and other places ... however, I managed to flash new firmware ...
Here is the description:
slatedroid.com/topic/19685-dropad-a8x-hardware/page__gopid__255906#entry255906
Great thanks to Adam and especially Rebellos for his fantastic hack.
Please read my story completely as I was just to impatient and messed it up after all (if any one can be of any assistance as how to go further .
However, the method lets you flash new firmware using Odin or Adam's One-Click tool.

[DEV][HOWTO] Extracting stock firmware files from .tot files

Hello everyone!
First off:
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE WHILE USING ANY OF THE INFORMATION LOCATED BELOW. IF YOU DO NOT UNDERSTAND WHAT IS BEING DONE, PLEASE DO NOT TRY ANYTHING DONE HERE!
This is still in a VERY basic phase. I am not sure how helpful it will be, but currently, I have been able to extract some of the smaller partitions from the AT&T firmware file.
Starting off, when LGNPST is used to image a phone, it creates a log file in C:\LG Electronics\LGNPST\Models\LOG\ For example, mine was called LS970Log_COM5.log. We are really only interested in one part of this file, located close to the bottom when the phone is actually being imaged. It should look something like this:
0Download mode locking
0Download : PrimaryGPT 0x 0 Size: 0x 512Kb, File Offset: 0x 100000
0 3.182994E-313mmc Init
0Partition Count : 35======================================================
0======================================================
0Download : modem 0x 800000 Size: 0x 54272Kb, File Offset: 0x 180000
0Download : sbl1 0x4800000 Size: 0x 512Kb, File Offset: 0x3680000
0Download : sbl2 0x4880000 Size: 0x 512Kb, File Offset: 0x3700000
0Download : sbl3 0x4900000 Size: 0x 1024Kb, File Offset: 0x3780000
0Download : aboot 0x4b00000 Size: 0x 512Kb, File Offset: 0x3880000
0Download : rpm 0x4b80000 Size: 0x 512Kb, File Offset: 0x3900000
0Download : boot 0x5000000 Size: 0x 7168Kb, File Offset: 0x3980000
0Download : tz 0x6800000 Size: 0x 512Kb, File Offset: 0x4080000
0(null)kip misc Partition
0Download : system 0xb000000 Size: 0x 131072Kb, File Offset: 0x4900000
0Download : system 0x13000000 Size: 0x 512Kb, File Offset: 0xc900000
0Download : system 0x1325e000 Size: 0x 129024Kb, File Offset: 0xc980000
0Download : system 0x1b1fd000 Size: 0x 129536Kb, File Offset: 0x14780000
0Download : system 0x2325e000 Size: 0x 129024Kb, File Offset: 0x1c600000
0Download : system 0x2b1fd000 Size: 0x 129536Kb, File Offset: 0x24400000
0Download : system 0x3325e000 Size: 0x 129024Kb, File Offset: 0x2c280000
0Download : system 0x3b1fd000 Size: 0x 129536Kb, File Offset: 0x34080000
0Download : system 0x4325e000 Size: 0x 129024Kb, File Offset: 0x3bf00000
0Download : system 0x4b1fd000 Size: 0x 76800Kb, File Offset: 0x43d00000
0Download : system 0x53000000 Size: 0x 512Kb, File Offset: 0x48800000
0Download : system 0x5b000000 Size: 0x 512Kb, File Offset: 0x48880000
0Download : system 0x63000000 Size: 0x 512Kb, File Offset: 0x48900000
0Download : persist 0x7a800000 Size: 0x 4608Kb, File Offset: 0x48980000
0Download : recovery 0x8b000000 Size: 0x 8192Kb, File Offset: 0x48e00000
0Download : BackupGPT 0xab380000 Size: 0x 512Kb, File Offset: 0x49600000
0
*********************************************************************************************
Click to expand...
Click to collapse
What do we see that is important here? Image sizes and offsets for data in the file! For example, lets take the boot partition.
0Download : boot 0x5000000 Size: 0x 7168Kb, File Offset: 0x3980000
Click to expand...
Click to collapse
We have a offset of 0x3980000 and a size of 7168Kb. That converts to an equivalent of an offset of 60293120 bytes and a size of 7340032 bytes (I really hope I got that right. As I'm sitting here writing this, I'm thinking of how many different ways I could have messed up that calculation...)
Here, I am using dd on linux in order to separate the partitions from the binary file, but it can be done using equivalent tools on windows.
$ dd bs=1 skip=60293120 count=7340032 if=LGE970AT-00-V10o-ATT-US-SEP-29-2012+0.tot of=boot.img
Click to expand...
Click to collapse
Basically, what I am doing here is copying 7340032 bytes, starting at byte 60293120, from the .tot file to boot.img.
Now, lets check out the backups made with FreeGee when you unlock, to see if it matches with what was actually written to the phone. In order to see if they are equal, we need to trim the backup, because the backup that is taken is actually of the entire partition, not just the actual data.
$ dd bs=1 count=7340032 if=boot-att-backup.img of=boot-att-backup-trimmed.img
Click to expand...
Click to collapse
This is doing basically the same, starting at the first byte, copying 7340032 bytes to boot-att-backup-trimmed.img. This is just making sure you only get the same amount of data that was written.
Now, If of course we want to see if the data is actually the same, so we will also use the diff command, also found on linux, and I'm sure is also available on windows.
$ diff -s boot.img boot-att-backup-trimmed.img
Click to expand...
Click to collapse
If both files are identical, which means everything was done correctly, this should result in the output "Files boot.img and boot-att-backup-trimmed.img are identical", which it does! (The -s flag makes diff report identical files.)
So, now that we know that we can successfully extract the boot partition, I also tried this with the aboot partition, and it worked as well! I have not had success extracting the system partition yet, as it is split up into several partitions. I was hoping that someone with more knowledge could piece together a system image. Enjoy

SnowLeopardJB said:
Hello everyone!
First off:
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE WHILE USING ANY OF THE INFORMATION LOCATED BELOW. IF YOU DO NOT UNDERSTAND WHAT IS BEING DONE, PLEASE DO NOT TRY ANYTHING DONE HERE!
This is still in a VERY basic phase. I am not sure how helpful it will be, but currently, I have been able to extract some of the smaller partitions from the AT&T firmware file.
Starting off, when LGNPST is used to image a phone, it creates a log file in C:\LG Electronics\LGNPST\Models\LOG\ For example, mine was called LS970Log_COM5.log. We are really only interested in one part of this file, located close to the bottom when the phone is actually being imaged. It should look something like this:
What do we see that is important here? Image sizes and offsets for data in the file! For example, lets take the boot partition.
We have a offset of 0x3980000 and a size of 7168Kb. That converts to an equivalent of an offset of 60293120 bytes and a size of 7340032 bytes (I really hope I got that right. As I'm sitting here writing this, I'm thinking of how many different ways I could have messed up that calculation...)
Here, I am using dd on linux in order to separate the partitions from the binary file, but it can be done using equivalent tools on windows.
Basically, what I am doing here is copying 7340032 bytes, starting at byte 60293120, from the .tot file to boot.img.
Now, lets check out the backups made with FreeGee when you unlock, to see if it matches with what was actually written to the phone. In order to see if they are equal, we need to trim the backup, because the backup that is taken is actually of the entire partition, not just the actual data.
This is doing basically the same, starting at the first byte, copying 7340032 bytes to boot-att-backup-trimmed.img. This is just making sure you only get the same amount of data that was written.
Now, If of course we want to see if the data is actually the same, so we will also use the diff command, also found on linux, and I'm sure is also available on windows.
If both files are identical, which means everything was done correctly, this should result in the output "Files boot.img and boot-att-backup-trimmed.img are identical", which it does! (The -s flag makes diff report identical files.)
So, now that we know that we can successfully extract the boot partition, I also tried this with the aboot partition, and it worked as well! I have not had success extracting the system partition yet, as it is split up into several partitions. I was hoping that someone with more knowledge could piece together a system image. Enjoy
Click to expand...
Click to collapse
would it be possible to guide me through this from the very beginning? i want to start cooking for this device, but i need a legit flashable Rom. Please and Thank you.

You are most likely better off just pulling a system image off your device. So, if you are rooted, you can pull your system with something like this:
# busybox tar cf /sdcard/system.tar /system/*
Click to expand...
Click to collapse
That should give you all of the system files all together in a tar archive on your internal sdcard.

I messaged you, but is there any way to use this on the Sprint version to create a flashable .zip?

sorry about the resurrection,
but has there been any progress made on this? More of a curiosity, then anything.
Thanks

[Q] Flash by apx

Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you

APX is a hardware defect, no solution for that at the moment....yes there is one ! Replace the mainboard

THe thing is I switched the tegra IC and now its stuck on APX but I can Use APX only need the files.
Nothing like the known problem...

Ow oke......good luck then

Thanks
Any one knows a way to full flash by apx ?"

Maybe you can look by posts from nitrous2 or TripnRaver......they know more about APX. At least in general so it might be helpful

Some one any ideas ?

Trip has released drivers for apx mode however you will need the sbk for the one x in order to flash anything which is something that nobody except HTC have
Sent from my HTC One X using xda app-developers app

deadwolf666 said:
Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you
Click to expand...
Click to collapse
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!

Bugz! said:
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!
Click to expand...
Click to collapse
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.

Thanks for the reply !
I have been able to communicate with the device from the second link you provided, but it gives errors when trying to repartition it.
I will post the errors first thing in the morning as I don't have the device with me now to regenerate it
I've read on so many forums that the mainboard may be fried as in it needs to be replaced, but then again I've proven forums wrong before when it comes to unknown errors and situations, so I'm hoping they're wrong again.
I'm curious, how far did you go with your device? where did you stop and give up on it?

deadwolf666 said:
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.
Click to expand...
Click to collapse
Ok here's my log:
Code:
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>nvflash -
-blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile fl
ash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d256462581c11
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>pause
Press any key to continue . . .
Did you get this far? I don't know what this error means as I don't have any experience with nvflash
I'll be looking into the error code, just wanted to share this in case someone is following the footsteps

HTC One X Boot Repair (APX Mode can removed)

Htc One x dead boot repair can be fixed with attched file including sbk
All credits goes legija from riff box team
Select the device 16GB or 32GB properly.
https://drive.google.com/file/d/0B2bytCPhOCX4ZzI1bm1hdHB2d00/edit?usp=sharing

Coolmfarshard said:
Htc One x dead boot repair can be fixed with attched file including sbk
All credits goes legija from riff box team
Select the device 16GB or 32GB properly.
https://drive.google.com/file/d/0B2bytCPhOCX4ZzI1bm1hdHB2d00/edit?usp=sharing
Click to expand...
Click to collapse
this is the error go_32g.bat
Script error:
....
....
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass sto
rage (code: 9) message: nverror:0x8 (0x9) flags: 0

Can you show your device manager which drivers is installed
Normally if the nvidia drivers mismatch giving this error
Sent from my SM-N7505 using XDA Free mobile app

Coolmfarshard said:
Can you show your device manager which drivers is installed
Normally if the nvidia drivers mismatch giving this error
Sent from my SM-N7505 using XDA Free mobile app
Click to expand...
Click to collapse
my drivers is trip and droid drivers can you give me other drivers?

Can he post the drivers used?

Thant said:
my drivers is trip and droid drivers can you give me other drivers?
Click to expand...
Click to collapse
I also have the same error as you and also have the same driver, so, what driver we need ¿?
Thx

Good News!
Hello mates,
I have good news, I have resurrected my HTC!
After many attempts, I succeeded ...
First of all, the script is incomplete, you always need the system.img ficherp that you have to get from your RUU, so I've gotten, installing drivers above.
Here you have a test script:
Nvflash v1.2.57794 started
Using blob v1.1.57813ata\RoeD<Ì6↔
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d2d422434000a
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 DIA please wait.. done!
Formatting partition 6 BIF please wait.. done!
Formatting partition 7 GP1 please wait.. done!
Formatting partition 8 WLN please wait.. done!
Formatting partition 9 WDM please wait.. done!
Formatting partition 10 RCA please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 SOS please wait.. done!
Formatting partition 13 PG1 please wait.. done!
Formatting partition 14 PG2 please wait.. done!
Formatting partition 15 PG3 please wait.. done!
Formatting partition 16 SIF please wait.. done!
Formatting partition 17 SP1 please wait.. done!
Formatting partition 18 RV1 please wait.. done!
Formatting partition 19 APP please wait.. done!
Formatting partition 20 CAC please wait.. done!
Formatting partition 21 ISD please wait.. done!
Formatting partition 22 UDA please wait.. done!
Formatting partition 23 DUM please wait.. done!
Formatting partition 24 MSC please wait.. done!
Formatting partition 25 RFS please wait.. done!
Formatting partition 26 DLG please wait.. done!
Formatting partition 27 PDT please wait.. done!
Formatting partition 28 GPT please wait.. done!
done!
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
sending file: board_info.bin
- 20/20 bytes sent
board_info.bin sent successfully
sending file: WDM.img
/ 262144/262144 bytes sent
WDM.img sent successfully
sending file: boot.img
/ 4417536/4417536 bytes sent
boot.img sent successfully
sending file: recovery.img
/ 5974016/5974016 bytes sent
recovery.img sent successfully
sending file: SIF.img
- 6144/6144 bytes sent
SIF.img sent successfully
sending file: system.img
| 1029059140/1029059140 bytes sent
system.img sent successfully
sending file: userdata.img
\ 44118872/44118872 bytes sent
userdata.img sent successfully
Once complete, the phone reboots itself.

I would like to try this tool but my problem is how on earth do I get the phone in APX mode.
See problems below why I would like to try it.
My phone stays 5 minutes black when I turn it on.
Then I have 5 minutes white screen with htc logo.
After this 10 minutes wait the phone finally starts booting and seems to work ok.
Sometimes USB works when it is on and sometimes no USB when it is on.
G-sensor is not working
Compass is not working
Fastboot USB allways seem to work.
So anybody any idea how I get it in APX mode?
Greetings from someone with a weird phone.

celica7 said:
hello i try to recover one htc one with the same scrip but i get one error
HTML:
C:\adb>go_32g.bat
C:\adb>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105
--configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813100110C┘¾Ñßì
rcm version 0X0
Command send failed (usb write failed)
C:\adb>pause
Presione una tecla para continuar . . .
can you help me
Click to expand...
Click to collapse
Same here .. anyone find the solution

some help, i have same error, but first can get error not found system.img.
now get that error
C:\adb>go_32g.bat
C:\adb>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105
--configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813100110C┘¾Ñßì
rcm version 0X0
Command send failed (usb write failed)
or
C:\adb>go_32g.bat
C:\adb>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105
--configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813100110
(hang up)
---------- Post added at 09:02 PM ---------- Previous post was at 08:54 PM ----------
sending file: system.img
| 1029059140/1029059140 bytes sent
system.img sent successfully
not forme simply not found

without apx drivers this whole thread and nvflash tool is useless

shakeelajmal said:
without apx drivers this whole thread and nvflash tool is useless
Click to expand...
Click to collapse
I give you the link for the apx drivers in other your post the thread is important and with sure not useless

Anyone else have any success with this? I have installed APX driver, When I run go_32G
I get Using blob v1.1.57813\Kevine↕▀█eF
rcm version 0X0
Command send failed (usb write failed)

wigankev said:
Anyone else have any success with this? I have installed APX driver, When I run go_32G
I get Using blob v1.1.57813\Kevine↕▀█eF
rcm version 0X0
Command send failed (usb write failed)
Click to expand...
Click to collapse
You need to put the phone into the correct mode for accepting the NVFlash stuff I think? With the phone connected to USB press and hold the volume down and power button until you hear the PC make the sound of a USB device disconnecting and then reconnecting - takes about 7 seconds I think? (however mine isn't doing anything now as I think the battery is completely drained....).
If you have the APX drivers installed correctly it should appear as 'NVIDIA USB Boot-recovery driver for Mobile devices'. You should then be able to run the 'go_32g.bat' script which should completely wipe and restore your device as per RaikoGP post.
Unfortunately I awas getting the same error as thant:
.....
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass sto
rage (code: 9) message: nverror:0x8 (0x9) flags: 0
Click to expand...
Click to collapse
It isn't even recognised by the PC now as I think the battery is completely drained and I think it is beyond repair and needs a new motherboard though...
Andy
---------- Post added at 12:04 PM ---------- Previous post was at 11:50 AM ----------
Just managed to get it recognised by the PC again and this is output I get from the 'go_32g.bat' batch file:
rcm version 0X30001
System Information:
chip name: unknown
C:\\RD_release(with_sbk)without sis>go_32g.bat
C:\RD_release(with_sbk)without sis>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813es (x8↕]4½↕±
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d18844a4bf408
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
C:\RD_release(with_sbk)without sis>pause
Press any key to continue . . .
Click to expand...
Click to collapse
If I try to run the batch file again it just hangs at this:
C:\\RD_release(with_sbk)without sis>go_32g.bat
C:\RD_release(with_sbk)without sis>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813es (x8↕]4½↕±
Click to expand...
Click to collapse
unless I put the device in the correct 'mode' by holding the volume down and power buttons for at least 7-seconds:
Any help?
Andy

ADB100 said:
You need to put the phone into the correct mode for accepting the NVFlash stuff I think? With the phone connected to USB press and hold the volume down and power button until you hear the PC make the sound of a USB device disconnecting and then reconnecting - takes about 7 seconds I think? (however mine isn't doing anything now as I think the battery is completely drained....).
If you have the APX drivers installed correctly it should appear as 'NVIDIA USB Boot-recovery driver for Mobile devices'. You should then be able to run the 'go_32g.bat' script which should completely wipe and restore your device as per RaikoGP post.
Unfortunately I awas getting the same error as thant:
It isn't even recognised by the PC now as I think the battery is completely drained and I think it is beyond repair and needs a new motherboard though...
Andy
---------- Post added at 12:04 PM ---------- Previous post was at 11:50 AM ----------
Just managed to get it recognised by the PC again and this is output I get from the 'go_32g.bat' batch file:
rcm version 0X30001
System Information:
chip name: unknown
If I try to run the batch file again it just hangs at this:
unless I put the device in the correct 'mode' by holding the volume down and power buttons for at least 7-seconds:
Any help?
Andy
Click to expand...
Click to collapse
APX doesn't allow you to get into Hboot, from a lot of searching, looks like motherboard is dead, already bought a new phone

RaikoGP said:
Hello mates,
I have good news, I have resurrected my HTC!
After many attempts, I succeeded ...
First of all, the script is incomplete, you always need the system.img ficherp that you have to get from your RUU, so I've gotten, installing drivers above.
Here you have a test script:
Nvflash v1.2.57794 started
Using blob v1.1.57813ata\RoeD<Ì6
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d2d422434000a
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 DIA please wait.. done!
Formatting partition 6 BIF please wait.. done!
Formatting partition 7 GP1 please wait.. done!
Formatting partition 8 WLN please wait.. done!
Formatting partition 9 WDM please wait.. done!
Formatting partition 10 RCA please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 SOS please wait.. done!
Formatting partition 13 PG1 please wait.. done!
Formatting partition 14 PG2 please wait.. done!
Formatting partition 15 PG3 please wait.. done!
Formatting partition 16 SIF please wait.. done!
Formatting partition 17 SP1 please wait.. done!
Formatting partition 18 RV1 please wait.. done!
Formatting partition 19 APP please wait.. done!
Formatting partition 20 CAC please wait.. done!
Formatting partition 21 ISD please wait.. done!
Formatting partition 22 UDA please wait.. done!
Formatting partition 23 DUM please wait.. done!
Formatting partition 24 MSC please wait.. done!
Formatting partition 25 RFS please wait.. done!
Formatting partition 26 DLG please wait.. done!
Formatting partition 27 PDT please wait.. done!
Formatting partition 28 GPT please wait.. done!
done!
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
sending file: board_info.bin
- 20/20 bytes sent
board_info.bin sent successfully
sending file: WDM.img
/ 262144/262144 bytes sent
WDM.img sent successfully
sending file: boot.img
/ 4417536/4417536 bytes sent
boot.img sent successfully
sending file: recovery.img
/ 5974016/5974016 bytes sent
recovery.img sent successfully
sending file: SIF.img
- 6144/6144 bytes sent
SIF.img sent successfully
sending file: system.img
| 1029059140/1029059140 bytes sent
system.img sent successfully
sending file: userdata.img
\ 44118872/44118872 bytes sent
userdata.img sent successfully
Once complete, the phone reboots itself.
Click to expand...
Click to collapse
definitely right i did same and i got this
>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813nProgreÕ=Ù'¥
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d25783b242206
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 DIA please wait.. done!
Formatting partition 6 BIF please wait.. done!
Formatting partition 7 GP1 please wait.. done!
Formatting partition 8 WLN please wait.. done!
Formatting partition 9 WDM please wait.. done!
Formatting partition 10 RCA please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 SOS please wait.. done!
Formatting partition 13 PG1 please wait.. done!
Formatting partition 14 PG2 please wait.. done!
Formatting partition 15 PG3 please wait.. done!
Formatting partition 16 SIF please wait.. done!
Formatting partition 17 SP1 please wait.. done!
Formatting partition 18 RV1 please wait.. done!
Formatting partition 19 APP please wait.. done!
Formatting partition 20 CAC please wait.. done!
Formatting partition 21 ISD please wait.. done!
Formatting partition 22 UDA please wait.. done!
Formatting partition 23 DUM please wait.. done!
Formatting partition 24 MSC please wait.. done!
Formatting partition 25 RFS please wait.. done!
Formatting partition 26 DLG please wait.. done!
Formatting partition 27 PDT please wait.. done!
Formatting partition 28 GPT please wait.. done!
done!
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
sending file: board_info.bin
- 20/20 bytes sent
board_info.bin sent successfully
sending file: WDM.img
/ 262144/262144 bytes sent
WDM.img sent successfully
sending file: boot.img
/ 4417536/4417536 bytes sent
boot.img sent successfully
sending file: recovery.img
/ 5974016/5974016 bytes sent
recovery.img sent successfully
sending file: SIF.img
- 6144/6144 bytes sent
SIF.img sent successfully
sending file: system.img
- 1013466364/1013466364 bytes sent
system.img sent successfully
sending file: userdata.img
\ 44118872/44118872 bytes sent
userdata.img sent successfully
but device didn't reboot nor even boot no respond at all and after few hours i back and plug it into pc red light comes and pc know it as a htc device and show the storage but just for 4or 5sec then turns one screen always black...after 3 or 4 times with the same behaviors it back to the first situation nvida recover boot ( apx) tried to flash one more time it gives the first error....
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x8 (0x9) flags: 0
any help please ?

anyone revived this device using this nv drivers ?
any news ?

strongmen said:
anyone revived this device using this nv drivers ?
any news ?
Click to expand...
Click to collapse
one guy but he reported after few days it is again in apx mode.

is changing the battery necessary ?
Thant said:
one guy but he reported after few days it is again in apx mode.
Click to expand...
Click to collapse
is changing the battery necessary ?
after flashing more than 3 times using this nvflash tool what i had is just the the device disconnect after done and nothing happens and if plug again pc won't recognize until some time pass about 20-30min + trying combo power + vol.
any way what i did is putting the device in the freezer 2-5min after plug it into the pc the red led light and the pc recognize it as adb device but just for 4-5sec tried that 2 or 3 times and got mad so what i did is just taking the laptop close to the freezer so i could keep the device in the freezer while working (it might sounds strange or fool but reality ) cool so i can use fastboot command in order to lock the bootloader and flash a stock RUU tried many ways using RUU.exe manual command also soft (one click) all fail error battery low than 30% so lost hope from the freezer ...
the next step is taking the battery and charge it out side nice the pc show the device as an adb and battery full near to be 42000mv finally flashed a stock rom..after that the phone vibrate if turn on the red led shows but screen always black ... after awhile it shows in apx mode and back to the first situation.
so i daily flash with nvflash more than 5 times with no result.
could that be a hard problem (motherboard) ?

Someone know how to push to push recovery or .img/.bin files via Ubuntu?

Can someone tell me how to push recovery or .img/.bin files via Ubuntu?
Issue: When flashing Clodyg5 2.5 ATT was chosen instead of Tmobile
I have already search all the threads and forums unless I missed something. I have tried all the methods and only seems to be hope in Ubuntu
Here's what I have already tried so far:
1. KDZ and TOT methods and both fail.
2. I tried forcing the device into QHUSB 9008/ Test mode and using BoardDiag3.99c.exe and that also fails with the error displayed to put the device into Dload mode.
3. ADB with fastboot. Does not detect device even though it shows LGE Android device in device manager
4. Used Latest drivers
5. Used XP, Win 7 and Win 8 same results
6. What I can do is see the partitions in Ubuntu. I need the correct command to push the .bin/.img files extracted from the TOT or KDZ and push them via Ubuntu. I was able to do it to an SD Card to try to boot off of it as done for the G2. In other words I copied the bin and recovery to a micro sd and tried to boot off of it but nothing happened.
So this is as far as I can get in Ubuntu:
~$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
[email protected]:~# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sda: 41943040 sectors, 20.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 86525607-AEFC-47E3-A2D2-06EB166B5267
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 41943006
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 39845887 19.0 GiB 8300 Linux filesystem
5 39847936 41940991 1022.0 MiB 8200 Linux swap
[email protected]:~# gdisk -l /dev/sda1
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Disk /dev/sda1: 39843840 sectors, 19.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3FFEC32B-2D8F-483A-9325-437E5CC6AB8D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 39843806
Partitions will be aligned on 2048-sector boundaries
Total free space is 39843773 sectors (19.0 GiB)
Number Start (sector) End (sector) Size Code Name
[email protected]:~# gdisk -l /dev/sda2
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Main partition table overlaps the first partition by 32 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sda2: 2 sectors, 1024 bytes
Logical sector size: 512 bytes
Disk identifier (GUID): D87AD6B9-A79F-4AB6-9139-171BE2D5DDC4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 18446744073709551584
Partitions will be aligned on 2-sector boundaries
Total free space is 18446744073707458527 sectors (8.0 ZiB)
Number Start (sector) End (sector) Size Code Name
1 2 2093057 1022.0 MiB 8200 Linux swap
[email protected]:~# gdisk -l /dev/sda5
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Disk /dev/sda5: 2093056 sectors, 1022.0 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): 57A1286F-0AD3-467A-A46B-457AA89BC218
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2093022
Partitions will be aligned on 2048-sector boundaries
Total free space is 2092989 sectors (1022.0 MiB)
Number Start (sector) End (sector) Size Code Name
[email protected]:~#
I have already extracted the TOT and KDZ and have recovery.img just don't want to fully brick it.
Links I used as reference:
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/showthread.php?t=2600575

Issue resolved, please close this thread. Thanks to everyone who chimed in with their suggestions.

Develop Bugs

welcome