My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
b1969 said:
My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
Click to expand...
Click to collapse
don't think S-OFF or unlocked matters, just stock rom and recovery required
if i run RUU will that give me stock recovery?
b1969 said:
if i run RUU will that give me stock recovery?
Click to expand...
Click to collapse
If you have a ruu for your currently installed rom, you can extract the recovery from the zip and install.
Otherwise
http://forum.xda-developers.com/showthread.php?t=2545227
Pick the one that matches your current rom version
b1969 said:
My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
Click to expand...
Click to collapse
My phone is unlocked/S-OFF. On the previous OTA updates, all I had to do was reflash the stock recovery and the updates proceeded normally, installed just fine. On this new OTA update to 4.4.2, however, that didn't work. I tried relocking the bootloader, flashed the stock recovery... nothing worked (it would get the red slash during the recovery part of the OTA update). Evidently, T-Mobile/HTC are now much more picky about modified devices.
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Fuzi0719 said:
My phone is unlocked/S-OFF. On the previous OTA updates, all I had to do was reflash the stock recovery and the updates proceeded normally, installed just fine. On this new OTA update to 4.4.2, however, that didn't work. I tried relocking the bootloader, flashed the stock recovery... nothing worked (it would get the red slash during the recovery part of the OTA update). Evidently, T-Mobile/HTC are now much more picky about modified devices.
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Click to expand...
Click to collapse
Thank you for the information.
Fuzi0719 said:
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Click to expand...
Click to collapse
4.3.1???
Im only on 4.3 and cant update. Ex:3.24.531.3
no-root, Unlocked and s-off only
Related
Hi - im a bit of a newb at this so bear with me!
i recently unlocked my bootloader and installed a stock 4.3 JWR66Y.H1 gpe rom and TWRP.
i am now getting the OTA notification but when i try to update it boots in to twrp, flashes the update, reboots and then i end up with a weird green screen. i have restored a backup in twrp back to 4.3, and everytime i try and install the update it does the same thing.
the phone is s-on - i have tried to s-off using rumrunner but it doesnt seem to like the rom and wont work (im on hboot 1.54).
any help would be greatly appreciated in getting the update to flash properly.
blackic3 said:
Hi - im a bit of a newb at this so bear with me!
i recently unlocked my bootloader and installed a stock 4.3 JWR66Y.H1 gpe rom and TWRP.
i am now getting the OTA notification but when i try to update it boots in to twrp, flashes the update, reboots and then i end up with a weird green screen. i have restored a backup in twrp back to 4.3, and everytime i try and install the update it does the same thing.
the phone is s-on - i have tried to s-off using rumrunner but it doesnt seem to like the rom and wont work (im on hboot 1.54).
any help would be greatly appreciated in getting the update to flash properly.
Click to expand...
Click to collapse
Make sure you follow all the instructions for rumrunner. You can't flash any unsigned firmware on s-on. Try manually flashing the update. Download the update and flash in recovery.
Ktan188 said:
Make sure you follow all the instructions for rumrunner. You can't flash any unsigned firmware on s-on. Try manually flashing the update. Download the update and flash in recovery.
Click to expand...
Click to collapse
so to clarify - the ota update is failing because the phone is s-on?
i have flashed the elemental kernel and will try rumrunner again later if thats the case.
4.4 rom
blackic3 said:
so to clarify - the ota update is failing because the phone is s-on?
i have flashed the elemental kernel and will try rumrunner again later if thats the case.
Click to expand...
Click to collapse
Having same issue, is there a ROM that can be loaded instead of going through ota update. I can't get s off to work no matter what I try
You MUST get S-OFF before you get 4.4 OTA, as if things go south, you are in big do-do. Read the last 5-6 pages and you will get an idea.
So do NOT install OTA until you have S-OFF and unlocked bootloader..
soff trouble
SaHiLzZ said:
You MUST get S-OFF before you get 4.4 OTA, as if things go south, you are in big do-do. Read the last 5-6 pages and you will get an idea.
So do NOT install OTA until you have S-OFF and unlocked bootloader..
Click to expand...
Click to collapse
How do I get soff doesn't seem to work no matter what I try
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
pc010121 said:
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
Click to expand...
Click to collapse
you can use this then take the OTA updates
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
pc010121 said:
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
Click to expand...
Click to collapse
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Edit: I am relocked as I am S-ON. I can't update firmware as the signature check fails. Flashing the 3.04.651.2 zip has a signature verify fail, as well.
Hope this helps
cheesesoda said:
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Click to expand...
Click to collapse
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
pc010121 said:
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
Click to expand...
Click to collapse
Actually, it seems that the phone is wiped; I can't boot my recovery. As a result, I can't really get S-OFF. I'll try the 4.06 RUU, but would it make a difference that it's .4 and not .9?
EDIT: I'm talking out of my ass right now. Long day, and this isn't helping. I am figuring it out; unlocked the bootloader, and now things seem to be functional. Well, except CM doesn't seem to want to boot any longer, but that shouldn't matter for long.
EDIT 2: How can I get S-OFF without enabling debugging? As of right now, CM is just in a boot loop.
Sim Unlock Sprint HTC One Max
I almost cannot believe how many different ROMs I've tried to flash after wiping out my original ROM.
Bootloader unlocked and rooted I managaged to relock the bootloader while trying to fastboot flash a stock ROM, which also failed.
Beleive it or not, I've have found a couple that will boot up with my Sprint HTC One Max . I was able to re-unlock the bootloader, flash a new rom and even recover user data I had backed up to my PC via adb backup.
All this for not, as I still cannot find a Sense ROM that will flash on my device and allow me to unnlock the Sim via Sim Unlock Helper.
Any help would be greatly appreciated!!!
TAMPERED
UNLOCKED
Sprint HTC One T6WL S-OFF
CID-SPCS_001
HBOOT-2.49.000
RADIO-1.48.50.0425
I recall reading somewhere that the Unlock Sim Helper should work on Sense 4.1.2 ROM. ????
Hi all,
When I first got my M7, I unlocked it and installed TWRP to make backups. I had experience doing this with my sensation and followed the guides posted here. When the Sense 6 update came out, I wanted to update, so I was tried using REVONE to remove the TAMPERED and UNLOCKED but it set it to RELOCKED. Apparently, it wasn't compatible with the android version 4.4.2, which I realized too late.
Now, I'm trying to get S-OFF and unlock the bootloader so I can flash an 4.2 rom, then use REVONE and go back to stock. I've tried using nkk71's SuperGUIDE to returning 100% back to stock, but neither Firewater nor Rumrunner will work with my device (HBOOT 1.56) - they both finish early and tell me I'm out of luck.
What's the next possibility? I'm in Asia with the TW stock rom. I can probably bring it to the store and let them handle it, but it'll take up to 7 days to get it completely back to stock. Is there anything else I can try before doing that?
tl;dr: Phone is Stock ASIA TW rom & recovery, HBOOT 1.56, *TAMPERED*, *RELOCKED*, and *S-ON*. Can't flash OTA or get S-OFF with Firewater.
EDIT: Nevermind. Seem to have soft-bricked my phone while attempting to install ARHD. Now no OS and can't load anything except TWRP. ADB Sideload doesn't work, ADB push doesn't work. Guess I'll bring it to the store and see if they can fix it.
MPenguin said:
Hi all,
When I first got my M7, I unlocked it and installed TWRP to make backups. I had experience doing this with my sensation and followed the guides posted here. When the Sense 6 update came out, I wanted to update, so I was tried using REVONE to remove the TAMPERED and UNLOCKED but it set it to RELOCKED. Apparently, it wasn't compatible with the android version 4.4.2, which I realized too late.
Now, I'm trying to get S-OFF and unlock the bootloader so I can flash an 4.2 rom, then use REVONE and go back to stock. I've tried using nkk71's SuperGUIDE to returning 100% back to stock, but neither Firewater nor Rumrunner will work with my device (HBOOT 1.56) - they both finish early and tell me I'm out of luck.
What's the next possibility? I'm in Asia with the TW stock rom. I can probably bring it to the store and let them handle it, but it'll take up to 7 days to get it completely back to stock. Is there anything else I can try before doing that?
tl;dr: Phone is Stock ASIA TW rom & recovery, HBOOT 1.56, *TAMPERED*, *RELOCKED*, and *S-ON*. Can't flash OTA or get S-OFF with Firewater.
EDIT: Nevermind. Seem to have soft-bricked my phone while attempting to install ARHD. Now no OS and can't load anything except TWRP. ADB Sideload doesn't work, ADB push doesn't work. Guess I'll bring it to the store and see if they can fix it.
Click to expand...
Click to collapse
If it's not too late, I have been in this situation before. I bought an OTG cable and downloaded a stock ROM guru reset. From there, I successfully S-OFFed my device with HBOOT 1.56 using the firewater method.
Hope this helps
I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
dirtrider129 said:
I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
Click to expand...
Click to collapse
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
clsA said:
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
Click to expand...
Click to collapse
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
dirtrider129 said:
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
Click to expand...
Click to collapse
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Oh ok, now I understand. Thanks
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Once I flash the RUU zip, will I lose root also?
dirtrider129 said:
Once I flash the RUU zip, will I lose root also?
Click to expand...
Click to collapse
of course you'll have to re-flash recovery and root again
revone failing
clsA said:
of course you'll have to re-flash recovery and root again
Click to expand...
Click to collapse
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
dirtrider129 said:
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
Click to expand...
Click to collapse
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
coolshritz said:
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
Click to expand...
Click to collapse
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
dirtrider129 said:
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
Click to expand...
Click to collapse
It is not mandatory to S-Off to flash a rom. Your rom will anyway work in a good way.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
dirtrider129 said:
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
Click to expand...
Click to collapse
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
clsA said:
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
Click to expand...
Click to collapse
Do you think firewater will work with viper+Elemental X kernel? If I used the same guide as with ARHD. I tried to s-off with revone by flashing a 4.2.2 viper Rom but I lost all signal and service, so I restored my backup. Also I was wondering since I'm running the 3.17 ruu to update radio and stuff , should I use the 4.18 ruu since its newer? Thanks again for all the help.
UPDATE: Well ran firewater since coudnt get revone to work , took all of like 45 seconds and it said device is s-off. Couldn't believe it after all the trouble I've had.Awesome!
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.