ATT M7 unlocked via htcdev and rooted: BAD FLASH - One (M7) Q&A, Help & Troubleshooting

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.

Related

[Q] HELP!!! Unroot Attempt - Different Fastboot than the normal

Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:

[Q] How can I install the OTA?

Hi
I have a European HTC One, with stock HTC HBOOT 1.54.
TWRP 2.6.3.0
And I flashed a pure GPE 4.3 ROM with no root.
Like many people I got the last OTA notification.
When I try to install it. It gets stuck at the end of the reboot countdown (in the system).
Can I do this security update?
Maybe by doing it through TWRP? It is a minor update so it should be OK, no?
Thanks for your help.
You need the stock recovery to flash the OTA
EddyOS said:
You need the stock recovery to flash the OTA
Click to expand...
Click to collapse
You mean the HTC stock recovery or the GPE stock recovery?
GPe, you can get it in the GPe RUU thread
EddyOS said:
GPe, you can get it in the GPe RUU thread
Click to expand...
Click to collapse
I put the Stock GPE recovery. No change. It still gets stuck at the end of the reboot countdown (in the system).
Can't I install the update with another method?
Nope. You could download the OTA file, copy it to the internal memory and flash it from the stock recovery manually and see if that works. Worked fine for me the other day (but I've since gone back to Sense)

T Mobile Update To 4.4.2 with S-OFF?

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

[Q] Unroot Sprint HTC One from CM11

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. ????

[Q] update issue

Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
dirtrider129 said:
Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
Click to expand...
Click to collapse
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
update issue
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
dirtrider129 said:
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
Click to expand...
Click to collapse
alray said:
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
Click to expand...
Click to collapse
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
dirtrider129 said:
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.
update question
[/Quote]better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.[/QUOTE]
After lots and lots of research into this before doing I've decided to go with viperone custom Rom, if I understand it right I won't have to mess with s-off for this,please correct me if I'm wrong. But I have found some conflicting instructions, I read somewhere that I will have to copy the boot.img from the Rom and flash it before flashing the Rom then others without that step, so I'm confused, I wanna male sure I do this right the first time. Also are there any files that I need to have updated before flashing a 4.4 sense 6 custom Rom or will it all be included in the Rom?
Thank you
Dirtrider
Hi there
Been a long time since I've posted and hope I'm in the right place. Did a search for my question and wound up here.
My phone is stock and s-on, I haven't done anything to it, it's exactly the same as when it came out the box, but I haven't been able to update the software in settings>about>software updates for a while now, it just keeps coming back with download unsuccessful. Any ideas how I can sort this, or do it another way?
Thanks in advance
Sent from my HTC One using XDA Free mobile app

Categories

Resources