this text is on the phone's screen.
This build is for development purpose only Do not distribute outside of HTC without HTC's written permission failurwe to comply may lead to legal action.
UNLOCKED
htc_hiaeuhl PVT S-ON
LK-1.0.1.000
[email protected]
Opendsp-5.12.2.00204-8952_1213
OS-2.17.401.2
fastboot devices HT617BE63849
fastboot oem readcid HTC-034
fastboot oem readmid 2PQ910000
htc download mode
security warning
ıf you flash this phone with any ROM that was not officially released by HTC you take the risk of relesingyour personal and finalcial information to unknown sources.
help me
what kind of help you need ????
Appears to have flashed twrp recovery... That's standard message after changing either boot image or recovery image.... No way to remove that message on the A9
this message appears on the phone screen and the phone is not turned on
Wonders_Never_Cease said:
Appears to have flashed twrp recovery... That's standard message after changing either boot image or recovery image.... No way to remove that message on the A9
Click to expand...
Click to collapse
I don't care about the message, but I believe it is possible to use stock boot and recovery with magisk v14. and the message should not appear in that case. True?
alperr38 said:
this message appears on the phone screen and the phone is not turned on
Click to expand...
Click to collapse
These messages are not a concern, you won't have any legal issues neither be compromising your financial information. Just the standard disclaimer that you'll find on all HTC phones when flashing unsigned images.
If device is powered off and message is still on screen as stated... Id try flashing the official RUU for your region and see if it disappears...If still on screen when phone is powered off... I'd look into an rma
Variant System Version
damncut said:
what kind of help you need ????
Click to expand...
Click to collapse
Hi bro, My HTC A9 has a system update but when i update it, after downloading the setup it tells that "We have determined that your phone may be running a modified version of its system software. For your protection , we cannot update your phone. Please revert your phone to the official HTC system software to update your phone."
Tell me the sollution sir..
Thank You!
Ata Jalani said:
Hi bro, My HTC A9 has a system update but when i update it, after downloading the setup it tells that "We have determined that your phone may be running a modified version of its system software. For your protection , we cannot update your phone. Please revert your phone to the official HTC system software to update your phone."
Tell me the sollution sir..
Thank You!
Click to expand...
Click to collapse
Your MID doesn't match your software version. Either you changed your MID or you flashed a stock rom not matching yours.
Related
Hi!!
I just got a Desire S, i' am new to rooting... so i need to know whether i can go back to the stock ROM (2.3.3 with sense 2.1) after i root the device.
This is the only dilemma holding me back from rooting my desire s.
Thank you for your Time! : )
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
rusor123 said:
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
Click to expand...
Click to collapse
Let me guess - when you power on your device you have the T-Mobile logo
Your current software version is higher then the T-Mobile RUU provided here (RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_3 8.03.02.11_M_release), so to restore Stock you will have to downgrade and then update via the Software actualization option in your settings (if such OTA is available) to return it to the current state. This is more tricky process, that can be done flawlessly if your device is healthy. But if you get in trouble and some system components are not responding (brick, bootloop) there is a great change that you will be not able to S-ON again. Happened to a lot of branded devices, reported here.
So my advice is to keep using it that way - it is still a great phone even with Stock software. You can S-OFF and root it of course at your own risk.
It is up to you
Dude you are right man... the T-mobile sign does come up, thanks for the heads up, appreciate it... don't want to brick ma phone... i' ll keep using it this way.
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
rusor123 said:
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
Click to expand...
Click to collapse
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
thnx!!!!!!!!!!!
amidabuddha said:
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
Click to expand...
Click to collapse
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
rusor123 said:
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
Click to expand...
Click to collapse
Yes you should receive the update, because the update check from your phone settings is made on a central server (both on WiFi and Mobile data, the phone connects to the same place in the Internet)
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
hey im kinda a noob so what u said means i can or not, i have a desire s and i cant wait for the sense 3.0 update so if i download a custom rom for now, and when the official update comes in my region can i go back to the stock android then update it normally??????
Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed
http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.
Link does not work:
Sorry - no matches. Please try some different terms.
I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?
Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S
I have tried few others RUU and every single of them is falling during the installation.
ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?
So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab
I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.
Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.
I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.
I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.
i for one don't believe this
So their replay is bull**** in that case?
In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.
So i will try through HTC Clip in that case. But why I can upload any new RUU?
like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.
help!!!!!!!!!!!!
kindly let me know if I can install RUU_ACCORD_U_APO_00_HTC_Europe_2.00.401.03_1.11b.3 2.19.23_2_15.42.32_RETAIL_ENC_RELEASE.exe
in my HTC T-MOBILE DE 8X with CID MOB-001?
bootloader (175731)
I await response. thanks
priologiacomo said:
help!!!!!!!!!!!!
kindly let me know if I can install RUU_ACCORD_U_APO_00_HTC_Europe_2.00.401.03_1.11b.3 2.19.23_2_15.42.32_RETAIL_ENC_RELEASE.exe
in my HTC T-MOBILE DE 8X with CID MOB-001?
bootloader (175731)
I await response. thanks
Click to expand...
Click to collapse
Based on your bootloader version, I don't think you can, but I might be wrong.
What Windows Phone version are you running?
As of yet, there's no way to flash an RUU version 2.00.401.03 on a phone that has a greater version installed (if you've installed any updates, you'll have a greater version).
IF you could flash, you would first need to debrand your phone first (search for ACDU fix for that), since the RUUs that have been released are straight from HTC, with no carrier modifications and they would fail to flash on a branded phone.
Potis20 said:
Based on your bootloader version, I don't think you can, but I might be wrong.
What Windows Phone version are you running?
As of yet, there's no way to flash an RUU version 2.00.401.03 on a phone that has a greater version installed (if you've installed any updates, you'll have a greater version).
IF you could flash, you would first need to debrand your phone first (search for ACDU fix for that), since the RUUs that have been released are straight from HTC, with no carrier modifications and they would fail to flash on a branded phone.
Click to expand...
Click to collapse
ok this is the situation. I wanted to know if it was possible to install the rom suitable to remove the logo T-MOBILE and have the cid 11111111
thanks await response.
priologiacomo said:
ok this is the situation. I wanted to know if it was possible to install the rom suitable to remove the logo T-MOBILE and have the cid 11111111
thanks await response.
Click to expand...
Click to collapse
From what I've read as far as flashing goes, the operation is a no-go because the OS version is too high and it would cause the flashing progress to stop at the error message "Image version less than..". Do not attempt it since you'll be left with a brick.
Potis20 said:
From what I've read as far as flashing goes, the operation is a no-go because the OS version is too high and it would cause the flashing progress to stop at the error message "Image version less than..". Do not attempt it since you'll be left with a brick.
Click to expand...
Click to collapse
ok thanks more.
Potis20 said:
From what I've read as far as flashing goes, the operation is a no-go because the OS version is too high and it would cause the flashing progress to stop at the error message "Image version less than..". Do not attempt it since you'll be left with a brick.
Click to expand...
Click to collapse
I pm xboxmod and he told me tried to flash uefi.nbh until got uefi error.But I tried all the nbh I could find on the Internet,failed.Now,no one knows how to disable OS version check except htc
fengsam said:
I pm xboxmod and he told me tried to flash uefi.nbh until got uefi error.But I tried all the nbh I could find on the Internet,failed.Now,no one knows how to disable OS version check except htc
Click to expand...
Click to collapse
Have you tried the nbh in the ACDU fix? That one caused my device to show a uefi provision error.
Potis20 said:
Have you tried the nbh in the ACDU fix? That one caused my device to show a uefi provision error.
Click to expand...
Click to collapse
That key.nbh?I tried just say 'Image version less than Device version''
fengsam said:
That key.nbh?I tried just say 'Image version less than Device version''
Click to expand...
Click to collapse
Hmm, I guess whatever that nbh flashes has been updated.
I can't understand why they decided to have that check in place... if I flash a stock RUU, it shouldn't matter what was previously running on the device, it should flash everything back to stock. Why do they make this so user un-friendly?
Potis20 said:
Hmm, I guess whatever that nbh flashes has been updated.
I can't understand why they decided to have that check in place... if I flash a stock RUU, it shouldn't matter what was previously running on the device, it should flash everything back to stock. Why do they make this so user un-friendly?
Click to expand...
Click to collapse
yep,but htc8s don't have this check.In China,someone leaks the official gdr3 ruu for htc c620d(cdma) to repair the bricked phone.My phone is security unlocked,so I tried it,failed.
HI all !
I have the same problem i can't use my phone and i can't downgrade it.
PM232002 P S WP I
SBL1-1.0.21009.0
SBL2-1.0.21009.0
SBL3-1.0.21009.0
RPM-1.1.03078.0
TZ-303.000.241
UEFI -0.0.3030.0(175731)
OS-4.12.401.01
eMMC SMS 14910 MB F-15
CID-HTC_032
Radio-1.20b.32.19.04_15.67b.32.19
MSM8260A v 3.2.1-p1
If i try use RUU.exe phone reboot on 1% and i had error 270
If i try to use Y-connector i have error what my version is higher , or this error DongLeFail:CheckDeviceImage Signature Error.
Can you help me ?
Thanks
Hi
I can't find stock rom for my htc u11
Ocndugl0401 model.
Someone knows where to download?
Thank you
yossim66 said:
Hi
I can't find stock rom for my htc u11
Ocndugl0401 model.
Someone knows where to download?
Thank you
Click to expand...
Click to collapse
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Sent from my HTC U11 using Tapatalk
speeddemon1891 said:
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Click to expand...
Click to collapse
Hi
I saw that page before but didn't find htc_0401
Thank you
You mix up software version (401) with CID.
You can check your CID with "Simple CID Getter" on the Play Store.
kurtschmeichel said:
You mix up software version (401) with CID.
You can check your CID with "Simple CID Getter" on the Play Store.
Click to expand...
Click to collapse
You right, i get cid_060.
I download the ruu.
Thank you
https://androidfilehost.com/?
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------
Hi this is linked for all ruu frimwork
Sorry
This link
https://androidfilehost.com/?a=show&w=files&flid=183767
There are any ota and ruu and frimwork
This thread may help.
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page99
mehrdad_esmaeeli said:
https://androidfilehost.com/?
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------
Hi this is linked for all ruu frimwork
Sorry
This link
https://androidfilehost.com/?a=show&w=files&flid=183767
There are any ota and ruu and frimwork
Click to expand...
Click to collapse
همش غیر فعاله
Hi everyone
Customer brought a phone to me to repair as they have bricked it with a custom rom, then deleted the system & recovery, then did the absolute unthinkable and relocked the bootloader i was told,
The os version is still there however when the device is booted with the power button a message appears with the device is corrupt and cannot be trusted and will not boot,
I cannot find a working stock HTC signed ruu.exe for this model & have downloaded the correct packages for the model and cid but it returns 9ruu security error zip from usb command, system also shows as modified in bootloader aswell.
This is what i am working with
Fastboot oem readmid returned 2PZC10000
Fastboot oem readcid returned htc_039
I cannot go supercid 11111111 with fastboot oem writecid11111111 as it return as not allowed
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
i cannot boot to any recovery
I cannot obtain the identifier tokken as it displays killswitch enabled on the 3 options and i cannot flash the original unlock_code.bin that was provided on the thumb drive with the phone and also return not allowed on production build also
I have tried the following commands trying to flash the OTA's and also the firmware
Fastboot flash all <zip>
Fastboot flash <zip>
Fastboot flash zip <zip>
Fastboot update <zip>
All fail with some error
and also used htc_fastboot, minimal adb and fastboot 1.7msi & also power shell im using windows 8 also but no matter what i do cannot get anything to flash to the customers phone i downloaded the OTA's & firmware from the google spreadsheet i dont know what im doing wrong and the only RUU.exe i do have for htc_ocnuhl returns an error with incorrect model id please use the correct update utility,
What should i do tell him his phone is kaput or ?? Ive been at this 3 days now ive been working on phones for 10 years nothing takes 3 days !!!!!!
Any help would be greatly appreciated
Matty1993 said:
Hi everyone
Customer brought a phone to me to repair as they have bricked it with a custom rom, then deleted the system & recovery, then did the absolute unthinkable and relocked the bootloader i was told,
The os version is still there however when the device is booted with the power button a message appears with the device is corrupt and cannot be trusted and will not boot,
I cannot find a working stock HTC signed ruu.exe for this model & have downloaded the correct packages for the model and cid but it returns 9ruu security error zip from usb command, system also shows as modified in bootloader aswell.
This is what i am working with
Fastboot oem readmid returned 2PZC10000
Fastboot oem readcid returned htc_039
I cannot go supercid 11111111 with fastboot oem writecid11111111 as it return as not allowed
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
i cannot boot to any recovery
I cannot obtain the identifier tokken as it displays killswitch enabled on the 3 options and i cannot flash the original unlock_code.bin that was provided on the thumb drive with the phone and also return not allowed on production build also
I have tried the following commands trying to flash the OTA's and also the firmware
Fastboot flash all <zip>
Fastboot flash <zip>
Fastboot flash zip <zip>
Fastboot update <zip>
All fail with some error
and also used htc_fastboot, minimal adb and fastboot 1.7msi & also power shell im using windows 8 also but no matter what i do cannot get anything to flash to the customers phone i downloaded the OTA's & firmware from the google spreadsheet i dont know what im doing wrong and the only RUU.exe i do have for htc_ocnuhl returns an error with incorrect model id please use the correct update utility,
What should i do tell him his phone is kaput or ?? Ive been at this 3 days now ive been working on phones for 10 years nothing takes 3 days !!!!!!
Any help would be greatly appreciated
Click to expand...
Click to collapse
Hi everyone so customer didn't want the phone in the end as it couldn't be repaired so didnt bother returning to pick it up so like I do with all things I tinker and I've spent a long long time trying to fix the OS and I have finally done it yayyy scored myself a free U11,
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5 or something like that, my bootloader was re locked and S-ON and nothing I tried would work phone had no recovery and would not boot all i would get is your device is corrupt, couldn't unlock the bootloader again all I would get is a message to state the 3 killswitches are active and to disable them but couldn't without a functional OS.
The 1.11.710.5 file I tried over the course since last post with normal fastboot didn't work, then I tried a series of htc_fastboot didnt work, I even used the fastboot binaries provided by HTCdev that didnt work, I tried every command I could rack up in my brain but still the body thing wouldnt flash I fixed roughly 6 RUU flash errors I was facing but the only one I couldn't get past was Ruu security fail zip from USB command, this told me it was something system wise, but had reinstalled everything including drivers gave all fastboots elevated privileges tried a million diff computers and cords ( lucky I run a phone shop hehehe )
Now something has completely slipped my mind I had a HTC 10 batch tool on my computer and had completely forgotten it had it's own terminal interafce, (which is a fully sik purple might I say) all I did was place the file into the path that the batch took was installed to which was com I do believe and then opened the batch tool up & typed " htc_fastboot oem rebootRUU" after i had put the device into download mode and connected device,
Device rebooted to RUU, all I did was type htc_fastboot flash zip <file_name> and it flashed all 28 zips from the 1.11.710.5 device rebooted and was now met with the HTC logo and phone booted straight up like nothing ever happened, once I had gotten the FRP lock removed (only took 5 minutes) not very good HTC lol I then went to the setting menu to software Info only to find out that the firmware was still 2.33.710.9 but the firmware file was specifically 1.11.710.5 as i had gotten it from the google spread sheet here on xda developers,
So there you have it everyone I hope this helps you repair your devices it seems it's all in the terminal used to flash the device as long as the file is also signed though I can't be 100% on that as I'm not sure the zip i used was signed either but anyway phone is working great and now it gets to be used and abused as a dev phone for myself
Matty1993 said:
Hi everyone so customer didn't want the phone in the end as it couldn't be repaired so didnt bother returning to pick it up so like I do with all things I tinker and I've spent a long long time trying to fix the OS and I have finally done it yayyy scored myself a free U11,
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5 or something like that, my bootloader was re locked and S-ON and nothing I tried would work phone had no recovery and would not boot all i would get is your device is corrupt, couldn't unlock the bootloader again all I would get is a message to state the 3 killswitches are active and to disable them but couldn't without a functional OS.
The 1.11.710.5 file I tried over the course since last post with normal fastboot didn't work, then I tried a series of htc_fastboot didnt work, I even used the fastboot binaries provided by HTCdev that didnt work, I tried every command I could rack up in my brain but still the body thing wouldnt flash I fixed roughly 6 RUU flash errors I was facing but the only one I couldn't get past was Ruu security fail zip from USB command, this told me it was something system wise, but had reinstalled everything including drivers gave all fastboots elevated privileges tried a million diff computers and cords ( lucky I run a phone shop hehehe )
Now something has completely slipped my mind I had a HTC 10 batch tool on my computer and had completely forgotten it had it's own terminal interafce, (which is a fully sik purple might I say) all I did was place the file into the path that the batch took was installed to which was com I do believe and then opened the batch tool up & typed " htc_fastboot oem rebootRUU" after i had put the device into download mode and connected device,
Device rebooted to RUU, all I did was type htc_fastboot flash zip <file_name> and it flashed all 28 zips from the 1.11.710.5 device rebooted and was now met with the HTC logo and phone booted straight up like nothing ever happened, once I had gotten the FRP lock removed (only took 5 minutes) not very good HTC lol I then went to the setting menu to software Info only to find out that the firmware was still 2.33.710.9 but the firmware file was specifically 1.11.710.5 as i had gotten it from the google spread sheet here on xda developers,
So there you have it everyone I hope this helps you repair your devices it seems it's all in the terminal used to flash the device as long as the file is also signed though I can't be 100% on that as I'm not sure the zip i used was signed either but anyway phone is working great and now it gets to be used and abused as a dev phone for myself
Click to expand...
Click to collapse
Congrats on getting the phone revived. I tried all what you had mentioned in your earlier post except what you mentioned about the "HTC 10 Batch Tool". Never heard of it until now. Well too bad for my phone as I sent it out to HTC Repair and it is in their hands now (3 weeks and counting). Yep, my mistake was relocking the phone when I wanted to receive the OTA update (phone was rooted but I didn't flash any custom ROM). Thanks for the post.
mauiblue said:
Congrats on getting the phone revived. I tried all what you had mentioned in your earlier post except what you mentioned about the "HTC 10 Batch Tool". Never heard of it until now. Well too bad for my phone as I sent it out to HTC Repair and it is in their hands now (3 weeks and counting). Yep, my mistake was relocking the phone when I wanted to receive the OTA update (phone was rooted but I didn't flash any custom ROM). Thanks for the post.
Click to expand...
Click to collapse
Hey mate yeah I spent weeks on end trying everything it seems the HTC 10 batchtool was the saviour here on xda somewhere as that's where I got it from the batch tool has it's own terminal built into it and it must still hold official HTC code in it somewhere to allow the package to be flashed,
Least you know for next time if it happens again to avoid that hefty repair bill by HTC
Matty1993 said:
Hey mate yeah I spent weeks on end trying everything it seems the HTC 10 batchtool was the saviour here on xda somewhere as that's where I got it from the batch tool has it's own terminal built into it and it must still hold official HTC code in it somewhere to allow the package to be flashed,
Least you know for next time if it happens again to avoid that hefty repair bill by HTC
Click to expand...
Click to collapse
That's the story of my life, a day late and a dollar short. All the best.
Matty1993 said:
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5
Click to expand...
Click to collapse
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.
wojownikhaha said:
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.
Click to expand...
Click to collapse
When you use Sunshine.apk you can set S-Off and flash Nougat
wojownikhaha said:
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.
Click to expand...
Click to collapse
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
miffymiffy said:
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
Click to expand...
Click to collapse
I read this topic, but this metod requires working TWRP partition I got only (relocked) bootloader and download mode, so have to try Chimera Tool or something like that.
snoopyhaeckers said:
When you use Sunshine.apk you can set S-Off and flash Nougat
Click to expand...
Click to collapse
I was still S-ON and had Relocked BL OEM unlock was OFF due to no working OS ( was corrupt) no recovery, only download, bootloader and RUU mode,
the HTC fastboot batch tool allows rollback of the bootloader without paying $25 for sunshine off to do it, ive just seen this now to lol only took 3 months to reply
I actually made a post on how to fix any flash errors like that a while ago its in the HTC U11 forums 1.5k veiws and counting
Matty1993 said:
I was still S-ON and had Relocked BL OEM unlock was OFF due to no working OS ( was corrupt) no recovery, only download, bootloader and RUU mode,
the HTC fastboot batch tool allows rollback of the bootloader without paying $25 for sunshine off to do it, ive just seen this now to lol only took 3 months to reply
I actually made a post on how to fix any flash errors like that a while ago its in the HTC U11 forums 1.5k veiws and counting
Click to expand...
Click to collapse
Sorry man I doesn't have a htc 10 at I have at the moment u 11
Sent from my HTC U11 using XDA Labs
where do I download zip version of signed HTC ruu firmware?
Hello everybody,
I can't update my phone HTC One A9 to nougat using RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2.exe, an error 10 occurs when updating. After contacting HTC Support, they tell me that my phone have three changes on three parts (the bootloader status (formerly UNLOCKED, now RELOCKED), (2) the security status (S-OFF) and (3) the Recovery tool (TWRP). Since all three have been changed i must proceed restoring the stock features step by step. The first thing they recommend is to restore the Android Recovery tool to the stock recovery.
For the bootloader is OK , it is now relocked, but i cant restore the recovery.
I need your help, my phone is not stable at all.
thanks in advace.
Phone info:
Htc download mode :
*** RELOCKED***
htc_hiaewhl PVT S-OFF
CID-11111111
LK-1.0.0.0000
[email protected]
OpenDSP-5.8.4.00190-8952_0922
OS-1.09.651.1
Oct 3 2015,00:19:23(633326)
==============================
IMEI 990005706216091
Model HTC One A9
Serial Number HT5BESZ01367
Part 99HAHD001-00
Series HIMA_AERO#WHL-R2
Part Description SKU , SPCS , English-WWE , USA , HTC , Bootloader Lock , Carbon Gray , DEF01 , w/o SIM Lock , HIMA_AERO#WHL-R2
Customer Description SPRINT NEXTEL CORPORATION
MEID 99000570621609
Country USA
Lock status Relocked
Warranty start 2015/11/23
Warranty end 2017/02/23
==============================
REcovery:
Team win recovery project 2.8.8.2_CPTB-TEST2
Hello every body
more than 1 month after posting here and i cant find any help from our experts. it seems my problem is so tough.
after reinstalling Htc sync manager and trying to update with RUU it give error 132 signature error.
i am starting to hate HTC. After 8 years of fidelity I think it s time to change my beloved company.
Unlock bootloader again
Change cid to correct version
You may have to do updates manually up to latest to be able to flash 2.18 RUU
Boot phone into download mode
Run the RUU If get an error try suggested manual updates
Good luck
Khayrou said:
Hello everybody,
I can't update my phone HTC One A9 to nougat using RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2.exe, an error 10 occurs when updating. After contacting HTC Support, they tell me that my phone have three changes on three parts (the bootloader status (formerly UNLOCKED, now RELOCKED), (2) the security status (S-OFF) and (3) the Recovery tool (TWRP). Since all three have been changed i must proceed restoring the stock features step by step. The first thing they recommend is to restore the Android Recovery tool to the stock recovery.
For the bootloader is OK , it is now relocked, but i cant restore the recovery.
I need your help, my phone is not stable at all.
thanks in advace.
Phone info:
Htc download mode :
*** RELOCKED***
htc_hiaewhl PVT S-OFF
CID-11111111
LK-1.0.0.0000
[email protected]
OpenDSP-5.8.4.00190-8952_0922
OS-1.09.651.1
Oct 3 2015,00:19:23(633326)
==============================
IMEI 990005706216091
Model HTC One A9
Serial Number HT5BESZ01367
Part 99HAHD001-00
Series HIMA_AERO#WHL-R2
Part Description SKU , SPCS , English-WWE , USA , HTC , Bootloader Lock , Carbon Gray , DEF01 , w/o SIM Lock , HIMA_AERO#WHL-R2
Customer Description SPRINT NEXTEL CORPORATION
MEID 99000570621609
Country USA
Lock status Relocked
Warranty start 2015/11/23
Warranty end 2017/02/23
==============================
REcovery:
Team win recovery project 2.8.8.2_CPTB-TEST2
Click to expand...
Click to collapse
Khayrou said:
Hello every body
more than 1 month after posting here and i cant find any help from our experts. it seems my problem is so tough.
after reinstalling Htc sync manager and trying to update with RUU it give error 132 signature error.
i am starting to hate HTC. After 8 years of fidelity I think it s time to change my beloved company.
Click to expand...
Click to collapse
The first post made me lol, HTC CS as bad as usual, they don't know their own product.
Re-locking the bootloader wasn't necessary
Flashing back the stock recovery neither
You are getting error 132 because you are trying to flash a Nougat ruu (2.x.xxx.x) but your phone still runing the Marshmallow firmware (1.x.xxx.x). Normally this is not a problem to update HTC phones using a RUU but this particular model of HTC is problematic because they changed signature key between version 1.x and 2.x which mean even if you are trying to flash the right RUU version for your phone, you'll get a signature error if flashing from marshmallow to nougat.
This is easily fixable, manually update your firmware to Nougat (so your phone will have the new key) using fastboot then flash the Nougat RUU
https://androidfilehost.com/?fid=673368273298932288
http://dl3.htc.com/application/RUU_...609.550203457.1539034826-348587674.1533856707
This thread might help, in particular post #2 faq #4