Related
I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app
dpshptl said:
I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.
nkk71 said:
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.
Click to expand...
Click to collapse
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.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: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
dpshptl said:
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.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: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back
If you can get s off you can go back to stock t mobile. I did it with my o2-UK phone. But you def need s off first
Sent from my HTC One using xda app-developers app
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Have you tried using firewater to get s off? If it doesn't work, as mentioned above, guru reset only option
Sent from my HTC One using xda app-developers app
dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
no the Guru reset does not require s-off
you flash it like a rom and choose to install stock recovery during install
---------- Post added at 06:32 PM ---------- Previous post was at 06:27 PM ----------
dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Read this page very carefully you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset
http://www.htc1guru.com/downloads/stock-rom-downloads/
No the guru reset does not require s off. It will not be stock t mobile though as well
Sent from my HTC One using xda app-developers app
Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.
clsA said:
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back
Click to expand...
Click to collapse
But how is he going to get LOCKED not relocked?
dpshptl said:
Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.
Click to expand...
Click to collapse
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"
I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.
dpshptl said:
I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.
Click to expand...
Click to collapse
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it
clsA said:
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it
Click to expand...
Click to collapse
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader
dpshptl said:
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader
Click to expand...
Click to collapse
install the guru reset .. your phone should boot up
The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.
dpshptl said:
The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.
Click to expand...
Click to collapse
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?
nkk71 said:
But how is he going to get LOCKED not relocked?
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"
Click to expand...
Click to collapse
clsA said:
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?
Click to expand...
Click to collapse
Yeah guru flashed without any problems. Then auto rebooted into bootloader, where it was still tampered and unlocked. I went into recovery but it just kept looping to boatloader. So i flashed TWRP again and wiped everything and here I am. I think its some major hardware problem because whenever the phone reboots from anywhere on the phone, it starts looping and hanging. The phone has been wiped clean so many times and had everything installed from a jump drive. So I cant imagine something being left on there that is causing the problem.
Can someone give me a link to the stock RUU. I'm confused between all of them. The phone seems to be stable now. I reboot it several times and it works. But I do need to use a mouse cuz the touch screen does not work.
Their is no RUU
You need to start working on getting s_off
Sent from my HTC One_M8 using Tapatalk
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.
I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible
gravity02 said:
I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible
Click to expand...
Click to collapse
So is your device ***LOCKED*** or ***RELOCKED*** by which I mean has it ever been unlocked before or this is the first time?
Normally the course of action for bootloader unlocking issues is to flash a matching firmware package and request a new Unlock_code.bin. But let's see what variant of M7 you have first not all M7s can be unlocked via HTCdev.
Could you post the out put of
Code:
fastboot getvar all
Please remove your IMEI and Serial numbers before posting for security purposes
If you can't use HTCdev and your device is s-on then the only option is Sunshine App but it costs $25 so let's see what you've got and go from there :good:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
gravity02 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Ok your s-off That's good you have a couple of options here. You can flash a firmware package and request a new Unlock_code.bin as I mentioned above. :good: I'll see if I can find a firmware zip for you and post the link here
EDIT: -You can download a matching firmware here http://d-h.st/NPJ. Do you know how to flash firmware.zips with fastboot?
Or you can boot a custom recovery and unlock it yourself using "adb shell"
With the recovery image file in your fastboot folder. Connect fastboot usb and in the command window type
Code:
[B]fastboot boot recovery "name-of-recovery".img[/B]
[B]adb shell[/B]
[B]su[/B] (if needed to get a*#*prompt)
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/B]
(i would very strongly recomend you copy/paste this)
[B]exit[/B]
(exit a second time if you need to to get back to a normal > prompt)
[B]adb reboot bootloader[/B]
verify you are now unlocked
The above method is taken from this thread http://forum.xda-developers.com/showthread.php?t=2475914 Thanks should go to the OP :good:
thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?
gravity02 said:
thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?
Click to expand...
Click to collapse
HTCdev method will wipe your DATA and SDCARD
Recovery command method will not wipe anything :good:
Quoted from the Main Thread in above link
piterk said:
Could you tell me if this method to lock/unlock bootloader wipes phone data like the method via htcdev?
Click to expand...
Click to collapse
scotty1223 said:
no,it does not erase data.
the flashing of unlock code,and relock command initiate hboot to factory reset. this is only changing the flag that hboot checks.
Click to expand...
Click to collapse
tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?
gravity02 said:
tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?
Click to expand...
Click to collapse
Mmmm that's strange try again but this time use CWM https://www.dropbox.com/s/82kt3edku0j2sup/cwm.img?dl=0 you don't need to flash it just boot it with
Code:
fastboot boot cwm.img
Failing that did you try the firmware method?
I haven't tried the firmware method. can you walk me through it?
gravity02 said:
I haven't tried the firmware method. can you walk me through it?
Click to expand...
Click to collapse
Download the firmware package linked in my previous post. Put the zip in your fastboot folder and rename it "firmware.zip"
Boot your phone to the bootloader and connect fastbootusb, Now in the fastboot command line type
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now go to htcdev and complete the Unlock my bootloader procedure to get a new Unlock_code.bin :fingers-crossed:
FYI :- Flashing the firmware will restore the Stock Recovery so after the Unlock you will need to flash your Custom recovery again
I followed the steps but my phone is now stuck in the htc logo. I can't even switch it off
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.
Seanie280672 said:
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.
Click to expand...
Click to collapse
Don't forget it needs to be in a bright lighted room (really!)
gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Your Stuck on the HTC logo because you flashed the firmware and you have a custom rom. The Firmware restored your Stock Recovery and boot.img. Were you able to unlock the bootloader? You need to do that before you try flash anything. It was the Custom recovery and boot.img that caused the problem with unlocking the bootloader.
To make your phone boot to your rom again open the zip file of the rom installed on the phone and extract the boot.img to your fastboot folder. Then flash it with fastboot
Code:
fastboot flash boot boot.img
or just flash your rom again or any compatible rom :good:
P.S for the record when you post you should be quoting my last post or mention me like this @Danny201281 Then I will get a notification and you will get a faster response :good:
i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?
gravity02 said:
i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?
Click to expand...
Click to collapse
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
---------- Post added at 10:44 AM ---------- Previous post was at 10:30 AM ----------
Danny201281 said:
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
Click to expand...
Click to collapse
Ok it seems your in luck. There's plenty of RUU's for your T-Mobile device. Look here http://forum.xda-developers.com/showthread.php?t=2375223 and download this T-Mobile HTC One RUU 1.27.531.11
Simple to use just connect fastboot usb in the bootloader and launch the ruu on your pc. This will also wipe your device and return you to Stock.
@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?
gravity02 said:
@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?
Click to expand...
Click to collapse
You can't flash recovery while the bootloader is locked not even with s-off.
You could open the firmware zip you flashed and replace the recovery and boot.img with twrp and the boot.img of your Rom. Then flash the firmware zip. The phone should then boot up no problem. And you'll have the custom recovery back. If you want you can send me the boot.img or a link to the Rom on your phone and I can make the zip for you
Can I ask why you locked it in the first place? There's really no need to lock or relock when the device is s-off.
It's starting to look more like a hardware problem though. As I say normally it's some customization in the firmware that causes the problem. But with non of the methods working even with stock firmware it seems like the bootloader is not excepting any unlock instruction.
@ Danny201281, I replaced the stock recovery in the firmware.zip with twrp and flashed the firmware and was able to boot into twrp. I then copied a nandroid backup I made previously into the phone and restored it and the phone booted up properly.
how do I extract the boot.IMG from the nandroid?
thanks for your help so far
Hi there,
I bought a 2nd hand phone [HTC M7] off ebay with Revolution 90.1 / Android 5.02 / Build No. 7.15.401.1
Everything works great...but I can't make or receive calls. I figured this was the same issue that struck HTC phones in Dec, but from my understanding 7.15.401.1 is more recent than the official HTC fix (6.10.531.10) & Rev. 90.1 already has this fix included also. I've also installed Viperone 7.02 (fix incl.), but no difference, so I'm now back to Rev. 90.1. I've also cleared google caches, froze HTC lockscreen etc etc but now I've run out of ideas.
Can anybody help?!
Thanks..!
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
synt3k said:
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Tinky24 said:
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Click to expand...
Click to collapse
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Seanie280672 said:
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Click to expand...
Click to collapse
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Tinky24 said:
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Click to expand...
Click to collapse
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Seanie280672 said:
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Click to expand...
Click to collapse
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Tinky24 said:
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Click to expand...
Click to collapse
dont change to windows 8 you will have all sorts of problems due to your HBOOT, you are on a very early firmware there and as you are s-off, that helps alot, I think you really need to bring your phone back up to speed to be sure thats not whats causing the issues your having, bear with me whilst I find the link of 401 firmwares. (version-main: 1.29.401.2)
If there is anything on the phone you need to keep, pictures, photo's music etc, please back it up now as firmware flash can wipe the device in some cases.
OK heres the link to the firmwares, you need to flash them one at a time, starting with the earliest 2.24.401's then the 3xxxxxx's then the 4xxxxx's then the 5xxxxxx and finally the 6xxxxxx's,: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ this issue you experiencing was fixed in the 7xxxxxx firmware which i'll find the link for shortly.
Do you know how to flash the firmware ?
Thanks so much.
I've found a guide
Tinky24 said:
Thanks so much.
Is it the same way as flashing a ROM i.e. Recovery > Install?
Click to expand...
Click to collapse
no, heres a good guide on how to do it: https://trjlive.com/guide-install-firmware-htc-one-m7/
if your phone is already in fastbootUSB mode, then skip the first 2 commands, also something not mentioned in the guide is the firmware.zip file MUST be in the same folder as your adb and fastboot files on your computer, when you download the firmware files (one at a time) they will be named as per the name on the site, just rename them to firmware.zip for ease, once you've finished flashing each one and the phone has finished booting, delete it and download the next then follow the prceedure once again.
your battery must be 50% or more before proceeding, but I can see yours is good at the moment at 4250mv
If you check yourself, no need to post each one, you should notice the version main number going up, the HBOOT version going up, you will also have stock recovery (a red triangle with an exclamation mark)
do not skip any steps and you'll be fine, report back after the first flash and let us know how it went, any problems, just ask.
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Tinky24 said:
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Click to expand...
Click to collapse
perfect, as long as it still says your s-off, ps, never go s-on, you'll regret it, you can do one of the following.
You can flash this firmware https://www.androidfilehost.com/?fid=95897840722644637 (unsigned) not official yet, but will work for you as your s-off, if you go s-on your phone will brick, and then test your rom, your issue should be fixed.
Or you can do this which is what I did: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 This is official
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
"can not mount SD card"
Tinky24 said:
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
Click to expand...
Click to collapse
hold down the power button with the volume down, keep holding whilst the home and back bottuns on the bottom flash about 15 times, when they stop flashing, release the power button, but continue to hold down the volume down, the phone should boot to the bootloader, factory reset is in the list, use the volume button up / down to highlight it and power button to select, why do you want to factory reset ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
cannot mount sdcard is a normal error if you have entered recovery, there is no sdcard.
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Tinky24 said:
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Click to expand...
Click to collapse
yeah just system reboot, the lollipop rom's do really require Lollipop firmware which is what you just flashed in order toi work properly, your firmware was about 2 years out of date.
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Tinky24 said:
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Click to expand...
Click to collapse
The firmware flash may of messed up your rom, did you flash android revolution 90.1 yourself ?
No it came with Rev. Should I reflash it?
Tinky24 said:
No it came with Rev. Should I reflash it?
Click to expand...
Click to collapse
yes, or a rom of your choice, you will need a custom recovery first, so download this:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
put your phone into fastbootUSB mode on the screen again by holding down the volume down and power button method again as I described earlier, this is the white screen not the black screen with silver HTC logo.
rename the download above to recovery.img and place it in the same folder as adb and fastboot again and with your phone plugged in issue these commands one at a time:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, as long as your drivers are working correctly, this recovery supports MTP so the computer should see the internal storage, just downlaod and copy the rom you want to flash straight to the internal storage, unplug your phone and install it, its recommended to install option with full wipe, dont worry, internal storage isnt touched, just wipes data and system.