Bricked! Possible fried eMMC chip? - AT&T HTC One (M7)

Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!

skandalous1 said:
Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!
Click to expand...
Click to collapse
Did you fastboot erase cache ?

clsA said:
Did you fastboot erase cache ?
Click to expand...
Click to collapse
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.

skandalous1 said:
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.
Click to expand...
Click to collapse
Pretty crazy .. I hope you get it solved

Related

[Q] HTC One Bootloader Issues - Can't Recover At All

Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
sprezz32 said:
Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
Click to expand...
Click to collapse
How about this
http://forum.xda-developers.com/showthread.php?t=2676986
sprezz32 said:
Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
Click to expand...
Click to collapse
your going to reflash recovery then a rom
download twrp 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
then flash it in fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then download the rom post below and sideload it to your phone
boot to recovery then
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
mb_guy said:
How about this
http://forum.xda-developers.com/showthread.php?t=2676986
Click to expand...
Click to collapse
He can't get into recovery
Thank you!
Thank you for your help! Your instructions worked perfectly. As a side note, I noticed that I could use adb when the TWRP recovery image was loaded, but not when I was just in the bootloader screen. Anyway, thank you again for the help!

[Q] Rooted phone, no custom ROM boot looping

Hey guys,
I've seen plenty threads regarding custom ROMs boot looping, but nothing so far regarding a rooted, stock ROM. I am unaware if I received an OTA (wasn't prompted or anything) or what exactly just changed, but I've had my phone rooted for 4 months now with no issue but suddenly today I noticed that apps were lagging and acting weird so I rebooted my phone. After startup, the phone will go to the home screen and load, but will reboot after 1 minute. I've verified that the phone will not loop once I make it to recovery (TWRP 2.6.3.3) but that's as far as I've gotten. For starters, here is the getvar for the phone:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4T.24.3218.09
version-cpld: None
version-microp: None
version-main: 4.18.502.7
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4168mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-c6bbb6d4
hbootpreupdate: 11
gencheckpt: 0
I'm not that experienced with rooting and such, I was able to teach myself enough to do the rooting and adding recovery but I've not had any issues so I'm scratching my head a bit here. I don't think that resetting to factory and starting over is a good first start, but I don't think I've made any recovery points to roll back to (I'm not sure if it will auto-add recovery points), so where do I go from here? Any and all help is greatly appreciated!
light_pollution said:
Hey guys,
I've seen plenty threads regarding custom ROMs boot looping, but nothing so far regarding a rooted, stock ROM. I am unaware if I received an OTA (wasn't prompted or anything) or what exactly just changed, but I've had my phone rooted for 4 months now with no issue but suddenly today I noticed that apps were lagging and acting weird so I rebooted my phone. After startup, the phone will go to the home screen and load, but will reboot after 1 minute. I've verified that the phone will not loop once I make it to recovery (TWRP 2.6.3.3) but that's as far as I've gotten. For starters, here is the getvar for the phone:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4T.24.3218.09
version-cpld: None
version-microp: None
version-main: 4.18.502.7
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4168mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-c6bbb6d4
hbootpreupdate: 11
gencheckpt: 0
I'm not that experienced with rooting and such, I was able to teach myself enough to do the rooting and adding recovery but I've not had any issues so I'm scratching my head a bit here. I don't think that resetting to factory and starting over is a good first start, but I don't think I've made any recovery points to roll back to (I'm not sure if it will auto-add recovery points), so where do I go from here? Any and all help is greatly appreciated!
Click to expand...
Click to collapse
start by wiping cache and dalvik cache from twrp then reboot and see if you are able to boot in the OS

Soft bricked htc one m7_ul !!need help to flash ruu

Hi ,
Yesterday I tried to root my htc one m7_ul ,
I unlocked the bootloader success fully , installed cwm but when I came to install Supersu a message promp after flashing It was something like :yes fix root
disable recovery flash
and no cant remember what I choose but after this I wasnt able to boot into android anymore .
So I made some reasearch and found a guide on how to unbrick using RUU
so I relocked the bootloader using fastboot and tried to flash a zip ruu (bottom of the post) and then this message pop on cmd ;
"invalid sparse file format at header magi"
so now I am stuck
i tried to re unlock the bootloader and using sideload to transfer a rom using adb but after flashing the token I enter recovery (cwm) and I dont get why because I relocked the boot loader and after rebooting I still have a relocked device.
my phone :
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.17.666.35
version-misc: PVT SHIP S-ON
serialno: HT345W913157
imei: 354439054403581
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: BM___001
battery-status: low
battery-voltage: 3527mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
this phone used to be a Bell phone but now is Unlocked .
and Im trying to flash this ruu PN07IMG_M7_UL_L50_SENSE60_MR_BM_7.17.666.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420193_signed.zip
from this forum :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
thanks everyone :good::good:

Softbrick? HTC One Max

Dear xda community,
2 days ago I accidentally wiped the Dalvik Cache, System, Cache, Data and Internal Storage of my device using TWRP advanced wipe, I'm fairly new to all of this and had trouble finding and/or flashing the right RUU on my device.
I tried installing CM 12.1 and a selection of gapps since I couldn't find any stock roms but it gets stuck on the logo.
I have access to the recovery and fastboot and can transfer files on an external SD.
Any advice would be really appreciated!
Here is my getvar all:
version: 0.5
version-bootloader: 2.49.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 3.19.161.3
version-misc: PVT SHIP S-ON
serialno: ----------------------
imei: --------------------------
meid: 00000000000000
product: t6ul
platform: HBOOT-8064
modelid: 0P3P51000
cidnum: VODAP110
battery-status: good
battery-voltage: 3731mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0

HTC 825 Bootloop 32 header error

Hi,
I accidentally deleted all the system files when I was trying to do a factory reset ( I know, stupid mistake)
So here I am without OS stuck in a bootloop (the white HTC logo)
From an error to another i got stuck at the "remote: 32 header error" when trying to flash with fastboot an RUU
I also tried using a backup from the internet but after it completes and it reboots its gets stuck at the HTC logo.
Some help would be really welcome
This is from getvar:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 3.0.U205561.60412G
version-cpld: None
version-microp: None
version-main: 1.00.401.4
version-misc: PVT SHIP S-ON
serialno: HT65WBW00034
imei: 357488070783853
imei2: Not Support
meid: 00000000000000
product: a56_uhl
platform: hTCBmsm8226
modelid: 2PUK20000
cidnum: HTC__034
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 2d0013a9
hbootpreupdate: 11
gencheckpt: 0

Categories

Resources