Trying to load an RUU to my soft-bricked VZW htc one - One (M7) Q&A, Help & Troubleshooting

I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA441S903495
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.

Williamck said:
I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.
Click to expand...
Click to collapse
Just a quick FYI. TWRP signature fail is because your bootloader is locked. You must unlock the bootloader to flash any custom software. Never mind TWRP for now. You need the bootloader locked to flash an ruu.
Try this RUU. https://www.androidfilehost.com/?fid=24052804347761412 It's in zip form so you'll need to manually flash it with htc_fastboot which you can download here https://www.androidfilehost.com/?fid=95916177934550031.
Download both files. Rename the ruu zip file to "ruu" then copy both htc_fastboot and the ruu to your fastboot folder.
Boot the phone to fastboot usb mode in the bootloader. Then flash the ruu with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The progress bar on the phone screen won't quite reach 100% that's normal. As long as the command window has finished it's output with a successful message your good.
Code:
fastboot reboot-bootloader
Select reboot from the bootloader menu :fingers-crossed:
Obviously with water damage there's no telling if it will still boot but let me know how it goes. :good:
Sent from my HTC One M9 using Tapatalk

Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) start image[emmc_fw32] unzipping & flushing...
FAILED (status read failed (Too many links))
Execution time is 71(s)
Click to expand...
Click to collapse
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.

Williamck said:
Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.
Click to expand...
Click to collapse
OK well the pre-update fail is normal. This is the bootloader being updated before the firmware is flashed.
The caution symbols in ruu mode are because the RUU did not complete. Strange that it stopped where it did though.
It may be that emmc is damaged and not writable. Try flashing the ruu again. Hopefully it will complete. If not check to see if it ends at the same point.
Also make sure your using a USB port at the back of your PC not the front ones. :good:
Sent from my HTC One M9 using Tapatalk

The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop

Williamck said:
The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop
Click to expand...
Click to collapse
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?

I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?

hansbogert said:
I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?
Click to expand...
Click to collapse
The difference is Google's generic fastboot can't handle zip files larger than 1.5gb.
Most HTC lollipop and Marshmallow ruu's are all 1.6gb up-to 2.2gb. So you have to use htc_fastboot to flash them because it's designed to flash larger files.
Sent from my HTC One M9 using Tapatalk

Williamck said:
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?
Click to expand...
Click to collapse
Yeah in rice is the best way normally for a day or two is enough. I guess it for quite wet?
To be honest it could be anything. A spot of corrosion in the right place could do it.
But without opening the phone it's impossible to know exactly what damage if any the water has caused.
The ruu you've flashed is officially signed from HTC. The same package the service center would use to restore the device. That's why I say it's unlikely to be a software issue.
Out of interest how long did you wait for the phone to boot, it can take up-to 20mins for first boot after flashing an ruu. The phone will hang on the HTC logo for 20mins+ before starting the app optimization.
Sent from my HTC One M9 using Tapatalk

It wouldn't give any indication of working at all, on the order of a week maybe. After that it started to show a generic charging symbol on the screen when plugged in, although no progression bar for charge, and the light would turn green but that's it. Only after several weeks would the screen start to show that the battery actually was charging, with a percentage, and turn on into bootloader.
So yeah, I think it must be pretty damaged. Now when I try to turn it on, like I said, it's a bootloop. the htc logo stays for a while but eventually it turns itself off and back on, again to the logo.
I think I'll try to open the back and see what it looks like...I've read that cleaning the logic board with alcohol will clear the buildup of contaminants from the river water, which could be causing this weird stuff to happen.

Related

[Q] HTC One - Soft Brick

I wanted to change my rom on my HTC One. I first fastbooted a new recovery img TWRP.
On the TWRP recovery screen, I decided to wipe all of my data on my phone out with the advanced settings of wipe on TWRP..I still don't why I did that. The data isn't the problem however, I then decided to go back to Clockwork recovery and use adb to push a stock rom to fix my problem.
However after flashing the Stock rom onto my phone, the phone is stuck on the boot loading screen. My HTC One is S-On so I used a special rom that works for S-On HTC One phones. However the stock rom doesn't seem to work.
I'm stuck here not knowing on what to do next. I've tried everything...different roms etc.
Any Ideas?
HabitRPG said:
I wanted to change my rom on my HTC One. I first fastbooted a new recovery img TWRP.
On the TWRP recovery screen, I decided to wipe all of my data on my phone out with the advanced settings of wipe on TWRP..I still don't why I did that. The data isn't the problem however, I then decided to go back to Clockwork recovery and use adb to push a stock rom to fix my problem.
However after flashing the Stock rom onto my phone, the phone is stuck on the boot loading screen. My HTC One is S-On so I used a special rom that works for S-On HTC One phones. However the stock rom doesn't seem to work.
I'm stuck here not knowing on what to do next. I've tried everything...different roms etc.
Any Ideas?
Click to expand...
Click to collapse
oh dear, got yourself into a bit of a mess there.
first thing is to get your phone back to the bootloader, so hold down the power button and the volume down together, DO NOT LET GO, the lights on the bottom will flash 10-15 times, when they stop flashing, release the power button only, continue to hold down the volume down, it will now enter the bootloader.
Post your fastboot getvar all please, WITHOUT IMEI & SERIAL NUMBER.
also, please provide some links to the special :fingers-crossed: stock rom you flashed ? all rom's for your model work, s-on or s-off.
Seanie280672 said:
oh dear, got yourself into a bit of a mess there.
first thing is to get your phone back to the bootloader, so hold down the power button and the volume down together, DO NOT LET GO, the lights on the bottom will flash 10-15 times, when they stop flashing, release the power button only, continue to hold down the volume down, it will now enter the bootloader.
Post your fastboot getvar all please, WITHOUT IMEI & SERIAL NUMBER.
also, please provide some links to the special :fingers-crossed: stock rom you flashed ? all rom's for your model work, s-on or s-off.
Click to expand...
Click to collapse
C:\AndroidSDK>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3677mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I can't post links because of my post count however it was a Stock Rom guru reset
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
HabitRPG said:
C:\AndroidSDK>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3677mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I can't post links because of my post count however it was a Stock Rom guru reset
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
ok, guru reset works fine, recovery is the problem, you need to use twrp 2.6.3.3, push the zip again and install, select wipe data, install stock recovery and install stock radio.
also check the MD5 and file size before pushing the zip, the site has some issues with the files at the moment.
however, once you have done that, you have a good HBOOT there, so if you want s-off on your phone, now is the time to do it after you've got that guru reset installed, before any OTA's, try rumrunner to get s-off.
Seanie280672 said:
ok, guru reset works fine, recovery is the problem, you need to use twrp 2.6.3.3, push the zip again and install, select wipe data, install stock recovery and install stock radio.
also check the MD5 and file size before pushing the zip, the site has some issues with the files at the moment.
however, once you have done that, you have a good HBOOT there, so if you want s-off on your phone, now is the time to do it after you've got that guru reset installed, before any OTA's, try rumrunner to get s-off.
Click to expand...
Click to collapse
i flashed TWRP 2.6.3.3
however i can't adb the rom
C:\AndroidSDK>adb sideload Guru_Reset_M7_3.62.401.1.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
when i used Clockwork i used
adb usb
adb push filename.zip /sdcard/obb
which put the file onto the sdcard and i was able to flash the zip file
however this doesn't work with TWRP because it doesn't show me the obb file on the SD card and just comes up blank.
HabitRPG said:
i flashed TWRP 2.6.3.3
however i can't adb the rom
C:\AndroidSDK>adb sideload Guru_Reset_M7_3.62.401.1.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
when i used Clockwork i used
adb usb
adb push filename.zip /sdcard/obb
which put the file onto the sdcard and i was able to flash the zip file
however this doesn't work with TWRP because it doesn't show me the obb file on the SD card and just comes up blank.
Click to expand...
Click to collapse
from the main screen only inside TWRP recovery, no sub menus, you seem quite experienced, but obviously the zip must be inside your adb and fastboot folder, it will appear unresponsive, takes about 5 mins to push, but your cmd window will let you know when its done.
Code:
adb push Guru_Reset_M7_3.62.401.1.zip /sdcard/
Seanie280672 said:
from the main screen only inside TWRP recovery, no sub menus, you seem quite experienced, but obviously the zip must be inside your adb and fastboot folder, it will appear unresponsive, takes about 5 mins to push, but your cmd window will let you know when its done.
Code:
adb push Guru_Reset_M7_3.62.401.1.zip /sdcard/
Click to expand...
Click to collapse
same problem is still occurring, I've installed the new zip file with TWRP, I wiped, rooted and installed radio etc. Still stuck on the HTC one loading screen.
I've check the MD5 and it matched however instead of 1.11GB as stated on the site its 1.12GB with the file being 1,176,264. I don't know if that means anything.
HabitRPG said:
same problem is still occurring, I've installed the new zip file with TWRP, I wiped, rooted and installed radio etc. Still stuck on the HTC one loading screen.
I've check the MD5 and it matched however instead of 1.11GB as stated on the site its 1.12GB with the file being 1,176,264. I don't know if that means anything.
Click to expand...
Click to collapse
that's strange, Try these commands:
Code:
fastboot erase cache
fastboot reboot
Seanie280672 said:
that's strange, Try these commands:
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Sadly nothing has changed. I used erase cache after installing the recovery, if that means anything.
HabitRPG said:
Sadly nothing has changed. I used erase cache after installing the recovery, if that means anything.
Click to expand...
Click to collapse
just wondering:
1- is the installation successful
2- how long are you waiting for the phone to boot up?
nkk71 said:
just wondering:
1- is the installation successful
2- how long are you waiting for the phone to boot up?
Click to expand...
Click to collapse
1. yes the installation is successful
2.It takes the same amount of time as a HTC One usually takes however it hangs on the HTC one loading screen after the green HTC logo screen
HabitRPG said:
1. yes the installation is successful
2.It takes the same amount of time as a HTC One usually takes however it hangs on the HTC one loading screen after the green HTC logo screen
Click to expand...
Click to collapse
I had hoped you would say something like __ minutes, because i don't know how long "same amount of time" actually is.
When I do a clean install of a 4.4 ROM, it takes close to 20 minutes for it to boot up properly, but when I just reboot the phone, it's done in less than 2 minutes.... so i don't know which one of those would be the "same amount of time".
nkk71 said:
I had hoped you would say something like __ minutes, because i don't know how long "same amount of time" actually is.
When I do a clean install of a 4.4 ROM, it takes close to 20 minutes for it to boot up properly, but when I just reboot the phone, it's done in less than 2 minutes.... so i don't know which one of those would be the "same amount of time".
Click to expand...
Click to collapse
when i boot up the phone it takes 30 seconds for it to go on the HTC one beats audio screen, then it hangs there. However I've never left it for more than 5 minutes as I have never experienced any phone taking that long to load. I'll leave it on this time for 30 minutes and see if that is any change
HabitRPG said:
when i boot up the phone it takes 30 seconds for it to go on the HTC one beats audio screen, then it hangs there. However I've never left it for more than 5 minutes as I have never experienced any phone taking that long to load. I'll leave it on this time for 30 minutes and see if that is any change
Click to expand...
Click to collapse
small recommendation: reflash the ROM first (including wipe), then let it boot up, if you check the Frequently Asked Question sticky page 3
you'll see my personal opinion about bootup time (and other things)
This is very strange as ive used that guru-reset file myself, and its never taken much longer than 5 to 10 mins to boot, however, if its getting past the splash screen, then onto the boot screen, then its defiantly doing something, usually a boot loop is a phone stuck at the splash screen or a restart whilst booting.
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Seanie280672 said:
This is very strange as ive used that guru-reset file myself, and its never taken much longer than 5 to 10 mins to boot, however, if its getting past the splash screen, then onto the boot screen, then its defiantly doing something, usually a boot loop is a phone stuck at the splash screen or a restart whilst booting.
Click to expand...
Click to collapse
Once you're past the bootsplash, it should be OK, but "5 minutes" has become a relative term.... It's usually the 4.4+ ROMs that take a lot longer to load than the previous ones, but I have seen someone post "I waited 10 minutes" and the two posts were 3 minutes apart (after he waited it worked fine)... so a little exaggeration about the close to 20 minutes is just trying to encourage a little patience
---------- Post added at 09:52 PM ---------- Previous post was at 09:46 PM ----------
HabitRPG said:
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Click to expand...
Click to collapse
okay, that's too long, check the Frequently Asked Question sticky page 3
iirc only GPE ROMs need S-Off, all the others should be fine; make sure you're using a recovery (and ROM) meant for m7_u / ul
HabitRPG said:
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Click to expand...
Click to collapse
This may sound crazy, but when you flash the guru reset file, and booting it, your phone needs to be unplugged from the computer, I only discovered this problem myself a few days ago, I couldn't figure out why it was stuck on the splash screen, pulled the usb cable and it fired straight up (try this first before below comment)
Download this one mate, it will work fine, again use twrp 2.6.3.3 I know there are newer versions on the TeamWin site, but this version is proven to be the most compatible with roms, this rom is stock looks and stock features, you should get S-OFF easily with it using rumrunner, and once your S-OFF, you can just use an RUU to get to fully stock if that's what you want.
again, download the zip and just push it to your sdcard and install
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
Seanie280672 said:
This may sound crazy, but when you flash the guru reset file, and booting it, your phone needs to be unplugged from the computer, I only discovered this problem myself a few days ago, I couldn't figure out why it was stuck on the splash screen, pulled the usb cable and it fired straight up (try this first before below comment)
Download this one mate, it will work fine, again use twrp 2.6.3.3 I know there are newer versions on the TeamWin site, but this version is proven to be the most compatible with roms, this rom is stock looks and stock features, you should get S-OFF easily with it using rumrunner, and once your S-OFF, you can just use an RUU to get to fully stock if that's what you want.
again, download the zip and just push it to your sdcard and install
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
Click to expand...
Click to collapse
Tried both methods and still the same problem occurs.
HabitRPG said:
Tried both methods and still the same problem occurs.
Click to expand...
Click to collapse
So you've tried downloading and flashing the ARHD 31.6 rom too and that did the same thing ?

[Q] Seemingly strange soft brick happening to my phone

Hey guys, I've tried searching everywhere for info related to my situation, but couldn't find any...hopefully someone here will be able to help.
This all started earlier today, when I was using my phone (AT&T, m7, converted to GPE) as normal. I was at work, browsing Facebook or whatever, when suddenly I got a quick notification that Gapps had force closed. A few seconds after that, the phone suddenly restarted.
From there, I noticed the Google splash logo had a strange pixelated band across it, as shown in the attached photo.
Then it proceeded to bootloop.
After trying a couple basic things, none of them succeeded, and I decided to just wait until I got home, at which point I tried to enter recovery. It took me to the bootloader, which looked pretty weird, as it had a bunch of jumbled letters in the options, also shown in the attached photo.
From there, all I could get to was stock recovery. I tried flashing TWRP, but it wouldn't recognize ADB, and then I tried to flash using fastboot. Fastboot would accept the commands "./fastboot devices" (which recognized that my phone was connected) and "./fastboot getvar all." Any other command, including "./fastboot flash recovery" would give me the error "FAILED (remote: not allowed)".
I'm now at a loss. As you can see in the photos, my bootloader is unlocked, with S-OFF. I have no idea how to recover from this.
Any suggestions? Thanks.
Oh, also, I'm on a Mac, with Yosemite.
jon_marfrag said:
Hey guys, I've tried searching everywhere for info related to my situation, but couldn't find any...hopefully someone here will be able to help.
This all started earlier today, when I was using my phone (AT&T, m7, converted to GPE) as normal. I was at work, browsing Facebook or whatever, when suddenly I got a quick notification that Gapps had force closed. A few seconds after that, the phone suddenly restarted.
From there, I noticed the Google splash logo had a strange pixelated band across it, as shown in the attached photo.
Then it proceeded to bootloop.
After trying a couple basic things, none of them succeeded, and I decided to just wait until I got home, at which point I tried to enter recovery. It took me to the bootloader, which looked pretty weird, as it had a bunch of jumbled letters in the options, also shown in the attached photo.
From there, all I could get to was stock recovery. I tried flashing TWRP, but it wouldn't recognize ADB, and then I tried to flash using fastboot. Fastboot would accept the commands "./fastboot devices" (which recognized that my phone was connected) and "./fastboot getvar all." Any other command, including "./fastboot flash recovery" would give me the error "FAILED (remote: not allowed)".
I'm now at a loss. As you can see in the photos, my bootloader is unlocked, with S-OFF. I have no idea how to recover from this.
Any suggestions? Thanks.
Oh, also, I'm on a Mac, with Yosemite.
Click to expand...
Click to collapse
Ouch, that doesn't look nice at all!!!
are you able to get to RUU mode? "fastboot oem rebootRUU"
if yes then you should flash a full ruu.zip to try and restore your messed up partitions (obviously this will wipe your phone)
nkk71 said:
Ouch, that doesn't look nice at all!!!
are you able to get to RUU mode? "fastboot oem rebootRUU"
if yes then you should flash a full ruu.zip to try and restore your messed up partitions (obviously this will wipe your phone)
Click to expand...
Click to collapse
Nope, getting the same error:
FAILED (remote: not allowed)
finished. total time: 0.002s
Not sure if it helps, but here's the ./fastboot getvar all info it spits back.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.07.154
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -----------------
(bootloader) imei: -------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4289mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b296905a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Click to expand...
Click to collapse
jon_marfrag said:
Nope, getting the same error:
FAILED (remote: not allowed)
finished. total time: 0.002s
Not sure if it helps, but here's the ./fastboot getvar all info it spits back.
Click to expand...
Click to collapse
yep, doesnt look nice at all in here :crying:
could be a hardware problem... i'll check in tomorrow, can't do this tonight sorry
PS: recommend you also try a different pc (mac, Win7, linux), with up to date adb/fastboot (and if needed [ie Win7] drivers), stay away from USB3 ports or any hubs.... seems hboot is corrupt, and only way to flash that is using ruu mode, or using a custom recovery (TWRP or CWM... even rooted ROM would do)
nkk71 said:
yep, doesnt look nice at all in here :crying:
could be a hardware problem... i'll check in tomorrow, can't do this tonight sorry
PS: recommend you also try a different pc (mac, Win7, linux), with up to date adb/fastboot (and if needed [ie Win7] drivers), stay away from USB3 ports or any hubs.... seems hboot is corrupt, and only way to flash that is using ruu mode, or using a custom recovery (TWRP or CWM... even rooted ROM would do)
Click to expand...
Click to collapse
Great, I appreciate your help!
Yeah, looking like it could be a hardware issue, huh? That's what I was afraid of, especially since it seemed to happen randomly without me doing anything to directly cause it.
I'll try using a different mac tonight (no PCs around me I can borrow that I can think of).
If hboot is corrupted, but I can't do anything but access flashboot and I can't even flash from fastboot, it looks like I might be a little screwed?
jon_marfrag said:
Great, I appreciate your help!
Yeah, looking like it could be a hardware issue, huh? That's what I was afraid of, especially since it seemed to happen randomly without me doing anything to directly cause it.
I'll try using a different mac tonight (no PCs around me I can borrow that I can think of).
If hboot is corrupted, but I can't do anything but access flashboot and I can't even flash from fastboot, it looks like I might be a little screwed?
Click to expand...
Click to collapse
yes, unfortunately, i'm inclined to believe it's a hardware fault (not of your doing!!)
there are only two ways i know of, of "messing"/"fixing" partitions (including hboot <only when s-off>), and those would be
1) ruu mode flash <- highly preferred
2) "dd" <-very bad, if you mistype a single character... boom
and yes,
3) given you current firmware, there may be a way to get somewhere even "worse" or "better" ....
but in all likelihood it's probably a hardware fault, nothing you did wrong
nkk71 said:
yes, unfortunately, i'm inclined to believe it's a hardware fault (not of your doing!!)
there are only two ways i know of, of "messing"/"fixing" partitions (including hboot <only when s-off>), and those would be
1) ruu mode flash <- highly preferred
2) "dd" <-very bad, if you mistype a single character... boom
and yes,
3) given you current firmware, there may be a way to get somewhere even "worse" or "better" ....
but in all likelihood it's probably a hardware fault, nothing you did wrong
Click to expand...
Click to collapse
Okay, here's one little thing I hadn't thought of yet. As I said in my first post, I could get into the Stock Recovery (Android system recovery <3e> KOT49H.H1 release-keys). Also, a few weeks ago I finally bought a USB OTG cable.
Don't know why it took me this long to think about trying it, but I finally realized I should see if the stock recovery could detect a USB drive plugged into the OTG cable when "apply from an SD card" is selected. Of course, it could.
So! That seems like it might be a possible way to flash what I need to flash, correct? If so, what exactly should I try flashing? I'm worried that I'm in a really precarious spot here and I don't want to flash the wrong thing and lose the ability to use even stock android recovery.
Should I try reflashing the bootloader? TWRP? (if it screws up the TWRP flash will I lose stock recovery?) Something else?

[Q] HTC ONE (M7UL) imei problems + rebooting + s-on

Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
shieldeverything said:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5(bootloader) version-bootloader: 1.57.0000(bootloader) version-baseband: 4A.21.3263.04(bootloader) version-cpld: None(bootloader) version-microp: None(bootloader) version-main: 6.09.401.10(bootloader) version-misc: PVT SHIP S-ON(bootloader) serialno: (bootloader) imei: (bootloader) meid: 00000000000000(bootloader) product: m7_ul(bootloader) platform: HBOOT-8064(bootloader) modelid: PN0710000(bootloader) cidnum: HTC__102(bootloader) battery-status: good(bootloader) battery-voltage: 3972mV(bootloader) partition-layout: Generic(bootloader) security: on(bootloader) build-mode: SHIP(bootloader) boot-mode: FASTBOOT(bootloader) commitno-bootloader: dirty-6d8a0b9b(bootloader) hbootpreupdate: 11(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
Click to expand...
Click to collapse
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
shieldeverything said:
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
Click to expand...
Click to collapse
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...
Thx for your help anyways!

[Q] HTC One M7 disaster

Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4138mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
usb debugging has nothing to do with the bootloader, adb or fastboot, it is only required to be on when you want to mod something or control your phone using adb commands inside a booted rom, as you cant boot, then that's not an option.
if your bootloader is locked and you have warranty, send it back, because if you unlock your bootloader then your warranty will be void and you'll have to pay for repairs.
Hi there & thnx for your concern,
The warranty is not an option , cause I bought it in another country and have no service support here.
For the usb debugging mode , as far as I know , it needs to be "on" so the smartphone can be connected to adb.
I looked on the net how to turn it on without having access to android I got some command but I need an android command-line shell to make it work , wich is not an option right now.
I'm all open for suggestions.
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Rave201 said:
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Click to expand...
Click to collapse
only thing you can do is unlock your bootloader, try again, get a new unlock token from HTC Dev.
by the way, adb commands are only for in a rom or in recovery, use fastboot commands only in the bootloader, if you cant unlock the bootloader then theres not a lot you can do.
could you post your fastboot getvar all please, remove imei and serial number information before posting, maybe there is an RUU we can run.
Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now try the RUU again
clsA said:
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
lol how I missed that I don't know
Thanks ! : downloading , I'll leave answer after I test.
Hi again ;
So I downloaded and followed the steps I got errors :/
on the RUU flash I got Error 171 at "Bootloader waiting" and later saying that it couldn't connect to the device . It did connect to it in the first place though and device rebooted and so .
So I followed the second parts and I got errors aswell :
Code:
c:\mini-sdk>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.016s]
finished. total time: 0.016s
c:\mini-sdk>fastboot flash zip firmware.zip
sending 'zip' (43508 KB)...
OKAY [ 2.870s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 6.538s
Any help please
anyone ?
Rave201 said:
anyone ?
Click to expand...
Click to collapse
bootloader needs to be locked / relocked to flash the RUU or firmware as your s-on.
"fastboot oem lock" is the command without quotes.
Hi there, I did it already , it says device already locked.
Rave201 said:
Hi there, I did it already , it says device already locked.
Click to expand...
Click to collapse
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Seanie280672 said:
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Click to expand...
Click to collapse
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Rave201 said:
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Click to expand...
Click to collapse
what I meant was when fastboot usb is showing, have a look in windows device manager and make sure it see's your phone, should say MyHTC.
only drivers you need which have never let me down, even on Windows 10 is HTC sync manager, just download and install the latest version from the HTC site, I would uninstall all current phone drivers first, then run a cleaner like CCleaner to remove old files, reboot computer then install HTC sync manager, after the install, un-install HTC sync, just leaving HTC driver package above it alone.
make sure your phone is unplugged when doing the above, leave your phone in the bootloader, and when you have finished the last step of un-installing HTC sync, then plug your phone into the computer and let it load the fastboot driver, thats the main one you need right now.
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Rave201 said:
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Click to expand...
Click to collapse
It's a 2 year old phone, it's really only worth fixing if you already have the parts for free.
This phone sells for $149 New in the US, and even cheaper used on eBay.
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Rave201 said:
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Click to expand...
Click to collapse
SD_HW_ERROR = probably a defective emmc. You can't replace the emmc chip, its soldered directly on the Motherboard so you will indeed need to replace the motherboard but like clsA said it really doesnt worth it. You can get a new M7 for 150$. HTC sells their Motherboard around 100$ + you'll probably need to replace the body like many users who tried to open the phone themselves (very fragile around the volume rockers). Even if I love my M7, I wouldn't spent 100$ to replace the MB.
And buying a used motherboard is not a good idea. You don't know if its working good + you don't know if the IMEI is blacklisted.
Thanks for the explanation alray, I excpected the fail in the emmc too cause read_mmc emmc didn't work.
Anway I don't live in the us . Here though, a new one cost roughly 300 $ and the motherboard is about 80$ or less.
Thanks again

Soft brick (i think?) help please :(

Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)
misticknight1 said:
Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)
Click to expand...
Click to collapse
s-on is nothing to do with it, as long as your bootloader is unlocked, that's enough to flash custom roms.
TWRP is required to flash custom sense based roms, which version of TWRP depend on which rom you are trying to flash, so Lollipop based sense roms require TWRP 2.8.6.0, whereas the later ones require TWRP 2.6.3.3
after flash recovery, be sure to erase the cache and reboot the bootloader before trying to enter recovery, this clears anything that the previous recovery may of left behind, reboot bootloader is basically for changes to take effect, so your commands should look like this:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
when you enter recovery, personally in your situation, I would go into wipe, and select the format data button, this will wipe everything off your phone including the internal storage, so be sure to backup anything you need first, you can do this with the adb pull /sdcard/0 command from the recovery main screen. once the format is complete, reboot back into recovery again, and adb push or copy a rom to your internal storage, be sure to unplug your phone now and then flash it, also be sure to select full wipe during the installation.
you can only really use lollipop based custom roms if you are on lollipop firmware, people on lower firmware are reporting problems like no wifi, Bluetooth etc, so it would be helpful if you post your fastboot getvar all without your imei and serial number.
how do i get that? and i am using twrp 2.8.6.0.
misticknight1 said:
how do i get that? and i am using twrp 2.8.6.0.
Click to expand...
Click to collapse
well you know how to use fastboot commands, so with the phone booted in the bootloader and fastbootUSB showing on the screen and plugged into the computer the command is fastboot getvar all post the output here without imei and serial number.
Sorry took so long to respond to my own topic i was at work. heres the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Bump
Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.
misticknight1 said:
Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.
Click to expand...
Click to collapse
First step go into TWRP / Wipe / Advanced / Format Data ... type yes
when it's done go to Reboot / Recovery
now download and install this Rom >> https://www.androidfilehost.com/?fid=23991606952602541
during install choose Wipe system
the phone will take almost 10 min to boot ..wait on it and be patient
I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".
misticknight1 said:
I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".
Click to expand...
Click to collapse
unplug and replug in the phone and start over ... don't let it sleep
Nevermind found out it hadn't completed properly, redownloading now hopefully it should be alright.
Thanks heaps it worked
misticknight1 said:
Thanks heaps it worked
Click to expand...
Click to collapse
Great !!
Spoke a bit too soon used it for a bit now it still resets I guess that's a hardware problem for sure now though and not much I can do about it unless I take it to a pro.

Categories

Resources