So lets start out with I was using Beanstalk and really enjoyed it till my internet was malfunctioning. So I was checking out how to do a PLR update and noticed that the version I had didn't support it. So in turn I decided to look for a rom that had the Sense, so I chose the Viper rom. I went through the the CWM to load it and it wouldn't work (multiply tries.) I then tried using an older version of TWRP, I think 2.6, and it was working but then it would fail at status 7. I did some research and there were a few posts that mentioned to use the newest version. So I downloaded it, it gets as far as installing the rom and I still get the status 7 failure. So then the phone would only boot into the bootloader, so I reinstalled TWRP, it worked but wont load the rom. I reinstall the rom and I get as far as the bootloader again and need to reinstall TWRP. Now my phone is locked in the bootloader, it says at the top:
TAMPERED
RELOCKED
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.
Tsvallette said:
TAMPERED
RELOCKED
M7_WLW PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.
Click to expand...
Click to collapse
your phone is M7_WLV variant which means its not a gsm variant (M7_UL or M7_U) so you must use recoveries and roms specifically for your phone variant, M7_WLV
bootloader doesnt lock back by itself, so you probably did by mistake, same for s-on/s-off.
learn how to use adb and fastboot and get rid of this toolkit. always better to use adb and fastboot directly from the terminal
then
unlock bootloader
flash the correct recovery for your phone variant
flash a compatible rom for your phone variant
here is the coorect forum for your phone: http://forum.xda-developers.com/verizon-htc-one
I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.
Tsvallette said:
I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.
Click to expand...
Click to collapse
you don't need full sdk
Just need adb mini tool that's enough for all process
from HTC One
Related
Hello,
I'm using HTC One which was initially locked by 3 network (UK) and i got it unlocked last month. I have unlocked my boot-loader and rooted my phone recently. My phone got updated to android version 4.3, after the upgrade i tried performing S-OFF using REVONE but i was not able to S-OFF my device. To install a custom ROM i have to be S-OFF. I have to revert back to stock android version. Could anybody please suggest me which version of RUU should i use to install stock ROM to my device?
I have HBOOT version 1.55.0000
I don't know what is it but when i start my device in boot-loader mode these are all the information i could find:
M7_UL PVT SHIP S-ON RH
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
I have relocked my device and all set to revert back to stock android version. please help me to find correct version of RUU to use for my device. I'm totally new to all these ROM stuffs and if i have mentioned some technical terms wrong my apologize guys.
Thanks in advance.
rprx134 said:
Hello,
I'm using HTC One which was initially locked by 3 network (UK) and i got it unlocked last month. I have unlocked my boot-loader and rooted my phone recently. My phone got updated to android version 4.3, after the upgrade i tried performing S-OFF using REVONE but i was not able to S-OFF my device. To install a custom ROM i have to be S-OFF. I have to revert back to stock android version. Could anybody please suggest me which version of RUU should i use to install stock ROM to my device?
I have HBOOT version 1.55.0000
I don't know what is it but when i start my device in boot-loader mode these are all the information i could find:
M7_UL PVT SHIP S-ON RH
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
I have relocked my device and all set to revert back to stock android version. please help me to find correct version of RUU to use for my device. I'm totally new to all these ROM stuffs and if i have mentioned some technical terms wrong my apologize guys.
Thanks in advance.
Click to expand...
Click to collapse
1- relocking was not the wisest decision, better unlock again
2- to install custom rom, you only need unlocked bootloader and custom recovery. S-Off is NOT needed
3- to get s-off on hboot 1.55, use http://rumrunner.us/ (with compatible ROM, I think ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023)
Android 4.4 rom Installation in HTC One.
nkk71 said:
1- relocking was not the wisest decision, better unlock again
2- to install custom rom, you only need unlocked bootloader and custom recovery. S-Off is NOT needed
3- to get s-off on hboot 1.55, use http://rumrunner.us/ (with compatible ROM, I think ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023)
Click to expand...
Click to collapse
Thanks a lot for your help, and i did S-OFF for my device. If you don't mind please help me with this issue i tried installing android kitkat 4.4 rom for my HTC One using clockworkMod recovery but i ended up getting some error and my installation was aborted. The error is like this "Warning - No Context found". Please help me to figure out the problem.
Thanks.
rprx134 said:
Thanks a lot for your help, and i did S-OFF for my device. If you don't mind please help me with this issue i tried installing android kitkat 4.4 rom for my HTC One using clockworkMod recovery but i ended up getting some error and my installation was aborted. The error is like this "Warning - No Context found". Please help me to figure out the problem.
Thanks.
Click to expand...
Click to collapse
use latest TWRP (2.6.3.3 or above), i believe CWM hasn't been updated for 4.4 ROMs yet: http://forum.xda-developers.com/showthread.php?t=2173870
verify MD5 of twrp before flashing!!
TWRP should work, maybe need to format. I always use the HTC One Developer Edition RUU zip that can be found on HTC Dev site as well as the numerous threads around XDA.
roryrjb said:
TWRP should work, maybe need to format. I always use the HTC One Developer Edition RUU zip that can be found on HTC Dev site as well as the numerous threads around XDA.
Click to expand...
Click to collapse
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.
for righuen
st.zapto said:
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.
Click to expand...
Click to collapse
Hello, I meant i unlocked my device in a boutique. I don't think we can do that our-self. Thanks.
st.zapto said:
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.
Click to expand...
Click to collapse
Actually I haven't tried a different SIM, but I'm sure it would work.
Hey guys been going at this for about 14 hours
Story
flashed amazing android hd 3.1 thinking i had 5.1, when i realized that, i downloaded 5.1 and flashed it. Seemed to work except as soon as phone began to boot i got a pink screen followed by the htc and beats audio screen (logos were different colors) at this point it wouldn't do anything else.
I rebooted and went in recovery (twrp 2.6.3.0) and wiped cache, tried re flashing and same thing so i went in twrp (im a nweb haven't done this since i had my hero) formatted the data. Yes everything was gone no OS to boot from so i tried using sideloader but it wouldnt go past start up process i resorted to using adb, i pushed the amazing android 3.1 rom and flashed it. everything seemed to go fine. Seemed to boot, when i went to unlock the screen to set the phone up it just rebooted, it kept doing that over and over. Installed insert coin rom and did the same thing. idk what else to do :/ tried loading stock ruu but it gave me a fail message (cant remember what it was)
I never made any back ups as i didnt care about losing any data
Would appreciate some help guys
Im on mac and windows 7
Can you list what it says in your bootloader?
BD619 said:
Can you list what it says in your bootloader?
Click to expand...
Click to collapse
THANKS FOR THE QUICK RESPONSE
TAMPERED
UNLOCKED
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
OPENDSP-v32.120.274.0909
OS-4.06.651.4
eMMC-boot 2048MB
dang, all caps lol
manny_ said:
THANKS FOR THE QUICK RESPONSE
TAMPERED
UNLOCKED
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
OPENDSP-v32.120.274.0909
OS-4.06.651.4
eMMC-boot 2048MB
dang, all caps lol
Click to expand...
Click to collapse
There is no RUU for 4.06.651.4
However you can use this guide to fix your phone
Any questions PM or post here
BD619 said:
There is no RUU for 4.06.651.4
However you can use this guide to fix your phone
Any questions PM or post here
Click to expand...
Click to collapse
thanks, im about to give it a shot
good morning lol
ok since im on s-on 4.06 do i skip this?
If you are S-OFF flash the 3.04 s-off firmware or 3.05 s-off firmware or 3.05.651.6 s-off firmware or 4.06.651.4 s-off firmware and you are done. If you are already on 4.06.651.4 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included (use the same commands from 5.)
1.Download the 3.04 s-on firmware or 3.05 s-on firmware or 3.05.651.6 s-on firmware or 4.06.651.4 s-on firmware
2.Rename it firmware.zip (put the firmware.zip into the platform tools folder or the folder attached below)
3.Boot to bootloader
4.Lock bootloader(fastboot oem lock)
5.Then use these commands:
and go straight to this?
7.Then unlock the bootloader again and re-flash TWRP 2.6.3.0. (before formatting go to setting/screen and disable screen timeout)
8.Within TWRP 2.6.3.0 select Wipe > Format Data(it will ask you to confirm by typing YES) once done adb push a rom to your phone (adb push nameofrom.zip /sdcard/ ).
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
9.Optional but recommended: S-OFF using Rumrunner or Firewater
10.Win lol
:') thank you so much
Im about to do revone then flash amazing android hd google experience 6.1
Is there anything i should be doing to avoid this again?
manny_ said:
:') thank you so much
Im about to do revone then flash amazing android hd google experience 6.1
Is there anything i should be doing to avoid this again?
Click to expand...
Click to collapse
Make sure the International roms you flash have Sprint support (does android hd google experience 6.1 have Sprint support yet?)
Also S-OFF it will save you headaches in the future
BD619 said:
Make sure the International roms you flash have Sprint support (does android hd google experience 6.1 have Sprint support yet?)
Also S-OFF it will save you headaches in the future
Click to expand...
Click to collapse
you are right, is there any google experience 4.4.2 roms that you can recommend?
http://forum.xda-developers.com/showthread.php?t=2183023
this one says sprint support in the tittle but says "For HTC One International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint)" inside
thats actually the rom i flashed that got me in the situation :\
manny_ said:
you are right, is there any google experience 4.4.2 roms that you can recommend?
http://forum.xda-developers.com/showthread.php?t=2183023
this one says sprint support in the tittle but says "For HTC One International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint)" inside
thats actually the rom i flashed that got me in the situation :\
Click to expand...
Click to collapse
[ROM]★☆★Nocturnal GE CDMA|4.4.2|1/19/2014|★☆★
★☆★[ROM] Team Nocturnal xR1|SPRINT|Odex|Pure Vanilla|KitKat|Dec 18th 2013|★☆★
Check the threads and make sure there are no issues for folks on the latest OTA
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Looks like your OS is gone. Did you try and reflash twrp?
---------- Post added at 08:25 AM ---------- Previous post was at 07:55 AM ----------
24.531
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Try running this 3.24.531.3 ruu, instructions on page.
http://forum.xda-developers.com/showthread.php?t=2375223
Thanks very much folks. Somehow, I was able to reflash twrp. From there, I realized that one mistake I made was overlooking that I needed s-off activated before flashing the ROM. (I think that was the beginning of my difficulties.)
Before reflashing twrp, I tried the RUU suggestion (TY!), but that needed bootloader turned back on, which in turn needed s-off...quite a procedure.
Anyway, With s-off done (thanks to the very persistent rumrunner_HTC_0.5.0.zip !), a second flash attempt of the rom at http://forum.xda-developers.com/showthread.php?t=2341395 worked seemingly perfectly. I now just trying to figure out whether I can get wifi calling working reliably (should be able to in theory, and at least one poster in that thread says he's done so).
Getting the HTC one properly modded is not a simple process relative to my prior experiences. I'm grateful for the help!
All of that work in the beginning was not needed. All you had to do was unlock bootloader, S-Off, change CID to 11111111, and run the GPE RUU from HTC. That's it. I had an ATT version that saw every different incarnation of software and it was that easy every time. Went from ATT to GPE, to T-Mobile, to Dev Edition and back without a problem. Well, red triangles of death be damned, but it never slowed me down, and the only time I got those was when I mis-matched the recovery img, or tried an update with a HBoot higher that 1.44, those are the only thinga to watch for. Make sure your ducks are in a row and update away. Stock recovery and lower Hboot worked awesome. I probably should put together a master file of everything I have for DL because I have it all and would make life so easy if someone hasn't done it already.
It's been awhile since I've messed with ROMs, and much has changed. I think I might have bit off more than I can chew, but hopefully it's a quick fix. I've been trying to scan for solutions, but so far no luck.
About a week ago I decided I was tired of avoiding apps that had crazy permissions and decided to get root on my phone so I could use AppOpps. I went through the HTCDev route and unlocked the bootloader. I got stuck when firewater, temproot & Weaksauce wouldn't work.
So, I relocked the bootloader (shows **relocked**) and figured I'd wait until someone pushed an updated tool. Got an OTA notice, and now I can't update the software. The update fails about 1/3 of the way through, going from green circled arrows to red triangled exclamation.
I've tried using fastboot to push the OTA ROM, but have had no success. I can flash the newest firmware successfully (as noted here http://forum.xda-developers.com/showthread.php?t=2766604), but still no joy on the OEM ROM.
Do I really have to go to the trouble of flashing older firmware, downgrading the HBoot and ROM to an older version, etc.. to get up and running with a **locked** phone that will get OTA update?
Such a PITA to get control over my data/permissions.
Thanks in advance for help.
So just RUU and call it a day
Sent from my HTCONE using Tapatalk
Weaksauce does not work on the Sprint variants.
I would give Firewater another shot as s-off will save you headaches like this down the road. I would also suggest doing it before you update HTC has a way of making thing harder for us with every OTA.
If your phone is inoperable at the moment use this guide to get up and running.
http://forum.xda-developers.com/showthread.php?t=2503646
Recent RUU
olorolo said:
So just RUU and call it a day
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
At the moment, all I can find is an older RUU, not the latest/greatest.
I've found a Sprint_HTC_One_m7wls_4.06.651.4_RUU download, but my phone is reporting Software version 4.06.651.9
Would this be close enough?
xenor said:
At the moment, all I can find is an older RUU, not the latest/greatest.
I've found a Sprint_HTC_One_m7wls_4.06.651.4_RUU download, but my phone is reporting Software version 4.06.651.9
Would this be close enough?
Click to expand...
Click to collapse
If your running Sprint it should be fine
Sent from my HTCONE using Tapatalk
Phone is working OK
BD619 said:
Weaksauce does not work on the Sprint variants.
I would give Firewater another shot as s-off will save you headaches like this down the road. I would also suggest doing it before you update HTC has a way of making thing harder for us with every OTA.
If your phone is inoperable at the moment use this guide to get up and running.
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
So far, the phone seems to be working fine, other than deleting my Amazon saved games
If I run the RUU as suggested: Sprint_HTC_One_m7wls_4.06.651.4_RUU, will I still be in a good position to try firewater again?
xenor said:
So far, the phone seems to be working fine, other than deleting my Amazon saved games
If I run the RUU as suggested: Sprint_HTC_One_m7wls_4.06.651.4_RUU, will I still be in a good position to try firewater again?
Click to expand...
Click to collapse
That RUU won't work it's older then the software you are currently on.
Give firewater a try without using weaksauce
Update information
BD619 said:
That RUU won't work it's older then the software you are currently on.
Give firewater a try without using weaksauce
Click to expand...
Click to collapse
You are correct, the RUU did not work. It failed completely on Windows 8.1 x64, so I ran in on Windows 7 x64, and it stopped at about 4%. The phone screen was black with the HTC logo and it just stayed like that for over an hour (I took the dog for a walk).
The Boot reports the following:
*** RELOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
Once the phone is booted up, the Settings->About reports the following:
Software version: 4.06.651.9
Android 4.4.2
HTC Sense 5.5
Can an OTA flash the firmware and die before updating the software?
Do I need to flash the firmware to match the reported software in the system?
xenor said:
You are correct, the RUU did not work. It failed completely on Windows 8.1 x64, so I ran in on Windows 7 x64, and it stopped at about 4%. The phone screen was black with the HTC logo and it just stayed like that for over an hour (I took the dog for a walk).
The Boot reports the following:
*** RELOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
Once the phone is booted up, the Settings->About reports the following:
Software version: 4.06.651.9
Android 4.4.2
HTC Sense 5.5
Can an OTA flash the firmware and die before updating the software?
Do I need to flash the firmware to match the reported software in the system?
Click to expand...
Click to collapse
I've never personally did an OTA so not sure.
If you use the guide I posted and use the 5.03.651.3 s-on firmware and rom it will be just like taking the OTA
OK, it took a little bit of research, because you probably assume most folks already know how to do this, but I got through your tutorial. Getting the latest TWRP was a bit confusing. At first I thought I had to have the TWRP app from the Google Play Store, which requires root, but then I found the TWRP page pointing to GooManager which automatically found the latest file and installed.
After that, it took a minute to figure out I had to go into HBOOT and select recovery to get the TWRP tool. I thought I was going to be using an Android utility to accomplish this (I guess I mean to say an app from the play store, not a BIOS like utility).
Lastly, for some reason the Android MyHTC driver died, so I had to manually remove and re-install. Re-running HTC Sync Manager install did not help. Once I got that figured out, I was able to adb push the file to the SDCard (Too bad one can't just drag and drop, but I'm guessing MTP dies with the flash?) and then load it from TWRP.
At the moment, I'm happy. I have the newer software and plenty to play with. I will give Firewater a try again, but I'm guessing it will be more difficult with the newest firmware/ROM?
I started with this guide a few days ago, but didn't push forward when I couldn't figure out the TWRP information. It might help to update that part of the guide, unless you want to avoid too many noobs getting into trouble.
Thanks for your help, and pointing me back in the right direction so quickly.
Hello,
I have just been given a rooted HTC M7 (AT&T). It hasn't been used for almost a year, but it seems to work. It only has a recovery on it, not a ROM. I have no idea how to get it from where it is up to the latest and greatest. Any help or recommendations would be appreciated. I tried to read up on everything, but i couldn't parse out the info I needed from existing threads. I hope my terminology is correct!
Here's what I've got:
Device: AT&T HTC One M7
BOOTLOADER Info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.4.4.0000
RADIO-4a.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 19:16:59: -1
RECOVERY Info:
TWRP 2.8.1.0
ROM INFO:
I have not loaded a rom onto the device at this point. I haven't felt comfortable since I don't know if the phone in its current state will run the latest roms.
Here's what I need to know.
1. Do I need to update my bootloader? It seems like 1.44 is much older than what other people are currently using. I've seen most people on 1.57 or 1.56. If I do need to update it, what version should I update to?
2. My recovery seems to be almost up to date. I am pretty sure i know how to get the .zip for the latest version, but I don't know if I have to flash it or use another way to install it.
3. I cannot get fastboot working on my windows 8.1 machine. It does work on an old windows 7 laptop I have. It seems like others have this issue on hboot 1.44. Is there any fix for it?
4. Firmware, Kernals, and Radios. How do you know what firmware, kernel, and radio to use for a given device? does it depend on the rom you choose? There seems to be so many and it isn't clear to me.
5. Does it matter if i choose a GPE rom, a Cyanogen Rom, or a Sense Rom? Do kernels, firmwares, and radios depend on the type of rom I choose?
Thanks for all your help! I look forward to using my new to me device.
thenaysayer said:
Hello,
I have just been given a rooted HTC M7 (AT&T). It hasn't been used for almost a year, but it seems to work. It only has a recovery on it, not a ROM. I have no idea how to get it from where it is up to the latest and greatest. Any help or recommendations would be appreciated. I tried to read up on everything, but i couldn't parse out the info I needed from existing threads. I hope my terminology is correct!
Here's what I've got:
Device: AT&T HTC One M7
BOOTLOADER Info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.4.4.0000
RADIO-4a.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 19:16:59: -1
RECOVERY Info:
TWRP 2.8.1.0
ROM INFO:
I have not loaded a rom onto the device at this point. I haven't felt comfortable since I don't know if the phone in its current state will run the latest roms.
Here's what I need to know.
1. Do I need to update my bootloader? It seems like 1.44 is much older than what other people are currently using. I've seen most people on 1.57 or 1.56. If I do need to update it, what version should I update to?
2. My recovery seems to be almost up to date. I am pretty sure i know how to get the .zip for the latest version, but I don't know if I have to flash it or use another way to install it.
3. I cannot get fastboot working on my windows 8.1 machine. It does work on an old windows 7 laptop I have. It seems like others have this issue on hboot 1.44. Is there any fix for it?
4. Firmware, Kernals, and Radios. How do you know what firmware, kernel, and radio to use for a given device? does it depend on the rom you choose? There seems to be so many and it isn't clear to me.
5. Does it matter if i choose a GPE rom, a Cyanogen Rom, or a Sense Rom? Do kernels, firmwares, and radios depend on the type of rom I choose?
Thanks for all your help! I look forward to using my new to me device.
Click to expand...
Click to collapse
you have an AT&T Phone with s-off. Start updating with this RUU from windows 7
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
After this RUU windows 8 will see your phone again
Then this Firmware > http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
followed by this RUU >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
To flash the Firmware use
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
when your done check for software updates in settings before you flash a custom recovery and root.
you should get the 5.x.502 OTA update
Amazing. Thank you so much.
clsA said:
you have an AT&T Phone with s-off. Start updating with th....and root.
you should get the 5.x.502 OTA update
Click to expand...
Click to collapse
just clearing concepts
Why you told him to 1st flash ruu then firmware then higher ruu
Why not higher firmware or ruu directly ?
yatindroid said:
just clearing concepts
Why you told him to 1st flash ruu then firmware then higher ruu
Why not higher firmware or ruu directly ?
Click to expand...
Click to collapse
because a lot of people have problem flashing the 4.x RUU alone, they get a error 155 .. flashing the firmware first solves this problem
And the 3.x Full RUU insures he does not get any problem upgrading from hboot 1.44
so he in fact went the same route AT&T released the updates