Database Info

Possible to change "modelid" of HTC One S?

Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!

In the build.prop
T-MobileUS HTC One S

fastboot write mid?
Sent from pixels to more pixels

usaff22 said:
fastboot write mid?
Sent from pixels to more pixels
Click to expand...
Click to collapse
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.

Charkatak said:
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.
Click to expand...
Click to collapse
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels

usaff22 said:
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels
Click to expand...
Click to collapse
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Edit: I checked my build.prop and it has MID PJ4010000. So this MID is also stored somewhere apart from build.prop. Damn it !!

chota_shivaji said:
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Click to expand...
Click to collapse
You need an Engineering HBOOT which supports those commands

usaff22 said:
You need an Engineering HBOOT which supports those commands
Click to expand...
Click to collapse
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).

chota_shivaji said:
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).
Click to expand...
Click to collapse
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.

I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app

dc211 said:
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.
Click to expand...
Click to collapse
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
leald said:
I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app

chota_shivaji said:
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app

leald said:
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for TMOUS MID and decrypted. Once I get that, I can use via RUU mode of fastboot.

chota_shivaji said:
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for EU MID and decrypted. Once I get that, I can use via RUU mode of fastboot.
Click to expand...
Click to collapse
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.

Charkatak said:
Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!
Click to expand...
Click to collapse
I think you should put the breaks on your project. Why exactly are you trying to change your MID anyways. If it's to get a RUU to run I'd suggest that you not go forward with your plan. There is no real reason to run an RUU if you have S-off other then to "start over" on a clean install of everything.
You can flash any: rom, firmware, radio, and hboot you choose so why change the model ID to run a RUU. Which is something I've NEVER seen anyone do in this forum to run a RUU. What's the full name of the RUU you want to run?
It looks like you're doing all this just to get to the official Jelly Bean release is that your goal? If so why not just flash it without using a RUU?

If so why not just flash it without using a RUU?[/QUOTE]
because the JB zip won't flash in a Tmous device because of different model id..

cyriantherockstar said:
because the JB zip won't flash in a Tmous device because of different model id..
Click to expand...
Click to collapse
Why not just install the rom that someone made compatible with TWRP then flash the firmware separately?

you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.

chota_shivaji said:
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.
Click to expand...
Click to collapse
correct me if i am wrong here, but why dont you just take the rom.zip from the ruu, decrypt it and change the androidinfo.txt and change the model id to say the one you need. then rezip it with winrar or 7zip and feed it to the hboot... you are s-off so it shouldnt ask any questions regarding the signiture of the zip file, but i am not sure about the compression.

untrueparadox said:
you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.
Click to expand...
Click to collapse
Has anyone had success doing this?

back to stock firmware onex at&t

As the title says. I just bought a hox at&t version and did a root metod and it failed. The phone is still save and I can normally use it. Now I want to re-flash the stock firmware that the phone was runing the first time I used it. I am scared with the fact about I wouldn't update to Jelly Bean beacuse it might contains any corrupt file due the failed root.
Is there a detailed how to'' guide? I only see guys in here says about flash RUU.
please help!

If you are going to give up that easily, than maybe root is not for you.
What firmware number (1.85, 2.20, etc.) is the phone now? What root method did you try? Root method varies by firmware version, so its a common mistake to use the wrong one. Also, even with the correct method, you may need multiple attempts before its successful (not necessarily due to anything you are doing wrong).
If you truly want to return to stock, just find the RUU for your version number. Download to your computer. Connect the phone via USB. Then just run the RUU. Its an .exe, no guide needed.
Links to the RUUs are on my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?

jics91 said:
thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
all you need to do is "fastboot oem lock" and run the ruu at the fastboot screen.

jics91 said:
but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
RUU flashes everything: Stock recovery, radio, kernel, and I believe hboot. It will also wipe the phone, so backup anything you want to keep. As DvineLord said, your bootloader needs to be locked. Other than that, just run the RUU, and it does the rest.
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
jics91 said:
now I'm downloading the RUU,
Click to expand...
Click to collapse
Make sure you dowload the right RUU for your firmware version. RUU will only run if the RUU is the right CID, and same version number or a later one (older RUU will not run).

[Q] How to Update to OTA_K2_UL_JB422_SENSE50_MR_hTC_Asia_WWE_3.12.707.2

Hi Guys,
Good day!
Have received a system update notification on my One SV and downloaded the file:
OTA_K2_UL_JB422_SENSE50_MR_hTC_Asia_WWE_3.12.707.2-2.14.707.5_release_3445776pznn0vdk5c0jhzu
However, my phone is rooted, with CWM Recovery v6.0.3.2.
Please help on how will I able to install the update.
Thanks!
My bootloader info:
TAMPERED
UNLOCKED
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 7 2013, 22:41:40:-1

You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!

old.splatterhand said:
You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!
Click to expand...
Click to collapse
Thanks for the reply!
Can you please teach me how to restore everything?
I have read your guide but I think it will not be applicable(?) in my case since my phone is Asia WWE and there is no available RUU for K2_UL.
Thanks!

I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones

old.splatterhand said:
I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones
Click to expand...
Click to collapse
Thanks again for the reply.
During downgrade of hboot, I have received the ff. error:
Model ID incorrect! Update Fail!
When I run the command on Terminal Emulator, I got 2 model IDs:
PL8010000, PL8015000
Please help.
Thanks!

The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.

old.splatterhand said:
The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.
Click to expand...
Click to collapse
That's sad news..
I think the problem is that my hboot cannot be downgraded, since the RUU issue can be solved using @russellvone 's method.
Anyway, thanks a lot!

You can update with a special firmware.zip. You need to backup your radio.img first, and replace it with the one inside the firmware.zip. Then you need to edit the model id in the android-info.txt of firmware.zip.
This must be flashed and then you can restore a european backup/rom.
Maybe @renanski still has his radio.img and can share it with us. He has also asia k2ul.

I've got a copy if needed @old.splatterhand @palamanTM

russellvone said:
I've got a copy if needed @old.splatterhand @palamanTM
Click to expand...
Click to collapse
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?

old.splatterhand said:
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?
Click to expand...
Click to collapse
uploading now
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
K2_UL_Asia_Radio.img_PL80IMG.zip
@old.splatterhand

Thanks, @russellvone for this!
Have replaced the android-info.txt in the original PL80IMG.zip file and tried again to downgrade the hboot.
But I got "CID Incorrect!" error.
after moonshine S-OFF, my phone's info is now:
K2_UL PVT SHIP S-OFF RL
CID-HTC_044
HBOOT-2.00.4444
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Thanks again for the assistance!

You need to get Supercid first. Use this fastboot cmd:
fastboot oem writecid 11111111
Click to expand...
Click to collapse

old.splatterhand said:
You need to get Supercid first. Use this fastboot cmd:
Click to expand...
Click to collapse
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.

palamanTM said:
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.
Click to expand...
Click to collapse
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.

old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
I was hoping I can get my phone back to stock to receive the "official" update.
But since there is still no RUU available, I'll go with your stock odexed rom.
Thanks a lot for the assistance, @old.splatterhand and @russellvone! my phone is now 4.2.2!

old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?

Fysiks said:
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?
Click to expand...
Click to collapse
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk

Modding.MyMind said:
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Am I required to flash the boot.img inside the ROM?

Fysiks said:
Am I required to flash the boot.img inside the ROM?
Click to expand...
Click to collapse
If you are S-On, then:
flash Rom via custom recovery after you have conducted a factory reset wipe from within your custom recovery, to include the system partition which can be found in the advance options if using TWRP.
Then, wipe dalvik cache and cache after it finishes
Then, reboot your bootloader, and via fastboot, flash the boot.img which would require you to extract it from the Rom and placing it where your proper adb/fastboot files are on your PC. Use this command:
Code:
fastboot flash boot boot.img
If you are S-Off, then just flash the Rom via custom recovery as explained above. You will not need to flash the boot.img via fastboot. Just wipe dalvik cache and cache after it finishes, and reboot your device.

[Q] Unable to get in to recovery or install CWM or TWRP

I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.

Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...

I've tried that too, still just reboots as normal.

Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.

HTC One S S4 running Android 4.0.4 ICS

mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all

LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?

mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before

LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.

mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.

LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good:

Help Nougat Htc One A9 hiaeuhl

i need help to install nougat on my htc one a9
-Now i run actually in cyanogenmod 14.1
- when i try to update manually my phone, with 2PQ9IMG_HIA_AER[email protected]61209_60.00_F_release_500842_combined_signed_2.zip
i have an error : could not find meta-inf/com/google/android/update-binary in the zip file
I need help, please
Sorry for my translation thank you

first flash firmware

amirinda said:
first flash firmware
Click to expand...
Click to collapse
ok first a need to flash the firmware
i have a htc one A9 hiaeuhl, with S-ON
can you give me a link to download appriopriate firmware for my phone

thobama said:
ok first a need to flash the firmware
i have a htc one A9 hiaeuhl, with S-ON
can you give me a link to download appriopriate firmware for my phone
Click to expand...
Click to collapse
Try https://www.androidfilehost.com/?fid=745425885120707133

thobama said:
could not find meta-inf/com/google/android/update-binary in the zip file
Click to expand...
Click to collapse
RUU are not flashed using TWRP, flash using fastboot

alray said:
RUU are not flashed using TWRP, flash using fastboot
Click to expand...
Click to collapse
i try this procedure:
- adb reboot bootloader
- in bootloader mode i choose the "download mode"
-adb sideload firmware2.16.401.3.zip
loading: 'firmware2.16.401.3.zip'adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found

thobama said:
i try this procedure:
- adb reboot bootloader
- in bootloader mode i choose the "download mode"
-adb sideload firmware2.16.401.3.zip
loading: 'firmware2.16.401.3.zip'adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
Flash using fastboot, not twrp neither adb, fastboot.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
or use the sd card method
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2

First of all, he should not flash 2.16.401.3.

Didusieq said:
First of all, he should not flash 2.16.401.3.
Click to expand...
Click to collapse
Even if I agree with you, it doesn't really matter if he flash the 2.16 or the 2.17 firmware before flashing the 2.17.401.2 RUU. As long as the HOSD is updated with the new decryption key which is the same in both 2.16 or 2.17 the phone will accept the 2.17.401.2 RUU

But there are two different Firmware files. I would install newer one.

alray said:
Flash using fastboot, not twrp neither adb, fastboot.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
or use the sd card method
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Click to expand...
Click to collapse
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched

Didusieq said:
But there are two different Firmware files. I would install newer one.
Click to expand...
Click to collapse
Yes I agree with that,just saying there will by no difference in the end result since the 2.17 ruu will flash the 2.17 firmware over the 2.16. As long as he update his firmware to 2.xx he will be fine to flash the 2.17 ruu.
---------- Post added at 02:38 AM ---------- Previous post was at 02:38 AM ----------
thobama said:
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched
Click to expand...
Click to collapse
What is your cid?

alray said:
Yes I agree with that,just saying there will by no difference in the end result since the 2.17 ruu will flash the 2.17 firmware over the 2.16. As long as he update his firmware to 2.xx he will be fine to flash the 2.17 ruu.
---------- Post added at 02:38 AM ---------- Previous post was at 02:38 AM ----------
What is your cid?
Click to expand...
Click to collapse
CID htc___247

thobama said:
CID htc___247
Click to expand...
Click to collapse
Can you see "HTC__247" listed under the 2.17.401.2 ruu?
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344#post63640734
Have you read the FAQ at post 2 ?
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
This ruu is not compatible with your phone, unless you make it S-OFF and change the CID.

alray said:
Can you see "HTC__247" listed under the 2.17.401.2 ruu?
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344#post63640734
Have you read the FAQ at post 2 ?
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
This ruu is not compatible with your phone, unless you make it S-OFF and change the CID.
Click to expand...
Click to collapse
i understand now
can you help me do this? i try sunshine apk but i didnt work

thobama said:
i understand now
can you help me do this? i try sunshine apk but i didnt work
Click to expand...
Click to collapse
Sunshine work best on stock rom. Go back to your stock rom (there is MM ruu for Bouygues in the collection) and try sunshine again. Or even simpler, go back to your stock rom and check if there is an ota update for Nougat.

alray said:
Sunshine work best on stock rom. Go back to your stock rom (there is MM ruu for Bouygues in the collection) and try sunshine again. Or even simpler, go back to your stock rom and check if there is an ota update for Nougat.
Click to expand...
Click to collapse
thanks a lot for your help

amigo instalaste
tengo el modelo htc__322 de claro y me salen los mismos errores

wilson230997 said:
tengo el modelo htc__322 de claro y me salen los mismos errores
Click to expand...
Click to collapse
Please post in English (see forum rules)
I'm not sure what error you are referring to exactly. If you're talking about the error discussed at post #1, it's simple, you can't flash a RUU using a custom recovery, it must be flashed using fastboot (read last page discussion).
If you're referring to the error discussed at post #11, you're trying to flash a RUU version not compatible with your phone. HTC__322 is the A9_UL and will only accept x.xx.600.x ruu version. See the ruu collection threads post #2 for more info.

thobama said:
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched
Click to expand...
Click to collapse
Dude, have you really taken time to fully read the instructions? It is all there, just read it! RTFM!!!
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2