Related
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 ?
Hello,
Few days back my M7 went black and stopped responding at all. I have S-ON but was able to unlock the phone and install TWRP.
Today, I first flashed the recovery, then boot and then radio images using fastboot method. (I could not take the backup since phone was already dead )
Boot and recovery flash was successful but radio flash failed.
Now, when I try to restart the phone all I see is black screen and LEDs flashing. I cannot even get to the boot screen nor see the HTC logo screen.
Can any expert here guide what can I do now?
(I checked some similar posts but they too don't have any answers)
cagashe said:
Hello,
Few days back my M7 went black and stopped responding at all. I have S-ON but was able to unlock the phone and install TWRP.
Today, I first flashed the recovery, then boot and then radio images using fastboot method. (I could not take the backup since phone was already dead )
Boot and recovery flash was successful but radio flash failed.
Now, when I try to restart the phone all I see is black screen and LEDs flashing. I cannot even get to the boot screen nor see the HTC logo screen.
Can any expert here guide what can I do now?
(I checked some similar posts but they too don't have any answers)
Click to expand...
Click to collapse
What did you flash specifically?
Have you tried turning the phone on placing it under a really bright light?
stovie_steve said:
What did you flash specifically?
Have you tried turning the phone on placing it under a really bright light?
Click to expand...
Click to collapse
Sorry.. but could get your question.. why would I need to place it under really bright light?
Yes.. I tried turning on the phone and all I see is black screen and flashing LEDs (Home button and back arrow button).
cagashe said:
Sorry.. but could get your question.. why would I need to place it under really bright light?
Yes.. I tried turning on the phone and all I see is black screen and flashing LEDs (Home button and back arrow button).
Click to expand...
Click to collapse
Try holding the power button and volume down buttons down, while holding the proximity sensor directly under a very bright light...
I've seen this fix problems for phones not turning on
cagashe said:
Sorry.. but could get your question.. why would I need to place it under really bright light?
Yes.. I tried turning on the phone and all I see is black screen and flashing LEDs (Home button and back arrow button).
Click to expand...
Click to collapse
He's correct about the bright light and power + volume down
we still need to know the exact file you flashed (link)
and a fastboot getvar all minus your serial no and IMEI is always helpful
stovie_steve said:
Try holding the power button and volume down buttons down, while holding the proximity sensor directly under a very bright light...
I've seen this fix problems for phones not turning on
Click to expand...
Click to collapse
Yes the proximity sensor keeps the phone from coming on in your pocket / purse
clsA said:
He's correct about the bright light and power + volume down
we still need to know the exact file you flashed (link)
and a fastboot getvar all minus your serial no and IMEI is always helpful
Yes the proximity sensor keeps the phone from coming on in your pocket / purse
Click to expand...
Click to collapse
You guys are genious :good::good: I can now see phone booting up and its in the Hboot screen where I see the regular options such as factory reset, recovery etc. I have played a lot with the phone so I am sure I am going to need proper steps as what to do next to get the phone up and running.. (Honestly I am a newbie totally frustrated with HTC and AT&T ). I am in software testing so do understand technical terms but haven't really done much in troubleshooting these kind of issues.... I don't mind sitting whole night fixing it if I need to
Below is the fastboot getvar information (excluding serial no and IMEI:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4292mV
(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
Okay... so looks like I made some progress by following below thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
1. Downloaded Guru_Reset, TWRP etc.
2. Installed TWRP
3. So now I am able to boot into recovery, get into TWRP etc.
Now I am stuck at the point where it asks me to do adb sideload. I keep getting error:closed. I do see my device when I issue adb devices.
I also tried adb push but it seems to take forever. Any thoughts?
cagashe said:
Okay... so looks like I made some progress by following below thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
1. Downloaded Guru_Reset, TWRP etc.
2. Installed TWRP
3. So now I am able to boot into recovery, get into TWRP etc.
Now I am stuck at the point where it asks me to do adb sideload. I keep getting error:closed. I do see my device when I issue adb devices.
I also tried adb push but it seems to take forever. Any thoughts?
Click to expand...
Click to collapse
adb push can take some time, between 5-10 minutes, maybe a little more depending on the file size. When you adb push a file, the command prompt will be unresponsive for the duration of the file transfer, this is normal, just wait until adb display a message to confirm that the file was successfully pushed (something like: X amount of bytes transferred in X amount of time)
then in twrp, select "install" and choose your guru reset file.
Adb sideload fails sometimes so better to use adb push. If you still prefer to use sideload, make sure you have latest drivers and that you also have latest adb version 1.0.31. Sideload was introduced in adb at version 1.0.29 so anything below that version wont work.
to see your adb version, open a cmd prompt and type "adb version" without the quotes.
???????????
alray said:
adb push can take some time, between 5-10 minutes, maybe a little more depending on the file size. When you adb push a file, the command prompt will be unresponsive for the duration of the file transfer, this is normal, just wait until adb display a message to confirm that the file was successfully pushed (something like: X amount of bytes transferred in X amount of time)
then in twrp, select "install" and choose your guru reset file.
Adb sideload fails sometimes so better to use adb push. If you still prefer to use sideload, make sure you have latest drivers and that you also have latest adb version 1.0.31. Sideload was introduced in adb at version 1.0.29 so anything below that version wont work.
to see your adb version, open a cmd prompt and type "adb version" without the quotes.
Click to expand...
Click to collapse
Thanks.. adb push worked like a charm :laugh:
My phone is up and running now... I cannot thank you enough to all of you.. this is perhaps the best forum I have worked with :good::good:
On a different note... after lot of thinking, I am almost assuming my phone crashed due to one particular app. The app name World Cricket Champion Pro.
Is there a way or an app I can install to see if I have any battery/CPU hogging app. I am trying to stay away from some games which I know take lot of memory. Thanks in advance.
cagashe said:
On a different note... after lot of thinking, I am almost assuming my phone crashed due to one particular app. The app name World Cricket Champion Pro.
Is there a way or an app I can install to see if I have any battery/CPU hogging app. I am trying to stay away from some games which I know take lot of memory. Thanks in advance.
Click to expand...
Click to collapse
glad it worked! :highfive:
I think everyone here use GSam Battery Monitor from the play store. Give it a try
And it started again....
alray said:
glad it worked! :highfive:
I think everyone here use GSam Battery Monitor from the play store. Give it a try
Click to expand...
Click to collapse
Not sure what's going on with my phone. About a week from when I originally restored my phone it crashed again. Luckily I had it unlocked and got it right back after using recovery option from HBOOT.
However, again since yesterday it restarted twice on its own. Once it was kept for charging and was not in use. I tried to unlock the phone (battery level 100%) and boom it just restarted. Then today it restarted on its own again when I was browsing. (battery level 57%).
Any suggestions? Do I need to look through any logs etc? I am really worried and don't want to end up restoring it once very week.
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?
So I have been an absolute fool, broken every rule that xda set out + tried to root my phone + commit all sorts of shindiggery over a period of months. After various roms, fails, bootloops + catastrophes we arrive at the present day. My phone will randomly say; press the power button to restart in 3, 2,1... then just turns off, bootloops over and over until I somehow get the right power click + it loads correctly. Its continuously doing this, I have since got it to a stable point (it has been on + working for about 2 hours this morning). But I havent fixed anything so I assume the problem is still there.
I also have noticed, if I try and add files, like music and stuff, to my phone from my computer, they wont move across. It glitches out and says the device is no longer recognised.
Another interesting point, I believe I have both clockwork mod and twrp installed, which confuses me because I thought you only needed one.
At the moment my phone (HTC one M7) has these attributes:
Android - 4.2.2
Kernel - [email protected]#1 SMP PREEMPT
Baseband version: 4A 17.3250.14_10.39.1150.04L
Build number: 2.24.771.3 CL211355 release keys.
Can someone please help, im in big doo doos!
gzaajoyce said:
So I have been an absolute fool, broken every rule that xda set out + tried to root my phone + commit all sorts of shindiggery over a period of months. After various roms, fails, bootloops + catastrophes we arrive at the present day. My phone will randomly say; press the power button to restart in 3, 2,1... then just turns off, bootloops over and over until I somehow get the right power click + it loads correctly. Its continuously doing this, I have since got it to a stable point (it has been on + working for about 2 hours this morning). But I havent fixed anything so I assume the problem is still there.
I also have noticed, if I try and add files, like music and stuff, to my phone from my computer, they wont move across. It glitches out and says the device is no longer recognised.
Another interesting point, I believe I have both clockwork mod and twrp installed, which confuses me because I thought you only needed one.
At the moment my phone (HTC one M7) has these attributes:
Android - 4.2.2
Kernel - [email protected]#1 SMP PREEMPT
Baseband version: 4A 17.3250.14_10.39.1150.04L
Build number: 2.24.771.3 CL211355 release keys.
Can someone please help, im in big doo doos!
Click to expand...
Click to collapse
Ok well looks like your on H3G but just so I know exactly what I'm dealing with here can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
And try to confirm which recovery you have. It's not possible to have CWM and TWRP recovery. Ideally you want TWRP though.
Danny201281 said:
Ok well looks like your on H3G but just so I know exactly what I'm dealing with here can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
And try to confirm which recovery you have. It's not possible to have CWM and TWRP recovery. Ideally you want TWRP though.
Click to expand...
Click to collapse
I will have to wait till tomorrow, to use a windows comp, nor sure how to do it on mac.
Also when I do put my phone into recovery, it is the clockworkmod recovery I have, although Ive definitely had TWRP before...
thanks for offer of help aswell
gzaajoyce said:
I will have to wait till tomorrow, to use a windows comp, nor sure how to do it on mac.
Also when I do put my phone into recovery, it is the clockworkmod recovery I have, although Ive definitely had TWRP before...
thanks for offer of help aswell
Click to expand...
Click to collapse
No problem post the getvar when your able and we'll take it from there :good:
Hi,
Think ive got the info here..
(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: 2.24.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
gzaajoyce said:
Hi,
Think ive got the info here..
(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: 2.24.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok cool, thanks. So first we are gonna need twrp recovery. Download it here http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Put the Image file in your fastboot folder and flash recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now we are going to need to format the device. If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.
When your happy you have everything you want to keep backed up, Select "Wipe" from the TWRP menu then " Format Data" you will be prompted to type yes to confirm. When it's done Select "Reboot" then Reboot Recovery.
You will see a message "No OS Installed" reboot anyway and say no when twrp asks if you want to install root. :good:
Ok so now you have a clean formatted device lets install a new Rom. For clarity sake we'll start with the stock Rom.
Download this http://settlecruise.org/Dovo?q=Guru_Reset_M7_2.24.771.3.zip
Using MTP in recovery again copy the Rom to your internal storage. And install it with TWRP. During the install choose these options
Code:
Stock Radio = Yes
Stock Recovery = No
Root = No
When the install is done Reboot the phone. It may stick at the HTC boot splash screen for 15 mins+ as this is a complete clean install.
Let me know how that goes :good: any questions just ask
Okay, so I did what you said, up until 'now we are going to need to format the device . If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.'.
After I flashed the new recovery image?, erased cache and rebooted the bootloader. something weird happened though, it took me to a weird menu cant remember the options but recovery wasnt offered. Then I clicked bootloader, it then offered me recovery, clicked that, it started going into recovery but then my phone immediately turned off and started bootlooping again.
Managed to get it to turn on, then rebooted into recovery. Recovery started, TWRP logo up + and it started flashing something i guess, but then it turned off again + started bootlooping.
Then when I turned it on again, all my files were gone + i had to go through all the set up stuff again.
Not sure where to go from here
Danny201281 said:
Ok cool, thanks. So first we are gonna need twrp recovery. Download it here
Put the Image file in your fastboot folder and flash recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now we are going to need to format the device. If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.
When your happy you have everything you want to keep backed up, Select "Wipe" from the TWRP menu then " Format Data" you will be prompted to type yes to confirm. When it's done Select "Reboot" then Reboot Recovery.
You will see a message "No OS Installed" reboot anyway and say no when twrp asks if you want to install root. :good:
Ok so now you have a clean formatted device lets install a new Rom. For clarity sake we'll start with the stock Rom.
Download this
Using MTP in recovery again copy the Rom to your internal storage. And install it with TWRP. During the install choose these options
Code:
Stock Radio = Yes
Stock Recovery = No
Root = No
When the install is done Reboot the phone. It may stick at the HTC boot splash screen for 15 mins+ as this is a complete clean install.
Let me know how that goes :good: any questions just ask
Click to expand...
Click to collapse
gzaajoyce said:
Okay, so I did what you said, up until 'now we are going to need to format the device . If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.'.
After I flashed the new recovery image?, erased cache and rebooted the bootloader. something weird happened though, it took me to a weird menu cant remember the options but recovery wasnt offered. Then I clicked bootloader, it then offered me recovery, clicked that, it started going into recovery but then my phone immediately turned off and started bootlooping again.
Managed to get it to turn on, then rebooted into recovery. Recovery started, TWRP logo up + and it started flashing something i guess, but then it turned off again + started bootlooping.
Then when I turned it on again, all my files were gone + i had to go through all the set up stuff again.
Not sure where to go from here
Click to expand...
Click to collapse
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Hi, sorry I get confused with all the terminology. The issues i was having yesterday have seemed to resolve themselves ,I tried it again and it worked up until putting the Guru_reset+.zip.dmg file on my phone. I use MTP, it comes up on my computer as 'One' with a folder called TWRP in it, when I put the the .zip.dmg file on it I cant find it on the phone?!
I am looking in internal storage, sdcard, TWRP, have selected view Zips + I still cant see it..
Unsure what to do now.
Okay, worked it out, for some reason it was downloading it with .dmg on the end, so it wasnt working as a zip, I changed the file name but then it doesnt flash properly . I get to the 'swipe to confirm flash' page and it reboots instantly to the TWRP logo then back into recovery... not sure what to do now
gzaajoyce said:
Hi, sorry I get confused with all the terminology. The issues i was having yesterday have seemed to resolve themselves ,I tried it again and it worked up until putting the Guru_reset+.zip.dmg file on my phone. I use MTP, it comes up on my computer as 'One' with a folder called TWRP in it, when I put the the .zip.dmg file on it I cant find it on the phone?!
I am looking in internal storage, sdcard, TWRP, have selected view Zips + I still cant see it..
Unsure what to do now.
Click to expand...
Click to collapse
it should have only a .zip extension. Did you download it from the link I posted? I just checked the link it seems to be bad
http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/ or use a previous copy of you have one. But it should be named guru_reset_m7_2-24-771-3.zip if your sure the file is ok try deleting the .dmg from the file name :good:
---------- Post added at 05:26 PM ---------- Previous post was at 05:15 PM ----------
gzaajoyce said:
Okay, worked it out, for some reason it was downloading it with .dmg on the end, so it wasnt working as a zip, I changed the file name but then it doesnt flash properly . I get to the 'swipe to confirm flash' page and it reboots instantly to the TWRP logo then back into recovery... not sure what to do now
Click to expand...
Click to collapse
Did you do the data format? If you got that download from the first link I posted try downloading it from the second in my above post. :good:
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Hi!
Well I decided to install viper+rom, as I couldnt get the old one to function and so far it seems to be working all right ! Thanks again for bearing with me through this Cheers!
gzaajoyce said:
Hi!
Well I decided to install viper+rom, as I couldnt get the old one to function and so far it seems to be working all right ! Thanks again for bearing with me through this Cheers!
Click to expand...
Click to collapse
Ok sweet, if it's working great. :good:
For future reference I have a thread here for Stock files for H3G branded phones with s-on. If you ever need anything
http://forum.xda-developers.com/showthread.php?t=3028559
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Hi Danny,
Oh dear, its since gone from bad to worse. I have a definite hardware issue, at least im 90% certain. Now Im gonna have to send it off for repairs, but I wont be quoted until the engineers have it + its gonna come to at least 30 quid.
They know I've tampered with the phone + opened the bootloader, so warranty doesnt cover it. Is there anyway to reset this, to hide to 3/HTC that ive accessed the forbidden fruit + messed my phone up?
Thanks,
George
gzaajoyce said:
Hi Danny,
Oh dear, its since gone from bad to worse. I have a definite hardware issue, at least im 90% certain. Now Im gonna have to send it off for repairs, but I wont be quoted until the engineers have it + its gonna come to at least 30 quid.
They know I've tampered with the phone + opened the bootloader, so warranty doesnt cover it. Is there anyway to reset this, to hide to 3/HTC that ive accessed the forbidden fruit + messed my phone up?
Thanks,
George
Click to expand...
Click to collapse
How bad is it? Do you still have a functioning Rom?
You can return it to stock so it looks Untampered but you will need s-off to do it. And to get s-off you need a functioning Rom.
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Danny201281 said:
How bad is it? Do you still have a functioning Rom?
You can return it to stock so it looks Untampered but you will need s-off to do it. And to get s-off you need a functioning Rom.
Click to expand...
Click to collapse
Okay, well as it stands it wont turn on. I have charged + it constantly bootloops. Not sure how to proceed from here? Danny have I truly f**ked it ?
gzaajoyce said:
Okay, well as it stands it wont turn on. I have charged + it constantly bootloops. Not sure how to proceed from here? Danny have I truly f**ked it ?
Click to expand...
Click to collapse
Sorry for the wait my weekend was very busy. So the device no longer powers on (no sign of life) or is bootlooping on boot screen?
It does seem like maybe there is a hardware issue here, sorry if I already asked this but Do you have warranty? Maybe return to stock and send it for repair. It will need to boot to a somewhat stable Rom to get s-off though.
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.