Related
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
if you're using twrp, select wipe from main menu>advanced wipe>select dalviccache, cache, data, and system, then flash rom.
Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta
Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
krazyflipj said:
Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.
Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
Yes, actually I accidentally downloaded the 4.3 google edition leak rom without realizing it wasnt for the sprint version
insuusvenerati said:
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.
Click to expand...
Click to collapse
This is exactly the problem I'm having now if I install any other rom
So I relocked the bootloader and tried installing a stock ruu, but I just get an error message, no idea what to do. -_-
Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?
Dysnomia said:
Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?
Click to expand...
Click to collapse
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.
insuusvenerati said:
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.
Click to expand...
Click to collapse
already said I can't use that one because I already updated my phone to 1.31.651.2
Dysnomia said:
already said I can't use that one because I already updated my phone to 1.31.651.2
Click to expand...
Click to collapse
im on the same version have you found a solution yet???
Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)
Aldo101t said:
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)
Click to expand...
Click to collapse
i will give that a shot
Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.
where can i get the revone ??? sorry it this is a dumb question...
Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
There is a sticky in this forum that has the info for s off. Also in one of the dev forums there is an all in one tool that makes using revone easy.
Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2319412
Or you can use this tool
http://forum.xda-developers.com/showthread.php?t=2236814
Dysnomia said:
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.
Click to expand...
Click to collapse
hi,
which rom did you install which allowed you to get revone onto the device?
ya im in the same boat. loaded a rim labeled as a sprint rom, when in aroma, i asked att tmobi or international, i selected international. had this problem ever since. just got my phone maybe 2 days ago. familiar withh rooting and android, fastboot and what not, this is my 4th htc. hero, evo , evo3d and now this please tell me it's not dead. i'm not used to all this no sd card stuff. =[
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
MrFixit007 said:
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Click to expand...
Click to collapse
Pm me your teamviewer information and I'll help you out.
bigdaddy619 said:
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
Click to expand...
Click to collapse
I am on 1.31. I have tried running the RUU from my PC and I got error 140. I tried looking that up and could not find any solutions to that. I figured it was because I am on 1.31 and not 1.29 and I still had s-on. That is when I tried to get s-off so that I could apply the 1.29. Is it possible to open a fastboot shell? I was going to try to push the revone files to the phone via fastboot and then run the commands via fastboot, but didn't get around to trying that out last night.
Indirect said:
Pm me your teamviewer information and I'll help you out.
Click to expand...
Click to collapse
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
MrFixit007 said:
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
Click to expand...
Click to collapse
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
What do you want to know?
Sent from?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
im0rtalz said:
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
Click to expand...
Click to collapse
bigdaddy619 said:
What do you want to know?
Sent from?
Click to expand...
Click to collapse
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
MrFixit007 said:
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
Click to expand...
Click to collapse
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
bigdaddy619 said:
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
Click to expand...
Click to collapse
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
MrFixit007 said:
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
Click to expand...
Click to collapse
Check PM
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect is a beast
bigdaddy619 said:
Indirect is a beast
Click to expand...
Click to collapse
yep! Indirect and bigdaddy are both beasts!
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect and bigdaddy have both helped me out bunches tonight!!! I am completely back in action!!
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
Probably downgraded him from 1.31 to 1.29 so he could RUU
Sent from?
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
MrFixit007 said:
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
Click to expand...
Click to collapse
I got him fixed up
I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation
Let the phone download OTA and apply it
sent from my mobile device
SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.
It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app
Yea lock bootloader
sent from my mobile device
No dice. Same deal.
Sent from my HTC One using xda app-developers app
Text/Photo of the error?
SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.
Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.
Hi,
I am unable to make/receive calls and can't send/receive SMS text messages.
WiFi and data over 3G works fine, so email/browsing is OK.
I have tried SIM cards from other working phones but it's the same problem on this phone.
Used to work fine couple of days ago but now when I try to make a call to someone it says straight away call ended.
Has anyone encountered the same problem? Can anybody help please?
Info:
My phone is HTC One (M7)
Used to be rooted, in my attempt to resolve the problem I have unrooted it and now has stock android, which i flashed on.
The only thing that is different is that my phone is s-off.
I have done a factory reset but this did not fix it.
For some reason, when i try to update my phone over ota, I get a red triangle with a !.
My phone version is 3.62.401.1.
It is Android 4.3. Not 4.4 kitkat.
I can use wifi, and have 3G/H signal.
That's about it. If anybody can help me with this problem, please do! Thanks in advance.
Does anybody know?
alhal1 said:
Does anybody know?
Click to expand...
Click to collapse
toggle airplane mode and data and see what happens
you say you flashed something back to stock ? do you still have custom recovery? that would stop any updates
clsA said:
toggle airplane mode and data and see what happens
you say you flashed something back to stock ? do you still have custom recovery? that would stop any updates
Click to expand...
Click to collapse
No i no longer have custom recovery.
Yes i flashed so i could get rid of custom recovery and go back to my stock android.
airplane mode and data don't help.
alhal1 said:
No i no longer have custom recovery.
Yes i flashed so i could get rid of custom recovery and go back to my stock android.
airplane mode and data don't help.
Click to expand...
Click to collapse
did you flash a RUU ? which one ?
clsA said:
did you flash a RUU ? which one ?
Click to expand...
Click to collapse
stock_3.62.401.1
alhal1 said:
stock_3.62.401.1
Click to expand...
Click to collapse
Try this one
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
clsA said:
Try this one
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
Ah my mistake, I didn't flash using an ruu, but i will try this. Will i need a custom recovery to use it? Can i use it for WWE?
No custom recovery and yes it's fine for WWE
Sent from my HTC One_M8 using Tapatalk
clsA said:
No custom recovery and yes it's fine for WWE
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It did not work, it still ends at 00:00 but my phone did update to latest version.
alhal1 said:
It did not work, it still ends at 00:00 but my phone did update to latest version.
Click to expand...
Click to collapse
hardware failed send it to HTC for repair
clsA said:
hardware failed send it to HTC for repair
Click to expand...
Click to collapse
How do i change my relocked to locked without using revone?
alhal1 said:
How do i change my relocked to locked without using revone?
Click to expand...
Click to collapse
if your s-off use this
http://forum.xda-developers.com/showthread.php?t=2475914
clsA said:
if your s-off use this
http://forum.xda-developers.com/showthread.php?t=2475914
Click to expand...
Click to collapse
Do you know how to change s-off to s-on?
Did you flash anything that could have caused this problem? I assume you have flashed a RUU that contained firmware?
If I were you, I'd try to get the original firmware back onto the phone, then install a "known good" ROM so you know the system isn't screwed up somehow.
alhal1 said:
Do you know how to change s-off to s-on?
Click to expand...
Click to collapse
./fastboot oem writesecureflag 3 to bring back to S-ON
clsA said:
./fastboot oem writesecureflag 3 to bring back to S-ON
Click to expand...
Click to collapse
Thanks so much, i will send it to the htc company soon
fenstre said:
Did you flash anything that could have caused this problem? I assume you have flashed a RUU that contained firmware?
If I were you, I'd try to get the original firmware back onto the phone, then install a "known good" ROM so you know the system isn't screwed up somehow.
Click to expand...
Click to collapse
well i originally flashed an recovery.img containing the original version of the version I had. I then tried an RUU. Still didn't work though. What do you mean by 'known good' ROM?
alhal1 said:
well i originally flashed an recovery.img containing the original version of the version I had. I then tried an RUU. Still didn't work though. What do you mean by 'known good' ROM?
Click to expand...
Click to collapse
I mean a popular third party ROM that most people can use without problems. ARHD, for example. But now that I think about it, if you successfully installed a RUU and did a factory reset, I agree with the other person that said it sounds like a hardware defect. I've had this problem on another phone and it was the firmware and RIL (a problem that only exists for Samsung), but if you flashed a RUU it should have sorted that out.
If you can get warranty service for this phone, try it. This is one of those cases where you should revert the phone to stock, though, because the most obvious answer to why a rooted phone doesn't have calls is "you screwed up the software/firmware".
fenstre said:
I mean a popular third party ROM that most people can use without problems. ARHD, for example. But now that I think about it, if you successfully installed a RUU and did a factory reset, I agree with the other person that said it sounds like a hardware defect. I've had this problem on another phone and it was the firmware and RIL (a problem that only exists for Samsung), but if you flashed a RUU it should have sorted that out.
If you can get warranty service for this phone, try it. This is one of those cases where you should revert the phone to stock, though, because the most obvious answer to why a rooted phone doesn't have calls is "you screwed up the software/firmware".
Click to expand...
Click to collapse
So my phone is broken?
i just used firewater and weaksauce to unlock s-off and root my htc one verizon 1.56 hboot 4.4.2.
everything stated it was successful. bootloader shows unlocked, s-off and i installed twrp successfully.
i attempted to flash viperone and skydragons rom. both installs successfully and then it stuck in a bootloop. i have downloaded the rom multiple times.
i cant get pass the boot loop.....
tried wiping davik, cache.
tried using fix permissions in twrp but it fails.
help please
So just because your phone doesn't boot, you immediately blame firewater/weeksauce? Right...
Theshawty said:
So just because your phone doesn't boot, you immediately blame firewater/weeksauce? Right...
Click to expand...
Click to collapse
im sorry, i didnt mean to blame firewater/weaksauce. im sure its something i did wrong on my end.
just trying to figure out what happened.
Kleany said:
im sorry, i didnt mean to blame firewater/weaksauce. im sure its something i did wrong on my end.
just trying to figure out what happened.
Click to expand...
Click to collapse
What TWRP version do you have? Some of the newer ones are unreliable. I myself use 2.7.0.4b by cschmitt and it works very well.
Theshawty said:
What TWRP version do you have? Some of the newer ones are unreliable. I myself use 2.7.0.4b by cschmitt and it works very well.
Click to expand...
Click to collapse
openrecovery-twrp-2.7.0.0-m7.img
i flashed the latest version i seen on twrp site
Kleany said:
my htc one verizon 1.56 hboot 4.4.2.
Click to expand...
Click to collapse
Are you flashing roms from this forum? If so, that's your issue. These are all GSM roms. You need to go to the Verizon One forum.
iElvis said:
Are you flashing roms from this forum? If so, that's your issue. These are all GSM roms. You need to go to the Verizon One forum.
Click to expand...
Click to collapse
oh wow, i didnt realize there was a different verizon forum. ill definitely try it once i get home from school. thanks!
Kleany said:
oh wow, i didnt realize there was a different verizon forum. ill definitely try it once i get home from school. thanks!
Click to expand...
Click to collapse
LOL, yeah, that's the issue then, mate.
The verizon m7 is also known as m7_vzw, whereas the european LTE variant is called m7_ul.
Theshawty said:
LOL, yeah, that's the issue then, mate.
The verizon m7 is also known as m7_vzw, whereas the european LTE variant is called m7_ul.
Click to expand...
Click to collapse
i just read that the ViperONE rom is for all variants. GSM and LTE....i installed that rom 3 times and it would still get stuck on boot loop....
im trying a rom i found in the VERIZON HTC ONE forum NuSenseSIX-Max. hopefully this one works.
so i tried CM11....twrp sideload failed stated the rom as for "m7vzw" and that my device was a "m7"....no idea what thats all about.
but then i tried the NuSenseSix rom, it flashed and phone is now working =) thanks guys!
really wanted to use the VIPERone. ill keep messing around to see if i can figure out what the issue is.
Kleany said:
so i tried CM11....twrp sideload failed stated the rom as for "m7vzw" and that my device was a "m7"....no idea what thats all about.
but then i tried the NuSenseSix rom, it flashed and phone is now working =) thanks guys!
really wanted to use the VIPERone. ill keep messing around to see if i can figure out what the issue is.
Click to expand...
Click to collapse
Your phone isn't a GSM unit. It's a CDMA unit (and has different hardware from the GSM units).
Sent from my HTC One using Tapatalk