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
Hi Guys,
Hope that anyone can help me with the following:
I normally have Openrecovery-twrp-2.6.3.3-m7 running on my M7.
However, with the new software update of 5.11.1540.9 pushed out, I normally go back to original recover, then update my software by downloading it an installing on the phone.
A couple of months ago I changed my version, originally an ATT phone, to I think a European or WWE version. I am not sure anymore.
Anyway, when I try to flash the original recovery ecovery_Cingular_US_3.17.502.3.img back and reboot in to recovery I get a black screen and eventually a phone icon with exclamation mark.
After holding the power button for a while, I can reboot and get back in the phone or restore TWRP.
My question is, does anyone know how to get the original recovery working again so that I can run the update.
This is the info of the bootloader:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 111111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I rather do not wipe the whole device if I don't have to. Before I changed the firmware to European or WWE I was able to restore the original bootloader at leisure. So I think it would be best to go back to the correct country firmware, or find a recovery file that does work with my current firmware.
If I can install the latest Developer Edition ROM with TWRP, and have to wipe, that is fine. I don't want to risk bricking my phone with doing all kind of updates. Have done so many and it is still working, would hope to keep it that way
Any help appreciated.
I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery
mike-y said:
I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery
Click to expand...
Click to collapse
Well, last time it worked for me when I had the Dev edition. My phone was unlocked with S-On, and I had TWRP for recovery.
I remember receiving the OTA, installing it and then seeing the message in TWRP that it couldn't install.
I then set the Recovery_Cingular_US_3.17.502.3.img for recovery and I was able to install the OTA.
After that I went back to TWRP.
Couple of months ago I set my CID to 11111111 and S-off and I installed, I believe a european version or a WWE version (not sure anymore what i did ) to get a radio that might unlock 4G here in Australia (which failed cause of hardware restrictions of bands).
Anyway, my phone works fine and I received the OTA but I can't repeat the back to stock recovery trick cause after flashing the Recovery_Cingular_US_3.17.502.3.img it doesnt enter recovery. Probably something to do with my WWE or Euro firmware?
What does relock mean in this case.
I also am at loss at what the correct RUU is. Is RUU firmware, or a whole complete ROM?
Can you see from my bootloader info what version I have and should consider?
I am just a bit confused with all the terms and was quite into it a couple of months ago, but now its a blur.
You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One
yatindroid said:
You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One
Click to expand...
Click to collapse
Well I tried your suggestion but it doesnt work. After I hold the power button when seeing the exclamation mark, the phone finally reboots. It tried to install the OTA this way, but it doesnt work.
I think the current recovery:Recovery_Cingular_US_3.17.502.3.img doesnt match my current firmware of something like that.
Any other suggestions?
Can I just install a fresh ROM with the latest version, not sure where to get it from.
Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.
mattileblanc said:
Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2791123
from HTC One
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 guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(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!
finished. total time: 0.047s
Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(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!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
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.