So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2
yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.
iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.
Hi all,
Sorry if this isn't posted in the right place, please tell me and I will shift it!
Essentially I have been stuck for a few weeks. I need to send my phone back to Vodafone but I recent rooted it, didn't take a back up of the legit software and now can't get back!
Some details on the phone:
CID: VODAP001
HBOOT: 1.56
VERSION: 4.19.161.Xx (i forget the last bit)
Last version of android running (encase it helps): 4.4.2
I've tried HTC guru reset but when applying the ota it just hits a boot loop. I've tried all s-off methods (firewater and rumrunner) with a mixture of roms + kernels to no success.
I'm rather stumped and not sure what to do next! Any help would be appreciated, or if someone has the RUU to reinstall?
Thanks in advance for any help / advice you can off!
Sent from my not-quite-right HTC One
linkjack said:
Hi all,
Sorry if this isn't posted in the right place, please tell me and I will shift it!
Essentially I have been stuck for a few weeks. I need to send my phone back to Vodafone but I recent rooted it, didn't take a back up of the legit software and now can't get back!
Some details on the phone:
CID: VODAP001
HBOOT: 1.56
VERSION: 4.19.161.Xx (i forget the last bit)
Last version of android running (encase it helps): 4.4.2
I've tried HTC guru reset but when applying the ota it just hits a boot loop. I've tried all s-off methods (firewater and rumrunner) with a mixture of roms + kernels to no success.
I'm rather stumped and not sure what to do next! Any help would be appreciated, or if someone has the RUU to reinstall?
Thanks in advance for any help / advice you can off!
Sent from my not-quite-right HTC One
Click to expand...
Click to collapse
When you ran the Guru Reset did you select stock recovery? Did it complete or did it give you an error? If it completed and you tried to receive the OTA did you relock your bootloader first? To successfully run an OTA you must have the stock recovery, stock rom and locked/relocked bootloader if you are S-ON.
majmoz said:
When you ran the Guru Reset did you select stock recovery? Did it complete or did it give you an error? If it completed and you tried to receive the OTA did you relock your bootloader first? To successfully run an OTA you must have the stock recovery, stock rom and locked/relocked bootloader if you are S-ON.
Click to expand...
Click to collapse
Hi majmoz,
Thanks for the quick reply!
Unfortunately no errors, it ran through fine, installed ok with no errors and restarted fine ( and yes selected stock recovery). Works fine until I try and install an ota.
I've tried a few times now, each time I have re-locked the boot loader and it still just sends my phone into a boot loop
linkjack said:
Hi majmoz,
Thanks for the quick reply!
Unfortunately no errors, it ran through fine, installed ok with no errors and restarted fine ( and yes selected stock recovery). Works fine until I try and install an ota.
I've tried a few times now, each time I have re-locked the boot loader and it still just sends my phone into a boot loop
Click to expand...
Click to collapse
Could you post a fastboot getvar all deleting your imei and serial number before posting? To see what is really on your phone.
linkjack said:
Hi all,
Sorry if this isn't posted in the right place, please tell me and I will shift it!
Essentially I have been stuck for a few weeks. I need to send my phone back to Vodafone but I recent rooted it, didn't take a back up of the legit software and now can't get back!
Some details on the phone:
CID: VODAP001
HBOOT: 1.56
VERSION: 4.19.161.Xx (i forget the last bit)
Last version of android running (encase it helps): 4.4.2
I've tried HTC guru reset but when applying the ota it just hits a boot loop. I've tried all s-off methods (firewater and rumrunner) with a mixture of roms + kernels to no success.
I'm rather stumped and not sure what to do next! Any help would be appreciated, or if someone has the RUU to reinstall?
Thanks in advance for any help / advice you can off!
Sent from my not-quite-right HTC One
Click to expand...
Click to collapse
Don't worry, fastboot getvar all is not required, I have a TWRP backup here of that rom:
https://drive.google.com/file/d/0B_nEcSZr5peRZnpMSHRPRjlzX2c/edit?usp=sharing
you will need to get it onto your phone then restore it through TWRP
However, what do you intend to do about the TAMPERED and UNLOCKED flags you have in your bootloader ? this voids warranty.
Seanie280672 said:
Don't worry, fastboot getvar all is not required, I have a TWRP backup here of that rom:
(URL deleted as I'm a newbie and they won't let me say thanks with it in)
you will need to get it onto your phone then restore it through TWRP
However, what do you intend to do about the TAMPERED and UNLOCKED flags you have in your bootloader ? this voids warranty.
Click to expand...
Click to collapse
Thanks so much!
I intend to hope they don't look hehe. From my experience if it's hardware they do a quick check on the settings, about phone then get down to business.
After that, I won't do an update until I can s-off and put everything back to how it should be.
Thanks again!
Well i dun goofed. I tried to flash the furnace kernel to overclock my HTC one m8 but it got stuck on the boot screen with red letters saying "This build is for development purposes only Do not distribute outside of HTC without HTC's written permission Failure to comply may lead to legal action" . So then i went into recovery and wiped everything even the os. to try to fix it now am stuck here with a phone without an OS and dont know how to fix it.
Details on the phone-
Its rooted and has an unlocked bootloader
S-on
Please help me fix my phone
Is the rom.zip still on your sdcard?
If not you can either mount usb storage while booted to twrp or adb push the rom also while in twrp.
BTW you could have dirty flashed the rom and it would have fixed the problem.
BD619 said:
Is the rom.zip still on your sdcard?
If not you can either mount usb storage while booted to twrp or adb push the rom also while in twrp.
BTW you could have dirty flashed the rom and it would have fixed the problem.
Click to expand...
Click to collapse
Ya but my phone wont flash it
well it took a while but i managede to get paranoid android on it but i want the original os for my phone any one know where i can find a link for stock HTC one m8 Sprint OS?
RUU will bring it back to stock
EVOuser94 said:
RUU will bring it back to stock
Click to expand...
Click to collapse
How do i find out which one to use
anyone got the SPCS_001 1.54.651.8 version
Look in the first post of the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
Magnum_Enforcer said:
Look in the first post of the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Problem with this is i dont know which one to use
toto4871 said:
Problem with this is i dont know which one to use
Click to expand...
Click to collapse
Use the one that matches the software version you posted.
https://www.androidfilehost.com/?fid=23578570567713017
Magnum_Enforcer said:
Use the one that matches the software version you posted.
https://www.androidfilehost.com/?fid=23578570567713017
Click to expand...
Click to collapse
I try to flash it in FUU and it gives me error 155 what do i do
Forget what i said am in fastboot getting signature faliures what do i do know
Nevermind all i did was relock the bootloader and it fixed the 155 error in FUU
I have a Sprint HTC One (M7) and I am having trouble. I have an unlocked bootloader and TWRP installed. I have lock it and flashed the stock recovery and locked the boot loader but I can't get any RUU to work. They keep giving me errors. I have tried 4.06.651.4, 5.05.651.2 & 6.16.651.2 RUUs. I have tried to flash ViperOne 7.0.2, Android Revolution 31.6 and 5.03.651.3 with TWRP. They fully install but the phone just keeps going into a boot loop. I can get to the unlock screen but that's it. My phone is S-ON and myHBoot is 1.56 and my OS is 5.05.651.2 (4.06.651.9). Can someone help me get this phone working?
Thanks
og style said:
I have a Sprint HTC One (M7) and I am having trouble. I have an unlocked bootloader and TWRP installed. I have lock it and flashed the stock recovery and locked the boot loader but I can't get any RUU to work. They keep giving me errors.
Click to expand...
Click to collapse
What was the error codes/messages?
I have tried to flash ViperOne 7.0.2, Android Revolution 31.6 and 5.03.651.3 with TWRP.
They fully install but the phone just keeps going into a boot loop. I can get to the unlock screen but that's it.
Click to expand...
Click to collapse
Because you are flashing GSM roms on your CDMA phone. It won't work, flash roms compatible with Sprint (CDMA) variant.
Can someone help me get this phone working?
Click to expand...
Click to collapse
post the output of "fastboot getvar all". Make sure to remove your IMEI, MEID and SERIALNO before posting.
I was finally able to get the 4.06.651.4 ruu to work. Thanks for the help.
Hey guys. So I flashed Android 4.4.3 (KitKat) - latest official HTC One 6.09.401.12 (WWE) firmware (84.x series) to my Att HTC M7. I unlocked bootloader and rooted prior to that. Installed TWRP recovery. I didn't back up my original OS nor do a nandroid back up.
When I first flash it was 1/2 ok. I was able to get to the setup wizard on the rom. Then it reboot to recovery. All I can get is bootloader and recovery.
in order for adb sideload or just adb to work the steps I have to take are peculiar. I stumbled on this today. I have to connect my usb cable when the M7 is off. I boot into the bootloader via *power button and *volume down. Then I select fastboot, then I go back and select recovery. When it boots to recovery then I touch advanced and my device shows up. Also my OTG connection works fine.
So I downloaded the stock version odexed. I get errors on install. Actually I get errors trying to install any rom now. I've tried to unzip and rezip using winrar. Any clues as what I should try now? I wanted to post a pic of my bootloder info and the error message but alas I dont have 10 post.
BOOTLOADER
***TAMPERED***
***unlocked****
m7_ul S-on RH
HBOOT 1.57.0000
RADIO 4M.27.3218.14
OS 5.13.502.3
Error i get
E: unable to open zip file
error flashing zip '/usb-otg/one_.......
Thanks
MackadociousPrime38 said:
Hey guys. So I flashed Android 4.4.3 (KitKat) - latest official HTC One 6.09.401.12 (WWE) firmware (84.x series) to my Att HTC M7. I unlocked bootloader and rooted prior to that. Installed TWRP recovery. I didn't back up my original OS nor do a nandroid back up.
When I first flash it was 1/2 ok. I was able to get to the setup wizard on the rom. Then it reboot to recovery. All I can get is bootloader and recovery.
in order for adb sideload or just adb to work the steps I have to take are peculiar. I stumbled on this today. I have to connect my usb cable when the M7 is off. I boot into the bootloader via *power button and *volume down. Then I select fastboot, then I go back and select recovery. When it boots to recovery then I touch advanced and my device shows up. Also my OTG connection works fine.
So I downloaded the stock version odexed. I get errors on install. Actually I get errors trying to install any rom now. I've tried to unzip and rezip using winrar. Any clues as what I should try now? I wanted to post a pic of my bootloder info and the error message but alas I dont have 10 post.
BOOTLOADER
***TAMPERED***
***unlocked****
m7_ul S-on RH
HBOOT 1.57.0000
RADIO 4M.27.3218.14
OS 5.13.502.3
Error i get
E: unable to open zip file
error flashing zip '/usb-otg/one_.......
Thanks
Click to expand...
Click to collapse
Ok so i don't know why but after 4 tries I was able to flash a ROM. But its an ATT stock ROM I got it from the att ROM section. But I'm on tmobile
MackadociousPrime38 said:
Ok so i don't know why but after 4 tries I was able to flash a ROM. But its an ATT stock ROM I got it from the att ROM section. But I'm on tmobile
Click to expand...
Click to collapse
You won't receive ota update on an at&t phone if you are not on the at&t network.
What is your custom recovery version?
I would achieve s-off using Sunshine so you can fully convert your phone to another version which doesn't require a specific carrier to receive update like the WWE version (x.xx.401.x) or the Developer version (x.xx.1540.x)
alray said:
You won't receive ota update on an at&t phone if you are not on the at&t network.
What is your custom recovery version?
I would achieve s-off using Sunshine so you can fully convert your phone to another version which doesn't require a specific carrier to receive update like the WWE version (x.xx.401.x) or the Developer version (x.xx.1540.x)
Click to expand...
Click to collapse
So I achieved s off using Sunshine. Changed cid and mid to corresponding t-mobile spec. Flashed the RUU for t-mobile from the HTC website download. Now when I flash the RUU I suppose it takes out my recovery and flashed a stock recovery?
I had TWRP but now I have some weird recovery. Last time I went into it and I rebooted out it factory reset my HTC. Pain in the ass more than anything.
I was thinking I could flash a ROM and see if it performs as or better than the RUU. The only benefit of using the stock tmobile is OTA updates right?
Oh and since I don’t have twrp anymore should can I reflash that? I would like to make a backup of my OS before I start screwing around.
MackadociousPrime38 said:
So I achieved s off using Sunshine. Changed cid and mid to corresponding t-mobile spec. Flashed the RUU for t-mobile from the HTC website download. Now when I flash the RUU I suppose it takes out my recovery and flashed a stock recovery?
Click to expand...
Click to collapse
Yes, a ruu will re-write all stock software and firmware to the phone (system, recovery, kernel, radio, bootloader, drivers, and so on)
I had TWRP but now I have some weird recovery. Last time I went into it and I rebooted out it factory reset my HTC. Pain in the ass more than anything.
Click to expand...
Click to collapse
You can't do much using stock recovery except a factory reset. Stock recovery is needed for ota updates but if you are already on last version you don't reallt need it anymore and you can reflash twrp over it.
I was thinking I could flash a ROM and see if it performs as or better than the RUU. The only benefit of using the stock tmobile is OTA updates right?
Click to expand...
Click to collapse
If you already flashed the latest t-mobile ruu (lollipop), you will not receive any more ota updates. Lollipop 5.0.2 Sense 6 should be the last version for the M7. At least flashing the ruu was not a waste of time since it upgraded your firmware; newer custom roms requires the latest firmware to work properly.
Oh and since I don’t have twrp anymore should can I reflash that? I would like to make a backup of my OS before I start screwing around.
Click to expand...
Click to collapse
Yep I would relfash twrp and make a backup before trying other toms. You can always revert back to stock using the same ruu if you don't have a backup.