Develop Bugs

HTC restricting those with s-off?

I was lucky enough to have a s-off/supercid unit, was previously on a carrier ROM then flashed the 1.29.401.7 RUU. So today I see .11 has been released OTA and go to update. It downloads fine, verifies the update then this
{
"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"
}
I've tried it three times upon three reboots and same message. I'm not sure if it is HTCDev unlocked but it isn't rooted
Have any other s-off owners encountered this? If not, then move along and ignore me...

Where did you get an s-off/supercid handset from?

farnsbarns said:
Where did you get an s-off/supercid handset from?
Click to expand...
Click to collapse
Basically got a pre-retail unit from a local carrier

P1n3apqlExpr3ss said:
Basically got a pre-retail unit from a local carrier
Click to expand...
Click to collapse
How did you wangle that? Did they send it by mistake?

farnsbarns said:
How did you wangle that? Did they send it by mistake?
Click to expand...
Click to collapse
Got chosen to write a series of posts about the One X for a blog sponsored by the carrier, part of that is a free phone. Oh and I'm sure the fact we got it a week or two ahead of the local launch helped as well

Might be best you stop trying to do any updates bro, and make yourself known to the good folks in this thread
http://forum.xda-developers.com/showthread.php?t=1604300
PS, can you post screen shot of your fastboot screen??

777ace said:
Might be best you stop trying to do any updates bro, and make yourself known to the good folks in this thread
http://forum.xda-developers.com/showthread.php?t=1604300
PS, can you post screen shot of your fastboot screen??
Click to expand...
Click to collapse
Posted in that thread many times offering any help, noticed a post in there replying to another guy with s-off and apparently we're not much help anyway

I see. All good, just thought you might have held the holy grail...
Actually, you could be of help. Send me your phone and I'll send mine, that'd be a HUGE help!!

Well the thing is. Your phone maybe SuperCID but the SN still belongs to a branded phone. Maybe this makes the confusen... Just wait for the full RUU and flash that one.

Hmz, just checked the firmware.zip and seen this command: erasebcid: 1
NVM, this command is also present in older OTA.

xmoo said:
Well the thing is. Your phone maybe SuperCID but the SN still belongs to a branded phone. Maybe this makes the confusen... Just wait for the full RUU and flash that one.
Click to expand...
Click to collapse
What do you mean by SN?
Going to try and get someone I know to try and replicate it, s-off with Asia unlocked unit

Just got this reply from HTC. Firstly I am not rooted (at least last time I checked). Secondly I am going to check whether it is HTCDev unlocked when I get home. Does being HTCDev unlocked mean I cannot get OTA updates?
Thanks for contacting HTC.
We understand that you have some concern with regard to updating your phone’s software. Please allow us to discuss your concern and assist you.
HTC manufactures each Android phone to the exact specifications as set by Google, the platform’s developer. The partner mobile operators who distribute a said phone model then customize the software for use in their respective networks. This is why the phone’s warranty is automatically void if the default phone software has been modified in any way.
Based on your email, you have rooted your phone and installed custom or modified software. In this case, please understand that you will not be able to receive or install the latest software that will be release by your dealer. Any updates you will be receiving will come from the developer of the modified software. If you want to update your HTC One X software, please contact the developer of the European RUU.
The only way you can restore the phone’s original software is to go through your dealer where you purchased the phone or its authorized service center and have it reinstalled for a fee. This is needed so you can download and install the latest software released by your dealer. Please be advised that according to the dealer’s terms and conditions, any modification to the default phone software automatically voids the warranty. However, if you have the software reinstalled by an authorized service center, you will still have a shorter service warranty in effect (the standard warranty being already voided).
Important: Please be advised that HTC distributes handsets through our partner mobile operators which we have contracts with. Our partner mobile operators also determine the software and specifications for the particular handset model they are distributing. Any queries regarding repair, assessments, replacements, upgrades and warranty claims are best discussed with your authorized dealer. Please be reminded to back up your phone’s data before going to your dealer.
Click to expand...
Click to collapse

P1n3apqlExpr3ss said:
Just got this reply from HTC. Firstly I am not rooted (at least last time I checked). Secondly I am going to check whether it is HTCDev unlocked when I get home. Does being HTCDev unlocked mean I cannot get OTA updates?
Click to expand...
Click to collapse
No, it does not.
Sent from my HTC One X using xda premium

^ Thought that might be the case. I am locked and I am not rooted, yet this occurs.
Plus my reply to HTC's above message ^^^
Hi,
In reply to your reply... my One X is s-off/SuperCID, meaning I can flash whatever RUU I wish and it should get OTA updates for that region, as it did (except it fails). As far as I am concerned there is no trace on the phone linking it back to Telecom NZ at all, except possibly the IMEI - does this affect the installation of OTA updates?
I have not HTCDev unlocked, nor rooted the phone. It is merely s-off, thanks to HTC most likely. Within the bootloader it says I am locked, not unlocked or relocked, and apps like superuser or mybackup root do not work - as expected. The 1.29.401.7 RUU is signed by HTC and comes from HTC themselves, it isn't something from a custom ROM developer, the RUU I ran - and currently have on my phone - is 100% stock Android 4/Sense 4.0.
What I am trying to say, I effectively have an unlocked European One X (that is s-off) yet fails to install European OTAs because apparently I have "modified software". Doesn't sound right if you ask me.
Cheers
Click to expand...
Click to collapse

You're emailing first line support at HTC, who probably have NO idea what being S-OFF is, and are just going to give you a generic answer to anything you send them. Don't waste your time
You said you changed your CID to HTC__001 in a past post - have you changed it back to Super CID? If not, do it and try again
Otherwise, just flash the RUU. And for the record there's someone in the UK with an S-OFF handset who got .11 OTA with no issues (and has never changed the CID at any point)

According to CIDGetter I am still SuperCID, scrolling down to ro.aa.maincid is HTC_001, the update region I presume, so I have no need to change it back to SuperCID
Would really prefer update OTA (or flash the update.zip, how do I do this? Im sure I've downloaded it enough times) since I can't be bothered unlocking and rooting for titanium backup
Good to hear it's perhaps just me then

You don't need to unlock to backup, there's a thread in general on how to do it via adb

Cheers for the tip, forgot about that
As for the guy that did manage to update, was he originally HTC_001 (update region) anyway? I still haven't ruled out that carrier and asia phones will have trouble once s-off is achieved, they flash the EU RUU and expect OTA updates only to get the same problem as me

Nope, he's never touched it so it was always 11111111 - the ro.aa.maincid is irrelevent as it's not the CID
Try this:
1. Connect in fastboot
2. Run 'fastboot getvar cid' and see what comes up
If it's 11111111 you have Super CID, if it's HTC_001 it's not a real CID, if it's HTC__001 then you have the unbranded EU CID

P1n3apqlExpr3ss said:
According to CIDGetter I am still SuperCID, scrolling down to ro.aa.maincid is HTC_001, the update region I presume, so I have no need to change it back to SuperCID
Would really prefer update OTA (or flash the update.zip, how do I do this? Im sure I've downloaded it enough times) since I can't be bothered unlocking and rooting for titanium backup
Good to hear it's perhaps just me then
Click to expand...
Click to collapse
Think it's meant to be HTC__001 not HTC_001 ie 2 underscores.
Maybe this could be the reason?

Can't install ROM or update

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

[SOLVED]Friend messed up his phone-gave it to me to fix-seems to be stuck in fastboot

Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"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"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.

eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.

Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....

eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.

All is well, got the running properly now - thanks everyone!

eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems

Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.

xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs

Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").

How can convert my Htc M9 HimaWhl to HimaUhl?

I want convert my M9 Hima_Whl Sprint To Other version,developer editio for example,but cant flash any RUU because flash failed,i have unlocked bootloader and S-Off Supercid.
I want recover my phone trying flashing other RUU,because im make downgrade from 7.0 to 6.0 and get "Unknow Imei And Baseband" and cant make calls o send sms.
{
"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"
}
PD.My M9 its rare,because this version is not for sale,its a prototype device,but its functional.

In short, you can not. Attempting to use any firmware not made specifically for a CDMA model (like yours) will almost certainly damage your phone, possibly irreparably.
You can read about the why of this in the readme thread, particularly in device conversion section (post #4) and RUU section (post #5).

computerslayer said:
In short, you can not. Attempting to use any firmware not made specifically for a CDMA model (like yours) will almost certainly damage your phone, possibly irreparably.
You can read about the why of this in the readme thread, particularly in device conversion section (post #4) and RUU section (post #5).
Click to expand...
Click to collapse
Thanks a lot....But,can help me to repair imei and baseband? or can put a link for a thread for repair this error? only want recover my device.

Panzer_88 said:
Thanks a lot....But,can help me to repair imei and baseband? or can put a link for a thread for repair this error? only want recover my device.
Click to expand...
Click to collapse
Hmm. Let's put a hold on flashing anything until we understand what has been done. Could you walk through the steps of what you've done with your phone?
- what is the current state (bootloader locked/unlocked, S-ON/S-OFF, rooted/unrooted, OS/firmware version)?
- what is the current CID & MID?

computerslayer said:
Hmm. Let's put a hold on flashing anything until we understand what has been done. Could you walk through the steps of what you've done with your phone?
- what is the current state (bootloader locked/unlocked, S-ON/S-OFF, rooted/unrooted, OS/firmware version)?
- what is the current CID & MID?
Click to expand...
Click to collapse
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000

Panzer_88 said:
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000
Click to expand...
Click to collapse
Okay, so you need to read the readme thoroughly, specifically the first five posts. Yes, it's a lot. Yes, it's worth spending the 1/2 hour to familiarize yourself with what you're doing.
Essentially your only hope is to try to restore your phone to stock. You are fortunate in that there is a RUU executable (not zip file, though you could follow the instructions later in the readme thread to create your own) provided for your device from Sprint.
In it's current state - with the CID and MID combination you have - the RUU executable will not recognize your phone as compatible and will refuse to install. You'll need to change the CID to match your SKU (651) in order to apply the RUU.
Since you've attempted to flash an incompatible RUU, this may not fix your phone. But it's your only shot, short of paying someone to take a look at your phone (see the readme thread).
---------- Post added at 12:46 AM ---------- Previous post was at 12:26 AM ----------
I've gone ahead and extracted the RUU zip from the Sprint RUU executable. I'm happy to share the file with you from my Google drive (I'm uploading now) - but in the meantime I'd like to re-iterate my exhortation to read through at least the first five posts of the readme thread.

Panzer_88 said:
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000
Click to expand...
Click to collapse
Supercid is no longer recognised. You MUST use a proper cid with a matching mid.
To update to nougat you will probably need to reset back to stock and take the ota if it exists. Be very careful about flashing firmware and roms. CDMA phones may not agree with gsm firmware and roms.
Beamed in by telepathy.

shivadow said:
Supercid is no longer recognised. You MUST use a proper cid with a matching mid.
To update to nougat you will probably need to reset back to stock and take the ota if it exists. Be very careful about flashing firmware and roms. CDMA phones may not agree with gsm firmware and roms.
Beamed in by telepathy.
Click to expand...
Click to collapse
I change te cid to the original,can flash the ruu,all process ok,but can recover the baseband and the imei!
Im try with fastboot getvar all and can see the baseband and imei its ok,but in the device say Unknow

computerslayer said:
Okay, so you need to read the readme thoroughly, specifically the first five posts. Yes, it's a lot. Yes, it's worth spending the 1/2 hour to familiarize yourself with what you're doing.
Essentially your only hope is to try to restore your phone to stock. You are fortunate in that there is a RUU executable (not zip file, though you could follow the instructions later in the readme thread to create your own) provided for your device from Sprint.
In it's current state - with the CID and MID combination you have - the RUU executable will not recognize your phone as compatible and will refuse to install. You'll need to change the CID to match your SKU (651) in order to apply the RUU.
Since you've attempted to flash an incompatible RUU, this may not fix your phone. But it's your only shot, short of paying someone to take a look at your phone (see the readme thread).
---------- Post added at 12:46 AM ---------- Previous post was at 12:26 AM ----------
I've gone ahead and extracted the RUU zip from the Sprint RUU executable. I'm happy to share the file with you from my Google drive (I'm uploading now) - but in the meantime I'd like to re-iterate my exhortation to read through at least the first five posts of the readme thread.
Click to expand...
Click to collapse
Im changed to original cid and flashed the ruu again,but cant recover the imei and baseband...With fastboot getvar all can see the imei and base and its ok...
Mmm....One friend have another M9 same of my phone,its the same(M9 Prototype) Can dump all system Rom from this phone? Same device HimaWhl and its updated to android 7.0 and work fine.

Another thing.
Have a battery drain and overheated device after to downgrade.

Tmobile: Relocked: S-ON: Stuck in bootloaded

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!!!!!