Hi XDA,
I have a VZW HTC One m7 that is seriously outdated, as in, it is still on all original versions from when I bought the phone last year the day it was released on Verizon. That day I took the phone and unlocked it (before Verizon blocked the unlock from HTC Dev) and rooted it. I put CWM recovery on it (version 6.0.3.6). Much later I also got it S-Off.
Currently I have Android 4.2.2, Sense 5.0, firmware 1.10.605.8, and baseband 1.12.42.0731 (I assume this is the radio?).
Because I have been rooted all along I have not been able to take the OTA updates for the last year.
How do I go about getting updated to the current versions of everything? Need step by step please as I'm pretty much a noob beyond what I have already done.
Your help is greatly appreciated.
Thanks,
Steve
lostnsound said:
Hi XDA,
I have a VZW HTC One m7 that is seriously outdated, as in, it is still on all original versions from when I bought the phone last year the day it was released on Verizon. That day I took the phone and unlocked it (before Verizon blocked the unlock from HTC Dev) and rooted it. I put CWM recovery on it (version 6.0.3.6). Much later I also got it S-Off.
Currently I have Android 4.2.2, Sense 5.0, firmware 1.10.605.8, and baseband 1.12.42.0731 (I assume this is the radio?).
Because I have been rooted all along I have not been able to take the OTA updates for the last year.
How do I go about getting updated to the current versions of everything? Need step by step please as I'm pretty much a noob beyond what I have already done.
Your help is greatly appreciated.
Thanks,
Steve
Click to expand...
Click to collapse
this is the way i did it, just follow the method in this section! not my work, but it has helped me get to the latest update! http://forum.xda-developers.com/showthread.php?t=2485319
abrego47 said:
this is the way i did it, just follow the method in this section! not my work, but it has helped me get to the latest update! http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
Thanks for the response! This is exactly what I was looking for, however I am concerned that it says "Using CWM, may cause you to lose root!" I would like to keep CWM and not lose my root. Any suggestions?
lostnsound said:
Thanks for the response! This is exactly what I was looking for, however I am concerned that it says "Using CWM, may cause you to lose root!" I would like to keep CWM and not lose my root. Any suggestions?
Click to expand...
Click to collapse
You need to update firmware.
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
From the thread above you most likely want this.
http://www.androidfilehost.com/?fid=23501681358539478
Instructions:
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
andybones said:
You need to update firmware.
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
From the thread above you most likely want this.
http://www.androidfilehost.com/?fid=23501681358539478
Instructions:
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Much thanks andybones!! This is very very helpful. Gonna give it a try tonight.
lostnsound said:
Much thanks andybones!! This is very very helpful. Gonna give it a try tonight.
Click to expand...
Click to collapse
Glad to help out whenever I can friend.
Let us know the results.
Best of luck,
Andy
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
If you are s-off you can now simply flash a stock rooted Rom. That will update your os for you. Your os is what's out of date now.
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
The newest rom on this thread is the most recent stock rom for VZW m7. http://forum.xda-developers.com/showthread.php?t=2485319
Just flash it from recovery, like Andy said. You may want to wipe data going from an older sense version to a newer one though, just a warning. Not all apps will dirty flash over, and some can cause issues.
lostnsound said:
Hey andybones,
So I just went through the steps you outlined (very very helpful btw, thanks again) but I have a question now. In the bootloader I can see that the OS version has now been updated to 4.10.605.3 and the radio to 1.13.41.0421. So it appears that it worked. However, when I boot into the UI and go to Settings>About>Software Information, I only see the radio version as being updated. The build version (I assume is the firmware version) still says 1.10.605.8. Is this to be expected? Did it actually work?
Thanks,
Steve
Click to expand...
Click to collapse
Very welcome, Steve, glad you are up and running the latest firmware now!
As for the numbers you are right on the money, the baseband is controlled by the device so no matter the ROM, your baseband will always be the same as what is flashed. As for the ROM name this is dependent on the ROM, to be direct and specific, the build.prop found in /system folder.
So technically, that is why you see ROMs saying things like mine for ex: Bonestock ROM v4.3, etc..
then you will get the build number, you can always change this to w.e. you'd like and tell ppl they are running so and so and they are not, lol, just explaining, but anyway, yes the build number will change depending on the ROM you are using, since you are now on the 4.10.605.3 firmware, your best bet, is to either,
1) if you want Stock
use the stock base ROM for 4.10.605.3
link: http://forum.xda-developers.com/showthread.php?t=2485319
actually the same as the one used for the firmware
2) or others, here is link to my ROM.
http://forum.xda-developers.com/showthread.php?t=2479587
Thank you guys so much again for all the help. I have successfully upgraded everything now. Now running the current firmware, Philz Touch recovery version 6.48.4, and santod's 4.4.2, Sense 6.0 Stock ROM. Everything is working like a charm now! :laugh: You guys have been so helpful, couldn't have done it without you! I will save all this information for future use so I don't forget how I did it next time.
Thanks again,
Steve
Related
Hello All,
I would have posted this in the rumrunner for vzw one forum but I am a new member so I cannot post on dev forums yet. I need to achieve s-off because I want to install CWM and install the stable build of CM10.2 that came out yesterday. I am by no means a noob as I been rooting and flashing custom roms on every android phone I have ever owned all the way back to the OG Droid. Although I am by no means a professional either, I guess I am just good at following write ups online put together by the people that actually build for Android.............or so I thought.
I followed a couple of articles I found online about using Rumrunner for the vzw one to achieve s-off for the device. I have installed the correct htc drivers and have disabled all firewalls and antivirus programs running. The device has USB debugging enabled as is all security settings on the device are are turned of just like the articles say. The trouble is when I execute rumrunner the program goes through the usual test ( boots into fastboot and then adb) and then reboots into fastboot, and then adb again. Then it says device detected and then says waiting for device. Here is where the trouble begins. The program will just sit there and say waiting for device and keep rebooting the device and looks like this below ( I cannot screenshot it because I have already closed it out but it looks just like below)
Waiting for Device
...........................................
Waiting for Device
............................................
Waiting for Device
...........................................
Waiting for Device
............................................
Waiting for Device
.............................................
Waiting for Device
.............................................
It will just keep doing this and whille rumrunner is doing that on the computer, the device is rebooting, staying on the homescreen like a normal startup, and then rebooting again. I have tried this on two computers and it gets stuck at the same spot. Any help would be great appreciated I have no idea what im doing wrong
Thanks
Sounds like you're using the wrong version for your firmware. Double check in settings about phone software info. You'll need to make sure firmware numbers match the version of rumrunner you're using. Either .2 .8 .10 or .15 at the end of the number
Sent from my One using Tapatalk
zeropally said:
Sounds like you're using the wrong version for your firmware. Double check in settings about phone software info. You'll need to make sure firmware numbers match the version of rumrunner you're using. Either .2 .8 .10 or .15 at the end of the number
Sent from my One using Tapatalk
Click to expand...
Click to collapse
This is exactly right. I had the same problem as you. I just needed to use the .15 instead of .10 or whatever I was using. I now have s-off, I just don't know how to actually root it from here
To root you need to flash either twrp or cwm recoveries and flash superuser or supersu via those. Check the original development sections for flyhalfs post of either recovery. Download them and boot into fastboot USB. Then open fastboot from the same folder the adb.exe file is in and use the command ' fastboot flash recovery (whatever you name the file).IMG this will give you recovery. And I'm out of time on break to give directions for superuser hopefully someone can post the rest
Make sure you put the recovery image into the same folder as adb
Sent from my One using Tapatalk
Once rumrunner successfully completes see this post - http://forum.xda-developers.com/showpost.php?p=48092277&postcount=10
nkrebs13 said:
This is exactly right. I had the same problem as you. I just needed to use the .15 instead of .10 or whatever I was using. I now have s-off, I just don't know how to actually root it from here
Click to expand...
Click to collapse
That was exactly it. I was using the .10 rumrunner version and when I needed .15. Thanks for all your help guys
Hello everyone, I I just got an M9 at my local Telus store and I would like to be able to do everything with it like I am able to do with my M7, so I know I will need to use sunshine to get S-OFF and I would also like to be able to change everything from the rom to the kernel to the OS, everything, so I was just wondering if someone could let me know the best order to go about doing things, meaning should I do sunshine first then worry about flashing a recovery and all that, or should I do the recovery first so that I can backup the phones current state? The phone currently says this in the hboot screen:
*** LOCKED ***
LK-1.0.0.0000
OS-1.32.661.6
and this is what it says on the phones Setting-About-Software screen:
Android version
5.0.2
HTC Sense version
7.0
Like I mentioned before, it would probably be best if I can make a backup of the phones current state just in case there are any issues, so to do that I know I need a recovery, but do I need to do the HTC Dev unlocker before I can do so? or do I have to flash a recovery first before everything else?
Now, before anyone gets upset with me for asking these questions because they have most likely been asked 1000 times before, I am not asking to be spoon feed all the details step by step, I am just asking to be pointed in the right direction and asking for you guy's opinions on the best way to go about doing things so that I do them right the first time... So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
apaquette420 said:
So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
Click to expand...
Click to collapse
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
bigp951 said:
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
Click to expand...
Click to collapse
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
apaquette420 said:
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
Click to expand...
Click to collapse
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
bigp951 said:
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
Click to expand...
Click to collapse
lol I so would have gotten caught up on that lol thanks again man!!! will post back later on...
cool..let me know if you get stuck anywhere
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
apaquette420 said:
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
Click to expand...
Click to collapse
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Here is a link for your stock firmware. not sure what the most up to date is but most custom roms are using the WWE firmware anyways.
p.s. either quote me or tag me if you need a faster response. I'm not getting notifications otherwise.
bigp951 said:
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Click to expand...
Click to collapse
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it? in all I plan to flash ViperOneM9 3.5.0 for the rom and it says it requires 2.10 but my phone is currently at 1.32
apaquette420 said:
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it?
Click to expand...
Click to collapse
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
bigp951 said:
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
Click to expand...
Click to collapse
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
apaquette420 said:
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
Click to expand...
Click to collapse
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
bigp951 said:
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
Click to expand...
Click to collapse
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
apaquette420 said:
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
Click to expand...
Click to collapse
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
bigp951 said:
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
Click to expand...
Click to collapse
do you know where I can find the latest international RUU? what rom are you running now?
@bigp951
Ok so I got the firmware updated to the latest international version 2.10 and was able to flash the ViperOne Rom and I love it just like I did for my M7... Everything is working great, except I have the problem that you mentioned would happen, I only show 1 bar for my signal strength, could you please let me know exactly what you had to do to fix it? Also, I would just like to say thank you once more, you helped me out a great deal and you made my upgrade to the M9 an absolute cake walk, so thank you very much for everything and for explaining the proper steps to take, I appreciate it very much...
Hello,
I am in need of some help.
2 weeks ago i bought the HTC One M9.
A few days ago the update to android 6.0 message popped up.
I have probably tried updating it like 15 times already, but everytime the first part is downloaded, and my phone reboots, after 1/4th of the updating it shows a red triangle with an exclamation point in it.
I have tried wiping the cache, it didn't help.
Honestly i don't have a clue what's wrong, or where i can find out what went wrong, so i would really appriciate all the help i can get.
Example of what happens:
malmgrens [dot] org/bilder/htc_recovery_mode [dot] jpg
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
computerslayer said:
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
Click to expand...
Click to collapse
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
appie.0606 said:
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
Click to expand...
Click to collapse
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
To learn about RUUs, VenomROM has a great page that explains about what they are and how to use them.
Peace,
Computerslayer
computerslayer said:
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
Peace,
Computerslayer
Click to expand...
Click to collapse
Yes my phone boots to current software without any problems right now.
Some info i found:
CID: VODAPE17
MID did not show for some reason. I tried multiple ways using adb shell and fastboot, but shell doesnt show anything and fastboot gets stuck at waiting for device.
Is finding my MID nessecary to fix this update problem? If so how can i find it?
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
bzhmobile said:
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
Click to expand...
Click to collapse
Hey thanks for your reply.
It says unlocked. Is that normal or could it be an/the issue?
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
bzhmobile said:
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
Click to expand...
Click to collapse
Alright, so if i understand correctly i can flash a RUU (whatever it is lol) without having to backup without doing a clean install. The phone wont wipe my data?
Would this guide be what you mean?
how-to-flash-ruu-firmware-htc-one-m9/
from naldotech
com
If you flash an RUU....your device will be wiped clean....as it came out of the box...
Then you can OTA on a clean....stock rom....g
The Thread is a good one.
More explication of what is needed in post2 or post 3 of TWRP thread (about Google's new limitation for the OTA).
Beware flashing a RUU will wipe everything, don't forget to backup all you take care...
So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.
lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions
lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
theteju said:
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
Click to expand...
Click to collapse
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# HT69XBN00387
it is GSM unlocked.
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
Now I know what you asking. may be this is proper answer.
fastboot getvar all
kernel: lk
product: htc_pmewl
version: 1.0
max-download-size: 1578400000
serialno: HT69XBN00387
slot-count: 0
current-slot:
imei: 354259077770388
version-main: 3.16.617.2
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS650000
cid: BS_US001
Click to expand...
Click to collapse
theteju said:
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# YOU CAN HIDE THIS.. NOT NEEDED AND SPECIFIC TO YOUR DEVICE.
it is GSM unlocked.
Click to expand...
Click to collapse
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
theteju said:
Now I know what you asking. may be this is proper answer.
Click to expand...
Click to collapse
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
andybones said:
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
theteju said:
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
Click to expand...
Click to collapse
You're so very welcome.
Trust me, I know how tough it can be to fully understand an htc device and it's workings. Once you start to get into it like you have now, I'm sure you came out with some knowledge, so I'm more than happy to help.
I didn't realize you were still on Android 7. You're on 8 now because the RUU I gave you was android 8.(don't try and downgrade. You can but it's not as easy as flashing the android 7 ruu)
The ruu contains everything to make your device stock again, including stock system, stock kernel, stock recovery.
Flashing ruu doesn't touch an soff flag nor bootloader lock.(boot on into download mode and check it out). But even if it did lock it, which won't ever happen, you can always re-unlock bootloader.
It's only us Verizon users who suffer by blocking us from unlocking. NOT COOL VERIZON!!!
You just need to flash twrp again (get latest version), then flash roms as you desire.
I suggest any recent Pie rom. Thanks to dev Fagyi he has really made this phone great again. He maintains Stock lineage 16 is awesome, and theirs a few roms out based on his lineage, including my crdroidandroid rom. Also Fagyi has I think 2 roms based on AOSP rather lineage.
If you want Sense then LeeDroid is the ROM you want.
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
theteju said:
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
Click to expand...
Click to collapse
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
andybones said:
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
Click to expand...
Click to collapse
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
theteju said:
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
Click to expand...
Click to collapse
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
andybones said:
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
Click to expand...
Click to collapse
I am temperory using iphone 4s. Life is in slowMotion mode using that phone since two weeks. LOL
I am eyeing Nokia 7.1. What are your thoughts?
any comment on Mi9?