[UNBRICK] HTC Unbricking Project

laminat · May 4, 2013

thx for help! But after unbrick i'm stuck on bootloader - no system, dont know why

edit:

I was thinking ...Now the system will not start because it is not signed but with unlock hboot the system run again ?

Sorry for my english

KernelDev101 · May 4, 2013 at 2:26 PM

laminat said:
thx for help! But after unbrick i'm stuck on bootloader - no system, dont know why

Because you need to run a RUU to get everything working again. I have pm you hun x

---------- Post added at 05:26 AM ---------- Previous post was at 05:21 AM ----------

laminat said:
thx for help! But after unbrick i'm stuck on bootloader - no system, dont know why

edit:

I was thinking ...Now the system will not start because it is not signed but with unlock hboot the system run again ?

Sorry for my english

No unlocking wont change anything PM me back thanks xx

dexter93 · May 4, 2013 at 9:08 PM

KernelDev101 said:
Then as long as he is rooted he can change his main version using the old misc version guides i did it the other day when my main version went over 4 somthing. it can be done but he needs to be rooted

Misc patching for mainver change can be achieved only if you can boot and with root access. He'd most probably have firmware mismatches too
Htcdev unlock ( if you can) and try to boot. If it boots, just patch it
Sent from the bricktator

KernelDev101 · May 4, 2013

dexter93 said:
Misc patching for mainver change can be achieved only if you can boot and with root access. He'd most probably have firmware mismatches too
Htcdev unlock ( if you can) and try to boot. If it boots, just patch it
Sent from the bricktator

He is okay now i helped him get it back to normal

Oh ye and with our sensation main ver patching ONLY works with S-OFF tested by me thousands of times

If i only unlock and root it gives me error opening input file but as soon as i gain s-off it is fine i tested this about 10 to 15 times and it only allows patching whilst my device is S-OFF x

KernelDev101 · May 4, 2013 at 11:14 PM

So dexter my uncle just got his own riff box and so i have been trying to replicate bricks all day. People say even somthing as little as CID not being right when using the writesecureflag comman can cause a brick. I have tested this command with custom roms installed custom recovery custom kernel everything but still no brick. Is there a deff answer as to the cause of so many people bricking ? What is the most common situation that is known at the moment. Because i have just tried again with viperS JB installed with 4ext and custom kernel and i did the secureflag 3 command and just rebooted to bootloader with a securtiy warning at the bootloader then i just re unlocked and it booted right up then i ran the s-off again. Thanks x

KernelDev101 · May 6, 2013 at 2:12 AM

I get this on my terminal using dmesg

Code:

[ 4636.295047] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4636.295442] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295503] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295563] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295623] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295681] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295738] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295795] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295852] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.295951] EXT4-fs error (device sdf23): ext4_put_super:819: Couldn't clean up the journal
[ 4636.306206] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306310] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306371] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306424] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306475] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306522] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306568] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306613] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306658] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306709] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306767] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.306826] EXT4-fs error (device sdf22): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4636.320969] EXT4-fs error (device sdf22): ext4_put_super:819: Couldn't clean up the journal
[ 4636.656049] hub 1-0:1.0: unable to enumerate USB device on port 3
[ 4638.380028] usb 1-3: new high-speed USB device number 97 using ehci_hcd
[ 4638.512579] usb 1-3: config 1 has an invalid interface number: 20 but max is 1
[ 4638.512582] usb 1-3: config 1 has no interface number 1
[ 4638.522632] scsi50 : usb-storage 1-3:1.20
[ 4639.527067] scsi 50:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[ 4639.528144] sd 50:0:0:0: [sdf] 4718592 512-byte logical blocks: (2.41 GB/2.25 GiB)
[ 4639.528641] sd 50:0:0:0: [sdf] Write Protect is off
[ 4639.528645] sd 50:0:0:0: [sdf] Mode Sense: 0f 0e 00 00
[ 4639.529136] sd 50:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4639.529522] sd 50:0:0:0: Attached scsi generic sg6 type 0
[ 4639.561660]  sdf: sdf1 sdf2 sdf3 sdf4 < sdf5 sdf6 sdf7 sdf8 sdf9 sdf10 sdf11 sdf12 sdf13 sdf14 sdf15 sdf16 sdf17 sdf18 sdf19 sdf20 sdf21 sdf22 sdf23 sdf24 sdf25 sdf26 sdf27 sdf28 sdf29 sdf30 sdf31 >
[ 4639.565215] sd 50:0:0:0: [sdf] Attached SCSI removable disk
[ 4640.628047] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4640.628052] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4640.637415] EXT4-fs (sdf22): warning: mounting fs with errors, running e2fsck is recommended
[ 4640.637971] EXT4-fs (sdf22): recovery complete
[ 4640.678659] EXT4-fs (sdf22): mounted filesystem with ordered data mode. Opts: (null)
[ 4640.720549] EXT4-fs (sdf27): recovery complete
[ 4640.720556] EXT4-fs (sdf27): mounted filesystem with writeback data mode. Opts: (null)
[ 4641.116053] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4641.116058] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4641.124045] EXT4-fs (sdf23): warning: mounting fs with errors, running e2fsck is recommended
[ 4641.124675] EXT4-fs (sdf23): recovery complete
[ 4641.126017] EXT4-fs (sdf23): mounted filesystem with ordered data mode. Opts: (null)
[ 4641.716190] EXT4-fs error (device sdf23): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4641.716192] Used itable blocks: 478itable unused count: 0
[ 4641.716192] 
[ 4641.716763] Aborting journal on device sdf23-8.
[ 4641.720200] EXT4-fs (sdf23): Remounting filesystem read-only
[ 4641.720206] EXT4-fs error (device sdf23) in ext4_init_inode_table:1200: IO failure
[ 4641.722647] EXT4-fs error (device sdf22): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4641.722649] Used itable blocks: 458itable unused count: 0
[ 4641.722650] 
[ 4641.728268] Aborting journal on device sdf22-8.
[ 4641.732205] EXT4-fs (sdf22): Remounting filesystem read-only
[ 4641.732211] EXT4-fs error (device sdf22) in ext4_init_inode_table:1200: IO failure
[ 4648.265549] usb 1-3: USB disconnect, device number 97
[ 4648.277576] journal commit I/O error
[ 4648.277582] journal commit I/O error
[ 4648.277584] journal commit I/O error
[ 4648.277586] journal commit I/O error
[ 4648.277588] journal commit I/O error
[ 4648.277591] journal commit I/O error
[ 4648.277595] journal commit I/O error
[ 4648.277599] journal commit I/O error
[ 4648.277603] journal commit I/O error
[ 4648.277610] journal commit I/O error
[ 4648.277612] journal commit I/O error
[ 4648.277615] journal commit I/O error
[ 4648.277621] journal commit I/O error
[ 4648.277623] journal commit I/O error
[ 4648.277625] journal commit I/O error
[ 4648.277628] journal commit I/O error
[ 4648.277631] journal commit I/O error
[ 4648.277633] journal commit I/O error
[ 4648.277638] journal commit I/O error
[ 4648.277640] journal commit I/O error
[ 4648.277643] journal commit I/O error
[ 4648.277648] journal commit I/O error
[ 4648.277650] journal commit I/O error
[ 4648.277652] journal commit I/O error
[ 4648.277656] journal commit I/O error
[ 4648.277669] journal commit I/O error
[ 4648.277673] journal commit I/O error
[ 4648.277675] journal commit I/O error
[ 4648.277682] journal commit I/O error
[ 4648.277684] journal commit I/O error
[ 4648.277687] journal commit I/O error
[ 4648.277692] journal commit I/O error
[ 4648.277694] journal commit I/O error
[ 4648.277699] journal commit I/O error
[ 4648.277703] journal commit I/O error
[ 4648.277705] journal commit I/O error
[ 4648.277707] journal commit I/O error
[ 4648.277709] journal commit I/O error
[ 4648.277712] journal commit I/O error
[ 4648.277716] journal commit I/O error
[ 4648.277720] journal commit I/O error
[ 4648.277722] journal commit I/O error
[ 4648.277725] journal commit I/O error
[ 4648.277727] journal commit I/O error
[ 4648.277731] journal commit I/O error
[ 4648.277734] journal commit I/O error
[ 4648.277737] journal commit I/O error
[ 4648.277743] journal commit I/O error
[ 4648.277747] journal commit I/O error
[ 4648.277749] journal commit I/O error
[ 4648.277753] journal commit I/O error
[ 4648.277756] journal commit I/O error
[ 4648.277759] journal commit I/O error
[ 4648.286785] sd 50:0:0:0: [sdf] Synchronizing SCSI cache
[ 4648.286823] sd 50:0:0:0: [sdf]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 4648.287025] EXT4-fs error (device sdf22): ext4_put_super:819: Couldn't clean up the journal
[ 4648.294741] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4648.294779] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4648.295219] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4648.295321] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4648.297381] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297429] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297474] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297518] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297563] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297607] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297650] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297693] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297736] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297775] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297816] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297852] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297889] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297922] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297955] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.297988] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.298021] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.298058] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.298101] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.298145] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm gvfs-gdu-volume: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.330435] EXT4-fs error (device sdf23): ext4_readdir:173: inode #2: comm pool: path /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__: directory contains a hole at offset 0
[ 4648.541095] EXT4-fs error (device sdf23): ext4_put_super:819: Couldn't clean up the journal
[ 4648.652047] hub 1-0:1.0: unable to enumerate USB device on port 3
[ 4650.376034] usb 1-3: new high-speed USB device number 99 using ehci_hcd
[ 4650.508386] usb 1-3: config 1 has an invalid interface number: 20 but max is 1
[ 4650.508391] usb 1-3: config 1 has no interface number 1
[ 4650.517538] scsi51 : usb-storage 1-3:1.20
[ 4651.517055] scsi 51:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[ 4651.522425] sd 51:0:0:0: Attached scsi generic sg6 type 0
[ 4651.522892] sd 51:0:0:0: [sdf] 4718592 512-byte logical blocks: (2.41 GB/2.25 GiB)
[ 4651.523388] sd 51:0:0:0: [sdf] Write Protect is off
[ 4651.523390] sd 51:0:0:0: [sdf] Mode Sense: 0f 0e 00 00
[ 4651.523888] sd 51:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4651.557646]  sdf: sdf1 sdf2 sdf3 sdf4 < sdf5 sdf6 sdf7 sdf8 sdf9 sdf10 sdf11 sdf12 sdf13 sdf14 sdf15 sdf16 sdf17 sdf18 sdf19 sdf20 sdf21 sdf22 sdf23 sdf24 sdf25 sdf26 sdf27 sdf28 sdf29 sdf30 sdf31 >
[ 4651.563647] sd 51:0:0:0: [sdf] Attached SCSI removable disk
[ 4652.546061] EXT4-fs (sdf27): recovery complete
[ 4652.546067] EXT4-fs (sdf27): mounted filesystem with writeback data mode. Opts: (null)
[ 4652.624040] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4652.624045] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4652.631491] EXT4-fs (sdf23): warning: mounting fs with errors, running e2fsck is recommended
[ 4652.636047] EXT4-fs (sdf23): recovery complete
[ 4652.636660] EXT4-fs (sdf23): mounted filesystem with ordered data mode. Opts: (null)
[ 4653.276048] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4653.276052] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4653.280107] EXT4-fs (sdf22): warning: mounting fs with errors, running e2fsck is recommended
[ 4653.280682] EXT4-fs (sdf22): recovery complete
[ 4653.322661] EXT4-fs (sdf22): mounted filesystem with ordered data mode. Opts: (null)
[ 4654.844046] EXT4-fs error (device sdf23): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4654.844048] Used itable blocks: 478itable unused count: 0
[ 4654.844049] 
[ 4654.844663] Aborting journal on device sdf23-8.
[ 4654.847790] EXT4-fs (sdf23): Remounting filesystem read-only
[ 4654.847797] EXT4-fs error (device sdf23) in ext4_init_inode_table:1200: IO failure
[ 4655.176051] EXT4-fs error (device sdf22): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4655.176053] Used itable blocks: 458itable unused count: 0
[ 4655.176054] 
[ 4655.208527] Aborting journal on device sdf22-8.
[ 4655.213645] EXT4-fs (sdf22): Remounting filesystem read-only
[ 4655.213652] EXT4-fs error (device sdf22) in ext4_init_inode_table:1200: IO failure
[ 4660.260800] usb 1-3: USB disconnect, device number 99
[ 4660.270478] journal commit I/O error
[ 4660.270482] journal commit I/O error
[ 4660.270484] journal commit I/O error
[ 4660.270486] journal commit I/O error
[ 4660.270488] journal commit I/O error
[ 4660.270491] journal commit I/O error
[ 4660.270495] journal commit I/O error
[ 4660.270499] journal commit I/O error
[ 4660.270504] journal commit I/O error
[ 4660.270512] journal commit I/O error
[ 4660.270514] journal commit I/O error
[ 4660.270517] journal commit I/O error
[ 4660.270522] journal commit I/O error
[ 4660.270524] journal commit I/O error
[ 4660.270526] journal commit I/O error
[ 4660.270529] journal commit I/O error
[ 4660.270532] journal commit I/O error
[ 4660.270533] journal commit I/O error
[ 4660.270538] journal commit I/O error
[ 4660.270541] journal commit I/O error
[ 4660.270543] journal commit I/O error
[ 4660.270547] journal commit I/O error
[ 4660.270550] journal commit I/O error
[ 4660.270552] journal commit I/O error
[ 4660.270555] journal commit I/O error
[ 4660.270565] journal commit I/O error
[ 4660.270569] journal commit I/O error
[ 4660.270571] journal commit I/O error
[ 4660.270576] journal commit I/O error
[ 4660.270578] journal commit I/O error
[ 4660.270580] journal commit I/O error
[ 4660.270585] journal commit I/O error
[ 4660.270587] journal commit I/O error
[ 4660.270592] journal commit I/O error
[ 4660.270595] journal commit I/O error
[ 4660.270597] journal commit I/O error
[ 4660.270600] journal commit I/O error
[ 4660.270602] journal commit I/O error
[ 4660.270605] journal commit I/O error
[ 4660.270608] journal commit I/O error
[ 4660.270612] journal commit I/O error
[ 4660.270615] journal commit I/O error
[ 4660.270618] journal commit I/O error
[ 4660.270620] journal commit I/O error
[ 4660.270623] journal commit I/O error
[ 4660.270625] journal commit I/O error
[ 4660.270629] journal commit I/O error
[ 4660.270634] journal commit I/O error
[ 4660.270638] journal commit I/O error
[ 4660.270640] journal commit I/O error
[ 4660.270644] journal commit I/O error
[ 4660.270647] journal commit I/O error
[ 4660.270649] journal commit I/O error
[ 4660.276741] sd 51:0:0:0: [sdf] Synchronizing SCSI cache
[ 4660.276808] sd 51:0:0:0: [sdf]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 4660.278688] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4660.278763] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4660.285980] EXT4-fs error (device sdf22): ext4_put_super:819: Couldn't clean up the journal
[ 4660.321606] EXT4-fs error (device sdf23): ext4_put_super:819: Couldn't clean up the journal
[ 4660.644046] usb 1-3: new high-speed USB device number 100 using ehci_hcd
[ 4660.778670] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 4660.778751] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[ 4669.380215] usb 1-3: USB disconnect, device number 100
[ 4669.380455] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 4669.380485] qcserial 1-3:1.0: device disconnected
[ 4898.736027] usb 1-3: new high-speed USB device number 101 using ehci_hcd
[ 4898.868377] usb 1-3: config 1 has an invalid interface number: 20 but max is 1
[ 4898.868384] usb 1-3: config 1 has no interface number 1
[ 4898.876686] scsi52 : usb-storage 1-3:1.20
[ 4899.877957] scsi 52:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
[ 4899.878914] sd 52:0:0:0: Attached scsi generic sg6 type 0
[ 4899.881461] sd 52:0:0:0: [sdf] 4718592 512-byte logical blocks: (2.41 GB/2.25 GiB)
[ 4899.882011] sd 52:0:0:0: [sdf] Write Protect is off
[ 4899.882017] sd 52:0:0:0: [sdf] Mode Sense: 0f 0e 00 00
[ 4899.882514] sd 52:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4899.914392]  sdf: sdf1 sdf2 sdf3 sdf4 < sdf5 sdf6 sdf7 sdf8 sdf9 sdf10 sdf11 sdf12 sdf13 sdf14 sdf15 sdf16 sdf17 sdf18 sdf19 sdf20 sdf21 sdf22 sdf23 sdf24 sdf25 sdf26 sdf27 sdf28 sdf29 sdf30 sdf31 >
[ 4899.924765] sd 52:0:0:0: [sdf] Attached SCSI removable disk
[ 4901.464164] EXT4-fs (sdf27): recovery complete
[ 4901.464170] EXT4-fs (sdf27): mounted filesystem with writeback data mode. Opts: (null)
[ 4901.550384] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4901.550388] EXT4-fs warning (device sdf22): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4901.552483] EXT4-fs (sdf22): warning: mounting fs with errors, running e2fsck is recommended
[ 4901.556076] EXT4-fs (sdf22): recovery complete
[ 4901.558265] EXT4-fs (sdf22): mounted filesystem with ordered data mode. Opts: (null)
[ 4901.824027] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4371: Filesystem error recorded from previous mount: IO failure
[ 4901.824031] EXT4-fs warning (device sdf23): ext4_clear_journal_err:4372: Marking fs in need of filesystem check.
[ 4901.828107] EXT4-fs (sdf23): warning: mounting fs with errors, running e2fsck is recommended
[ 4901.828675] EXT4-fs (sdf23): recovery complete
[ 4901.829900] EXT4-fs (sdf23): mounted filesystem with ordered data mode. Opts: (null)
[ 4905.140023] EXT4-fs error (device sdf23): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4905.140025] Used itable blocks: 478itable unused count: 0
[ 4905.140026] 
[ 4905.140519] Aborting journal on device sdf23-8.
[ 4905.146385] EXT4-fs (sdf23): Remounting filesystem read-only
[ 4905.146390] EXT4-fs error (device sdf23) in ext4_init_inode_table:1200: IO failure
[ 4905.147755] EXT4-fs error (device sdf22): ext4_init_inode_table:1157: comm ext4lazyinit: Something is wrong with group 0
[ 4905.147757] Used itable blocks: 458itable unused count: 0
[ 4905.147758] 
[ 4905.150505] Aborting journal on device sdf22-8.
[ 4905.158144] EXT4-fs (sdf22): Remounting filesystem read-only
[ 4905.158149] EXT4-fs error (device sdf22) in ext4_init_inode_table:1200: IO failure
[ 4908.642158] usb 1-3: USB disconnect, device number 101
[ 4908.647741] journal commit I/O error
[ 4908.647748] journal commit I/O error
[ 4908.647750] journal commit I/O error
[ 4908.647752] journal commit I/O error
[ 4908.647753] journal commit I/O error
[ 4908.647756] journal commit I/O error
[ 4908.647761] journal commit I/O error
[ 4908.647765] journal commit I/O error
[ 4908.647770] journal commit I/O error
[ 4908.647777] journal commit I/O error
[ 4908.647779] journal commit I/O error
[ 4908.647782] journal commit I/O error
[ 4908.647788] journal commit I/O error
[ 4908.647791] journal commit I/O error
[ 4908.647793] journal commit I/O error
[ 4908.647796] journal commit I/O error
[ 4908.647799] journal commit I/O error
[ 4908.647801] journal commit I/O error
[ 4908.647805] journal commit I/O error
[ 4908.647808] journal commit I/O error
[ 4908.647811] journal commit I/O error
[ 4908.647814] journal commit I/O error
[ 4908.647817] journal commit I/O error
[ 4908.647819] journal commit I/O error
[ 4908.647823] journal commit I/O error
[ 4908.647835] journal commit I/O error
[ 4908.647839] journal commit I/O error
[ 4908.647841] journal commit I/O error
[ 4908.647845] journal commit I/O error
[ 4908.647847] journal commit I/O error
[ 4908.647850] journal commit I/O error
[ 4908.647856] journal commit I/O error
[ 4908.647859] journal commit I/O error
[ 4908.647864] journal commit I/O error
[ 4908.647868] journal commit I/O error
[ 4908.647870] journal commit I/O error
[ 4908.647872] journal commit I/O error
[ 4908.647876] journal commit I/O error
[ 4908.647880] journal commit I/O error
[ 4908.647883] journal commit I/O error
[ 4908.647888] journal commit I/O error
[ 4908.647890] journal commit I/O error
[ 4908.647893] journal commit I/O error
[ 4908.647895] journal commit I/O error
[ 4908.647899] journal commit I/O error
[ 4908.647900] journal commit I/O error
[ 4908.647904] journal commit I/O error
[ 4908.647910] journal commit I/O error
[ 4908.647915] journal commit I/O error
[ 4908.647917] journal commit I/O error
[ 4908.647921] journal commit I/O error
[ 4908.647924] journal commit I/O error
[ 4908.647926] journal commit I/O error
[ 4908.656272] sd 52:0:0:0: [sdf] Synchronizing SCSI cache
[ 4908.656310] sd 52:0:0:0: [sdf]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 4908.658396] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4908.658434] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4908.658500] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4908.658532] EXT4-fs error (device sdf23): ext4_find_entry:935: inode #2: comm gvfsd-trash: reading directory lblock 0
[ 4908.662784] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4908.662842] EXT4-fs error (device sdf22): ext4_find_entry:935: inode #2: comm pool: reading directory lblock 0
[ 4908.671265] EXT4-fs error (device sdf23): ext4_put_super:819: Couldn't clean up the journal
[ 4908.683946] EXT4-fs error (device sdf22): ext4_put_super:819: Couldn't clean up the journal
[ 4908.968272] hub 1-0:1.0: unable to enumerate USB device on port 3
[email protected]:~/Unbrick_Pyramid_32bit$

Everything with unbricking goes fine but it wont unbrick now ? anyone want to help xx

---------- Post added at 05:12 PM ---------- Previous post was at 04:46 PM ----------

No1 want's to help then no ? fine that's okay ill remember that. Not being childish but i wote to Dexter he been online but ignored every single PM i wrote. But all i do is help others in need well guess i will stop that now and concentrate on myself. Thanks.

Don't mean to be bitchy but it is very true.

RussianBear · May 6, 2013 at 2:41 AM

You expect an answer in thirty minutes? Dex lives in Greece, last time I've checked, btw.

cajunflavoredbob · May 6, 2013 at 2:56 AM

KernelDev101 said:
---------- Post added at 05:12 PM ---------- Previous post was at 04:46 PM ----------

No1 want's to help then no ? fine that's okay ill remember that. Not being childish but i wote to Dexter he been online but ignored every single PM i wrote. But all i do is help others in need well guess i will stop that now and concentrate on myself. Thanks.

Don't mean to be bitchy but it is very true.

Wow. How childish and entitled can a person possibly be?

Online status doesn't mean jack squat. He might have an open XDA tab while he's asleep. Although with an attitude like yours, don't expect much, if any help...

KernelDev101 · May 6, 2013 at 2:58 AM

RussianBear said:
You expect an answer in thirty minutes? Dex lives in Greece, last time I've checked, btw.

No of course not hun i PM him ages and ages ago when he was online and he was online for 2 hours after i PM him. Can you give insight into it ? now on brick detect it just gives me sdf not sdf12 :S

RussianBear · May 6, 2013 at 3:09 AM

KernelDev101 said:
No of course not hun i PM him ages and ages ago when he was online and he was online for 2 hours after i PM him. Can you give insight into it ? now on brick detect it just gives me sdf not sdf12 :S

doesn't look like it's entering the needed mode. How did you brick it?

KernelDev101 · May 6, 2013 at 3:14 AM

RussianBear said:
doesn't look like it's entering the needed mode. How did you brick it?

I'm testing bricking and wanted to test how people was bricking because i tried bricking using every method people was saying they did but was unable to replicate so they must have done somthing else. and it seems the ONLY was i found to brick was to return to s-on on a custom hboot. no matter the changes i did to system recovery or boot it wouldnt brick just put tampered at top of bootloader. Then i flashed hboot from Juopunutbear and did the s-on command and it bricked 1st i recovered and all was well. Then i flashed RUU ICS and rebooted itself after RUU was done and went back into bricked mode

---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------

KernelDev101 said:
I'm testing bricking and wanted to test how people was bricking because i tried bricking using every method people was saying they did but was unable to replicate so they must have done somthing else. and it seems the ONLY was i found to brick was to return to s-on on a custom hboot. no matter the changes i did to system recovery or boot it wouldnt brick just put tampered at top of bootloader. Then i flashed hboot from Juopunutbear and did the s-on command and it bricked 1st i recovered and all was well. Then i flashed RUU ICS and rebooted itself after RUU was done and went back into bricked mode

[email protected]:~/Unbrick_Pyramid_32bit$ ./brickdetect.sh
Searching for bricked device...
The bricked device is on
sdf
Use the above node to perform operations using the emmc_recover tool
[email protected]:~/Unbrick_Pyramid_32bit$

dexter93 · May 6, 2013

KernelDev101 said:
I get this on my terminal using dmesg

Everything with unbricking goes fine but it wont unbrick now ? anyone want to help xx

---------- Post added at 05:12 PM ---------- Previous post was at 04:46 PM ----------

No1 want's to help then no ? fine that's okay ill remember that. Not being childish but i wote to Dexter he been online but ignored every single PM i wrote. But all i do is help others in need well guess i will stop that now and concentrate on myself. Thanks.

Don't mean to be bitchy but it is very true.

Just because someone is online, it doesn't mean he's always on a pc and has the time to go through everything. I'll be more than happy to explain a few things and answer your questions via pm, no need to derail the thread. Please use

KernelDev101 · May 7, 2013 at 11:13 PM

What does this mean ? take a look

http://pastebin.ca/2375973

Here is a short snippet of what's on pastbin

[ 78.767607] Raw EDID:
[ 78.767609] 00 ff ff ff ff ff ff 00 04 72 80 ad 11 dc 50 73
[ 78.767611] 00 a1 ff 03 08 29 1a 78 e8 9a e5 a6 58 49 99 23
[ 78.767613] 11 50 54 bf ef 80 90 4f 95 0f 81 80 81 40 81 0f
[ 78.767615] 81 00 71 90 71 4f c4 22 a0 a0 50 84 1a 30 30 20
[ 78.767617] 36 00 9a 01 11 00 00 1e 00 00 00 fd 00 38 4c 1f
[ 78.767618] 54 0e 00 0a 20 20 20 20 20 20 00 00 00 ff 00 4c
[ 78.767620] 38 30 30 43 30 33 32 34 30 32 34 0a 00 00 00 fc
[ 78.767622] 00 41 4c 31 39 31 36 57 0a 20 20 20 20 20 00 0a
[ 78.817676] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 107

dexter93 · May 8, 2013 at 12:23 AM

KernelDev101 said:
What does this mean ? take a look

http://pastebin.ca/2375973

Here is a short snippet of what's on pastbin

[ 78.767607] Raw EDID:
[ 78.767609] 00 ff ff ff ff ff ff 00 04 72 80 ad 11 dc 50 73
[ 78.767611] 00 a1 ff 03 08 29 1a 78 e8 9a e5 a6 58 49 99 23
[ 78.767613] 11 50 54 bf ef 80 90 4f 95 0f 81 80 81 40 81 0f
[ 78.767615] 81 00 71 90 71 4f c4 22 a0 a0 50 84 1a 30 30 20
[ 78.767617] 36 00 9a 01 11 00 00 1e 00 00 00 fd 00 38 4c 1f
[ 78.767618] 54 0e 00 0a 20 20 20 20 20 20 00 00 00 ff 00 4c
[ 78.767620] 38 30 30 43 30 33 32 34 30 32 34 0a 00 00 00 fc
[ 78.767622] 00 41 4c 31 39 31 36 57 0a 20 20 20 20 20 00 0a
[ 78.817676] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 107

It means that you need to check your monitors and graphics setup. Totally irrelevant

The worrying stuff is here

Code:

 [  120.074493] usb 1-3: USB disconnect, device number 10
[  120.074728] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[  120.074760] qcserial 1-3:1.0: device disconnected
[  122.720062] usb 1-3: new high-speed USB device number 11 using ehci_hcd
[  123.248017] usb 1-3: device not accepting address 11, error -71
[  123.304472] hub 1-0:1.0: unable to enumerate USB device on port 3

How did you brick exactly? Mind posting step by step what you did?
Sent from the big brick

KernelDev101 · May 8, 2013 at 11:49 AM

dexter93 said:
It means that you need to check your monitors and graphics setup. Totally irrelevant

The worrying stuff is here

Code:

[ 120.074493] usb 1-3: USB disconnect, device number 10 [ 120.074728] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0 [ 120.074760] qcserial 1-3:1.0: device disconnected [ 122.720062] usb 1-3: new high-speed USB device number 11 using ehci_hcd [ 123.248017] usb 1-3: device not accepting address 11, error -71 [ 123.304472] hub 1-0:1.0: unable to enumerate USB device on port 3

How did you brick exactly? Mind posting step by step what you did?
Sent from the big brick

Turned S-ON while i had JuopunutBear Hboot installed 1st everything was fine then i flashed RUU rebooted after the RUU had finished and it went straight back into bricked mode. But this time i couldnt use unbrick method because instead of getting a node of sdf12 i get just sdf and when using the unbrick tools it cannot find my phone. :S if i cant find a fix im sending back to the online store in morning

RussianBear · May 8, 2013 at 1:30 PM

^^ didn't you say you had a riff box?

dexter93 · May 8, 2013 at 5:08 PM

KernelDev101 said:
Turned S-ON while i had JuopunutBear Hboot installed 1st everything was fine then i flashed RUU rebooted after the RUU had finished and it went straight back into bricked mode. But this time i couldnt use unbrick method because instead of getting a node of sdf12 i get just sdf and when using the unbrick tools it cannot find my phone. :S if i cant find a fix im sending back to the online store in morning

While that is fixable. .

RussianBear said:
^^ didn't you say you had a riff box?

This one is the best solution and most hassle free

Sent from the bricktator

KernelDev101 · May 8, 2013 at 5:31 PM

dexter93 said:
While that is fixable. .

This one is the best solution and most hassle free

Sent from the bricktator

No my uncle has riff box but i still have warranty and if i get him to j tag it then my warranty is gone because they will know it been opened up

so i have packaged it up and it being sent back in morning they said they will replace for me

blade_h · Mar 18, 2012 81 5 38

Hello..Pease see my situaton http://forum.xda-developers.com/showthread.php?p=41725245#post41725245 and tell me if have way to use your guide to bring my phone from greiviard!
Thnaks

KernelDev101 · May 23, 2013 at 7:58 PM

blade_h said:
Hello..Pease see my situaton http://forum.xda-developers.com/showthread.php?p=41725245#post41725245 and tell me if have way to use your guide to bring my phone from greiviard!
Thnaks

Your phone is not bricked this will not help you in anyway shape or form. Look up how to create goldcard it might help you otherwise the only thing you can do is flash bootloader via hboot screen and eject battery when the bootloader is flashing this will brick your device then you can use this guide to flash a older hboot like 1.17 then you can use the goldcard method to flash the RUU for your device. I have done this before and it works fine thanks xx

[UNBRICK] HTC Unbricking Project

Did this work?

Yes!

No

I'm Waiting For Release

New member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Recognized Contributor

Senior Member

Senior Member

Recognized Contributor

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Recognized Contributor

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member