Related
Going through the process to repair my phone has educated me on tremendously about the errors of my ways. If anyone can provide any beneficial assistance, it would be greatly appreciated.
OTA (PRIOR- 4.4.2. kitkat )Sense 5.5 with updated firmware 4.06 HBOOT 1.56
Sprint HTC ONE M7_WLS
S-ON
TAMPERED
UNLOCKED
TWRP Recovery
UNDETECTED IN ADB
Remote signature failed
Remote access denied
Running on Windows 8.1 and ADB version 1.0.31
USB 1.0 (I know that 2.0+ is better)
Cause for boot loop = No OS available. (Yes, I am aware that I need to install a ROM but that is the issue I am having.)
What does this mean?
FLASHED CUSTOM RECOVERY (WRONGFULLY)
Click to expand...
Click to collapse
BD619 said:
What does this mean?
Click to expand...
Click to collapse
I originally had CWM recovery on there and wanted to use the TWRP recovery instead since it had the HTC dumblock on there, which helped out before. While my phone was in it current condition, I downloaded TWRP and flashed it into my HTC ONE. I know I must have done so wrongfully because now when I try to go into recovery... it freezes during "entering recovery" and reboots into boot loop.
from bootloader open a cmd window and type
fastboot erase cache
See if that helps
BD619 said:
from bootloader open a cmd window and type
fastboot erase cache
See if that helps
Click to expand...
Click to collapse
I've made that attempt already. But the strange thing is that it executes the command, but if used again it will give me a list of blocks and inods or something like that. But I will try the command and reboot the system. Ill update with the outcome.
ogmless collection
Okay I erased the cache, it confirmed the command. I rebooted and of course it was in boot loop. I entered bootloader, then to recovery... and the same problem persisted.
BestaAtMakingMistakes said:
Okay I erased the cache, it confirmed the command. I rebooted and of course it was in boot loop. I entered bootloader, then to recovery... and the same problem persisted.
Click to expand...
Click to collapse
You can try This see if it will get you up and running
Just make sure when you get to the part where you push to rom to your phone make sure you use a 4.4.2 rom or your phone may not boot.
What version of twrp did you flash?
Sent from my HTCONE using xda app-developers app
Okay so I went through and followed the steps... good news is that it fixed my recovery problem I had and now I can enter twrp. Now TWRP is telling me that I have no OS system. So if I install a ROM, will I be good?
BestaAtMakingMistakes said:
Okay so I went through and followed the steps... good news is that it fixed my recovery problem I had and now I can enter twrp. Now TWRP is telling me that I have no OS system. So if I install a ROM, will I be good?
Click to expand...
Click to collapse
Yeah just adb push a 4.4.2 rom to your phone
adb is not detecting my device so I am unable to push files.
BestaAtMakingMistakes said:
adb is not detecting my device so I am unable to push files.
Click to expand...
Click to collapse
Try this to get the drivers installed properly
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
foretell rublinke
Yes, I am running Windows 8.1.
BestaAtMakingMistakes said:
Yes, I am running Windows 8.1.
Click to expand...
Click to collapse
That only applies to fastboot you should be fine.
You should be fine in fastboot also.
BD619 said:
That only applies to fastboot you should be fine.
You should be fine in fastboot also.
Click to expand...
Click to collapse
So what would you suggest I do from here. Again, my USER name says it all. I'm about to give up and go to sprint and ask them to do whatever it is that they can do for my phone.
BestaAtMakingMistakes said:
So what would you suggest I do from here. Again, my USER name says it all. I'm about to give up and go to sprint and ask them to do whatever it is that they can do for my phone.
Click to expand...
Click to collapse
Check PM
Just to clarify, Windows 8.1 latest update has fixed fastboot issues! I was shocked after I applied the update I immediately checked fastboot and s-off'd
Sent from my HTC One using xda-developers app
rickyg87 said:
Just to clarify, Windows 8.1 latest update has fixed fastboot issues! I was shocked after I applied the update I immediately checked fastboot and s-off'd
Sent from my HTC One using xda-developers app
Click to expand...
Click to collapse
Not sure how adb was prior to this past week but I would agree that fastboot works great. Its the only thing that has worked or else I wouldn't have messed up my own phone.
BestaAtMakingMistakes said:
Not sure how adb was prior to this past week but I would agree that fastboot works great. Its the only thing that has worked or else I wouldn't have messed up my own phone.
Click to expand...
Click to collapse
Adb has always worked fine for me. However, in twrp there should be an option to mount, I've had to use this on my one x to load a Rom (and boot.img, since I was also s-on) onto my sd.
I flashed the Rom in twrp, reboot to bootloader then fastboot flashed the boot.img
Sent from my HTC One using xda-developers app
BD619 said:
Yeah just adb push a 4.4.2 rom to your phone
Click to expand...
Click to collapse
Yeah, my adb isn't working and hasn't been working from day one. I'm sure I'm just missing the fact that I cant debug my phone because it's in boot loop. But one more step left to see if everything I've learn in the past week pays off.
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Drakeskakes said:
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Click to expand...
Click to collapse
please specify the device, or just post a fastboot getvar all (excluding IMEI and s/n)
2.6.0.0 sound kind of outdated
Sounds like a firmware issue, you need be firnware with new touch screen driver
HTC One
Like nkk71 said get TWRP 2.6.3.4
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Drakeskakes said:
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Click to expand...
Click to collapse
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
clsA said:
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
Click to expand...
Click to collapse
So, to upgrade to Kit-kat then CM11 ....do I have to do a complete factory reset, then OTA update, then do unlock/root/s-off and install rom?
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
clsA said:
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
All I want to CM on my phone, Im rooted, have CMW premium, SUperSU and unlocked...
When I go to CWM, it doesn't work, when I try and DL from Goo, it doesn't work, when I try to download from CM app, doesn't work. I'm going to throw this phone across the room. I hve done custom roms before, but always using a toolkit for PC. I only have access to a mac for the time being
Drakeskakes said:
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
Click to expand...
Click to collapse
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
The Device must be unlocked and equipped with a Recovery,
you need a ROM.zip and optional GAPPS,the Download Links will you find here.
At first,make a Nandroid-Backup of your existing system!
When you first time flash the ROM or you changed from another ROM-Base,
do a Full Wipe via Recovery,flash the ROM, and then the GAPPS.
Restart to System,configure and enjoy CM11.
Click to expand...
Click to collapse
Are you still with hboot 1.44? Upgrade to have a newer touch driver pls
Sent from my HTC One using xda app-developers app
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
This thread was only about TWRP not working, but someone piggy backed off this conversations after I started the other one.
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
is GSM version for Sprint...before I go through with the DL
Drakeskakes said:
is GSM version for Sprint...before I go through with the DL
Click to expand...
Click to collapse
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
clsA said:
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Drakeskakes said:
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Click to expand...
Click to collapse
During the install, it aborted and now the stock rom won't load. It keep going into recovery and I have nothing to load it to. I can't shut it off, and I would like to just work on it tommorow. If it dies, I'm worried I wont be able to charge it back up to work on it. Now I'm pretty worried
Nevermind CM11 now working, switched from CWM to TWRP andf it works great
Brief history:
Htc One m7 Unlocked International version.
I was running ViperOne 6.2.1 with their stock kernel.
The ROM was giving me some issues listed below probably because of some xposed mudule that wasn't compatible.
I was using the following modules if it is relevant:
1. SwypeBack
2. YouTube AdAway
3. Instagram Downloader
4. CPUTemp in Status Bar
So I was facing some issues:
1. The Camera app wasn't working and showed me a black screen every time i launched it.
2. There were some menus that had white text on a white background which made it difficult for me to read.(This was because I checked the wrong option while installing a theme for the ViperOne from The Venom Hub).
3. Apps like clash of clans would start in landscape but only use half the screen..
So I decided that I would wipe the phone and install the Rom Again to make things fine.
This is what I did:
1. Get into TWRP 2.7.0.0
2. Wipe -> Factory Reset
3. Install -> ViperOne 6.2.1
4. Install -> AdAway hosts.zip
5. Wipe Cache/dalvik
6. Reboot
7. Everything was fine but the phone wasn't contacting google after i'd entered my id and password..(later I realized it was because my Wifi at home wasn't working..)
So I rebooted into the recovery again and did this:
1. Get into TWRP 2.7.0.0
2. Wipe -> Advanced Wipe -> System, Data, Cache, Dalvik
3. Install -> ViperOne 6.2.1
4. Install -> AdAway hosts.zip
5. Wipe Cache/dalvik
6. Reboot
7. Prompted to install SuperSU because phone does not appear to be rooted, so I "Swipe to install SuperSU" and then for a second, I see the log that says "failed to write to System/bin" and then phone reboots.
8. Now the phone is stuck at the "HTC quitely brilliant" bootscreen.
The phone has a Bootloader version hboot 1.56 unlocked via HTCDEV.
I have the htc drivers installed on the pc, I have the android sdk installed to run fastboot commands or adb commands but I am afraid to do anything because I'm not sure what I should be doing right now.
Edit:
I read through this thread http://forum.xda-developers.com/showthread.php?t=2386084
Was able to get into the bootloader and got into recovery from there. Restored a nandroid backup from an earlier date. Stock HTC Rom.
Now, When i select Reboot System, the recovery says "your phone does not appear to be rooted, would you like to install SuperSU now?" and i select "DO not install" because I didn't want to get stuck again.
How do I regain root access now?
.
So I rebooted into the recovery again and did this:
1. Get into TWRP 2.7.0.0
2. Wipe -> Advanced Wipe -> System, Data, Cache, Dalvik
Click to expand...
Click to collapse
You have wiped the system? it means there is no ROM on your device currently. Flash Viper again (if you have on the SD), if not use adb sideload function ADB sideload help from ARHD
davebugyi said:
You have wiped the system? it means there is no ROM on your device currently. Flash Viper again (if you have on the SD), if not use adb sideload function ADB sideload help from ARHD
Click to expand...
Click to collapse
I identified why I was stuck at bootloop. It was so simple I don't know how I missed that..
I was installing viperone 6.2.1.. the 6.2.1 was never released as a full Rom. It was a mini OTA update. So the phone didn't have a complete Rom I stalled..
Fixed by flashing viperone 6.2.0. That's what I was supposed to flash in the first place, I forgot that the 6.2.1 was a mini OTA and flashed that initially and freaked out when it didn't boot. XD
Sent from my HTC One using XDA Premium 4 mobile app
thetearer said:
I identified why I was stuck at bootloop. It was so simple I don't know how I missed that..
I was installing viperone 6.2.1.. the 6.2.1 was never released as a full Rom. It was a mini OTA update. So the phone didn't have a complete Rom I stalled..
Fixed by flashing viperone 6.2.0. That's what I was supposed to flash in the first place, I forgot that the 6.2.1 was a mini OTA and flashed that initially and freaked out when it didn't boot. XD
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
:laugh::laugh: Well, next time you know that a .zip with a few MBytes, is not a full ROM
davebugyi said:
:laugh::laugh: Well, next time you know that a .zip with a few MBytes, is not a full ROM
Click to expand...
Click to collapse
I wasn't able to or didn't notice the size when I selected the file to zip.. Haha xD
Sent from my HTC One using XDA Premium 4 mobile app
So today I flashed a Custom Rom (Viper rom), and it said it was successful and all in the installer. I then rebooted it as it asked for and it got on the Lock screen, but once I unlocked it, it would bring up a HTC one screen. I thought it was part of the installation so I waited but soon it gave me an error: Process com.htc.htcdialer isn't responding. So I did what I would do and Googled it up and it said it was cause the Radio wasn't working and all so I was told to try and install another rom and I flashed InsertCoin. In the installer it again said that it was successful but I got the same error, Process com.htc.htcdialer isn't responding. Please help me out as it's a new phone. I'm with Wind (Canadian) but I believe it should work with Unlocked stuff.
DeEpic6114 said:
So today I flashed a Custom Rom (Viper rom), and it said it was successful and all in the installer. I then rebooted it as it asked for and it got on the Lock screen, but once I unlocked it, it would bring up a HTC one screen. I thought it was part of the installation so I waited but soon it gave me an error: Process com.htc.htcdialer isn't responding. So I did what I would do and Googled it up and it said it was cause the Radio wasn't working and all so I was told to try and install another rom and I flashed InsertCoin. In the installer it again said that it was successful but I got the same error, Process com.htc.htcdialer isn't responding. Please help me out as it's a new phone. I'm with Wind (Canadian) but I believe it should work with Unlocked stuff.
Click to expand...
Click to collapse
I have forgotten to mention that it Shuts it self off every 90 seconds.
DeEpic6114 said:
I have forgotten to mention that it Shuts it self off every 90 seconds.
Click to expand...
Click to collapse
I'm using CWM
DeEpic6114 said:
I'm using CWM
Click to expand...
Click to collapse
thats probably your issue, reflash the rom using twrp 2.6.3.3
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery
in twrp, select ''install'' and browse the /sdcard folder to find your rom.zip
swipe to flash
then reboot phone into OS
I will second the previous member.. I had similar troubles until I used TWRP!
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
gothmog1114 said:
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
Click to expand...
Click to collapse
Follow this guide.
StormyNight said:
Follow this guide.
Click to expand...
Click to collapse
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
gothmog1114 said:
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Could you screenshot the bootloader for me?
Maybe you've got a whacked recovery. Reflash from fastboot from an md5 verified .img (make sure its m7wls version of TWRP). You should have no problems wiping any partition from within.
StormyNight said:
Could you screenshot the bootloader for me?
Click to expand...
Click to collapse
http://imgur.com/GwCBmpe
gothmog1114 said:
http://imgur.com/GwCBmpe
Click to expand...
Click to collapse
Are you using a Windows 8 computer? If so, try it with Windows 7. If you're using Windows 7, try a different port (preferably a USB 2.0 port).