HTC M7 bootloop E:cant mount sdcard etc AYUDA

[aaidaan]

alguien me ayuda a obtener una RUU tengo un problema de bootloop y quiero ver si con una consigo revivir mi htc one M7 lo que pasa es que en el recovery no puedo desde el sideload no puedo hacer nada por desconocidos motivos se me pone E: cant mount cache recovery
o cant mount sdcard alguien que me ayude acerca del tema se lo agradeceria.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.14.531.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35PW907601
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3863mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

[A.S.A.P.]

Hola Aaidaan :-)


Uhmmm ... lo primero que intentaría sería flashear nuevamente un recovery (TWRP) y probar.....

Por otro lado, eres S-ON, y la última RUU de T-Mobile que existe "creo" que es anterior (android v4.3) a la versión que llevas actualmente, por lo que no podrías flashearla (hacer downgrade) mientras seas S-ON...

Esta es la RUU de la que hablo:

http://www.htc1guru.com/?wpfb_dl=140

Asi pues, cuando tengas un recovery operativo, tendrías que salir del paso con una rom cocinada

----------


Salu2 ;-)

[aaidaan]

Hola Aaidaan :-)


Uhmmm ... lo primero que intentaría sería flashear nuevamente un recovery (TWRP) y probar.....

Por otro lado, eres S-ON, y la última RUU de T-Mobile que existe "creo" que es anterior (android v4.3) a la versión que llevas actualmente, por lo que no podrías flashearla (hacer downgrade) mientras seas S-ON...

Esta es la RUU de la que hablo:

http://www.htc1guru.com/?wpfb_dl=140

Asi pues, cuando tengas un recovery operativo, tendrías que salir del paso con una rom cocinada

----------


Salu2 ;-)

Gracias por responder man, mira te cuento, e hecho bastante flasheado ROM's Cambiado el Recovery (cambiando el recovery TWRP o CWM no sucede nada se queda el mismo que ya tenia no puedo flashear otro)
al intentar montar una ROM me aparece can't mount /data
no puedo hacer factory reset por que este me manda al recovery
ya intente formatear TODO el telefono con el ADB shell y formatear con mkfs.ext4
al intentar bloquear el bootloader no se bloquea al meter el comando fastboot oem lock no sucede nada se reinicia y queda igual.
segun lo que llevo de avance es que quedaron archivos corruptos en la particion y aun no se como borrarlos. te muestro:
al introducir esto en el adb shell
mount /data
aparece esto:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument

segun al introducir esto:
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
me aparece esto:


~ # /sbin/e2fsck -n -f /dev/block/mmcblk0p37
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 246211 has zero dtime. Fix? no

Inodes that were part of a corrupted orphan linked list found. Fix? no

Inode 246644 was part of the orphaned inode list. IGNORED.
Inode 248427 was part of the orphaned inode list. IGNORED.
Inode 251366 was part of the orphaned inode list. IGNORED.

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 893558: 1894656 1894657 1894658 1894659 18946
60 1894661 1894662 1894663 1894664 1894665 1894666 1894667 1894668 1894669 18946
70 1894671 1894672 1894673 1894674 1894675 1894676 1894677 1894678 1894679 18946
80 1894681 1894682 1894683 1894684 1894685 1894686 1894687 1894688 1894689 18946
90 1894691 1894692 1894693 1894694 1894695 1894696 1894697 1894698 1894699 18947
00 1894701 1894702 1894703 1894704 1894705 1894706 1894707 1894708 1894709 18947
10 1894711 1894712 1894713 1894714 1894715 1894716 1894717 1894718 1894719 18947
20 1894721 1894722 1894723 1894724 1894725 1894726 1894727 1894728 1894729 18947
30 1894731 1894732 1894733 1894734 1894735 1894736 1894737 1894738 1894739 18947
40 1894741 1894742 1894743 1894744 1894745 1894746 1894747 1894748 1894749 18947
50 1894751 1894752 1894753 1894754 1894755 1894756 1894757 1894758 1894759 18947
60 1894761 1894762 1894763 1894764 1894765 1894766 1894767 1894768 1894769 18947
70 1894771 1894772 1894773 1894774 1894775 1894776 1894777 1894778 1894779 18947
80 1894781 1894782 1894783 1894784 1894785 1894786 1894787 1894788 1894789
Multiply-claimed block(s) in inode 902007: 1894656 1894657 1894658 1894659 18946
60 1894661 1894662 1894663 1894664 1894665 1894666 1894667 1894668 1894669 18946
70 1894671 1894672 1894673 1894674 1894675 1894676 1894677 1894678 1894679 18946
80 1894681 1894682 1894683 1894684 1894685 1894686 1894687 1894688 1894689 18946
90 1894691 1894692 1894693 1894694 1894695 1894696 1894697 1894698 1894699 18947
00 1894701 1894702 1894703 1894704 1894705 1894706 1894707 1894708 1894709 18947
10 1894711 1894712 1894713 1894714 1894715 1894716 1894717 1894718 1894719 18947
20 1894721 1894722 1894723 1894724 1894725 1894726 1894727 1894728 1894729 18947
30 1894731 1894732 1894733 1894734 1894735 1894736 1894737 1894738 1894739 18947
40 1894741 1894742 1894743 1894744 1894745 1894746 1894747 1894748 1894749 18947
50 1894751 1894752 1894753 1894754 1894755 1894756 1894757 1894758 1894759 18947
60 1894761 1894762 1894763 1894764 1894765 1894766 1894767 1894768 1894769 18947
70 1894771 1894772 1894773 1894774 1894775 1894776 1894777 1894778 1894779 18947
80 1894781 1894782 1894783 1894784 1894785 1894786 1894787 1894788 1894789
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 2 inodes containing multiply-claimed blocks.)

File /media/0/Android/data/com.ea.games.r3_row/.depot/asset_list_base.txtCache.t
xt (inode #893558, mod time Sun Dec 21 06:11:00 2014)
has 134 multiply-claimed block(s), shared with 1 file(s):
/media/0/Android/data/com.ea.games.r3_row/.depot/vehicles/1995_ferrari_f
50/1995_ferrari_f50_int_shadows.atc.dds.z.bin (inode #902007, mod time Sun Dec 2
1 06:11:13 2014)
Clone multiply-claimed blocks? no

Delete file? no

File /media/0/Android/data/com.ea.games.r3_row/.depot/vehicles/1995_ferrari_f50/
1995_ferrari_f50_int_shadows.atc.dds.z.bin (inode #902007, mod time Sun Dec 21 0
6:11:13 2014)
has 134 multiply-claimed block(s), shared with 1 file(s):
/media/0/Android/data/com.ea.games.r3_row/.depot/asset_list_base.txtCach
e.txt (inode #893558, mod time Sun Dec 21 06:11:00 2014)
Clone multiply-claimed blocks? no

Delete file? no

Pass 2: Checking directory structure
Entry '2013_ferrari_458_spider' in /media/0/Android/data/com.ea.games.r3_row/.de
pot/vehicles (893155) has deleted/unused inode 902076. Clear? no

Entry '2012_ferrari_ff_d.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902068. Clear? no

Entry '2012_ferrari_ff_d.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, should be
2).
Fix? no

Entry '2012_ferrari_ff_b.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902069. Clear? no

Entry '2012_ferrari_ff_b.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, should be
2).
Fix? no

Entry '2012_ferrari_ff_f.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902070. Clear? no

Entry '2012_ferrari_ff_f.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, should be
2).
Fix? no

Entry '2012_ferrari_ff_g.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902071. Clear? no

Entry '2012_ferrari_ff_g.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, should be
2).
Fix? no

Entry '2012_ferrari_ff_h.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902073. Clear? no

Entry '2012_ferrari_ff_h.m3g' in /media/0/Android/data/com.ea.games.r3_row/.depo
t/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, should be
2).
Fix? no

Entry '2012_ferrari_ff_int.points' in /media/0/Android/data/com.ea.games.r3_row/
.depot/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902074. Clear
? no

Entry '2012_ferrari_ff_int.points' in /media/0/Android/data/com.ea.games.r3_row/
.depot/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, shoul
d be 2).
Fix? no

Entry '2012_ferrari_ff_cab.atc.dds.z' in /media/0/Android/data/com.ea.games.r3_r
ow/.depot/vehicles/2012_ferrari_ff (902004) has deleted/unused inode 902075. Cl
ear? no

Entry '2012_ferrari_ff_cab.atc.dds.z' in /media/0/Android/data/com.ea.games.r3_r
ow/.depot/vehicles/2012_ferrari_ff (902004) has an incorrect filetype (was 1, sh
ould be 2).
Fix? no

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 893155 ref count is 30, should be 29. Fix? no

Unattached inode 902097
Connect to /lost+found? no

Unattached inode 902098
Connect to /lost+found? no

Unattached inode 902099
Connect to /lost+found? no

Unattached inode 902100
Connect to /lost+found? no

Unattached inode 902101
Connect to /lost+found? no

Unattached inode 902102
Connect to /lost+found? no

Unattached inode 902103
Connect to /lost+found? no

Unattached inode 902104
Connect to /lost+found? no

Unattached inode 902105
Connect to /lost+found? no

Pass 5: Checking group summary information
Block bitmap differences: -(983694--983695) -(987550--987551) -(1878784--187884
7) -(1878887--1879039) -(1880032--1880052) -(1895552--1895654) -(1895663--189581
5) -(1896064--1896125) -(1896192--1896401) -(1896416--1896435) +(1902624--190264
0) +(1902656--1902689) +(1902720--1902737) +(1903360--1903560) -(3614513--361451
5) -(3619063--3619078) -(3619095--3619109) -(3622253--3622261) -(3622263--362226
4) -3622266 -(3622274--3622277) -(3622279--3622281) -3622283 -(3682059--3682061)
-5512226 -(5649452--5649453)
Fix? no

Free blocks count wrong for group #57 (21828, counted=17782).
Fix? no

Free blocks count wrong for group #110 (6279, counted=6096).
Fix? no

Free blocks count wrong for group #112 (3880, counted=3795).
Fix? no

Free blocks count wrong (1807251, counted=1772185).
Fix? no

Inode bitmap differences: -246211 -246644 -248427 -251366 -(902068--902071) -(9
02073--902078) -(902081--902096) +902105
Fix? no

Free inodes count wrong for group #110 (7179, counted=7085).
Fix? no

Directories count wrong for group #110 (56, counted=59).
Fix? no

Free inodes count wrong (1669628, counted=1669175).
Fix? no


/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*

/dev/block/mmcblk0p37: 34308/1703936 files (6.4% non-contiguous), 5008493/681574
4 blocks
de verdad gracias por tu tiempo. tu ya me habias ayudado antes cuando recien comenzaba con este HTC.

[A.S.A.P.]

Hola Aaidaan :-)


Uhmmm... pues es que yo sólo veo 2 posibilidades:

- O poder flashear la RUU que corresponda a ese modelo en concreto,

- O tener un recovery 100% funcional para tirar de roms cocinadas...

-----------


Salu2 ;-)

[aaidaan]

Hola Aaidaan :-)


Uhmmm... pues es que yo sólo veo 2 posibilidades:

- O poder flashear la RUU que corresponda a ese modelo en concreto,

- O tener un recovery 100% funcional para tirar de roms cocinadas...

-----------


Salu2 ;-)


lo de la RUU lo veo complejo por no poder bloquear el bootloader. Intentare mejor hacer funcionar el recovery
:gracias: