Related
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|uuoy uz?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 i yy???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.
yoY syA?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
y pingAddress
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.
we gingerbread guys need to get serious on this fricken flash counter, else we can't truely clone our SGYs.
reedit: by this time Doky has found it in bml15 and resets it in his galaxy tool app. ty !!
Kies knows about it and it has implications for asec stuff too.
manufacturing tried to keep the info on the flash counter's whereabouts a tightly guarded secret like some Bill Clinton sex affair, but now it is busted all out in the open ! <-- link
we gotta be able to reset that data to a fricken pristine state!
then we got a 100% CLONE !!
quote :
The flash counter and triangle state had to be stored somewhere. Everybody knew that ... You can dump and compare the entire /dev/block/mmcblk0 and you won't find a difference (you'll find a few unallocated and unused gaps, though).
on SGY mmcblk0 is the sd card, /dev/block/bml0!c = total internal NAND storage - which is what we are looking for. see: http://forum.xda-developers.com/showthread.php?t=1998471
however, the flash disk actually has two hidden boot partitions,
/dev/block/mmcblk0boot0 and
/dev/block/mmcblk0boot1
The MMC driver in the kernels used for Gingerbread did not present these partitions in the past, the MMC driver in the ICS kernel does.
Dump and compare the partitions and you'll have found them in no time.
Structure /dev/block/mmcblk0boot0 @ 0x00020000:
0x00020000 header magic: 32bit - 0x12340011
0x00020004 flash count: 16bit
0x00020006 future: 16bit - 0x0000
0x00020008 type: 16bit - 0x0000 unknown, 0x0001 custom (triangle), 0x0002 Samsung Official
0x0002000A name: max 16 chars
0x0002001A end: 16bit - 0x0000
The boot partitions are presented as readonly by default, but allowing modification is a simple matter of executing the following before writing the data:
### does not fullly apply to SGY ! other phones only !! ###
echo 0 > /sys/block/mmcblk0boot0/force_ro
A number of bytes trailing this structure also change between flashes and appear to be checksum related.
click Tags below for more related info !
neither I'm able to confirm nor negate, but I'm afraid the SGY have other storage areas.
and keep in mind, on SGSII this hidden device has appears only on the leaked beta ICS kernel. Moreover I don't see any good reason, why is it accessible under Android. Kies does not care about the bin counter. I was able to restore factory state with bin counter>0 and Kies recognized my devce as valid upgradeable. On the other hand, the bin counter is handled on the sbl runlevel, where kernel and android not yet loaded.
For further reference please see my research on the SGY partition system, decoded from the pit file:
Code:
[B]minor bml stl image[/B]
1 /bml1 /stl1 BcmBoot.img
2 /bml2 /stl2 sbl.bin
3 /bml3 /stl3 bl.bin
4 /bml4 /stl4 totoro.pit
5 /bml5 /stl5 BcmCP.img
6 /bml22 /stl6 param.lfs
7 /bml6 /stl7 boot.img
8 /bml7 /stl8 (boot backup)
9 /bml21 /stl9 system.img
10 /bml23 /stl10 csc.rfs
11 /bml24 /stl11 userdata.img
12 /bml8 /stl12 (efs)
13 /bml9 /stl13 sysparm_dep.img
14 /bml10 /stl14 HEDGE_NVRAM8_RF_LE.bin
15 /bml11 /stl15 (cal)
On much deeper details please see my spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0Arilp8uJromLdHdrdGpiZ2FSN3daRzRQMkIxR0pCZXc
Minor #12 and #15 is suspicious, might have some data, which not used by the OS, and not affected by ROM update packs.
This is good research, doky. I bookmarked your spreadsheet for future reference.
efs
Doky73 said:
12 /bml8 /stl12 (efs)
15 /bml11 /stl15 (cal)
Minor #12 and #15 is suspicious, might have some data, which not used by the OS, and not affected by ROM update packs.
Click to expand...
Click to collapse
efs is directly related to the SIM card file system, I take it.
"the /efs folder is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location."
<post deleted>
cal : calibration data
Doky73's SGY layout table: now, spot the flash counter
minor Start-offset --- End-offset ------ Size (hex) units ------- SIZE (bytes) -- BML --------- STL -- Internal name Image name ------ Description
01 0x00000000 0x00040000 0x00040000 001 000262144 /bml1 _/stl1 _bcm_boot BcmBoot.img Primitive boot loader
02 0x00040000 0x00240000 0x00200000 008 002097152 /bml2 _/stl2 _Loke sbl.bin Secondary boot loader
03 0x00240000 0x00440000 0x00200000 008 002097152 /bml3 _/stl3 _loke_bk bl.bin backup sbl
04 0x00440000 0x00480000 0x00040000 001 000262144 /bml4 _/stl4 _systemdata totoro.pit partition table
05 0x00480000 0x01100000 0x00c80000 050 013107200 /bml5 _/stl5 _Modem BcmCP.img modem/phone
06 0x01100000 0x01600000 0x00500000 020 005242880 /bml22 /stl6 _param_lfs param.lfs
07 0x01600000 0x01b00000 0x00500000 020 005242880 /bml6 _/stl7 _boot boot.img kernel & initramfs
08 0x01b00000 0x02000000 0x00500000 020 005242880 /bml7 _/stl8 _boot_backup - backup kernel & initramfs
09 0x02000000 0x10600000 0x0e600000 920 241172480 /bml21 /stl9 _System system.img ROM
10 0x10600000 0x12e00000 0x02800000 160 041943040 /bml23 /stl10 Cache csc.rfs CSC
11 0x12e00000 0x1f340000 0x0c540000 789 206831616 /bml24 /stl11 Userdata userdata.img data
12 0x1f340000 0x1f380000 0x00040000 001 000262144 /bml8 _/stl12 Efs - efs unique phone data
13 0x1f380000 0x1f3c0000 0x00040000 001 000262144 /bml9 _/stl13 sysparm_dep sysparm_dep.img
14 0x1f3c0000 0x1f400000 0x00040000 001 000262144 /bml10 /stl14 umts_cal HEDGE_NVRAM8_RF_LE.bin
15 0x1f400000 0x1f500000 0x00100000 004 001048576 /bml11 /stl15 cal - calibration data
note: not all /bml & /stl devices are visible, some of them not linked under the OS
------------------------------------------------------------
I guess, cloning all of minor 12 would be a mistake.
14 & 15 are sets of calibration data, probably for RF part (gsm radio)
mai77 said:
Darky's SGY layout table: now, spot the flash counter
Click to expand...
Click to collapse
Well, Darky is working on a custom rom for SGY???
Yep, we're saved!
Factory mode
also there is a difference between ODIN mode (via DOWN+HOME+POWER) and FACTORY MODE via USB jig 301KOhm.
makes a diff for displayed "official" vs. "custom" ROM
Any new ideas on this guys? I was wondering if this cant be hacked via the .pit file?
I wish I could find this damn partition and forcefully reset this
Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100
Princeomi said:
Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100
Click to expand...
Click to collapse
Are you sure?where did uou get that info??
Sent from my GT-S5360 using xda premium
Princeomi said:
Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100
Click to expand...
Click to collapse
Very interesting bro
Hmmmm.... That actually does make sense to me, because due to screen size limitations, I can't see the numbers carrying on into infinity. As it is when it gets to the teens, it starts screwing up the text on screen, so an ultimate limit would make sense.
I guess besides the fact that it voids your warranty if anybody had to see it from Samsung, I guess it does nothing but just annoy you cause you cant reset it
Not sure if I will try your method Princeomi but I will keep that in mind
---------- Post added at 08:23 PM ---------- Previous post was at 08:09 PM ----------
What I don't understand though is why does the USB jig not reset it on our phones but it does on the SGS2? I just watched a vid on you tube and Odin mode looks exactly the same as it does on our phones.
I read it in the news section of XDA, never tried it though as I am on zero
Sent from my GT-S5360
NanoSurfer said:
[/COLOR]What I don't understand though is why does the USB jig not reset it on our phones but it does on the SGS2? I just watched a vid on you tube and Odin mode looks exactly the same as it does on our phones.
Click to expand...
Click to collapse
actually it does not resets neither on SGSII. Only on some old/initial ROMs. The SBL has been modified by Samsung, to prevent users resetting the counter simply by USB JIG. To reset my SGSII's counter, I have to downgrade the SBL. (or upgrade to ICS , there's an other method, based on a new feature of the 3.x kernel)
Sent from my SGSII using Tapatalk 2 & Swype
Doky73 said:
actually it does not resets neither on SGSII. Only on some old/initial ROMs. The SBL has been modified by Samsung, to prevent users resetting the counter simply by USB JIG. To reset my SGSII's counter, I have to downgrade the SBL. (or upgrade to ICS , there's an other method, based on a new feature of the 3.x kernel)
Sent from my SGSII using Tapatalk 2 & Swype
Click to expand...
Click to collapse
Interesting Sir Doky
I kinda figured that Samsung would wise up to that trick sooner or later. BTW what you think of the max count trick?
doky's SGY partn table from above attached
remember,
dd if=/dev/block/bml0!c
gives you the complete NAND storage 501 MB file on SGY:
so this shell cmds gave me a 501 MB file which is probably the NAND dump :
adb shell
su
stop
dd if=/dev/block/bml0!c of=/sdcard/bml0c.outfile
## wait 2 minutes to finish
start
## wait 30 sec
I believe, the last 1 MB of the file is junk data or duplicate
bml0!c dump
the dump says:
OneNAND boot rev. 0.2
+cboot_uart_speed_handshake(0x%x)
Set Baudrate to 115k.
Set Baudrate to 230k.
¼:”Set Baudrate to 460k.
Set Baudrate to 921k.
Set Baudrate to 3m.
Invalid Baudrate, try again.
cboot_uart.c
assert at line %d in %s -cboot_uart_speed_handshake
###################################
Secondary Bootloader v3.1 version. Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: %s %s / %s %s TOTORO REV 03 Jan 14 2012 07:01:28
%s: debug level 0x%x %s: debug level low! PUMR: %d FOTA_BOOT FOTA_UAUP PUMR: 0x40 (AP only boot mode) loadmodem loadCPDATA loadkernel
boot SBL> %s: parse command error! (%s)
Autoboot (%d seconds) in progress, press any key to stop
Autoboot aborted..
booting code=0x%x stl init failed.. %s: j4fs_open.. success failed %s: bye~ bye! %s: booting stop.
%s: booting stop and power off..
S5360 console=ttyS0,115200n8 mem=362M kmemleak=off root=/dev/ram0 rw
androidboot.console=ttyS0 /mnt/rsv SNBL main
#############
prob. kernel command line for UART FOTA boot or whatever
#############
loke_exit
loke_init
command_loop
boot_kernel
SERIAL_SPEED LOAD_RAMDISK BOOT_DELAY LCD_LEVEL SWITCH_SEL PHONE_DEBUG_ON LCD_DIM_LEVEL LCD_DIM_TIME MELODY_MODE REBOOT_MODE NATION_SEL LANGUAGE_SEL SET_DEFAULT_PARAM PARAM_INT_13 PARAM_INT_14 VERSION CMDLINE DELTA_LOCATION PARAM_STR_3 PARAM_STR_4
mtdparts=bcm_umi-nand: %[email protected]%dK(%s)ro, %[email protected]%dK(%s)rw, fota_reboot FOTA
Boot cause : %s FOTA_BOOT FOTA_UAUP LOKE3 : FOTA_UPDATE_FOTA_BOOT
BOOT_FOTA=1 BOOT_FOTA=0
ATAG_CORE: %x
ATAG_INITRD2: %x
Linux-based NAND Flash software solution, offering higher performance and cost effectiveness for next-generation mobile phones. Samsung's Linux NAND Flash memory software allows the NAND Flash memory to store code as well as data. By eliminating the need for NOR Flash memory and supporting the Linux operating system with a demand-paging function, Samsung can lower overall costs and reduce space requirements in mobile handhelds.
Samsung's Linux file system, Robust File System (RFS), also offers greater data preservation capabilities in case of power disruption as well as wear-leveling for higher reliability. To address the problem of data loss from corrupted file allocation tables (FAT), Samsung's Linux-based NAND Flash memory solution also supports Transactional FAT for external memory cards. Compared to the conventional JFFS2 and YAFFS open file systems, Samsung's Linux file system enhances the NAND Flash write-speed up ten and four times , respectively.
This Flash memory solution is also available with Samsung's OneNAND (tm) Flash memory, which boasts a faster read speed compared to the conventional NAND Flash. With its advanced multi-tasking function, Linux will further accelerate the adoption of NAND Flash in next-generation mobile phones.
Importantly, as Samsung's new Linux NAND Flash memory software, RFS has completed verification in the Linux kernel 2.4.20-based Montavista Linux environment, Samsung's NAND Flash solution addresses the diverse needs of system developers for advanced performance, high reliability, shortened development time, and reduced costs.
SGY heimdall
with UBI running on oneNAND and UBIfs we SGY users can have our own "mobile ODIN" and Heimdall.
UBI is open source and part of the Linux kernel.
Hello
I've just recently got a HTC Desire HD. I've rooted it with the help of aahk-11092012.
I've installed CM 7 first and it all worked fine.
A bit later I installed JellyTime ( http://forum.xda-developers.com/showthread.php?t=1778202 ).
This worked fine for about 2 days. Than, suddenly, the phone crashed. The screen went black and I the phone would not accept any key presses anymore. So I removed the battery and started the phone again. It hung on the htc-logo.
I was still able to get into recovery but it complained that it could not access the cache partition.
Upon further investigation i found out, that the partition table of the internal memory is broken. I could not mount or format any of the partitions. Factory reset just complained about that it could not access the partitions.
So i switched off the phone and started adb.
dmesg shows this
Code:
<6>[ 7.630279] rs30000048:00040000 rs30000048:00040000: setting system clock to 2012-11-23 20:51:58 UTC (1353703918)
<4>[ 7.630645] Warning: unable to open an initial console.
<6>[ 7.630828] Freeing init memory: 156K
<6>[ 7.739837] mmc0: new high speed MMC card at address 0001
<6>[ 7.740966] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<6>[ 7.741851] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<4>[ 7.767913] mmcblk0: partition table partially beyond EOD, truncated
<4>[ 7.769744] mmcblk0: p28 size 42495 extends beyond EOD, truncated
<3>[ 7.816436] init: Unable to open persistent property directory /data/property errno: 2
And if I try to use parted I only get errors:
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print list
print list
Error: Can't have a partition outside the disk!
(parted)
The same error is show if I try to remove partitions.
When I try to write a new disklabel it just hangs there forever. No error message (also not in dmesg) or anything like this.
How can I fix the partition table of the internal memory and what do I have to do to get it to work again?
I guess that I will have to create a new partition table (and most probably destroy all the data on the internal memory in the process).
What will I have to reinstall in what order afterwards?
hboot?
cwm?
and how do I have to do this from the adb? Or is there a possibility do do this out of recovery?
I've tried several things in the meantime.
Ind the longer I try, the more I think that I have a bricked phone now since I seem to be unable to write anything to the emmc
I've tried to get back to the original firmware. So I copied the File PD98IMG.zip the the sd card, got into hboot and started the installation in hboot.
I could start it and it told me "Updating in progress, do not power off"
But there was no progress bar and after 10 minutes I pulled the battery. The phone is still in the same state as before so I think it did not write anything to the internal memory.
With fastboot, it seems to be the same. I can start fastboot on the phone aqnd it changes to "fastboot usb" when i plug the phone in. But every attempt to flash something to the phone just let's fastboot on the computer stop and hang (no message is shown, it's just sitting there and apparently doing nothing).
My computer system is debian linux btw.
I'm running out of ideas... please help... and it it's just the confirmation, that I have a bricked phone (that is long out of the warranty period anyway)
try with fastboot erase command. do google it a bit before you try
You have a full brick mate the EMMC is fried not amount of commands will fix it.
If you try fastboot getvar all then the try fastboot oem rebootRUU and the phone locks up its a new EMMC chip and jtag session to get it back online.
Google helps sometimes, you can also wipe out sectors on the emmc, because the partition table is corrupt.
http://archive09.linux.com/forums/topic/4033
Sent from my HTC Desire HD using Tapatalk 2
I have tried if he has the Dodgy EMMC doesn't matter what you try its fried and will not work. I have tried everything myself on a Bricked DHD with the Dodgy EMMC chip.
Here it is as I promised.
This phone (the model with one sim card) is sold as a device with 8GB internal memory. In fact the memory chip inside is 16GB, so we can increase the available internal space.
PLEASE READ CAREFULLY AND IF SOMETHING IS NOT CLEAR DO NOT HESITATE TO ASK.
*** The data on your device will be untouched after this operation. But again please read carefully! ***
*** A good practice is always to make a backup of everything which will be changed. I do it and I've made a backup of the entire internal memory of the device before the start of the operation which is described below. ***
*** At the end of the post there is a link to a ZIP file which can be flashed through TWRP in order to perform the procedure automatically. Also includes a check for the size of the EMMC (as there are devices on which the resizing cannot be performed...their chip is smaller).***
1. You can go to this thread and to say Thanks! @meghd00t as his static build of gdisk is used in the recovery below.
2. What is needed:
- A different TWRP Recovery with gdisk inside. It can be downloaded from here twrp-2.8.7.0-idol3-6039y-with-gdisk.img - md5sum: 66b3f82a3e2e1afe14627b3b900a9319
- (Optional) An SD card for backup of the original GPT partition layout.
- Patience and careful reading.
- The Windows users probably need the drivers from this post, for access to the device in recovery mode.
3. How to do it (the output used below is from the terminal window from which I've done this operation on my device):
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3-6039y-with-gdisk.img
- go to the device
Code:
adb shell
- unmount all partitions of the internal memory
Code:
~ # umount /cache
~ # umount /sdcard
~ # umount /and-sec
- ensure that there are no mounted partitions from mmcblk0. The output from the mount command should looks like this:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=713016k,nr_inodes=157853,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=713016k,nr_inodes=157853)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
- start gdisk
Code:
~ # gdisk /dev/block/mmcblk0
all partitions can be listed by pressing 'p' but we are interested by the last two:
Code:
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
and their information which will be shown by pressing 'i' and entering the partition number:
Code:
Command (? for help): i
Partition number (1-38): 37
Partition GUID code: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335 (Unknown)
Partition unique GUID: BDD7FA27-93D4-40BC-B266-313E074E0E87
First sector: 5000400 (at 2.4 GiB)
Last sector: 15269853 (at 7.3 GiB)
Partition size: 10269454 sectors (4.9 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdata'
Command (? for help): i
Partition number (1-38): 38
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: BD12CF41-10E7-BBF7-D096-5553B89882E7
First sector: 15269854 (at 7.3 GiB)
Last sector: 30535646 (at 14.6 GiB)
Partition size: 15265793 sectors (7.3 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdatabak'
The information which is needed from the above output is Partition GUID code, First sector, Last sector and Partition name. You can write these somewhere (if your values are different from the above) from where can be pasted easily later (alternatively you can use the scrollback function of the terminal ).
- if you have an SD card make a backup of the partitions layout (in case that something goes wrong):
Code:
Command (? for help): b
Enter backup filename to save: /external_sd/gpt_partitions_table.backup
The operation has completed successfully.
- delete partitions 37 and 38:
Code:
Command (? for help): d
Partition number (1-38): 38
Command (? for help): d
Partition number (1-37): 37
- create a new partition 37, bigger in size with the same (as before) Partition GUID code, and the same (as before) start sector:
Code:
Command (? for help): n
Partition number (37-40, default 37): 37
First sector (34-30535646, default = 5000400) or {+-}size{KMGTP}: 5000400
Last sector (5000400-30535646, default = 30535646) or {+-}size{KMGTP}: 30535546
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
Changed type of partition to 'Unknown'
The difference here is in the last sector of the partition 30535546.
- create a new partition 38 with same Partition GUID code, but with different First sector:
Code:
Command (? for help): n
Partition number (38-40, default 38): 38
First sector (34-30535646, default = 34) or {+-}size{KMGTP}: 30535547
Information: Moved requested sector from 30535547 to 30535548 in
order to align on 2-sector boundaries.
Use 'l' on the experts' menu to adjust alignment
Last sector (30535548-30535646, default = 30535646) or {+-}size{KMGTP}: 30535646
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
Changed type of partition to 'Microsoft basic data'
Please note that here in the output after 'n' the default first sector is 34, so you explicitly must enter the value!!! As can be seen I've entered the next available sector (after partition 37) 305355547 but it has been corrected automatically to 30535548. So you can use directly 30535548 as a start sector. The last sector is at the end of the memory 30535646.
- write the names of the new partitions:
Code:
Command (? for help): c
Partition number (1-38): 37
Enter name: userdata
Command (? for help): c
Partition number (1-38): 38
Enter name: userdatabak
- if you list the partitions again (with 'p') the end of the table should looks like this:
Code:
37 5000400 30535546 12.2 GiB FFFF userdata
38 30535548 30535646 49.5 KiB 0700 userdatabak
- now it is safe to write the changes by pressing 'w':
Code:
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
The operation has completed successfully.
- resize the file system:
Code:
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... hmm ... let's run it:
Code:
~ # e2fsck -f /dev/block/mmcblk0p37
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 12519/321280 files (5.8% non-contiguous), 678615/1283425 blocks
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... well the resize2fs have some checks and refuses to resize the file system therefore we must force the execution:
Code:
~ # resize2fs -fp /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /dev/block/mmcblk0p37 to 3191893 (4k) blocks.
The filesystem on /dev/block/mmcblk0p37 is now 3191893 blocks long.
The device now can be rebooted and its internal memory will be almost 12GB which compared to its previous size is a very nice upgrade. Screenshots before and after the repartitioning can be seen here.
Update (19.09.2015): This is a link to a flashabable zip which can be used from the TWRP to automate the process. Can be used with any TWRP recovery for 6039.
md5sum: c3f685310283bdc00cee5412fa33259c
Just tried it, and it worked like a charm. Thank you very much!
Wow ! Kudos to meghd00t and petrov.0. I just ordered this phone as a backup, waiting for my beloved Xperia Z1 Compact to be saved from watering (medium rain during less than 10min, so long Sony waterproof phones...). Can't wait to receive it and play with this extra storage !! Thank you :victory:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!
evilinheaven said:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!
Click to expand...
Click to collapse
Well ... I like crazy things. But is impossible just to add a chip.
The thread itself is for other things. I don't want more reminders from the moderators. So please use the general section next time.
Thank you in advance.
Here is the complete partition list for 8Gb single sim variant:
Code:
Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2-sector boundaries
Total free space is 256464 sectors (125.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 265215 1.5 MiB FFFF tunning
3 265216 267263 1024.0 KiB FFFF traceability
4 267264 267265 1024 bytes FFFF fsc
5 267266 267281 8.0 KiB FFFF ssd
6 267282 268305 512.0 KiB FFFF sbl1
7 268306 269329 512.0 KiB 0700 sbl1bak
8 269330 270353 512.0 KiB FFFF rpm
9 270354 271377 512.0 KiB 0700 rpmbak
10 271378 272401 512.0 KiB FFFF tz
11 272402 273425 512.0 KiB 0700 tzbak
12 273426 274449 512.0 KiB FFFF hyp
13 274450 275473 512.0 KiB 0700 hypbak
14 275474 278545 1.5 MiB FFFF modemst1
15 278546 281617 1.5 MiB FFFF modemst2
16 281618 283665 1024.0 KiB FFFF simlock
17 283666 286737 1.5 MiB FFFF efsdata
18 393216 393279 32.0 KiB FFFF DDR
19 393280 396351 1.5 MiB FFFF fsg
20 396352 396383 16.0 KiB FFFF sec
21 396384 398431 1024.0 KiB FFFF aboot
22 398432 400479 1024.0 KiB 0700 abootbak
23 400480 466015 32.0 MiB FFFF boot
24 466016 531551 32.0 MiB FFFF recovery
25 531552 4306427 1.8 GiB FFFF system
26 4325376 4390911 32.0 MiB FFFF persist
27 4390912 4407295 8.0 MiB FFFF splash
28 4407296 4448255 20.0 MiB 0700 tctpersist
29 4448256 4468735 10.0 MiB 0700 hdcp
30 4468736 4468751 8.0 KiB FFFF fota
31 4468752 4993039 256.0 MiB FFFF cache
32 4993040 4995087 1024.0 KiB FFFF misc
33 4995088 4996111 512.0 KiB FFFF keystore
34 4996112 4996175 32.0 KiB FFFF config
35 4996176 4996303 64.0 KiB FFFF oem
36 4996304 5000399 2.0 MiB FFFF FactoryRP
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
Maybe someone can post the list for 16Gb dual sim variant?
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitions have the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
rioachim said:
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitionshave the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
Click to expand...
Click to collapse
OK. But don't be fulled by the GUID. Most of the bak partitions contain data which is equivalent to the data in the primary ones (aboot, rpm, sbl1 etc.). The data is patched in both partitions with the same patch during an upgrade.
Script to repartition "internal memory"
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99
google99 said:
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99
Click to expand...
Click to collapse
No it is not:
Code:
GPT fdisk (aka gdisk) is a text-mode menu-driven program for creation and manipulation of partition tables.
Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!
Romagnolo1973 said:
Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!
Click to expand...
Click to collapse
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk
Rorshan said:
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
If you find a way to root the device after the update then may be there is a hope.
petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
Romagnolo1973 said:
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
Click to expand...
Click to collapse
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
petrov.0 said:
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
Click to expand...
Click to collapse
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
Romagnolo1973 said:
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
Click to expand...
Click to collapse
There is nothing wrong with the fastboot commands prior the update. I have doubts that they will be returned. Thanks for the info though (despite that I already know this by looking in the update files). I can't live without root access however therefore there is no option to loose it.
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
Rorshan said:
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
Click to expand...
Click to collapse
Everything after adb shell must be done directly on the device. The VID & PID of the device are different in the recovery and you don't have the necessary drivers. Try to install the drivers mentioned in the first post (- The Windows users probably need the drivers from this post, for access to the device in recovery mode).
Hi all,
I manage to (soft) brick my LG H815
It was working fine (using Nougat) until I decided it was time to poke with it (battery was draining way too fast)! Bad idea!
So I tried to upload a new ROM ... which happened to be a wrong variant (i suppose). After that, my device boots straight in to Download Mode all the time. However, I can put it in Fastboot mode (hold Vol + and connect USB cable).
But Fastboot mode doesn't seems to be of any use for me, as when I use ADB DEVICES it doesn't show my device (but it can reboot it, and even respond to a getvar command that shows that its bootloader is unlocked (printscreen attached)
I thought it could be a a driver problem (I use Win10 Pro - Build 16299), but LG Bridge seems to find my device ... but any attempt to fix/recover/update it always fail. Also, LGUP always give "error code = 0x2000, invalid command response" when I try to upload a new KDZ archive.
After 3 days reading all I could find and burning out my brain ... so, I'll be very gratefull if someone can give me a help :good::good:
PS: I added a few print screens from what i've got here. Pls let me know if there is any other useful info.
H815 soft bricked
anyone....?
I'm willing to try any suggestion (phone still bricked and useless)... even if it seems similar/identical to previews try... and I'm happy to donate some gold coins (ie: paypal :highfive for suggestions that leads to fix it.
LGUP = does not seems to work
ADB commands = does not see the device
You can't use *adb* commands in *fastboot* mode!
So when you boot into fastboot only fastboot commands will work. Example: fastboot flash boot twrp.img
So download the latest preview TWRP from my server and rename it to twrp.img then do the above command while in fastboot mode.
This should bring up TWRP temporarely. But that wouldn't help a lot.
The fix would require SALT. You would extract with SALT the correct kdz variant of your model and flash the bootloader stack while in fastboot.
Sent from my LG-H815 using XDA Labs
otavio_aon said:
Hi all,
I manage to (soft) brick my LG H815
It was working fine (using Nougat) until I decided it was time to poke with it (battery was draining way too fast)! Bad idea!
So I tried to upload a new ROM ... which happened to be a wrong variant (i suppose). After that, my device boots straight in to Download Mode all the time. However, I can put it in Fastboot mode (hold Vol + and connect USB cable).
But Fastboot mode doesn't seems to be of any use for me, as when I use ADB DEVICES it doesn't show my device (but it can reboot it, and even respond to a getvar command that shows that its bootloader is unlocked (printscreen attached)
I thought it could be a a driver problem (I use Win10 Pro - Build 16299), but LG Bridge seems to find my device ... but any attempt to fix/recover/update it always fail. Also, LGUP always give "error code = 0x2000, invalid command response" when I try to upload a new KDZ archive.
After 3 days reading all I could find and burning out my brain ... so, I'll be very gratefull if someone can give me a help :good::good:
PS: I added a few print screens from what i've got here. Pls let me know if there is any other useful info.
Click to expand...
Click to collapse
Try after read this: https://forum.xda-developers.com/showpost.php?p=76571471&postcount=23
And this: https://forum.xda-developers.com/showpost.php?p=76580594&postcount=17
steadfasterX said:
You can't use *adb* commands in *fastboot* mode!
So when you boot into fastboot only fastboot commands will work. Example: fastboot flash boot twrp.img
So download the latest preview TWRP from my server and rename it to twrp.img then do the above command while in fastboot mode.
This should bring up TWRP temporarily. But that wouldn't help a lot.
The fix would require SALT. You would extract with SALT the correct kdz variant of your model and flash the bootloader stack while in fastboot.
Click to expand...
Click to collapse
ALRIGHT ... after a few days I managed to install SALT (using a VirttualBox + FWUL 2.6 Forgetfull).
I did as instructed in the SALT tread
git clone https://github.com/steadfasterX/SALT.git
cd SALT
bash install-desktop.sh
...but not sudo pacman -Sy python-pyusb python-crypto as I installed FWUL 2.6
Click to expand...
Click to collapse
However, it failed to identify my device (attached print screen).
Any idea of what I should do? Am I skipping any crucial step? Could this problem be related to the "MODIFIED" mark that shows in red on my device Download Mode screen (photo attached)?
otavio_aon said:
ALRIGHT ... after a few days I managed to install SALT (using a VirttualBox + FWUL 2.6 Forgetfull).
I did as instructed in the SALT tread
However, it failed to identify my device (attached print screen).
Any idea of what I should do? Am I skipping any crucial step? Could this problem be related to the "MODIFIED" mark that shows in red on my device Download Mode screen (photo attached)?
Click to expand...
Click to collapse
if you use FWUL there is no need to install SALT. its already included (LG folder on the desktop) but anyways.
do you have attached the LG device in virtualbox settings after booted to download mode?
if yes: press the skip button when starting SALT and device is connected and open the advanced menu -> debug log -> upload button -> share the link
.
steadfasterX said:
if you use FWUL there is no need to install SALT. its already included (LG folder on the desktop) but anyways.
do you have attached the LG device in virtualbox settings after booted to download mode?
if yes: press the skip button when starting SALT and device is connected and open the advanced menu -> debug log -> upload button -> share the link
Click to expand...
Click to collapse
YEs ... i've attached the device on the VirtualBox setting (Settings -> USB -> Add New USB Filter -> LG Eletronic Inc.) but it doesn't look like it got detected by linux (even though LGE Android Phone appeared there... PHOTO ATTACHED)
The Log generated is HERE (I'll paste it below in case it expires).
Also, when I click Show Your Partitions it is empty (but I suppose that is expected as no_device_found is displayed everywhere)
Code:
2018-05-26 02:57:41: F_VCHK: newer SALT version found (316 / 3.16-0 vs. 38 / 3.8-2)
2018-05-26 02:57:41: F_MSGW: started
2018-05-26 02:57:53: New SALT version available!
You: <b>3.8-2</b>
Online: <b>3.16-0</b>
Do you want to update now?
2018-05-26 02:57:53: 0
2018-05-26 02:57:53: OS: Manjaro Linux
fwulversion=2.6
fwulbuild=1520439165
patchlevel=0
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=17.1.6
DISTRIB_CODENAME=Hakoila
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
ID=manjaro
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.manjaro.org/"
SUPPORT_URL="https://www.manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
2018-05-26 02:57:53: OS (lsb): LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 17.1.6
Codename: Hakoila
2018-05-26 02:57:53: yad: 0.40.0 (GTK+ 3.22.28)
2018-05-26 02:57:53: DEVCON before: 99
2018-05-26 02:57:53: F_CHKDEVCON: started
2018-05-26 02:57:58: F_MSG: started
2018-05-26 02:58:06: NO DEVICE CONNECTED?
If you have connected your device ensure that it is in DOWNLOAD mode
(<u>not</u> fastboot, <u>not</u> recovery, <u>not</u> booted Android)
2018-05-26 02:58:06: F_MSG: ended
2018-05-26 02:58:06: F_CHKDEVCON: msge result = 99
2018-05-26 02:58:06: F_CHKDEVCON: lsusb output = Bus 001 Device 006: ID 1004:633a LG Electronics, Inc. Ultimate 2 Android Phone L41C
2018-05-26 02:58:15: RET: 99
2018-05-26 02:58:15: DEVCON after: 99
2018-05-26 02:58:15: DEVCON before: 99
2018-05-26 02:58:15: F_CHKDEVCON: started
2018-05-26 02:58:20: F_MSG: started
2018-05-26 02:58:22: NO DEVICE CONNECTED?
If you have connected your device ensure that it is in DOWNLOAD mode
(<u>not</u> fastboot, <u>not</u> recovery, <u>not</u> booted Android)
2018-05-26 02:58:22: F_MSG: ended
2018-05-26 02:58:22: F_CHKDEVCON: msge result = 11
2018-05-26 02:58:22: F_CHKDEVCON: lsusb output = Bus 001 Device 006: ID 1004:633a LG Electronics, Inc. Ultimate 2 Android Phone L41C
2018-05-26 02:58:22: RET: 11
2018-05-26 02:58:22: DEVCON after: 11
2018-05-26 02:58:22: EXPERIMENTAL: 0
2018-05-26 02:58:22: F_MSGW: started
2018-05-26 02:58:53: Your device does <b>not</b> support direct flashing!
Flashing functionality <b>disabled</b>!
Activate flashing functionality by flashing a SALT compatible LAF partition.
Download it right here for <b>any</b> G4 model (requires unlocked device + TWRP):
<a href='https://www.androidfilehost.com/?fid=818070582850495147'>SALT-compatible-LAF_flash-in-twrp.zip</a>
You can still use many of the features SALT offering - just not the flashing part.
2018-05-26 02:58:53: 0
2018-05-26 02:58:53: Flashing functionality disabled bc: LAFVER = no_device_found and/or EXPERIMENTAL = 0
2018-05-26 02:59:18: F_ADVMENU: started
2018-05-26 02:59:23: F_LISTPARTS: started
2018-05-26 02:59:23: F_GETPARTS: started
2018-05-26 02:59:25: F_LISTPARTS: started
2018-05-26 02:59:25: F_GETPARTS: started
2018-05-26 02:59:25: (F_GETPARTS) created yad list:
2018-05-26 02:59:28: (F_GETPARTS) created yad list:
2018-05-26 02:59:47: getlog script started
2018-05-26 03:00:35: F_MSGOK: started
2018-05-26 03:00:51: Log uploaded successfully!
Please share this link:
http://bpaste.net/show/e883bf5d476c
2018-05-26 03:00:51: 0
2018-05-26 03:00:58: getlog script started
PS: Yes, I installed VirtualBox Extension Pack
PS2: I tried to connect my other mobile (an old Sony Xperia) using the same procedure, and I can access it in linux without a problem.
otavio_aon said:
YEs ... i've attached the device on the VirtualBox setting (Settings -> USB -> Add New USB Filter -> LG Eletronic Inc.) but it doesn't look like it got detected by linux (even though LGE Android Phone appeared there... PHOTO ATTACHED)
The Log generated is HERE (I'll paste it below in case it expires).
Also, when I click Show Your Partitions it is empty (but I suppose that is expected as no_device_found is displayed everywhere)
PS: Yes, I installed VirtualBox Extension Pack
PS2: I tried to connect my other mobile (an old Sony Xperia) using the same procedure, and I can access it in linux without a problem.
Click to expand...
Click to collapse
Try the same with USB 3 in VirtualBox settings
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Try the same with USB 3 in VirtualBox settings
Click to expand...
Click to collapse
:laugh:... it worked!
It's not fixed... but SALT has found my mobile (after I change it to USB3) 2 new things happened:
1) SALT identified all device's information (photo attached)
2) Download Mode screen changed (slightly) and does not display the "Modified" (in red) anymore. Not it shows: "633A 50.0 AS0.0 BB1 UHS || U U LG-H815TR 07.0 Hrev_10 CPU4 || H81529a" (but if I reboot the device, old message returns)
Debug log is HERE:
Code:
[INDENT] 2018-05-26 09:58:38: F_VCHK: newer SALT version found (316 / 3.16-0 vs. 38 / 3.8-2)
2018-05-26 09:58:38: F_MSGW: started
2018-05-26 09:58:46: New SALT version available!
You: <b>3.8-2</b>
Online: <b>3.16-0</b>
Do you want to update now?
2018-05-26 09:58:46: 0
2018-05-26 09:58:46: OS: Manjaro Linux
fwulversion=2.6
fwulbuild=1520439165
patchlevel=0
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=17.1.6
DISTRIB_CODENAME=Hakoila
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
ID=manjaro
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.manjaro.org/"
SUPPORT_URL="https://www.manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
2018-05-26 09:58:46: OS (lsb): LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 17.1.6
Codename: Hakoila
2018-05-26 09:58:46: yad: 0.40.0 (GTK+ 3.22.28)
2018-05-26 09:58:46: DEVCON before: 99
2018-05-26 09:58:46: F_CHKDEVCON: started
aarch64
2018-05-26 09:58:47: F_CHKDEVCON: Device seems to be connected!
2018-05-26 09:58:47: RET: 0
2018-05-26 09:58:47: DEVCON after: 0
2018-05-26 09:58:47: EXPERIMENTAL: 0
2018-05-26 09:58:47: F_GETINFO: started
2018-05-26 09:58:47: F_CDARB: started
2018-05-26 09:58:48,032 partitions: INFO: Wrote 1048576 bytes to -
2018-05-26 09:58:48: ARB valid and 0
2018-05-26 09:58:48: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2018-05-26 09:58:48: F_CDARB: ended
2018-05-26 09:58:48: F_GETINFO: ARB 0:0
2018-05-26 09:58:48: F_CKUSU: started
2018-05-26 09:58:48: F_DUMPPART: started with aboot
0:15:2048
1:31:2048
2:46:2048
3:62:2048
3:77:2048
4:93:2048
5:108:2048
6:124:2048
6:139:2048
7:155:2048
8:170:2048
9:186:2048
9:201:2048
10:217:2048
11:232:2048
12:248:2048
12:263:2048
13:279:2048
14:294:2048
15:310:2048
15:325:2048
16:341:2048
17:356:2048
18:372:2048
18:387:2048
19:403:2048
20:418:2048
21:434:2048
21:449:2048
22:465:2048
23:480:2048
24:496:2048
24:511:2048
25:527:2048
26:542:2048
27:558:2048
28:573:2048
28:589:2048
29:604:2048
30:620:2048
31:635:2048
31:651:2048
32:666:2048
33:682:2048
34:697:2048
34:713:2048
35:728:2048
36:744:2048
37:759:2048
37:775:2048
38:790:2048
39:806:2048
40:821:2048
40:837:2048
41:852:2048
42:868:2048
43:883:2048
43:899:2048
44:914:2048
45:930:2048
46:945:2048
46:961:2048
47:976:2048
48:992:2048
49:1007:2048
49:1023:2048
50:1038:2048
51:1054:2048
52:1069:2048
52:1085:2048
53:1100:2048
54:1116:2048
55:1131:2048
56:1147:2048
56:1162:2048
57:1178:2048
58:1193:2048
59:1209:2048
59:1224:2048
60:1240:2048
61:1255:2048
62:1271:2048
62:1286:2048
63:1302:2048
64:1317:2048
65:1333:2048
65:1348:2048
66:1364:2048
67:1379:2048
68:1395:2048
68:1410:2048
69:1426:2048
70:1441:2048
71:1457:2048
71:1472:2048
72:1488:2048
73:1503:2048
74:1519:2048
74:1534:2048
75:1550:2048
76:1565:2048
77:1581:2048
77:1596:2048
78:1612:2048
79:1627:2048
80:1643:2048
80:1658:2048
81:1674:2048
82:1689:2048
83:1705:2048
84:1720:2048
84:1736:2048
85:1751:2048
86:1767:2048
87:1782:2048
87:1798:2048
88:1813:2048
89:1829:2048
90:1844:2048
90:1860:2048
91:1875:2048
92:1891:2048
93:1906:2048
93:1922:2048
94:1937:2048
95:1953:2048
96:1968:2048
96:1984:2048
97:1999:2048
98:2015:2048
99:2030:2048
99:2046:2048
100:2048:2048
2018-05-26 09:58:49: F_CKUSU: USU=0 (1=yes, 0=no)
2018-05-26 09:58:49: F_CKUSU: ended
2018-05-26 09:58:49: F_GETINFO: USU 0:
2018-05-26 09:58:49: F_ROMCOMP: started
0
1
2018-05-26 09:58:50: UsU compatibility: 0 (0=h815, 1=h811)
2018-05-26 09:58:50: F_GETINFO: ROMCOMP H815
2018-05-26 09:58:50: F_CHKLAFV: started with this args:
2018-05-26 09:58:50: F_CHKLAFV: detected 1000006
2018-05-26 09:58:50: F_CHKLAFV: no comparison needed
2018-05-26 09:58:50: F_GETINFO: LAFVER 1000006
2018-05-26 09:58:51: F_GETINFO:
2018-05-26 09:58:51: F_GETINFO: ended
2018-05-26 09:58:51: parsing
2018-05-26 09:58:51: parsing H815
2018-05-26 09:58:51: parsing 0
2018-05-26 09:58:51: parsing 1000006
2018-05-26 09:58:51: parsing 85
2018-05-26 09:58:51: parsing H81529a
2018-05-26 09:58:51: parsing U
2018-05-26 09:58:51: parsing LGH815TRAT-00-V29a-OPT2-HQ-JUL-12-2017+0
2018-05-26 09:58:51: parsing imei:xxxxxxxxxxx
2018-05-26 09:58:51: parsing serial:xxxxxxxxxxx
2018-05-26 09:58:51: parsing LG-H815TR
2018-05-26 09:58:51: parsing GLOBAL
2018-05-26 09:58:51: parsing COM
2018-05-26 09:58:51: F_MSGW: started
2018-05-26 09:59:11: Your device does <b>not</b> support direct flashing!
Flashing functionality <b>disabled</b>!
Activate flashing functionality by flashing a SALT compatible LAF partition.
Download it right here for <b>any</b> G4 model (requires unlocked device + TWRP):
<a href='https://www.androidfilehost.com/?fid=818070582850495147'>SALT-compatible-LAF_flash-in-twrp.zip</a>
You can still use many of the features SALT offering - just not the flashing part.
2018-05-26 09:59:11: 0
2018-05-26 09:59:11: Flashing functionality disabled bc: LAFVER = 1000006 and/or EXPERIMENTAL = 0
2018-05-26 09:59:22: F_ADVMENU: started
2018-05-26 09:59:25: getlog script started
2018-05-26 10:00:10: F_MSGOK: started
2018-05-26 10:03:33: Log uploaded successfully!
Please share this link:
http://bpaste.net/show/1e10b2cccc7e
2018-05-26 10:03:33: 0
2018-05-26 10:03:37: F_LISTPARTS: started
2018-05-26 10:03:37: F_GETPARTS: started
2018-05-26 10:03:38: modem,1,32768,208895,812DD655-627C-0D0F-3FD2-815DCE5ABBC4
2018-05-26 10:03:38: pmic,2,229376,230399,DAF3727B-E6CE-D706-A1D0-56DA4D6215A3
2018-05-26 10:03:38: sbl1,3,230400,232447,1E04EB30-648D-3B3B-1AFE-374D798D8540
2018-05-26 10:03:38: tz,4,232448,234495,A1DB62E4-8B1D-79B6-9BBD-72E3067C629C
2018-05-26 10:03:38: sdi,5,234496,235519,91F2EC68-8B7A-48F9-E26D-738F3EDC27DE
2018-05-26 10:03:38: hyp,6,235520,236543,881AEE2F-4930-E620-D43E-6CF0BD5BBEAC
2018-05-26 10:03:38: rpm,7,236544,237567,13E54E57-3AC1-F5C8-EB08-058DE52AAC47
2018-05-26 10:03:38: aboot,8,237568,241663,666255B1-D974-5DBE-60A2-F8EBB81F7D2E
2018-05-26 10:03:38: sbl1bak,9,241664,243711,D146B23E-8F14-FE0F-8E63-CC1034FF3AD7
2018-05-26 10:03:38: pmicbak,10,243712,244735,78BFD764-AE7C-E491-D43B-D5D68FC7134E
2018-05-26 10:03:38: tzbak,11,244736,246783,C74DD66B-0C83-D518-BF9A-611675363680
2018-05-26 10:03:38: hypbak,12,246784,247807,F62B8FB5-CBDA-4056-EBBC-8F5ED7C3353F
2018-05-26 10:03:38: rpmbak,13,247808,248831,58579D64-17A6-89D0-1622-1397AA80A681
2018-05-26 10:03:38: abootbak,14,248832,252927,E6540864-B4B7-8698-0F1A-DEAF653DAAAA
2018-05-26 10:03:38: sdibak,15,252928,253951,79DD4B98-AD7D-470E-BDD9-CE9AA6E9246A
2018-05-26 10:03:38: limits,16,253952,254975,A22DAF2F-AB5C-9D30-2236-512209A6FAF2
2018-05-26 10:03:38: devinfo,17,254976,255999,72A30C09-12E8-C6FC-7423-949A8EBAAA82
2018-05-26 10:03:38: apdp,18,256000,257023,618ED72A-84A4-3214-9126-DA6BBB3CC4D1
2018-05-26 10:03:38: msadp,19,257024,258047,6E801307-7F0F-6724-D4B6-37031D5C21F7
2018-05-26 10:03:38: dpo,20,258048,259071,77476FA7-2D7F-AD3B-84CA-23BDC11EBCAC
2018-05-26 10:03:38: spare1,21,259072,262143,584CAAA9-BB9D-A018-D395-6DFDCC039918
2018-05-26 10:03:38: misc,22,262144,294911,882D6E37-322E-5861-C2A5-C612AA5DBE1B
2018-05-26 10:03:38: persist,23,294912,360447,977164A1-A02D-24E6-46D4-2419B28F4AF3
2018-05-26 10:03:38: modemst1,24,360448,363519,33A57E1C-8210-8A64-33F2-53421F06125D
2018-05-26 10:03:38: modemst2,25,363520,366591,E012A295-A5BA-0BA0-1A67-B7C75413A1FA
2018-05-26 10:03:38: fsg,26,366592,369663,623D5942-BC88-D653-C36D-0A6F5A5F7716
2018-05-26 10:03:38: fsc,27,369664,370687,0AE8652B-9C14-CC79-DD95-8B15609F0871
2018-05-26 10:03:39: ssd,28,370688,371711,FB4BCE9E-6095-FA8B-12E5-17057399E17F
2018-05-26 10:03:39: keystore,29,371712,372735,F8317C1D-2ABB-20BC-8C67-DBB39C650DB1
2018-05-26 10:03:39: DDR,30,372736,376831,3083DD35-923A-1FE5-791D-4D5DEB9586F3
2018-05-26 10:03:39: sec,31,376832,377855,7ADEF19D-27E6-B1A5-2BFD-3018BAF82F06
2018-05-26 10:03:39: encrypt,32,377856,378879,68A71FCC-004E-5596-E810-1B8006293C58
2018-05-26 10:03:39: eksst,33,378880,379903,A2E77524-2565-B443-9C2A-DD5EE575C1AF
2018-05-26 10:03:39: rct,34,379904,380927,FE2C06FE-D904-DE3A-4076-DA16207ACF17
2018-05-26 10:03:39: persistent,35,380928,385023,C4799A1F-49F9-C600-B2C6-1BD2C7D129C6
2018-05-26 10:03:39: spare2,36,385024,393215,4ECD70C8-B392-9B3A-7652-24148D00DF9D
2018-05-26 10:03:39: laf,37,393216,491519,855DCE51-2AEE-58FA-632F-BC315AE32250
2018-05-26 10:03:39: boot,38,491520,573439,BDBBAA7F-C1F8-65E6-5AD6-E18DDEBB3E44
2018-05-26 10:03:39: recovery,39,573440,655359,F12ADFD1-1B60-AEF0-6C81-67E7114D58ED
2018-05-26 10:03:39: drm,40,655360,671743,A0AA8F72-5649-8BA4-8B44-56F9E1615838
2018-05-26 10:03:39: sns,41,671744,688127,232664F5-B752-C025-3A48-9A7F059572ED
2018-05-26 10:03:39: mpt,42,688128,753663,CF573AF5-D1CB-0311-BC4B-7FA12852D52B
2018-05-26 10:03:39: factory,43,753664,847871,C09B2DD0-3A16-4C44-73C0-A56EF0DD92B6
2018-05-26 10:03:39: fota,44,847872,868351,B728E1E5-DCA5-11FA-B9A3-FA5344F5158A
2018-05-26 10:03:39: raw_resources,45,868352,876543,083A2C34-2EA0-0FA0-5AFD-0F0E80FDD16C
2018-05-26 10:03:39: raw_resourcesbak,46,876544,884735,8587FC90-5E3C-105D-B978-BC293D805FC5
2018-05-26 10:03:39: system,47,884736,9363455,B3364B13-EEB8-CBBA-2B8C-458B7FF5795A
2018-05-26 10:03:39: cust,48,9363456,9887743,030D4113-B0F9-5323-2268-9383055D0B80
2018-05-26 10:03:39: cache,49,9895936,12419071,9CE8E415-5EE6-28A1-DACB-E409CABF612B
2018-05-26 10:03:39: userdata,50,12419072,61046783,7F9EDF99-45E1-EFA5-4CE8-23A9EFE21C86
2018-05-26 10:03:39: grow,51,61046784,61071326,84DB071C-E681-B8AF-77CB-35FD426B4471
2018-05-26 10:03:39: (F_GETPARTS) created yad list: true
modem
1
32768
208895
812DD655-627C-0D0F-3FD2-815DCE5ABBC4
<span color='#558000'>system-partition</span>
2 true
pmic
2
229376
230399
DAF3727B-E6CE-D706-A1D0-56DA4D6215A3
bootloader
1 true
sbl1
3
230400
232447
1E04EB30-648D-3B3B-1AFE-374D798D8540
bootloader
1 true
tz
4
232448
234495
A1DB62E4-8B1D-79B6-9BBD-72E3067C629C
bootloader
1 true
sdi
5
234496
235519
91F2EC68-8B7A-48F9-E26D-738F3EDC27DE
bootloader
1 true
hyp
6
235520
236543
881AEE2F-4930-E620-D43E-6CF0BD5BBEAC
bootloader
1 true
rpm
7
236544
237567
13E54E57-3AC1-F5C8-EB08-058DE52AAC47
bootloader
1 true
aboot
8
237568
241663
666255B1-D974-5DBE-60A2-F8EBB81F7D2E
bootloader
1 true
sbl1bak
9
241664
243711
D146B23E-8F14-FE0F-8E63-CC1034FF3AD7
bootloader
1 true
pmicbak
10
243712
244735
78BFD764-AE7C-E491-D43B-D5D68FC7134E
bootloader
1 true
tzbak
11
244736
246783
C74DD66B-0C83-D518-BF9A-611675363680
bootloader
1 true
hypbak
12
246784
247807
F62B8FB5-CBDA-4056-EBBC-8F5ED7C3353F
bootloader
1 true
rpmbak
13
247808
248831
58579D64-17A6-89D0-1622-1397AA80A681
bootloader
1 true
abootbak
14
248832
252927
E6540864-B4B7-8698-0F1A-DEAF653DAAAA
bootloader
1 true
sdibak
15
252928
253951
79DD4B98-AD7D-470E-BDD9-CE9AA6E9246A
bootloader
1 true
limits
16
253952
254975
A22DAF2F-AB5C-9D30-2236-512209A6FAF2
<span color='#558000'>system-partition</span>
2 false
devinfo
17
254976
255999
72A30C09-12E8-C6FC-7423-949A8EBAAA82
<span color='#ff0000'>dangerous</span>
88 true
apdp
18
256000
257023
618ED72A-84A4-3214-9126-DA6BBB3CC4D1
<span color='#558000'>system-partition</span>
2 true
msadp
19
257024
258047
6E801307-7F0F-6724-D4B6-37031D5C21F7
<span color='#558000'>system-partition</span>
2 true
dpo
20
258048
259071
77476FA7-2D7F-AD3B-84CA-23BDC11EBCAC
<span color='#558000'>system-partition</span>
2 true
spare1
21
259072
262143
584CAAA9-BB9D-A018-D395-6DFDCC039918
unknown-type
2 false
misc
22
262144
294911
882D6E37-322E-5861-C2A5-C612AA5DBE1B
<span color='#ff0000'>dangerous</span>
88 false
persist
23
294912
360447
977164A1-A02D-24E6-46D4-2419B28F4AF3
<span color='#ff0000'>dangerous</span>
88 false
modemst1
24
360448
363519
33A57E1C-8210-8A64-33F2-53421F06125D
<span color='#ff0000'>dangerous</span>
88 false
modemst2
25
363520
366591
E012A295-A5BA-0BA0-1A67-B7C75413A1FA
<span color='#ff0000'>dangerous</span>
88 true
fsg
26
366592
369663
623D5942-BC88-D653-C36D-0A6F5A5F7716
<span color='#558000'>system-partition</span>
2 true
fsc
27
369664
370687
0AE8652B-9C14-CC79-DD95-8B15609F0871
<span color='#558000'>system-partition</span>
2 true
ssd
28
370688
371711
FB4BCE9E-6095-FA8B-12E5-17057399E17F
<span color='#558000'>system-partition</span>
2 true
keystore
29
371712
372735
F8317C1D-2ABB-20BC-8C67-DBB39C650DB1
<span color='#558000'>system-partition</span>
2 true
DDR
30
372736
376831
3083DD35-923A-1FE5-791D-4D5DEB9586F3
<span color='#558000'>system-partition</span>
2 true
sec
31
376832
377855
7ADEF19D-27E6-B1A5-2BFD-3018BAF82F06
<span color='#558000'>system-partition</span>
2 true
encrypt
32
377856
378879
68A71FCC-004E-5596-E810-1B8006293C58
<span color='#558000'>system-partition</span>
2 true
eksst
33
378880
379903
A2E77524-2565-B443-9C2A-DD5EE575C1AF
<span color='#558000'>system-partition</span>
2 true
rct
34
379904
380927
FE2C06FE-D904-DE3A-4076-DA16207ACF17
<span color='#558000'>system-partition</span>
2 false
persistent
35
380928
385023
C4799A1F-49F9-C600-B2C6-1BD2C7D129C6
<span color='#ff0000'>dangerous</span>
88 true
spare2
36
385024
393215
4ECD70C8-B392-9B3A-7652-24148D00DF9D
unknown-type
2 true
laf
37
393216
491519
855DCE51-2AEE-58FA-632F-BC315AE32250
bootloader
1 true
boot
38
491520
573439
BDBBAA7F-C1F8-65E6-5AD6-E18DDEBB3E44
<span color='#558000'>system-partition</span>
2 true
recovery
39
573440
655359
F12ADFD1-1B60-AEF0-6C81-67E7114D58ED
<span color='#558000'>system-partition</span>
2 false
drm
40
655360
671743
A0AA8F72-5649-8BA4-8B44-56F9E1615838
<span color='#ff0000'>dangerous</span>
88 false
sns
41
671744
688127
232664F5-B752-C025-3A48-9A7F059572ED
<span color='#ff0000'>dangerous</span>
88 true
mpt
42
688128
753663
CF573AF5-D1CB-0311-BC4B-7FA12852D52B
<span color='#558000'>system-partition</span>
2 true
factory
43
753664
847871
C09B2DD0-3A16-4C44-73C0-A56EF0DD92B6
<span color='#558000'>system-partition</span>
2 true
fota
44
847872
868351
B728E1E5-DCA5-11FA-B9A3-FA5344F5158A
<span color='#558000'>system-partition</span>
2 true
raw_resources
45
868352
876543
083A2C34-2EA0-0FA0-5AFD-0F0E80FDD16C
<span color='#558000'>system-partition</span>
2 true
raw_resourcesbak
46
876544
884735
8587FC90-5E3C-105D-B978-BC293D805FC5
<span color='#558000'>system-partition</span>
2 true
system
47
884736
9363455
B3364B13-EEB8-CBBA-2B8C-458B7FF5795A
<span color='#558000'>system-partition</span>
2 true
cust
48
9363456
9887743
030D4113-B0F9-5323-2268-9383055D0B80
<span color='#558000'>system-partition</span>
2 false
cache
49
9895936
12419071
9CE8E415-5EE6-28A1-DACB-E409CABF612B
unneeded
99 false
userdata
50
12419072
61046783
7F9EDF99-45E1-EFA5-4CE8-23A9EFE21C86
unneeded
99 false
grow
51
61046784
61071326
84DB071C-E681-B8AF-77CB-35FD426B4471
unneeded
99
2018-05-26 10:04:39: Reboot button script started
2018-05-26 10:04:43: REBOOT INITIATED by USER!
2018-05-26 10:04:44: Reboot button script ended
2018-05-26 10:08:50: F_ADVMENU: started
2018-05-26 10:09:42: F_ADVMENU: started
2018-05-26 10:10:49: F_ADVMENU: started
2018-05-26 10:15:45: getlog script started[/INDENT]
I need to admit that I'm a bit too excited to try to mess with it now (at least without some guidance ) as I cannot understand this log properly. For me there is no clear error/damage...and I'm already happy to know that the device still alive and it even list the partitions (Advanced Menu -> Show My Partitions).
What should I do now? Is just a matter of extract with SALT the correct kdz variant (that I suppose is the H815TR and not the H815) and flash it?
Thanks again for helping me
otavio_aon said:
:laugh:... it worked!
It's not fixed... but SALT has found my mobile (after I change it to USB3) 2 new things happened:
1) SALT identified all device's information (photo attached)
2) Download Mode screen changed (slightly) and does not display the "Modified" (in red) anymore. Not it shows: "633A 50.0 AS0.0 BB1 UHS || U U LG-H815TR 07.0 Hrev_10 CPU4 || H81529a" (but if I reboot the device, old message returns)
Debug log is HERE:
I need to admit that I'm a bit too excited to try to mess with it now (at least without some guidance ) as I cannot understand this log properly. For me there is no clear error/damage...and I'm already happy to know that the device still alive and it even list the partitions (Advanced Menu -> Show My Partitions).
What should I do now? Is just a matter of extract with SALT the correct kdz variant (that I suppose is the H815TR and not the H815) and flash it?
Thanks again for helping me
Click to expand...
Click to collapse
Great. On of the first things which happen when SALT is starting up is it checks for a new version. Please do not skip the update. It's really necessary to use the latest SALT version and you're using an outdated one. So just update first when ever asked.
Then do a backup in SALT before doing anything else. You can mount folders from your windows to VirtualBox and then access it from there which is the best way to backup in a VM. Check the FWUL thread ftp a howto.
When starting the backup you get asked about the type: choose "basic" or when you want to backup all your internal storage (will take hours and needs 33 GB free disk space) choose the full one. Basic will have all partitions which are important on your phone just without your personal stuff and the ROM itself as that can be easily recovered by extracting a kdz.
Now extract a kdz file of your model with SALT (the partitions you need are listed on the next step). Ensure you have the latest SALT version and ensure that no folder or the kdz file contains any spaces in its name (known bug atm).
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
sbl1
rpm
sdi
pmic
hyp
laf
aboot
tz
system
boot
modem
factory
like that:
fastboot flash sbl1 sbl1.bin
...
Then do this:
fastboot format userdata (will erase all your internal data)
fastboot format cache
fastboot reboot
Keep thumbs pressed. The first boot can take up to 15min!
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Great. On of the first things which happen when SALT is starting up is it checks for a new version. Please do not skip the update. It's really necessary to use the latest SALT version and you're using an outdated one. So just update first when ever asked.
Then do a backup in SALT before doing anything else. You can mount folders from your windows to VirtualBox and then access it from there which is the best way to backup in a VM. Check the FWUL thread ftp a howto.
When starting the backup you get asked about the type: choose "basic" or when you want to backup all your internal storage (will take hours and needs 33 GB free disk space) choose the full one. Basic will have all partitions which are important on your phone just without your personal stuff and the ROM itself as that can be easily recovered by extracting a kdz.
Click to expand...
Click to collapse
SALT updated to 3.16.0 :good:
Basic (dont need my personal data) Backup DONE :good: (and verified)
(set a Virtual Box shared folder with Auto mount, Full access and Permanent)
... however, the next part It wasn't so clear for me:
steadfasterX said:
Now extract a kdz file of your model with SALT (the partitions you need are listed on the next step). Ensure you have the latest SALT version and ensure that no folder or the kdz file contains any spaces in its name (known bug atm).
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
...
Click to expand...
Click to collapse
1) Should I download a new KDZ file and get the partitions from there?
2) Or I should get the partitions that are currently on my device?
I tried both:
1) Tried to extract a random KDZ (downloaded a time ago), but it don't know what to expect in case of success. I got a <*.kd> file and a <*.params>
2) if that is the case, it isn't very clear how to do it
otavio_aon said:
SALT updated to 3.16.0 :good:
Basic (dont need my personal data) Backup DONE :good: (and verified)
(set a Virtual Box shared folder with Auto mount, Full access and Permanent)
... however, the next part It wasn't so clear for me:
1) Should I download a new KDZ file and get the partitions from there?
2) Or I should get the partitions that are currently on my device?
I tried both:
1) Tried to extract a random KDZ (downloaded a time ago), but it don't know what to expect in case of success. I got a <*.kd> file and a <*.params>
2) if that is the case, it isn't very clear how to do it
Click to expand...
Click to collapse
Good!
Download and extract the latest version of h815 MM.. so I guess 20... whatever. Iirc 20p was the latest.
The backup with SALT is just to have it if something goes completely wrong. Then you may need it..
But to unbrick you should use the h815 20p kdz, extract it and after extraction completed you will be promoted by SALT to open the folder. Do that. Right click in that folder and choose : "open a terminal here". Then you can go on with the fastboot flash commands.
As said there is a known bug in SALT when the folder where the kdz is in contains spaces in its name or when the target folder where you extract the kdz to contains spaces in its name. So ensure that and you should be able to extract without a problem. If you can't extract a kdz share the SALT debug log after trying.
Sent from my LG-H815 using XDA Labs
OT:
Consider to press thanks from time to time when you think you get help from someone
steadfasterX said:
Download and extract the latest version of h815 MM.. so I guess 20... whatever. Iirc 20p was the latest.
...
But to unbrick you should use the h815 20p kdz, extract it and after extraction completed you will be promoted by SALT to open the folder. Do that. Right click in that folder and choose : "open a terminal here". Then you can go on with the fastboot flash commands.
Click to expand...
Click to collapse
I jsut cannot find the H815_20p anywhere ... so I'm considering using H815v29a (this version has already worked in the past) .... is it going to be a risky? Might it cause a problem? (SALT shows a AntiRollBack = 0 (which I suppose is good) in red (which I understand as a warning)
I also found the H815_20G at AutoPrime archive that seems to be an option...but I guess v29a is newer.
Also: is now the stage were I should get a rooted firmware?
Or I must go for a stock (and unrooted) ROM first... and then, when everything is done and working, I go and try to root it?
otavio_aon said:
I jsut cannot find the H815_20p anywhere ... so I'm considering using H815v29a (this version has already worked in the past) .... is it going to be a risky? Might it cause a problem? (SALT shows a AntiRollBack = 0 (which I suppose is good) in red (which I understand as a warning)
I also found the H815_20G at AutoPrime archive that seems to be an option...but I guess v29a is newer.
Also: is now the stage were I should get a rooted firmware?
Or I must go for a stock (and unrooted) ROM first... and then, when everything is done and working, I go and try to root it?
Click to expand...
Click to collapse
H815 20p is on my server, extracted or as a zip:
http://leech.binbash.it:8008/stock/LG/h815/20p/
Antirollback is in red because it's important not in general good or bad. If you would flash an ARB of anything higher then 0 to a h815 you will never be able to fully recover it.
Don't do any special things like rooting. First thing is to get back to normal and that's just pure stock.
Every side path may lead to issues.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
H815 20p is on my server, extracted or as a zip: http://leech.binbash.it:8008/stock/LG/h815/20p/
[...]
Click to expand...
Click to collapse
So I've downloaded the H81520p_00 stock ROM from your server.
In topic #10 you said that I should get files as ".bin" but in your servers they are all ".image". Should I just rename it to change the file extension? Or do I need to convert it somehow?
steadfasterX said:
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
sbl1
rpm
sdi
pmic
hyp
laf
aboot
tz
system
boot
modem
factory
like that: fastboot flash sbl1 sbl1.bin
...
Click to expand...
Click to collapse
I also tried to flash the "sdb1.bin" (assuming I just needed to rename the .image file) file into it ... but it didn't worked.
FIRST try:
rebooted in Fastboot mode
using FWUL 2.6 (same setup on VirtualBox), I started a terminal and entered command "fastboot flash sbl1 sbl1.bin "
Got Message "< waiting for any device >" ... and it was only this, even after waiting 10min.
SECOND try:
rebooted in Fastboot mode
using Win10, I started a CMD (as Admin) and entered command "fastboot flash sbl1 sbl1.bin " (PS: fastboot.exe in system path)
Got error message: FAILED (remote: cannot flash this partition in unlocked state)
Code:
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.058s]
writing 'sbl1'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.080s
So I decided to perform a simple test.
At Win10 CMD window, entered "fastboot getvar unlocked" ... and got "unlocked: yes || finished. total time: 0.008s"
At FWUL 2.6 Terminal, entered "fastboot getvar unlocked" ... and got same msg "< waiting for any device >". So apparently linux is connecting to the device while it's in download mode but cannot do it in fastboot mode.
Code:
For the records: how to reboot LG G4 in Fastboot mode:
[LIST=1]
[*] Turn OFF device
[*]remove battery
[*]hold Volume DOWN key
[*]insert battery back
[*]connect USB cable
[/LIST]
otavio_aon said:
So I've downloaded the H81520p_00 stock ROM from your server.
In topic #10 you said that I should get files as ".bin" but in your servers they are all ".image". Should I just rename it to change the file extension? Or do I need to convert it somehow?
I also tried to flash the "sdb1.bin" (assuming I just needed to rename the .image file) file into it ... but it didn't worked.
FIRST try:
rebooted in Fastboot mode
using FWUL 2.6 (same setup on VirtualBox), I started a terminal and entered command "fastboot flash sbl1 sbl1.bin "
Got Message "< waiting for any device >" ... and it was only this, even after waiting 10min.
SECOND try:
rebooted in Fastboot mode
using Win10, I started a CMD (as Admin) and entered command "fastboot flash sbl1 sbl1.bin " (PS: fastboot.exe in system path)
Got error message: FAILED (remote: cannot flash this partition in unlocked state)
So I decided to perform a simple test.
At Win10 CMD window, entered "fastboot getvar unlocked" ... and got "unlocked: yes || finished. total time: 0.008s"
At FWUL 2.6 Terminal, entered "fastboot getvar unlocked" ... and got same msg "< waiting for any device >". So apparently linux is connecting to the device while it's in download mode but cannot do it in fastboot mode.
[/LIST]
Click to expand...
Click to collapse
For the bin/image question read FAQ #11 here: https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864/post74811095
FWUL detects fastboot mode without any problems but when entering fastboot the USB id changes. That means when using VirtualBox you need to add that new USB device to FWUL. normally named android phone or similar.
But anyways the error you get in fastboot mode indicates that you can't flash anything useful in that firmware version. FWUL or windows makes no difference here.
So the only option is to flash in download mode then. Either come to IRC ( http://webchat.freenode.net/?channels=Carbonfusion-user ) or write me a PM with subject "SALT flashing mode".
Sent from my LG-H815 using XDA Labs
I have the same problem "Got error message: FAILED (remote: cannot flash this partition in unlocked state)". Please help how to flash in downloaded mode.
I have also tried "[GUIDE] Proper H815 unbrick through QFIL (Files included) by inteLzzz". Flashed different roms by LGUP. All went well, but nothing changed. Pls help.