Related
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray
I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.
soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy
Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium
panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL
area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.
I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.
So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2
coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
ImHuge07 said:
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
Click to expand...
Click to collapse
Hi,
Run a RUU.
Look HERE
malybru said:
Hi,
Run a RUU.
Look HERE
Click to expand...
Click to collapse
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
ImHuge07 said:
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
Click to expand...
Click to collapse
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
ImHuge07 said:
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Click to expand...
Click to collapse
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
ImHuge07 said:
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
Click to expand...
Click to collapse
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
malybru said:
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
Click to expand...
Click to collapse
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
ImHuge07 said:
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
Click to expand...
Click to collapse
Hi,
Radio and kernel are included in the RUU
ImHuge07 said:
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
Click to expand...
Click to collapse
Hi,
I would change the cid,run the RUU,and then s-on.
I have extracted and decrypted the att ruu for the htc one mini. Just so if anyone needs something out of it and doesnt want to flash the entire ruu
https://mega.co.nz/#!aQRUTaaJ!MkdTchfndvrpKTlHqcW4xgGKGr1s2d8Vqy9LqOv6SAY
hope it helps lemme know if link works. my mega screws up sometimes.
It's possible to unroot phone by this. I have s-off, Htc One Mini, UK T-mobile version, but I want back to s-on with unrooted phone to get my warranty again.
unlimited_pl said:
It's possible to unroot phone by this. I have s-off, Htc One Mini, UK T-mobile version, but I want back to s-on with unrooted phone to get my warranty again.
Click to expand...
Click to collapse
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
abzboi said:
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
Click to expand...
Click to collapse
ive used the ruu many times.lol its not risky at all.
abzboi said:
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
Click to expand...
Click to collapse
ive got two phones replaced already if you need warrany...brick the bastard solid so you have a dead black screen. play dumb like it just happened on the charger overnight.lol
Where can I find stock ruu for htc one mini?
If you're trying to return it for warranty then just brick your phone. Don't flash the AT&T ruu because when they check it will show AT&T suff in there and they will know about it. Unless it bricks don't flash it unless your phone is the AT&T version.
4.4.2 came out for at&t yesterday. Can you download it and extract it maybe?
cmvienneau said:
ive got two phones replaced already if you need warrany...brick the bastard solid so you have a dead black screen. play dumb like it just happened on the charger overnight.lol
Click to expand...
Click to collapse
Whats the best way to do this? .. My battery is really screwed ... operating extremely hot .. I htink I need to return for a warranty. Even when the phone has been off for 2 hours the back still has heat in it!
abzboi said:
4.4.2 came out for at&t yesterday. Can you download it and extract it maybe?
Click to expand...
Click to collapse
+1
in indonesia not getting update.my phone still jb 4.2.2 and never get update via ota.so sad
Sent from my HTC One mini using XDA Premium 4 mobile app
dalfshiro said:
+1
in indonesia not getting update.my phone still jb 4.2.2 and never get update via ota.so sad
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you root or s-off the phone? If yes, then I can help you get 4.4.2 ota update.
abzboi said:
Did you root or s-off the phone? If yes, then I can help you get 4.4.2 ota update.
Click to expand...
Click to collapse
i am not sure my phone rooted or not, couse i am buying from another people. but i have checked witch root checker and said not root. and i can confiirm my phone still locked and s-on. please help me
dalfshiro said:
i am not sure my phone rooted or not, couse i am buying from another people. but i have checked witch root checker and said not root. and i can confiirm my phone still locked and s-on. please help me
Click to expand...
Click to collapse
Try changing the date of the phone to the next day and check for update. If not, tell me what android version you're on and I'll help you update your phone to 4.4.2 via ota.
abzboi said:
Try changing the date of the phone to the next day and check for update. If not, tell me what android version you're on and I'll help you update your phone to 4.4.2 via ota.
Click to expand...
Click to collapse
I have changed my date to the next month.but still no update.my phone jb 4.2.2 software number 1.24.502.3
I am not using t mobile sim card.but using another sim card cause i am in indonesia.maybe thats the problem?pleasr help.thanks
Sent from my HTC One mini using XDA Premium 4 mobile app
dalfshiro said:
I have changed my date to the next month.but still no update.my phone jb 4.2.2 software number 1.24.502.3
I am not using t mobile sim card.but using another sim card cause i am in indonesia.maybe thats the problem?pleasr help.thanks
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Download this ruu and backup before you run it. If you bootloader is unlocked, lock it using fastboot oem lock. Link : http://dl3.htc.com/application/RUU_M...3_signed_2.exe
abzboi said:
Download this ruu and backup before you run it. If you bootloader is unlocked, lock it using fastboot oem lock. Link : http://dl3.htc.com/application/RUU_M...3_signed_2.exe
Click to expand...
Click to collapse
are you sure tahts the correct link?
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
dalfshiro said:
are you sure tahts the correct link?
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Click to expand...
Click to collapse
It's in this thread http://forum.xda-developers.com/showthread.php?t=2546757
abzboi said:
It's in this thread http://forum.xda-developers.com/showthread.php?t=2546757
Click to expand...
Click to collapse
can you give me step by step to install this RUU?need to s-on s-off?
dalfshiro said:
can you give me step by step to install this RUU?need to s-on s-off?
Click to expand...
Click to collapse
Just turn your phone into bootloader and fastboot then run the ruu and your done.
abzboi said:
Just turn your phone into bootloader and fastboot then run the ruu and your done.
Click to expand...
Click to collapse
i have installed htc sync manager on PC.but my phone wont detected fastboot.
edited : windows 8.1 cant detect htc usb driver
I have been doing a lot of reading up on changing the branding/region of the U11 and think I have the steps worked out. Would just like
someone who has done this to comment on if it seems right to them.
So Going from DUGL India to DUGL EMEA I would
1. Install sunshine for s-off so I can change the CID, current MID is the same as EMEA.
2. Change CID from download mode, fastboot oem writecid HTC__034
3. Download and install EMEA ruu
Thanks, MadMungo
Well I had time to give it a go and was successful. I am now on the (HTC__001) EMEA dual sim firmware from the (HTC__060) Indian dual sim firmware.
If anyone else wants to give it a go it was real simple, I just followed the following steps
1. Install sunshine for s-off to change the CID.
1a. Download EMEA RUU and copy to root of SD card and rename to 2PZCIMG.zip
2. run Sunshine to boot into s-off download mode,
2a. Change CID by running fastboot oem writecid HTC__001 on PC
2b. press Volume Down button to cancel RUU update and check CID = HTC__001
3. select reboot to Download Mode
3a. press Volume Up button to confirm flash of RUU
4. Once phone has been rebooted enjoy setting up new phone on EMEA firmware.
hope this helps someone else out there.
MadMungo said:
Well I had time to give it a go and was successful. I am now on the (HTC__001) EMEA dual sim firmware from the (HTC__060) Indian dual sim firmware.
If anyone else wants to give it a go it was real simple, I just followed the following steps
1. Install sunshine for s-off to change the CID.
1a. Download EMEA RUU and copy to root of SD card and rename to 2PZCIMG.zip
2. run Sunshine to boot into s-off download mode,
2a. Change CID by running fastboot oem writecid HTC__001 on PC
2b. press Volume Down button to cancel RUU update and check CID = HTC__001
3. select reboot to Download Mode
3a. press Volume Up button to confirm flash of RUU
4. Once phone has been rebooted enjoy setting up new phone on EMEA firmware.
hope this helps someone else out there.
Click to expand...
Click to collapse
Nice little guide mate. May I make a suggestion though. The better CID if one lives in central Europe would be HTC__034 as far as I remember.
Sent from my HTC U11 using XDA Labs
Thanks for the guide, am planning to change Indian Dual Sim CID to US Single Sim is tis achievable? please advise.
5m4r7ph0n36uru said:
Nice little guide mate. May I make a suggestion though. The better CID if one lives in central Europe would be HTC__034 as far as I remember.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Hey, I am in Australia and bought the phone from overseas vendor as it was cheaper and I needed a dual sim phone so I didn't have to carry 2 phones around. I now have a different job and don't have a need for dual sims I was wondering if it is possible to set the phone up as a single sim by changing the CID to one of either HTC__001 Prefered, (HTC__M27, HTC__002, HTC__034 Optional) and the MID to 2PZC10000.
MadMungo said:
Hey, I am in Australia and bought the phone from overseas vendor as it was cheaper and I needed a dual sim phone so I didn't have to carry 2 phones around. I now have a different job and don't have a need for dual sims I was wondering if it is possible to set the phone up as a single sim by changing the CID to one of either HTC__001 Prefered, (HTC__M27, HTC__002, HTC__034 Optional) and the MID to 2PZC10000.
Click to expand...
Click to collapse
Why wouldn't you use it as is, You could use the second SIM tray as an SD tray and all fine. Why convert it.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Why wouldn't you use it as is, You could use the second SIM tray as an SD tray and all fine. Why convert it.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thats what I am doing now. Am just curious if it is possible.
MadMungo said:
Well I had time to give it a go and was successful. I am now on the (HTC__001) EMEA dual sim firmware from the (HTC__060) Indian dual sim firmware.
If anyone else wants to give it a go it was real simple, I just followed the following steps
1. Install sunshine for s-off to change the CID.
1a. Download EMEA RUU and copy to root of SD card and rename to 2PZCIMG.zip
2. run Sunshine to boot into s-off download mode,
2a. Change CID by running fastboot oem writecid HTC__001 on PC
2b. press Volume Down button to cancel RUU update and check CID = HTC__001
3. select reboot to Download Mode
3a. press Volume Up button to confirm flash of RUU
4. Once phone has been rebooted enjoy setting up new phone on EMEA firmware.
hope this helps someone else out there.
Click to expand...
Click to collapse
Hey,
Thanks for the help and the guide. I was trying to do exactly the same thing.
I got stuck at the final stage. I was trying to SD card flash one of the combined nowipe firmware zips (https://androidfilehost.com/?fid=817906626617943112) and I get an error 10 when flashing, which makes no sense because the MID on my phone and in the zip are both correct. CID changed successfully and checked. S-OFF all ok and booted using sunshine before trying to flash the firmware.
any ideas? perhaps I am trying to flash the wrong thing and I have to do a full RUU flash somehow? Trying to avoid this because running leedroid rom and am lazy to setup again.
thanks for any ideas, Russ
bigruss said:
Hey,
Thanks for the help and the guide. I was trying to do exactly the same thing.
I got stuck at the final stage. I was trying to SD card flash one of the combined nowipe firmware zips (https://androidfilehost.com/?fid=817906626617943112) and I get an error 10 when flashing, which makes no sense because the MID on my phone and in the zip are both correct. CID changed successfully and checked. S-OFF all ok and booted using sunshine before trying to flash the firmware.
any ideas? perhaps I am trying to flash the wrong thing and I have to do a full RUU flash somehow? Trying to avoid this because running leedroid rom and am lazy to setup again.
thanks for any ideas, Russ
Click to expand...
Click to collapse
Russ,
Sorry to here you are having troubles. I am just a user, no technical knowledge but will try to help.
As far as I can tell from reading various posts on this, you will need to flash to the latest stock RUU, https://androidfilehost.com/?fid=745425885120762674 . Then you can flash the OTA http://fotadl-az.htc.com/secure/OTA_OCEAN_DUGL_N71_SENSE90GP_HTC_Europe_1.27.401.11-1.27.401.5_release_512994zou8hacebhmotmqg.zip using the original stock recovery, no need to be S-OFF for OTA flash.
Unfortunately you will then need to start with leedroid rom all over again.
Maybe one of the more technical guys could help you if you ask in the Firmware collection How-To Thread
thought that might be the case, thanks for the reply, much obliged.
HTC U11 India Oreo update:
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page99
Can we try something similar with the HTC TW ROM. I am guess its CID is 80.
I am guessing that the TW ROMs would receive updates from HTC before other regions.
Any inputs will be appreciated
Thank you!
Oreo update for the u11 EMEA from nougat 1.27.401.11
Hello guys, would really appreciate it if someone updates me on how to bring my U11 EMEA to Android 8.0 Oreo. I am currently running nougat version number 1.27.401.11. Thanks. Will keep checking this thread
benardssekitte said:
Hello guys, would really appreciate it if someone updates me on how to bring my U11 EMEA to Android 8.0 Oreo. I am currently running nougat version number 1.27.401.11. Thanks. Will keep checking this thread
Click to expand...
Click to collapse
Unlock bootloader via htc dev website.
Flash twrp.
Flash magisk
Buy s-off for $25 via sunshine.
Change cid to BS_001
Flash 1.xx.617.xx firmware (same version as you already have running on the phone but 617 region).
Update to oreo via ota.
Job done.
You will need the htc_fastboot.exe that is specifically made by htc for flashing. You can find it all over the m9 forums or on Google.
Thanks
benardssekitte said:
Hello guys, would really appreciate it if someone updates me on how to bring my U11 EMEA to Android 8.0 Oreo. I am currently running nougat version number 1.27.401.11. Thanks. Will keep checking this thread
Click to expand...
Click to collapse
Well, there's an OTA Update that will take you straight to Oreo from the version you're currently on. No need to unlock bootloader or anything else. It's there in this thread
You wouldn't lose any data either, but just take a backup nonetheless.
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
MadMungo said:
I have been doing a lot of reading up on changing the branding/region of the U11 and think I have the steps worked out. Would just like
someone who has done this to comment on if it seems right to them.
So Going from DUGL India to DUGL EMEA I would
1. Install sunshine for s-off so I can change the CID, current MID is the same as EMEA.
2. Change CID from download mode, fastboot oem writecid HTC__034
3. Download and install EMEA ruu
Thanks, MadMungo
Click to expand...
Click to collapse
Is there any particular reason why you wanted to (and subsequently) move(d) from Indian region to EMEA (I am guessing 1 reason to be quicker OTA updates). As far as I know, the Indian ROM doesn't have any bloatware.
That said, if there are any advantages (in terms of performance/battery life/etc) do let us know and I will move too. he he!
SKU 401 is already an EMEA device. He seems to try to change to US Unlocked unless I don't know for what that might be good. In addition this will probably keep to problems on further updates, as he can't change the confirmation of the variant from DUGL to WHL as this won't be altered by S-OFF or any step that could and might be taken.
I'd stay on Indian version 1.27.401.11 and await the upcoming Oreo update.
Sent from my HTC U11 using XDA Labs
Thanks all, but I guess will just wait for the Oreo update for the HTC U11 EMEA from nougat 1.27.401.11 coz I don't seem to find it on the links posted earlier. I don't understand y HTC doesn't just post the RUUs for each CID so that we can do it ourselves coz it seems not to be able to keep up with either the demand or it's own promises
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?