I recently got this phone and found out it was an EU version. I unlocked the bootloader and installed twrp. I made the major mistake of thinking I needed to relock the bootloader to install a ruu file. I can't get to recovery now to factory reset. If I try to reboot, it goes to an encryption screen that I can't get past. So I can't go to settings and turn the unlock bootloader option on or debugging. So, I can't unlock the bootloader either.
I also made the mistake of changing the cid and mid to USA dev. The cid and mid are: BS_US001 and 2PZC50000. The product: htc_ocnuhl.
The US unlocked RUUs should work, right? Well, I try to use the. exe. It won't work. I try to do the fastboot way, it says the file size is too large. I try the SD card way, it says 19 RU_MAIN_VER_FAIL is version in android info missing or i.
Am I just totally screwed?
Kaepernick said:
I recently got this phone and found out it was an EU version. I unlocked the bootloader and installed twrp. I made the major mistake of thinking I needed to relock the bootloader to install a ruu file. I can't get to recovery now to factory reset. If I try to reboot, it goes to an encryption screen that I can't get past. So I can't go to settings and turn the unlock bootloader option on or debugging. So, I can't unlock the bootloader either.
I also made the mistake of changing the cid and mid to USA dev. The cid and mid are: BS_US001 and 2PZC50000. The product: htc_ocnuhl.
The US unlocked RUUs should work, right? Well, I try to use the. exe. It won't work. I try to do the fastboot way, it says the file size is too large. I try the SD card way, it says 19 RU_MAIN_VER_FAIL is version in android info missing or i.
Am I just totally screwed?
Click to expand...
Click to collapse
This is a shot in the dark but trying reflashing your unlocker token you received from HTC and see if that will reunlock your phone so you can refresh recovery
Won't let me. Can't get into the os to turn the oem unlock on in developer's settings. When I try it, it tells me:
Last Byte is 0x00, disable unlock.
oem unlock Turn Off!
RLKirk said:
This is a shot in the dark but trying reflashing your unlocker token you received from HTC and see if that will reunlock your phone so you can refresh recovery
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Have you tried the proper htc_fastboot.exe?. You can find it easily on the forum. If that doesn't work can you get to download mode and change the cid and mid back to original?
Yeah, I've tried it. I've tried it with trying to get twrp to boot with, "fastboot boot twrp.img". No go there. I haven't tried to change the cid or mid back, but since I'm S-on now, I doubt I'll get very far. Temporary s-on. Just great. HTC really screwed me by making these changes. Four generations of phones work the same freaking way, but this one just had to be different.
shivadow said:
Have you tried the proper htc_fastboot.exe?. You can find it easily on the forum. If that doesn't work can you get to download mode and change the cid and mid back to original?
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Looked a bit on the forums and 19 ru_main_ver_fail can apparently mean wrong cid? Did you use the US ruu for the SD card method? Try the other (either your original cid or the US one) and see what happens?
EDIT: Also the output of fastboot getvar all would be helpful to debug
CurtisMJ said:
Looked a bit on the forums and 19 ru_main_ver_fail can apparently mean wrong cid? Did you use the US ruu for the SD card method? Try the other (either your original cid or the US one) and see what happens?
EDIT: Also the output of fastboot getvar all would be helpful to debug
Click to expand...
Click to collapse
Yeah, I used the US ruu after changing the cid and mid for the US dev version. RUU_OCEAN_WHL_O80_SENSE90GP_MR_NA_Gen_Unlock_2.42.617.7.exe.
Tried 2.42.617.1 8 via sd card. RU_SIGNATURE_FAIL
I tried a few others too. No dice. Said wrong OS. I tried the one that came with the phone using the sd card, the EU version, 2.33.401.10, and it says RU_MODELID_FAIL modelid in android-info mismatched
This wouldn't be a problem if I was S-Off. The OS version on the phone now is 2.33.401.10. If I could change the cid and mid back, it would probably work.
I tried using HTC fastboot:
C:\Android>htc_fastboot flash zip 2PZCIMG.zip
sending 'zip'... (2020158 KB) FAILdata too large, 2068641866 > 1951232000
FAILED (data size is too large(2020158 KB) for device to download ZIP file '2PZCIMG.zip'
)
Execution time is 2(s)
Then a newer version of fastboot:
C:\Android>fastboot flash zip 2PZCIMG.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#1002308
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 3.024s
I attached a picture of the getvar all command.
Kaepernick said:
Yeah, I used the US ruu after changing the cid and mid for the US dev version. RUU_OCEAN_WHL_O80_SENSE90GP_MR_NA_Gen_Unlock_2.42.617.7.exe.
Tried 2.42.617.1 8 via sd card. RU_SIGNATURE_FAIL
I tried a few others too. No dice. Said wrong OS. I tried the one that came with the phone using the sd card, the EU version, 2.33.401.10, and it says RU_MODELID_FAIL modelid in android-info mismatched
This wouldn't be a problem if I was S-Off. The OS version on the phone now is 2.33.401.10. If I could change the cid and mid back, it would probably work.
I tried using HTC fastboot:
C:\Android>htc_fastboot flash zip 2PZCIMG.zip
sending 'zip'... (2020158 KB) FAILdata too large, 2068641866 > 1951232000
FAILED (data size is too large(2020158 KB) for device to download ZIP file '2PZCIMG.zip'
)
Execution time is 2(s)
Then a newer version of fastboot:
C:\Android>fastboot flash zip 2PZCIMG.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#1002308
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 3.024s
I attached a picture of the getvar all command.
Click to expand...
Click to collapse
When in download mode u can flash install twrp recovery via adb then possibly flash a backup file, which hopefully u have or can get,,, or a rom. I have done this many times with a failed ruu install and it has worked.
Oh dear I think I see the issue. I don't see any RUUs for the US cid/mid that match the model htc_ocnuhl. I think you can only install an RUU that matches all three and it won't let you install a modified one because the signing will break
And now you can't get into s-off to change it again because the BL is locked. This looks bad...
There should be a warning somewhere about changing to cids your model doesn't support
CurtisMJ said:
Oh dear I think I see the issue. I don't see any RUUs for the US cid/mid that match the model htc_ocnuhl. I think you can only install an RUU that matches all three and it won't let you install a modified one because the signing will break
And now you can't get into s-off to change it again because the BL is locked. This looks bad...
There should be a warning somewhere about changing to cids your model doesn't support
Click to expand...
Click to collapse
Great. In past HTC phones, changing the cid and mid was enough. Now there's a third factor. Can you even change the model with s-off to install an official US RUU on a EU U11? Regardless, I'm stuck between a rock and a hard place. I had no idea that relocking the bootloader would block any chance to load twrp. That wasn't the case on the past phones and now I can't even do a factory reset.
All I need to do is get into the OS to switch bootloader unlocking on. (why they did this to make it more tedious, I don't know.)
The biggest reason I've stuck with HTC is because of how easy it used to be to change regions and install any RUU.
I still get the 155 unknown error when using a RUU.exe. I'm guessing that's why.
Sent from my HTC 10 using Tapatalk
Kaepernick said:
Great. In past HTC phones, changing the cid and mid was enough. Now there's a third factor. Can you even change the model with s-off to install an official US RUU on a EU U11? Regardless, I'm stuck between a rock and a hard place. I had no idea that relocking the bootloader would block any chance to load twrp. That wasn't the case on the past phones and now I can't even do a factory reset.
All I need to do is get into the OS to switch bootloader unlocking on. (why they did this to make it more tedious, I don't know.)
The biggest reason I've stuck with HTC is because of how easy it used to be to change regions and install any RUU.
I still get the 155 unknown error when using a RUU.exe. I'm guessing that's why.
Click to expand...
Click to collapse
The htc_* monikers seem to denote different hardware revisions. So probably different radios, partition layouts etc. You might have been able to change to EU unlocked but it probably can't figure out what to do with US firmware at all. Changing to super cid may have been a better option. This is genuinely a sucky situation though. Maybe there's a way out I don't know. Sorry about that.
EDIT: Are you sure you don't know the encryption password? Did you ever set one?
CurtisMJ said:
The htc_* monikers seem to denote different hardware revisions. So probably different radios, partition layouts etc. You might have been able to change to EU unlocked but it probably can't figure out what to do with US firmware at all. Changing to super cid may have been a better option. This is genuinely a sucky situation though. Maybe there's a way out I don't know. Sorry about that.
EDIT: Are you sure you don't know the encryption password? Did you ever set one?
Click to expand...
Click to collapse
Thanks for trying to help. I can't see a way out either. I never set a password for that. I did for the lock screen but said no when it asked me if I wanted to use it upon boot. Besides that, I'm pretty sure it factory reset when I unlocked the bootloader. Wish I hadn't locked it right after. ?
Sent from my HTC 10 using Tapatalk
One last resort. If it factory reset after unlock it might have a default password. I can vaguely remember something like that existing but can't seem to find it anywhere.
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Found it. Try "default_password". Otherwise I'm out of ideas.
CurtisMJ said:
One last resort. If it factory reset after unlock it might have a default password. I can vaguely remember something like that existing but can't seem to find it anywhere.
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Found it. Try "default_password". Otherwise I'm out of ideas.
Click to expand...
Click to collapse
Thanks, but it won't let me put any letters in. Only numbers seem to work. Can't even test it.
Sent from my HTC 10 using Tapatalk
You can try" fastboot format userdata" .
You should be able to enter the system without password.
But You will lost all data(Include Internal storage)
I'm fine with losing any data. New phone and there's nothing I need to save on it. I just need to be able to access the OS so I can unlock the bootloader. I'll give it a shot.
hcaelb said:
You can try" fastboot format userdata" .
But You will lost all data(Include Internal storage)
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Kaepernick said:
I'm fine with losing any data. New phone and there's nothing I need to save on it. I just need to be able to access the OS so I can unlock the bootloader. I'll give it a shot.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I've been following your thread and was hoping it would have led me to a solution to my own dilemma that is similar to your predicament. I had a U11 that I unlocked via HTC Dev website and I wanted to "relock" to get the OTA update. I used a ADB command to relock the phone and the phone boots to a encryption screen which of course won't allow me to bypass. I spent hours looking for a IMG and RUU file that would get my phone back to working order. Used the SD card and ADB process and could not find any joy.
I just sent my phone to the HTC service department. I am hoping they won't make me pay dearly for my mistake. Good luck in resolving this issue. I just got my phone in April and now I am using my old M8 that won't hold a charge for 4 hours.
Live and learn.
Sent from my HTC6545LVW using Tapatalk
Well, I think I know why the RUU.exe isn't working and I got the 155 unknown error. The os doesn't match. I'm guessing the os region needs to be the same, too, and since I can't seem to delete or format the os without unlocking the bootloader, the RUU won't work. [emoji58]
Sent from my HTC 10 using Tapatalk
Yeah, I wish this could have been more help for you, too. I just can't see a way out of it. I even tried changing the cid and mid in the firmware folder I downloaded from htcdev and flashing that. No joy.
mauiblue said:
I've been following your thread and was hoping it would have led me to a solution to my own dilemma that is similar to your predicament. I had a U11 that I unlocked via HTC Dev website and I wanted to "relock" to get the OTA update. I used a ADB command to relock the phone and the phone boots to a encryption screen which of course won't allow me to bypass. I spent hours looking for a IMG and RUU file that would get my phone back to working order. Used the SD card and ADB process and could not find any joy.
I just sent my phone to the HTC service department. I am hoping they won't make me pay dearly for my mistake. Good luck in resolving this issue. I just got my phone in April and now I am using my old M8 that won't hold a charge for 4 hours.
Live and learn.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Kaepernick said:
Yeah, I wish this could have been more help for you, too. I just can't see a way out of it. I even tried changing the cid and mid in the firmware folder I downloaded from htcdev and flashing that. No joy.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Yep, I tried all what you have done. No dice. Snake eyes. I was hoping to find the exact RUU version for my phone (2.42.617.6) but the I only could find the latest version which is on the HTCDev website. I am not able to get into recovery mode as the phone will give me the message that the phone is loaded with a different OS that it was originally installed. Dead end.
So after trying for over a week the same old steps and reading as much as I could on this and other websites, I knew there was no way I could figure this out or at the very least the phone was in a state beyond my abilities to repair. So my last resort was send it back to HTC. When I first was confronted with this issue I contacted HTC via chat. They were with me for an hour and a half explaining about getting into recovery mode and I explaining what was happening on the phone as we went into download mode and trying to get into recovery mode. Plus my typing skills isn't really proficient so it took time for me to compose and type. Ha! This initial contact with HTC and the start of the service process was on 1 September 2018. I have two weeks from the initial start of the process to send the phone back or I would have to initiate the process again. So this Monday I sent the phone in. The phone should be arriving in the Texas office tomorrow.
I posted this question on another thread and I'll just throw this out here also. If any member here knows or have had experience with HTC service department, what process do they go through to get the phone back to the original working order? Do they reflash the phone or do they actually need to physically replace a part in the phone to get it working again? My phone is still under warranty but I think bricking the phone is not covered even under their "Uh Oh" warranty. Any idea of the cost of repair? Aloha and mahalo.
Related
Hello,
I have maybe a stupid newb question. I've been searching around for an answer but with no luck.
My problem is as follow:
I've been using HTC Sensation for half a year now, with custom roms / rooted / SuperCID. So I'm not new to flashing stuff.
Somehow I managed to brick my device before (due to stupid flashing decisions). So I flashed a random EU RUU and send my phone for repairs (via insurance services). They "repaired" my phone. I'm not sure if I got a new one or they really repaired it? (IMEI changed but S/N is still the same)
Today I got my HTC Sensation back. I was very happy and started to check the phone. It appears the bootloader is locked and S-ON. (CID back to T-MO003)
So I tried to S-OFF using revolutionary.io , to bad without luck...
I started searching what might be the problem read something about downgrading and revolutionary works... got a bit confused about all the different posts around.
What is the correct way to get S-OFF, custom recovery, and so on... back on my phone?
Bootloader info:
Locked
S-ON
HBOOT 1.18.0000
Aug 2 2011.22:35:52
Thanks for your time!
Hoping for a fix,
Opletium
?????
how much did you end up paying for repairs
Nothing haha, I was suprised about that!
normally my insurance company bills 30 euro as "own risk".
I've read the agreements of the insurance and saw that damage caused to the phone by falling on the ground was covered. My phone had some visable damage on the egdes.
So I told the insurance that i dropped my phone. And because it stopped working i tried to reinstall the sofware to factory defaults.
What I did is: I flashed a RUU and that caused the brick, because the touch panel stopped working.
They "fell" for it.. kinda
ok tried to follow this guide:
http://forum.xda-developers.com/showthread.php?p=21922297#post21922297
problem, cant get my bootloader unlocked. HTCdev's unlock fails.
Error i get:
C:\bootloader_unlock>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.156s
File is in place, tried it multiple times and tried multiple tokens.. no clue on this!
Anyone that can help me to unlock and S-Off my device?
Did you try Revolutionary?
yes, I tried, but keeps failing aswel..
kinda start hating TMO for branding all their phones
This is the output of revolutionary
Enter beta key [ serial: HT17PV800204 ]: 47YUAhIWs2BusHJc
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Failed to get Root!
Press (almost) any key to exit.
Click to expand...
Click to collapse
is USB Debugging activated?
also have you got the drivers from HTC sync installed, but sync uninstalled, together with any other software that might attempt to sync with the phone?
USB debugging tried both enabled and disabled.
HTC drivers version 3.0.0.007 installed.
no other software on my laptop or PC that use my phone.
The thing that confuses me is that after repairs my IMEI number changed but my S/N stayed the same.
Guess they only replaced some hardware and not the total phone..
if that is the case then we should be aware that this HTC Sensation was S-OFF / rooted before.
When my touchpanel stopped working I flashed a RUU and locked bootloader and put the phone back to S-ON. I believe that I was on a lower version HBOOT while I send the phone back (before the phone went for repairs).
Try this
or try unlocking at HTC.
maumont said:
Try this
or try unlocking at HTC.
Click to expand...
Click to collapse
HTC Unlock does not work!! I have explained that a few posts back.
I tried your link... after the command
adb shell /data/local/tmp/tacoroot --root
Click to expand...
Click to collapse
my phone is bootlooping..
Ok did a factory reset via bootloader, now my phone works again.
but still no S-OFF..
The problem most likely is that you entered your details incorrectly at the HTC Dev site for unlocking your bootloader.
I don't think it checks the serial number to be genuine, I think as long as it follows a certain format it's accepted, so I would certainly check what you entered and try re-downloading the file from the Dev site. It's clearly NOT a driver issue, as CMD wouldn't even push the file to the phone if it was.
Hope this helps
Opletium said:
HTC Unlock does not work!! I have explained that a few posts back.
I tried your link... after the command
my phone is bootlooping..
Click to expand...
Click to collapse
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
khanem said:
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
Click to expand...
Click to collapse
Doubt this will work for them, as Revolutionary won't work without an Unlocked Bootloader and this is where they are getting stuck.
Just had contact with HTC themself to ask why the htcdev.com method is not working for me.
They explained that T-Mobile NL put their software on my phone while I send it for repairs. they put their bootloader on my phone, first i was like WTF but then he started mumbling about update that htcdev-tool does not support yet.. after some more " doubt-talk". He asked some software versions and made a case he would put trough to the technical support.
Guess that explains the HTCDev problem?????
/edit: I have tried over 15 times on the htcdev.com method
if I understand jaaystott correctly then first you need to have an unlocked bootloader in order to use revolutionary to S-OFF??
Any otherway to unlock the bootloader, because this htc method will take some time..
As for:
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
Click to expand...
Click to collapse
never tried it this way but I cant imagine that it would work since the bootloader is still locked.
Flash some other offical RUU, that should do it
jaaystott said:
Doubt this will work for them, as Revolutionary won't work without an Unlocked Bootloader and this is where they are getting stuck.
Click to expand...
Click to collapse
Taco root will give revolutionary access to files he cannot modify before. In all cases he can try if it doesn't work he will have to unlock first with htcdev then redo the whole operation.
Opletium said:
Just had contact with HTC themself to ask why the htcdev.com method is not working for me.
They explained that T-Mobile NL put their software on my phone while I send it for repairs. they put their bootloader on my phone, first i was like WTF but then he started mumbling about update that htcdev-tool does not support yet.. after some more " doubt-talk". He asked some software versions and made a case he would put trough to the technical support.
Guess that explains the HTCDev problem?????
/edit: I have tried over 15 times on the htcdev.com method
if I understand jaaystott correctly then first you need to have an unlocked bootloader in order to use revolutionary to S-OFF??
Any otherway to unlock the bootloader, because this htc method will take some time..
As for:
never tried it this way but I cant imagine that it would work since the bootloader is still locked.
Click to expand...
Click to collapse
Yes thats correct. Until the Bootloader is Unlocked nothing can be installed other than apps from the Market
As for the problem, I highly doubt that it's T-Mobile's Bootloader, I mean surely loads of other people on OTA's would have had this issue.. surely somewhere someone has reverted to stock and then realized that this is the problem?
I think it's likely the change of IMEI might have done it, could be the wrong IMEI associated with that Serial Number and so it won't flash.
Hi all,
I've a frustrating problem which is keeping me from being able to enjoy my wonderful Desire S -- hoping someone here can assist.
Background
I had a Desire S on the old 0.98 series HBoot which ran the Saga LBC mod ROM beautifully. Sadly it met with an unfortunate demise involving a glass of water in a dark room. The reason for sharing this is to explain that this model of phone, my SIM card and that ROM worked flawlessly on my network before.
Current State
I now have another Desire S, but it came with the annoying new HBoot which the Revolutionary hack can't deal with. I used the HTCdev method to unlock things meaning I could put custom ROMs on, although I have to use fastboot to flash the boot.img and then install the zip from recovery. No biggie.
However, I have been unable to connect to a 3G tower since having this new phone. I've tried both the Saga LBC mod (v0.6.0) and the Primo-S (v4.0) but only ever get a 2G connection. I've tried selecting WCDMA only via *#*#INFO#*#*, but when I do that it just immediately switches back to whatever option it was on before. I've tried other SIM cards, no joy (my SIM in an old Samsung works fine for 3G). The APN is definitely right.
I was going to try flashing a new radio, but the HTCdev unlock seems to block that:
Code:
mymachine$ ./fastboot flash radio radio.img
sending 'radio' (25856 KB)...
OKAY [ 4.328s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 8.701s
Doing the rename of the zip to PG88IMG.zip and putting on the SD card does result in it being unzipped in recovery, but then nothing happens -- no option to install it.
From reading round, I can't find any way of going back to 0.98 Hboot after using HTCdev unlock so that I could flash a radio. My current radio is 20.4801.30.0822U_3822.10.08.04_M
Help, I'm going mad!
Louis
2 options:
1) Your current Desire S is flawed.
2) Even though you think the APN is 100% right, it's actually wrong.
Option 1 is very improbable.
In any case, you can relock the phone to be able to downgrade and root it the Revolutionary way. There is a guide, please look for it, it's in the relevant sticky thread.
Jack_R1 said:
2 options:
1) Your current Desire S is flawed.
2) Even though you think the APN is 100% right, it's actually wrong.
Option 1 is very improbable.
In any case, you can relock the phone to be able to downgrade and root it the Revolutionary way. There is a guide, please look for it, it's in the relevant sticky thread.
Click to expand...
Click to collapse
Thanks for the reply -- do I take it that it is not possible that the radio image is incompatible just for 3G with these two ROMs? In other words, does the fact that the radio image works for 2G mean that it should work for 3G too and so playing with radio images is likely a waste of time?
Yes, the probability of faulty baseband firmware is close to 0. I wouldn't count on it happening.
Hello everyone. I've been following XDA since I first laid hands on a Nexus One. Thanks to all of you, I've been able to hack, mod, customize, etc. with only a few close calls. My ATT One X has proven to be a little more tricky and unforgiving. Long story short, I'm stuck in fast boot with an incorrectly changed CID (HTC_621) and a relocked bootloader. I was hoping to get another unlock token from HTC but I think they've abandoned the link. My only other hope was to edit the CID of the "android-info" file in the rom.zip of the RUU, but WinRAR says corrupt archive error when I change the text file. WinZIP won't even open the package--says its invalid. Bottom line, I've exhausted all resources as far as recovering from bad flashes and boot loop. My problem is that damn CID. Any bright ideas guys?
Official ROM zips are signed.
The signature makes the zip non standard so some apps wont open them and most everything else will not modify the file.
Even if you could modify you would make the signature invalid so it would not flash unless you had s-off.
By "Abandoned link" do you mean HTC will not send you an unlock token because the CID is invalid?
Have you tried your previous unlock token?
Without getting a valid unlock token I am unsure if what you can do.
Just out of curiosity, what were you trying to do exactly and what CID is that?
he was probably trying to flash the international jelly bean =)
redpoint73 said:
Just out of curiosity, what were you trying to do exactly and what CID is that?
Click to expand...
Click to collapse
It's an Endeavour CID for HTC Asia in Taiwan. And we wonder why HTC locks bootloaders and write-protects system partitions.
To the OP: This would not have worked anyway because you were trying to install software for a completely different phone.
Your original unlock token should still work. Trying unplugging and powering off your phone, rebooting your computer, and try flashing it again.
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
twistedddx said:
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
Click to expand...
Click to collapse
It's worth a shot. If it doesn't work, I don't see any way out. He can't run the RUU, he can't boot up, and he can't unlock. There might be some low-level fix via Linux. Try the unbricking Evita thread.
[S-OFF][tutorial] get rid of red text "this build is for development purposes..."
Moderators! Unfinished [tutorial]! Please give me some time to finish it
You must be [S-OFF] get rid of red text "this build is for development purposes..."
This build is for development purposes only. Do not distribute outside of HTC without HTC’s written permission. Failure to comply may lead to legal action.
Annoying red text message during boot splash with strong white background color disturbing my eyes
After S-OFF i installed CyanogenMod 13.0 on my Htc One A9
I did my research I found that I needed an image that is not signed, that is called aboot.bin for our model Htc one A9,
Therefore I requesting if someone have a aboot.zip so I can flash it with
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip aboot filename_aboot.zip
example this thread have a solution for HTC one M8 http://forum.xda-developers.com/showthread.php?t=2710503 Dev Santod040
It would also be nice to have a logo-Builder for the htc one A9 model and flash to the correct partition-block or adb'ing the shell witch busybox-binaries to the memory-Block in the emmc example ""dd if=/dev/block/mmcblk0p?? of=/sdcard/mmcblk0p??""
Example for the boot-logo-builder by Dev AnkadNikov
Send me aboot.zip-files so I can upload to you folks! or just post your self in this trhead with the right description of :
modelid
cidnum
mainversion
Warning! Don't do it until I confirm it works... It should also work with signed aboot.img I think (I will resarch, and tell you that later in this Htc One A9 development thread.
aboot.bin binaries for download
Here I will upload various aboot.bin for your precious phones, folks!
This is a bad idea. Flashing unsigned firmware to the A9 can result in 1) device automatically being set to S-ON, or 2) brickage (I know, because I bricked one this way). Unless you've tried this yourself and NOT bricked (and even if you have), I don't recommend this to anyone, and I'm pretty sure @jcase would agree.
datorprofessor said:
Here I will upload various aboot.bin for your precious phones, folks!
Click to expand...
Click to collapse
Here's aboot.bin I just dumped from my device. (mmcblk0p12)
https://drive.google.com/file/d/0B46kDSOkBccjYWp2RzFNdTJpUzA/view?usp=docslist_api
Att HTC a9 converted to developer edition after achieving s-off and now runing cm13.
The last ota I took from HTC was 1.55.617.4
HTC USA Unlocked
modelid: 2PQ912000
cidnum: BS_US001
For me only appears this red warning if i unlocked the bootloader. This is the reason why i always have boot relocked (no warning if s-off)
Is there any way to s-off without using sunshine? I'm Detailed for cash and can't afford the 25 at this time.
Only if xtc2clip owner s-off your device.
JochenP said:
Only if xtc2clip owner s-off your device.
Click to expand...
Click to collapse
i have this box
PD: to remove red text whithout s-off only flash original recovery
AnierinB said:
Here's aboot.bin I just dumped from my device. (mmcblk0p12)
https://drive.google.com/file/d/0B46kDSOkBccjYWp2RzFNdTJpUzA/view?usp=docslist_api
Hi,
Is this `aboot.bin` for HTC One A9 that will remove red text?
Click to expand...
Click to collapse
Does anyone know how to unhard-brick A9? I killed HBOOT accidentally. Now it's only detected as Qualcomm Device and nothing is being loaded?
---------- Post added at 11:35 AM ---------- Previous post was at 10:40 AM ----------
I have patched in hex editor and removed all that text that came in red (without changing the checksum) from `aboot.bin` that I extracted with `dd` from mmcblk0p12. Later, `fastboot flash aboot aboot.bin` under download mode didn't work. `dd` under `adb shell` also did not do anything.. Then I rebooted to bootloader and ran `fastboot flash aboot aboot.bin`. The message was - success. I happily rebooted and that was the end of the my HTC One A9 .
Is there a way to fix this POS? It's hard bricked!
@Captain_Throwback
You write in your post above that flashing unsigned firmware to the A9 is a bad idea.
Frist thing is I believe you...I also flashed on my first A9 modified hboot (without red warning)...
I made the same changes like I did on m7/M8/M9/HTC10 (had never a Problem with them) but with A9 baam!
I made a nice paperweight....can you tell me why did this happen only to A9?
Why did this modified hboot hurt only A9 so badly and all other devices I tried all went well?
thanks in advance
shivasrage said:
@Captain_Throwback
You write in your post above that flashing unsigned firmware to the A9 is a bad idea.
Frist thing is I believe you...I also flashed on my first A9 modified hboot (without red warning)...
I made the same changes like I did on m7/M8/M9/HTC10 (had never a Problem with them) but with A9 baam!
I made a nice paperweight....can you tell me why did this happen only to A9?
Why did this modified hboot hurt only A9 so badly and all other devices I tried all went well?
thanks in advance
Click to expand...
Click to collapse
Guys have the same question ... read this post .. and no luck.
C:\TMP>fastboot flash aboot aboot_signed.img
target reported max download size of 800000000 bytes
sending 'aboot' (800 KB)...
OKAY [ 1.035s]
writing 'aboot'...
(bootloader) HOSD CL#684509
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT aboot)
finished. total time: 2.048s
using 1.56.617.1 firmware.
Just don't do it*!
Guys!
It's not worth the risk! We have to obey our captain when he recommending.
:crying: I am Sorry guys for your's hard-bricked phones. Hopes your cat is still in live, at least.
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?