Here's the situation I'm in right now.
My phone is the HTC Desire Eye AT&T Model. I am not rooted, S-Off, Relocked, and on Stock Recovery and Lollipop Rom.
When in Fastboot mode the top of the screen reads:
*** Software status: Modified ***
*** RELOCKED ***
EYE_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.000
[email protected]
OpenDSP-v47.2.2-000564-M8974.1024
OS-2.09.502.3
eMMC-boot 2048MB
Aug 18 2015,20:36:07.0
Some information on how I got in this predicament:
My home internet provider is absolutely cancerous, such that tethering my 4G LTE connection is much faster.
I had an unlocked, S-Off, TWRP installed phone.
I am using T-Mobile right now, and I needed a way to tether my phone, which the phone does not allow through T-Mobile.
I did a Nandroid backup of my phone using TWRP
So, I unlocked the bootloader and installed the Taiwanese Lollipop ROM, then rooted from TWRP. I was now able to tether, and that was good enough for me.
Later, I found that Marshmallow was released. I wanted to receive the Taiwanese OTA update (AT&T could not give me the update, similarly to tethering, on T-Mobile).
I changed the CID to SuperCID. Somehow, I believe using some hex editor method, I changed the MID. However, the update could not be flashed because the Product ID was "eye_ul", which I still could not find out how to change. Even modifying build.prop didn't do anything.
I decided I must have went wrong somewhere, so I decided to start back at square one. This is where things went wrong. After I flashed the original backup I made of my phone, it was no longer rooted. I then proceeded to lock the bootloader, so I not only lost my custom recovery, but the way to flash it back as well. I went back to HTCdev and performed the unlock process, but there was this error described here.
I am aware that EYE_UL_CA is the AT&T product name, CID 11111111 is SuperCID, these two are fine.
However, the Model ID 0PFH20000 is Taiwanese. The original AT&T MID is 0PFH10000, but I don't know how to change it back
When running the command fastboot getvar all here is the information:
{
"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"
}
The unlock token I received was:
<<<< Identifier Token Start >>>>
41235A6270C9338D6B0CDC8783A0B2C8
D647EB5E2F2A2FE7828A885DB6214D97
41E99F77EA8619250FD1367851924861
A46DCD4301228035FD62578DFDC6A843
F79115EC1EBDCFB8AA95BA73F62C0E2A
30F58D5AA67DDA97F91F625099943710
D708BC3BB462F7AD71A70BDC06234766
4E7DE5F4116B1BB2B6FA46C52A72645B
A6416C72CA39E41CAF8031231E3A44CF
D304616C3BD5955DA409654FAF91880B
187F7079B8CBC57EE45714B94B4823AD
265BDFC7D61B32F8357C658DAC24977D
FCD99AB305B23943E2E6678D4B8C3331
5A7A4D997CABD525F6D2BAB1DF241936
C78DF80041A4690031D448A2C462FE9C
7433BF2B54ACC53C10AA8B6F2E71EE48
<<<<< Identifier Token End >>>>>
Then unlock_code.bin file is attached as a txt. When I try to flash it with fastboot flash unlocktoken unlock_code.bin, I get the following error message. FAILED (remote: unlock token check failed).
I read that running the original RUU makes unlocking work again. However, I cannot use it because the device Model ID is still Taiwanese, and I am unsure of how to change it back to the AT&T version.
It's possible that all these problems are because I cannot remember how to change my MID back. fastboot oem writemid is not a command that works on my phone ((bootloader) [ERR] Command error !!!). I remember working with a hex editor to edit some file, but I forgot what it was.
I know it's possible to change the MID back to AT&T because it's impossible to have started out as a Taiwanese MID.
Right now, I can't use my phone to tether, so I am using my incredibly slow home internet to post this. Please Help Me!
Update: I now have root access, and I have reverted the MID back to 0PFH10000. I installed the RUU, but the bootloader still has the same error when I try to unlock it. Please let me know if you are an expert in this error and know how I can unlock my relocked bootloader. Thanks!
Have you tried Windroid software to unlock the bootloader?
netikjoshi98 said:
Have you tried Windroid software to unlock the bootloader?
Click to expand...
Click to collapse
Hey, if you're online, netikjoshi98, I wanted to tell you that Windroid did the job. Thanks!
My bootloader is now unlocked, and I'm ready to install recovery and return everything to normal!
I'll provide details of the recovery steps tomorrow, so that other people with this problem will know how to fix it.
Cheers :good:
Fixing the relocked bootloader (that refuses to unlock)
If you are found in such a tangled kite string as having a relocked bootloader, a modified MID, no custom recovery, no root, and are S-Off so s-off/unlock tools don't work, then these are the steps that I took to fix it.
The general goal here is to run the RUU so u can get the device 100% back to stock, then the HTC unlock will work, or Windroid, or whatever it is that you like to unlock your phone with.
1. obtain root
U need to root without custom recovery, so get some program that can do it from ADB. I did it using KingoRoot, which worked great and I was very happy with the result.
2. Change the MID
follow this person's guide to change the MID: http://forum.xda-developers.com/desire-eye/general/update-to-android-5-0-2-t3081580
you need root to do this that's why the first step was root
you will need the hex editor, and if you are using taiwanese RUU u need to change to taiwan's MID and if you are AT&T or International you need to change to that.
3. Run the RUU
since the MID is now matching your device and CID, you can now run the RUU without a problem, unless you have some other modifications that makes the RUU detect your device as not matching itself.
If you have RUU disappearing problem after clicking accept you are missing some Windows dependency and need to look up which one it is. This step is very easy so I won't provide the links to external sites.
4. Unlock Device
I used Windroid Toolkit as recommended by the helpful person on this post but I believe you can probably also use HTC Unlock now, since the protocol is likely the same.
5. Flash the custom recovery or whatever it is you intended to do with the unlocked bootloader in the first place
I'm glad you found a solution to your problem. And thanks a lot for posting the guide on how you got it fixed. You rock, dude.
Related
Finally got it. One hour fu**ing with a Chinese captcha. Om nom nom...
RUU_Marvel_S_HTC_Europe_2.14.401.1_Radio_47.23e.35.3038M_7.57.39.01M_release_246629_signed.exe
Links:
http://dl.dbank.com/en_US/c05hrf513i
http://dl.dbank.com/c05hrf513i
{
"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"
}
well done.
since hboot 1.09.0099 is included I have the strong feeling this is the last update for the wildfire s
Will post on a faster download site once it eventually gets here. No issues with losing S-OFF?
I'm assuming too that we'll lose bootloader unlock and have to go through the whole update/unlock process again. Am I wrong?
can u plz check if it contains arabic language ?
d33ps1x said:
Will post on a faster download site once it eventually gets here. No issues with losing S-OFF?
Click to expand...
Click to collapse
Nope, I've updated and still s-off.
Although in the bootloader it says locked, it still says ship S-off.
Radio seems to give me better signal.
I can't get this rom rooted though. Apps requiring superuser are denied.
Chinese caparcha
That's crazy.
Sent from a Time Lord, using his TARDIS.
intel007 said:
Nope, I've updated and still s-off.
Although in the bootloader it says locked, it still says ship S-off.
Radio seems to give me better signal.
I can't get this rom rooted though. Apps requiring superuser are denied.
Click to expand...
Click to collapse
you will need to unlock the bootloader again after update
eoghan2t7 said:
you will need to unlock the bootloader again after update
Click to expand...
Click to collapse
But I'm s-off, I've never had any problems with rooting previous stock roms.
I think the updated radio has more security added to it.
Sent from my Wildfire S using xda premium
To root that rom just enter the CWM recovery and install this zip file:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
honda_hany said:
can u plz check if it contains arabic language ?
Click to expand...
Click to collapse
It doesn't contain the arabic language.
Done that but apps were being denied superuser permission.
I'll try the zip that d33psx1 provided and see what happens.
Thanks.
intel007 said:
Done that but apps were being denied superuser permission.
Click to expand...
Click to collapse
Did you use the zip from my post? Some old versions of su don't work but 3.0.7 should.
N00b question - Im not gonna lose S-Off installing this am I?
rezo said:
Did you use the zip from my post? Some old versions of su don't work but 3.0.7 should.
Click to expand...
Click to collapse
Ok I will try, I did download superuser latest version from their website.
Thanks
Ko_Ka said:
N00b question - Im not gonna lose S-Off installing this am I?
Click to expand...
Click to collapse
No you won't lose your s-off mate.
Another noobish question
So I've got:
CWM 5.0.2.8 S-On
HBOOT-1.08.0099
RADIO-7.53.39.03M
How do I update? Do I just install the RUU, and then follow the HTCDev bootloader unlock and then root the phone again or do I need to take any other steps?
ERROR 140 while updating
Hello guys,
i want to update my wfs to get the latest hboot and radio.
i have an unlocked bootloader and hboot 1.08.099 and i'm running the latest cm7.2 version by alquez.
my procedure was to relock my bootloader via fastboot oem lock (to avoid the 155 error) and then i run the ruu.exe (my mobile was in fastboot usb mode all the time and yes i cleared cache etc)
at first everything seems to be fine but when the exe update the signature (or sth like that) the setup aborted with the message "RUU Fehler 140 Bootloader Version" (i'm german.. so fehler <> error)
Does anyone knows how to solve this problem?
Thanks
NQNH
I updated to last ruu and loader says now locked but i have installed super user(rezo provided) and everything is working so i will leave as it is now(even if it says bootlader locked)
NQNH said:
Hello guys,
i want to update my wfs to get the latest hboot and radio.
i have an unlocked bootloader and hboot 1.08.099 and i'm running the latest cm7.2 version by alquez.
my procedure was to relock my bootloader via fastboot oem lock (to avoid the 155 error) and then i run the ruu.exe (my mobile was in fastboot usb mode all the time and yes i cleared cache etc)
at first everything seems to be fine but when the exe update the signature (or sth like that) the setup aborted with the message "RUU Fehler 140 Bootloader Version" (i'm german.. so fehler <> error)
Does anyone knows how to solve this problem?
Thanks
NQNH
Click to expand...
Click to collapse
Hi NQNH
I had the exact same error. This is what you need:
http://forum.xda-developers.com/showthread.php?p=21408713#post21408713
It seems that the "PG7610000_Marvel_hboot_1.08.0099_20111216.exe" you probably had to install to unlock your phone made a change to a version number in your misc.img.
Mine was something like 2.17.0.0 instead of 1.08.0099.
After the RUU failed you will be able to see something like "Main version is older" on the phone's screen (if you get rid of the HTC logo)
can someone extract the radio from that ruu?
I wanted to unlock my DHD's bootloader and flash a custom rom on it with the S-On method which require me to manually flash the boot everytime i flash a rom.
But i was unable to unlock my bootloader due to i was unable to get the identifier token from fastboot... I check on HTC dev website and it require me to upgrade my bootloader, yet again... failed!
I also tried the bootloader unlocking tool and it automatically download PD9810000_Ace_Sense30_S_hboot_2.00.0029 RUU for me and the result also same as the one i downloaded from HTC dev
Here are some pictures:
{
"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 am on HBOOT version 2.00.0027, not sure if it was the latest though
Currently i m using 3.13.707.4
As i know the previous owner did unlock and flash a custom rom on it before, and later he send it back to HTC service centre to flash it back to stock gingerbread
Any help / suggestions are appreciated and welcomed
Should download a RUU and reflash the phone?
did you already tried flashing it with different method...
you can read a guide in here..., this thread guide for htc sensation thread, but the guide is the same as for dhd too (but don't rename it like PG58IMG.zip for DHD..because this name code for sensation only, for DHD just rename it PD98IMG.zip)
just read guide especially at step 4.1 and 4.4, 4.4.1, 4.4.2
hope this help..and good luck..
JJeamy said:
did you already tried flashing it with different method...
you can read a guide in here..., this thread guide for htc sensation thread, but the guide is the same as for dhd too (but don't rename it like PG58IMG.zip for DHD..because this name code for sensation only, for DHD just rename it PD98IMG.zip)
just read guide especially at step 4.1 and 4.4, 4.4.1, 4.4.2
hope this help..and good luck..
Click to expand...
Click to collapse
Thanks for your reply bro... now should i flash the RUU which contains the full ROM or just with the HBOOT?
boonwuilow said:
Thanks for your reply bro... now should i flash the RUU which contains the full ROM or just with the HBOOT?
Click to expand...
Click to collapse
no..you don't needed flashing a full RUU...
just upgrade file firmware / hboot from the htc site that you're already download it..(this is will update it your hboot to version 2.00.0029)
you can try it in two way method..
1. flashing it PD98IMG.zip with fastboot method...
2. flashing it that loaded PD98IMG.zip file via bootloader from your sdcard..
JJeamy said:
no..you don't needed flashing a full RUU...
just upgrade file firmware / hboot from the htc site that you're already download it..(this is will update it your hboot to version 2.00.0029)
you can try it in two way method..
1. flashing it PD98IMG.zip with fastboot method...
2. flashing it that loaded PD98IMG.zip file via bootloader from your sdcard..
Click to expand...
Click to collapse
Ok i will try that later...
So basically the bootloader that can't support HTC dev unlock (or those that require a further update) are those without the "LOCKED" or "RELOCKED" status right?
And is the AAHK2 by Phiber2000 safe to unlock, s-off and root my phone?
http://forum.xda-developers.com/showthread.php?t=2367322
boonwuilow said:
Ok i will try that later...
So basically the bootloader that can't support HTC dev unlock (or those that require a further update) are those without the "LOCKED" or "RELOCKED" status right?
And is the AAHK2 by Phiber2000 safe to unlock, s-off and root my phone?
http://forum.xda-developers.com/showthread.php?t=2367322
Click to expand...
Click to collapse
yap..when htc launching the latest ota update (full RUU for DHD) just had a version of bootloader 2.00.0027, that time the htc itself is not yet officially opening/launching for supporting unlocking the bootloader..because of that..the version 2.00.0027 is not yet support for unlocking..and that's why don't have a state of LOCKED in the top of that bootloader too..so to unlocking you must update bootloader first to 2.00.0029 from that website..
AAHK2 is a simple way to fully rooting and had eng hboot for your DHD...i think that's a safe too..provide it if you follow all step carefully and follow all the rules that are required from that script it self...and because i've already using that script for 6 DHD..all the result is success..even with some of that DHD had some of little troubled while running that script..but i'm still can handle it..
just a advice from me...before you begin running that script..just read carefully and understand it all inside that thread (especially about a branded sdcard that are mentioned in there thread)..and prepared all stuff that are required..
good luck...
boonwuilow said:
I wanted to unlock my DHD's bootloader and flash a custom rom on it with the S-On method which require me to manually flash the boot everytime i flash a rom.
But i was unable to unlock my bootloader due to i was unable to get the identifier token from fastboot... I check on HTC dev website and it require me to upgrade my bootloader, yet again... failed!
I also tried the bootloader unlocking tool and it automatically download PD9810000_Ace_Sense30_S_hboot_2.00.0029 RUU for me and the result also same as the one i downloaded from HTC dev
Here are some pictures:
I am on HBOOT version 2.00.0027, not sure if it was the latest though
Currently i m using 3.13.707.4
As i know the previous owner did unlock and flash a custom rom on it before, and later he send it back to HTC service centre to flash it back to stock gingerbread
Any help / suggestions are appreciated and welcomed
Should download a RUU and reflash the phone?
Click to expand...
Click to collapse
If your build vesion is not supported to update the bootloader, you will need create a goldcard in order to flash a RUU with a build version that supports unlocking. That is the way...takes time and S-OFF is a better option IMO
JJeamy said:
yap..when htc launching the latest ota update (full RUU for DHD) just had a version of bootloader 2.00.0027, that time the htc itself is not yet officially opening/launching for supporting unlocking the bootloader..because of that..the version 2.00.0027 is not yet support for unlocking..and that's why don't have a state of LOCKED in the top of that bootloader too..so to unlocking you must update bootloader first to 2.00.0029 from that website..
AAHK2 is a simple way to fully rooting and had eng hboot for your DHD...i think that's a safe too..provide it if you follow all step carefully and follow all the rules that are required from that script it self...and because i've already using that script for 6 DHD..all the result is success..even with some of that DHD had some of little troubled while running that script..but i'm still can handle it..
just a advice from me...before you begin running that script..just read carefully and understand it all inside that thread (especially about a branded sdcard that are mentioned in there thread)..and prepared all stuff that are required..
good luck...
Click to expand...
Click to collapse
glevitan said:
If your build vesion is not supported to update the bootloader, you will need create a goldcard in order to flash a RUU with a build version that supports unlocking. That is the way...takes time and S-OFF is a better option IMO
Click to expand...
Click to collapse
I have successfully unlock the bootloader by the method @JJeamy show me, thank you very much for guiding me on how to unlock it :good::good::good:
Actually the process isn't very hard just go to HTC dev and download the bootloader that match your build number and manually flash the update by using fastboot and proceed to unlock the phone as instructed on htc dev
boonwuilow said:
I have successfully unlock the bootloader by the method @JJeamy show me, thank you very much for guiding me on how to unlock it :good::good::good:
Actually the process isn't very hard just go to HTC dev and download the bootloader that match your build number and manually flash the update by using fastboot and proceed to unlock the phone as instructed on htc dev
Click to expand...
Click to collapse
glad to hear that...and congrats.. :good:
Awesome
@JJeamy
I'm proud that you wrote that much,if i was in your place i would only redirects @boonwuilow to that chinese software the one i told you easy way to unlock bootloader.
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
Ok so I posted in another thread where I was trying to flash a custom but a few things went wrong but help has been slow there so I thought it may be better to post here.
I got MM through OTA updates, this was when my M9 was bootloader LOCKED, not custom recovery, everything stock. After I was on MM for a few days I used htcdev.com to unlock the bootloader, then I got TWRP 3.0.0 and then I got SuperSU 2.65 and installed it through TWRP. Before installing SuperSU I made a backup through TWRP of Boot, System and Data. I copied this backup to my computer as well. At this point this is the current information on the M9 (Look at 3 attached screenshots as well):
kernel: lk
product: htc_himaulatt
version: 1.0
version-main: 3.38.1500.2
boot-mode: download
version-baseband: 01.01_U11440801_96.01.51207G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: GLOBA001
So after creating the backup, I installed SuperSU 2.65, then booted up the phone, everythings fine. So I went back to TWRP and installed Android Revolution HD 20.0 (had it on an sd card) and used the wipe data option it gives before installing. So after a long time of optimizing apps the phone boots up and starts the setup. I got to entering google account information and it asked for 2 step verification which sends a code to my phone number, but I then noticed I had no signal and it said No Service so I couldn't sign in to Google and had to skip that. After the rest of the setup I popped out the SIM and put it back, still nothing (keep in mind the SIM is locked with a pin if that affects anything, but it never even asked for the pin).
Now I go to Accounts and try adding my google account but the phone gets stuck at checking info... and while i can use the rest of the phone there is no way for me to sign into any google account now because every attempt results in checking info loop. I tried to reboot the phone multiple times but that did nothing. Last thing to note is that when i went to Settings -> About, there was no IMEI number as well as other information about the phone was missing so something went wrong for sure.
After that I restored from the TWRP backup and its back to normal, SIM working, Google acc working, all that is good like it was before. So any suggestions on how to get ARHD 20 now? I noticed that since I'm on 3.38.1500.2 which is higher than the firmware that ARHD uses, maybe that is the problem since I'm essentially downgrading the firmware right? I read that you can't downgrade firmware unless you are S-off but my M9 is S-on. All help is appreciated
{
"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"
}
Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yea SuperSU 2.65 I understand but I heard 2.9.1.2 is quite stable? You don't agree?
Not tried it. I just flashed 2.9.0.1 and stuck with it because it boots. Beggars can't be choosers and a working phone is better than a broken one.
Sent from my HTC One M9 using Tapatalk
Just wanna update my situation as it is resolved and the solution: S-OFF
I was on 3.38 with twrp 3.0 and SuperSU 2.65 and flashing ARHD 20.0 (which is on 3.35) was messed up as my SIM card wasn't working and signing into Google account was not working.
I restored my nandroid backup, installed SuperSU 2.65 again and then bought S-OFF, which allowed me to change my cid to HTC__001 and mid to 0PJA10000. Next i flashed a nandroid that someone uploaded of 3.35.401.12 and once that was done I flashed ARHD 20.0 and boom its done. Basically from what I understand you can't flash ARHD 20.0 if the firmware you are on is lower (i failed to go from 3.38 to 3.35). Also my SKU was 1500 but ARHD is 401 so that might be a factor as well. So yea S-OFF is great
Future Note.
Always try to stick with the general update the ROM is based off of. The System partition in STOCK/CUSTOM roms have a firmware folder that have drivers and config files that are meant to be used with the firmware.zip originally in that update.
For example (not real sw numbers)
HTC releases an official update 3.40.1540.1
3.40.XXXX.X is generally the base while X.XX.1540.1 is any software mods made by carriers or specific region teams. Firmware Updates (Radio Baseband, TouchScreen Driver, etc) are released along side the actual Android/HTC software. These official ROMS have config files that are design around this new firmware. When developers here on XDA make custom roms they are in a weird XDA way a carrier (3.40.ARHD.1 etc). They modify the HTC rom and make it their own, but their roms are still based off that firmware update.
So if you start using a custom rom based off 3.40, but the last firmware your phone installed is 3.10. You will run into issues and they might be small (less battery life or cell signal) or pretty big. Your sim not working, or wifi, or any number of issues. Stick to ROMS based off the firmware you have on your phone. Or if youre S-OFF and want to take that ever present risk. Update your firmware to that newer version.
Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?
ig88b1 said:
Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?
Click to expand...
Click to collapse
Yea if you go to settings -> about -> software information it should say your firmware version. If your version is NOT 3.35 you'll get this problem, here are the nandroid files, you only need the 3.35 one but if I understand correctly restoring from this nandroid might make you lose all data. https://www.androidfilehost.com/?w=files&flid=48820
ALSO that nandroid is for 401 SKU which is HTC WWE, so if you're locked to tmobile i dont know how that'll affect you so dont just restore to that nandroid.
And yea i changed my CID and MID : (idk if you know but you need extra files on your pc to run the following commands from pc)
fastboot oem writecid HTC__001
fastboot oem writemid 0PJA10000
fastboot reboot
I did this right before the nandroid restore and everything turned out fine.
Awesome man thanks so much! that nandroid took care of it, couldn't find one.
ig88b1 said:
Awesome man thanks so much! that nandroid took care of it, couldn't find one.
Click to expand...
Click to collapse
Glad I could help
hello to all friends of XDA.
im not new but i lost my old email. :silly:
i have a htc one m8s thats stuck in bootloader with os version 1.21.111.1 from T-mobile DE.
the problem is that i try to flash the unlock token, flashing the file, i select accept on the screen phone but when the phone restarts the booloader is still locked.
i try to flash a stock recovery (not the same as the os version, because i didnt find it) but it still doesnt work.
i try ti find the last ruu or stock rom version 1.21.111.1 or even the firmware but i didnt find it.
however when i try to boot to RUU mode it doesnt reboot in RUU mode.
i try every steep with the new htc_fastboot. but i dont use the md5 verification or any md5 file (because i dont know how)
i would like to have the phone working even with Lineage os or something like.
please if someone can help me please let me know the steeps.
best regards to all and thanks in advance
{
"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"
}
htc one m8 , i see on twrp says All variants , gsm i think also SO this means any htc m8 will take twrp right ?? any model or carrier ect ??
wanna buy this phone only if twrp good to go and root
Htc one m8s
Joeykatie said:
htc one m8 , i see on twrp says All variants , gsm i think also SO this means any htc m8 will take twrp right ?? any model or carrier ect ??
Htc one m8s is not the same as m8 you cant apply this version of twrp , just dl and flash it in the thread below, and then flash supersu and you will get root and twrp
https://forum.xda-developers.com/ht...ral/make-custom-recovery-htc-one-m8s-t3114245
Click to expand...
Click to collapse
I think I can help
klevisi said:
hello to all friends of XDA.
im not new but i lost my old email. :silly:
i have a htc one m8s thats stuck in bootloader with os version 1.21.111.1 from T-mobile DE.
the problem is that i try to flash the unlock token, flashing the file, i select accept on the screen phone but when the phone restarts the booloader is still locked.
i try to flash a stock recovery (not the same as the os version, because i didnt find it) but it still doesnt work.
i try ti find the last ruu or stock rom version 1.21.111.1 or even the firmware but i didnt find it.
however when i try to boot to RUU mode it doesnt reboot in RUU mode.
i try every steep with the new htc_fastboot. but i dont use the md5 verification or any md5 file (because i dont know how)
i would like to have the phone working even with Lineage os or something like.
please if someone can help me please let me know the steeps.
best regards to all and thanks in advance
Click to expand...
Click to collapse
Did you get the phone in a locked, or unlocked state?
If locked, did you use Sunshine or a HTC unlock (the former option costs $$ and I would't recommend fabricated keys as they can break the device).
T-Mobile DE - a german version of the phone, or US version with German settings?
To reboot in RUU, you'll need to do so through ADB, while connected to a computer.
In order to run RUU, you actually have to re-lock the bootloader if it's unlocked. You also need to disable SuperCID, if it is enabled.
Do you have any more details? I was going to suggest a website that @graffixnyc used to keep updates on, but I don't see the list of files there anymore.
I bought mine three years ago and I feel bad that your outcome is like this.
furboom1240 said:
Did you get the phone in a locked, or unlocked state?
If locked, did you use Sunshine or a HTC unlock (the former option costs $$ and I would't recommend fabricated keys as they can break the device).
T-Mobile DE - a german version of the phone, or US version with German settings?
To reboot in RUU, you'll need to do so through ADB, while connected to a computer.
In order to run RUU, you actually have to re-lock the bootloader if it's unlocked. You also need to disable SuperCID, if it is enabled.
Do you have any more details? I was going to suggest a website that @graffixnyc used to keep updates on, but I don't see the list of files there anymore.
I bought mine three years ago and I feel bad that your outcome is like this.
Click to expand...
Click to collapse
The files are still there, they are just under Development Portfolio -> XDA Development Work -> Rom Development. http://graffixnyc.com/m8.php