Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
jdub1983 said:
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader?
xunholyx said:
What does it say next to "OS" in your bootloader?
Click to expand...
Click to collapse
Nothing is listed next to os in the bootloader mene
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jdub1983 said:
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
Click to expand...
Click to collapse
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
jdub1983 said:
I any attempts using flashboot do not work.
Click to expand...
Click to collapse
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
redpoint73 said:
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
Click to expand...
Click to collapse
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
If you give me a few things to do when I'm in front of the computer I'll execute them later on and report back the results.
jdub1983 said:
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
jdub1983 said:
None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
jdub1983 said:
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
Click to expand...
Click to collapse
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
redpoint73 said:
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
Click to expand...
Click to collapse
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
jdub1983 said:
I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
Click to expand...
Click to collapse
I didn't specify that it had to be an error code number. If the response is all text, tell us what it is. Cut and paste, or do a screenshot, if that is easier. Either way, it will probably tell me what is going wrong.
jdub1983 said:
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
Click to expand...
Click to collapse
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
No, they aren't.
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
EDIT: I see now that Redpoint has already linked you up. :good: Easier for me
xunholyx said:
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
Click to expand...
Click to collapse
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
redpoint73 said:
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
Click to expand...
Click to collapse
Gotcha! If I'm s-on though, how did everything get screwed up? Guess it's not important now.
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom. Something simple really, my m8 is my backup phone.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
jdub1983 said:
If I'm s-on though, how did everything get screwed up?
Click to expand...
Click to collapse
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
jdub1983 said:
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom.
Click to expand...
Click to collapse
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
redpoint73 said:
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
Click to expand...
Click to collapse
I'll give it a whirl when I get home and let you know of any errors, if any, hopefully not.
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Thanks again!
jdub1983 said:
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Click to expand...
Click to collapse
I doubt it. Rather, I think your syntax was incorrect (if you typed it exactly as you did before) as the part "RUU" (no quotes) should be in caps:
fastboot oem rebootRUU
If the phone is in RUU mode, it will show a black screen, with HTC logo.
jdub1983 said:
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
Click to expand...
Click to collapse
Here's the RUU.zip for you.
you both are amazing, thank you!
I feel so silly, considering I was using sneaky ghosts unsigned fullwipe firmware... Blah!
Again, you both are awesome, kind to a moron! The universe will provide for you both!
Thanks again!!!
Everything is working wonderful!!!!!
Related
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.
kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work
Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU
Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.
Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11
kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.
ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!
Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?
Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?
Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.
Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Hi every one I have htc one m8 now 2-3 years, I rooted and unlocked bootloader, on stock firmware which is : 4.18.708.12 and now I have system updates that I cant update cuz im rooted , so I relocked bootloader and tried to update , still when i try it goes to fastboot with this : system software modified, security warning and it doesnt update nor perform a factory reset, can some one help me out here? id be glad I need this help asap
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
madshark2009 said:
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you no longer have warranty, anyway. HTC warranty is only valid for 1 year.
redpoint73 said:
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you most likely don't have a warranty, anyway. HTC warranty is only valid for 1 year.
Click to expand...
Click to collapse
and how do i decide which RUU is suitable for my device?
android 5.0.1
software number : 4.18.708.12
I must point out that I never installed a custom rom nor recovery I just unlocked bootloader and rooted and thats it so how do I find my ruu and what to do if i dont?
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
madshark2009 said:
and how do i decide which RUU is suitable for my device?
software number : 4.18.708.12
how do I find my ruu and what to do if i dont?
Click to expand...
Click to collapse
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
redpoint73 said:
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
Click to expand...
Click to collapse
I didnt mean to get my warrenty back, I meant to get back to stock just like when getting back to original phone status like it came from the company, so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand I might need your further help perferably vie Direct message, but just to save all the efforts, Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
(sorry i am new thats why i ask a lot )
madshark2009 said:
I didnt mean to get my warrenty back
Click to expand...
Click to collapse
But its exactly what you posted:
madshark2009 said:
I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
I strongly suggest you take a bit more time thinking about what you post, and making sure its properly typed, (lack of proper capitalization, spelling and punctuation makes your posts a pain to read, to say the least) and conveys what you want it to. Otherwise, you're just making it harder for folks to understand and help you.
Any time you think you are saving by typing quickly, is being lost x10 by me having to ask you to clarify what you mean.
madshark2009 said:
so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand
Click to expand...
Click to collapse
The process isn't complicated. If you managed to unlock the bootloader and root the phone, you can certainly accomplish restoring the stock ROM and stock recovery. On that same note, it can be fairly said that anyone that is unable restore the phone by that method; probably shouldn't have unlocked the bootloader and rooted to begin with. Or look at it a slightly different way: you should never root a device without knowing how to return it to stock.
The guide looks long, mostly because its written in a very highly detailed, step-by-step manner (some folks seem to like that). But it just boils down to downloading the proper file, unzipping the folders, putting them in the right location on the phone, and restoring in TWRP.
If you have issues on a particular step, feel free to post again here, or the TWRP stock backup thread we are discussing.
madshark2009 said:
Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
Click to expand...
Click to collapse
I never said there was no RUU for your version number; or did you determine that yourself (your wording isn't clear)? I don't definitely know if there is or not; I was leaving it up to you to search. But doing a quick search myseld, it looks like NO.
If you looked, and there is no RUU for your version, you certainly cannot run any RUU you like. In fact, you can't run any RUU at all, unless its intended for your version, CID, MID.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
madshark2009 said:
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
Click to expand...
Click to collapse
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
yes thats what it means! what can i do now?
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
madshark2009 said:
yes thats what it means! what can i do now?
Click to expand...
Click to collapse
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
redpoint73 said:
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
Click to expand...
Click to collapse
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares and now when I rebooted as instructed it gets stuck at black screen after HTC logo on white screen and so I thought I could fix this by flashing twrp but now it says bootloader signatures veryfication error, so I cant proceed to the installation ..
madshark2009 said:
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
Click to expand...
Click to collapse
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
redpoint73 said:
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
Click to expand...
Click to collapse
yes it got a black screen.
to Unlock bootloader I need what exactly?
madshark2009 said:
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares
Click to expand...
Click to collapse
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
madshark2009 said:
yes it got a black screen.
to Unlock bootloader I need what exactly?
Click to expand...
Click to collapse
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
redpoint73 said:
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
Click to expand...
Click to collapse
so what are my options now?
madshark2009 said:
so what are my options now?
Click to expand...
Click to collapse
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
redpoint73 said:
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
Click to expand...
Click to collapse
ok it worked now im back to stock..
but now there are no software updates available
PS: I did exactly what the post said! now i am back to stock rom with stock recovery and when i go to check updates it says my device is up to date (on lolipop 5.0.1) but before I had 6.0.1 marshmallow available now its not.
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.
andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse
UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...
@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol
drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928
andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.
andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.
i have HTC ONE M8 with following boot properties
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Software Status: Official***
*** LOCKED ***
M8.WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.000
RADIO-1.09.20.0119
OpenDSP-v38.2.2-00542-M8974.0311
OS-3.30.651.2
eMMC-boot 2048MB
OCT 9 2014,21:03:31.33162
HBOOT
when i perform OTA i says my device is already updated but my Android Version is 4.4.4
i want to update it to latest possible android version.
You have the US Sprint version. Which won't get OTA unless you are connected to that actual carrier (Sprint).
To update with official RUU, you can get it here: https://forum.xda-developers.com/showthread.php?t=2729173
If updating to the latest (last) which is Marshmallow 6.20.651.3, then you will need to flash the 6.20.651.3 firmware, before flashing the RUU (peculiar requirement for flashing US Marshmallow RUUs). The firmware is also included on the link above.
Also note that your device may have an unbranded (not Sprint based) ROM installed by a 3rd party seller, in order for it to appear like an "unlocked" device. If you don't see any Sprint branding, such as Sprint logo on boot, Sprint apps, etc.; then it is likely that it has an unbranded ROM installed.
The RUU I linked will install official Sprint-branded ROM, so you may or may not like that. If you don't like the Sprint branding, after flashing firmware/RUU, you can go down the path of flashing a custom ROM (which support the Sprint version M8). But that is another process, and the firmware/RUU needs to be run even in that case, as your firmware (radio, WiFi, etc.) need to be updated to run the current custom ROMs, anyway.
redpoint73 said:
You have the US Sprint version. Which won't get OTA unless you are connected to that actual carrier (Sprint).
To update with official RUU, you can get it here: https://forum.xda-developers.com/showthread.php?t=2729173
If updating to the latest (last) which is Marshmallow 6.20.651.3, then you will need to flash the 6.20.651.3 firmware, before flashing the RUU (peculiar requirement for flashing US Marshmallow RUUs). The firmware is also included on the link above.
Also note that your device may have an unbranded (not Sprint based) ROM installed by a 3rd party seller, in order for it to appear like an "unlocked" device. If you don't see any Sprint branding, such as Sprint logo on boot, Sprint apps, etc.; then it is likely that it has an unbranded ROM installed.
The RUU I linked will install official Sprint-branded ROM, so you may or may not like that. If you don't like the Sprint branding, after flashing firmware/RUU, you can go down the path of flashing a custom ROM (which support the Sprint version M8). But that is another process, and the firmware/RUU needs to be run even in that case, as your firmware (radio, WiFi, etc.) need to be updated to run the current custom ROMs, anyway.
Click to expand...
Click to collapse
in the mentioned website there are alot of RUUs
which one should i use. i have downloaded the first one under 0P6BIMG RUUs heading (i.e 0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zi p) is it right for me or should i download another RUU?
Also there are alot of Firmwares FUU
1. Modified
2. Modified removed boot and recovery
3. Full
4. Signed Full
which one is better for me please tell me.
also which one should i install first RUU or FUU?
Another thing will i be able to run the Radio in new android 6 because currently radio app is installed but it does not work at all
Can i install Android Nougat?
alinazir said:
in the mentioned website there are alot of RUUs
which one should i use. i have downloaded the first one under 0P6BIMG RUUs heading (i.e 0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zi p)
Click to expand...
Click to collapse
I already suggested 6.20.651.3, so I don't know why you are wasting time confusing yourself. If asking for help, please try to read/understand more carefully; instead of asking questions that have already been answere, and making me repeat myself.
6.20.651.3 is the RUU for the "regular" (non-Harmon Kardon) Sprint version. 6.20.654.3 is the Harmon Kardon edition RUU. The only difference is the HK (software) mods. In actuality you can flash either one, since you have SuperCID (11111111). But seeing as your current version is non-HK (3.30.651.2), that is why I picked that one.
4.xx RUUs are Lollipop. Since the goal is to be updated, I would assume you want the latest possible, which is Marshmallow.
zip or exe format RUU is up to you. But for the zip format, you either need an SD card, or know how to use fastboot (and you will need the htc_fastboot instead of the "generic" Google fastboot, which cannot handle the large file size of the RUU).
For exe format, PC is required.
alinazir said:
Also there are alot of Firmwares FUU
1. Modified
2. Modified removed boot and recovery
3. Full
4. Signed Full
which one is better for me please tell me.
Click to expand...
Click to collapse
"Modified" firmware remove either recovery and/or boot.img. The main reason for using a "modified" firmware, is if you want to keep a custom recovery, or the current boot.img (kernel). Neither of those apply in your case.
My recommendation would be to flash the signed full firmware.
alinazir said:
also which one should i install first RUU or FUU?
Click to expand...
Click to collapse
Again, this is a question whose answer I already stated in my previous reply. You need to flash the firmware before flashing the RUU. Otherwise the RUU will fail.
There are 3 different methods for flashing firmware: FUU, SD card method, or fastboot method. Which you use if up to you. But SD card method (obviously) requires an SD card. And fastboot method required you knowing how to use fastboot.
alinazir said:
Another thing will i be able to run the Radio in new android 6 because currently radio app is installed but it does not work at all
Click to expand...
Click to collapse
I don't know. Flash the firmware and RUU and see if the FM radio works.
alinazir said:
Can i install Android Nougat?
Click to expand...
Click to collapse
There is no official HTC Nougat (RUU) for this phone, if that is what you mean.
If you like, you can try a Nougat (or Oreo) based custom ROM after updating the firmware/RUU. But as I previously said, flashing a custom ROM is another process altogether. After flashing the firmware/RUU, you would then need to unlock the bootloader, flash custom recovery TWRP, then flash a Sprint M8 compatible custom ROM of your choice.
Better to take things one step at a time. Update firmware/RUU first. Then go from there, if you like.
redpoint73 said:
I already suggested 6.20.651.3, so I don't know why you are wasting time confusing yourself. If asking for help, please try to read/understand more carefully; instead of asking questions that have already been answere, and making me repeat myself.....
Click to expand...
Click to collapse
Dear i have installed the marshmallow firmware (0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip) from firmware Update Utility FUU. My computer Screen says that the firmware has been installed successfully. My M8 is stuck on the start HTC Logo and on bottom of it powered by android is written . Please help me what should i do now.
alinazir said:
Dear i have installed the marshmallow firmware (0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip) from firmware Update Utility FUU. My computer Screen says that the firmware has been installed successfully. My M8 is stuck on the start HTC Logo and on bottom of it powered by android is written .
Click to expand...
Click to collapse
You are not following instruction properly. You do not flash the RUU using the FUU!
RUU and firmware are two different things!
Flash the firmware (53 MB) first (using FUU, as it seems that is the method you've chosen to flash firmware).
If firmware flash is successful (you may need to flash it twice if you see an error "flush again immediately), then flash the RUU (1.5 GB). Do not use FUU to flash RUU! Since you've chosen the zip format RUU, you need to flash RUU either using htc_fastboot, or SD card method. Otherwise, download and flash RUU in exe format.
redpoint73 said:
You are not following instruction properly. You do not flash the RUU using the FUU!
RUU and firmware are two different things!
Flash the firmware (53 MB) first (using FUU, as it seems that is the method you've chosen to flash firmware).
If firmware flash is successful (you may need to flash it twice if you see an error "flush again immediately), then flash the RUU (1.5 GB). Do not use FUU to flash RUU! Since you've chosen the zip format RUU, you need to flash RUU either using htc_fastboot, or SD card method. Otherwise, download and flash RUU in exe format.
Click to expand...
Click to collapse
Ok my mistake i wrote wrong, i have installed the FUU only the 53mb file and now it is stuck on the logo what should i do? i havn't installed the RUU. Only Firmware is installed. and also when i goto the bootloader it says OS-2.16.254.4 i dont know how did this came from. i copied the Firmware File renamed it to rom.zip and install as stated in the tutorial (6.20.651.3 Signed Full Firmware...(fastboot flashable))
alinazir said:
Ok my mistake i wrote wrong, i have installed the FUU only the 53mb file and now it is stuck on the logo what should i do? i havn't installed the RUU. Only Firmware is installed. and also when i goto the bootloader it says OS-2.16.254.4 i dont know how did this came from. i copied the Firmware File renamed it to rom.zip and install as stated in the tutorial (6.20.651.3 Signed Full Firmware...(fastboot flashable))
Click to expand...
Click to collapse
Stuck on HTC logo after flashing signed firmware is normal and expected, as it expects RUU to be flashed immediately after.
However, the OS number is not normal or expected. It should have changed to 6.20.651.3. I think you mean OS number 2.16.654.4 as there is no version 2.16.254.4 that I know of. Please make sure you type these kinds of number correctly, as they are very important, and telling me the wrong number is extremely confusing!
Check you downloaded the right firmware (6.20.651.3) and flash it again. If you are still getting 2.16.654.4, then the file must be the wrong one. Try the "unsigned Full" firmware 6.20.651.3
redpoint73 said:
Check you downloaded the right firmware (6.20.651.3) and flash it again. If you are still getting 2.16.654.4, then the file must be the wrong one. Try the "unsigned Full" firmware 6.20.651.3
Click to expand...
Click to collapse
how to install the firmware without usb debugging enabled. as i have said that i cannot go to the settings, it is stuck on the logo screen.
yeah thats my bad. its os-2.16.654.4
alinazir said:
how to install the firmware without usb debugging enabled. as i have said that i cannot go to the settings, it is stuck on the logo screen.
Click to expand...
Click to collapse
You flashed the firmware before already, you said (even if it was the wrong one 2.16.654.4). Why would debugging make a difference now, if it didn't before?
Flashing firmware doesn't require debugging. Everything is done by fastboot, not adb. adb needs debugging, fastboot does not.
redpoint73 said:
You flashed the firmware before already, you said (even if it was the wrong one 2.16.654.4). Why would debugging make a difference now, if it didn't before?
Click to expand...
Click to collapse
I have done the firmware with firmware update utility tool. not by fastboot. Can you please guide me how to do it with fastboot?
alinazir said:
I have done the firmware with firmware update utility tool. not by fastboot. Can you please guide me how to do it with fastboot?
Click to expand...
Click to collapse
Doing it with the FUU is fine. The FUU still connects via fastboot, and doesn't need adb, as far as I know.
redpoint73 said:
Doing it with the FUU is fine. The FUU still connects via fastboot, and doesn't need adb, as far as I know.
Click to expand...
Click to collapse
When the program ARUWizard.exe runs it says no device is connected. i used HTC Android Phone Firmware Update Utility 2.0.12.2014
alinazir said:
When the program ARUWizard.exe runs it says no device is connected. i used HTC Android Phone Firmware Update Utility 2.0.12.2014
Click to expand...
Click to collapse
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.
redpoint73 said:
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.
Click to expand...
Click to collapse
The first time i did it wasn't in bootloader. only usb debugging was on and nothing else. phone was on. it is again on the logo screen.
redpoint73 said:
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.
Click to expand...
Click to collapse
OK firmware installed now how would you suggest me to install the RUU?
alinazir said:
The first time i did it wasn't in bootloader. only usb debugging was on and nothing else. phone was on.
Click to expand...
Click to collapse
Honestly, I haven't used the FUU. But if it's the same as RUU, it works in fastboot mode.
Or just try fastboot or SD card methods. The instructions are on the thread you got the firmware from.
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
alinazir said:
OK firmware installed now how would you suggest me to install the RUU?
Click to expand...
Click to collapse
I gave you the options, and the differences between them. Make the decision yourself. I don't even understand why you are asking me this question.
The RUU is similar to the FUU, but even easier. Just download and run it. So that is probably your best bet.
---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------
alinazir said:
OK firmware installed now how would you suggest me to install the RUU?
Click to expand...
Click to collapse
How about explaining what you did different to make it work?
redpoint73 said:
How about explaining what you did different to make it work?
Click to expand...
Click to collapse
Actually i am a newbee i didn't knew that firmware can be updated in fastboot mode. i just did as you told me to do. Now i am installing the RUU from the .exe file. lets see what happens now. Thanks for ur help.
redpoint73 said:
How about explaining what you did different to make it work?
Click to expand...
Click to collapse
Rom Updated Successfully, Now Sprint Logo came and then htc logo, after that the phone turns on, then it got stuck on Hands Free Activation, and keeps on rotating the Activation. and its been half an hour its doing that.
alinazir said:
Rom Updated Successfully, Now Sprint Logo came and then htc logo, after that the phone turns on, then it got stuck on Hands Free Activation, and keeps on rotating the Activation. and its been half an hour its doing that.
Click to expand...
Click to collapse
Forgot about that Sprint Hands Free Activation crap. So you can't get past that, by pressing home, back, or anything like that?