INTRODUCTION
As I promised in my last guide, I have played around with the RUUs in an attempt to bypass the "Model ID Incorrect" error, and have successfully installed the Optus 2.3.3 RUU on my Bell IS!
WHAT IS REQUIRED?
-a S-OFF'ed IS (doesn't need to be radio S-OFF'ed)
- That's it! A goldcard MAY also be required(it wasn't for me, but people are reporting they still get CID errors).
INSTRUCTIONS
Follow this guide until the 4th bullet under "How to install the Gingerbread update if you're S-OFF" but copy the rom.zip to your Desktop instead of your phone.
Extract rom.zip into your Desktop and open the new "rom" folder
First of all, you should now see 12 files in this folder. Delete the file "hboot_1.13.0000_CRC_8a731c6e_0401.img"... (This is mandatory! You MUST delete this file for the update to succeed! You may flash it on after installing the RUU if you wish, but you will lose S-OFF if you do not have radio S-OFF.)
Now open "android-info.txt" in wordpad or another similar text editor... The use of notepad is discouraged.
Now this is where the magic happens.
Change the line "modelid: PG3213000" to "modelid: PG3212000" (This will fix the "Model ID Incorrect" error)
[Optional] If you would like to flash the RUU without using a gold card then:
Add the following lines after "cidnum: OPTUS001":
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Now click "File" -> "Save".
Now Select all the files in the rom folder(Ctrl + A), right click on one of the file and select "Send to" -> "Compressed (zipped) folder" and rename the folder to PG32IMG.zip.
Return to this guide and follow the rest of the bullets under "How to install the Gingerbread update if you're S-OFF"
Enjoy your gingerbread RUU
Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??
IXXBC said:
Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??
Click to expand...
Click to collapse
Did you add the lines:
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
a better way
this way works with every BRANDED IS (including canadian bell vr)
after using alpharevx to achieve s-off
u will want to install recovery next (just like any other tutorial tells you), but branded IS will always get a CID-incorrect
inorder to fix this, create a goldcard by following this link
wiki.cyanogenmod.com/index.php?title=Howto:_Create_a_Goldcard
except when you are on step 3, use this command instead
cat /sys/class/mmc_host/mmc2/mmc2:*/cid
USING MMC1 or MMC0 will never work!!!
using your goldcard, you will bypass all the cid incorrect problems
then you can use your gold card to flash recovery / radio
cheers
IXXBC said:
Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??
Click to expand...
Click to collapse
you will need to flash a new radio, under CM7 post he should have told you to flash a new radio. After flashing the new radio no audio bug will go away
Insufficient storage available after rooting!
Please ignore this post.
Hi
I followed all your instructions:
Downloaded : RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed
Then romved the hboot file
Updated android_info.txt to:
modelid: PG3212000
cidnum: OPTUS001
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
hbootpreupdate:13
mainver: 2.12.980.2
Zipped into the PG32IMG.zip file.
Uploaded to my sd card
Rebooted my phone in the bootloader...
But I get "CID incorrect"
What could I be doing wrong?
Then I checked XDA and found how to get my CID this is what I got:
C:\Users\fabian\Desktop\CWM>adb shell getprop ro.cid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
BM___001
How can I fix this?
Thanks.
Thanks.
My phone info:
vivo pvt ship s off lr
hboot 1.09.0000
Radio-38.02.01.17_m
eMMC-boot
Feb 11 2011 11:52:44
aresguerrero said:
Hi
I followed all your instructions:
Downloaded : RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed
Then romved the hboot file
Updated android_info.txt to:
modelid: PG3212000
cidnum: OPTUS001
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
hbootpreupdate:13
mainver: 2.12.980.2
Zipped into the PG32IMG.zip file.
Uploaded to my sd card
Rebooted my phone in the bootloader...
But I get "CID incorrect"
What could I be doing wrong?
Then I checked XDA and found how to get my CID this is what I got:
C:\Users\fabian\Desktop\CWM>adb shell getprop ro.cid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
BM___001
How can I fix this?
Thanks.
Thanks.
My phone info:
vivo pvt ship s on lr
hboot 1.09.0000
Radio-38.02.01.17_m
eMMC-boot
Feb 11 2011 11:52:44
Click to expand...
Click to collapse
This method will only work if you have s-off, not s-on. You need to run AlphaRevX to gain s-off and then you can flash a new ROM.
Hi sorry for the confusion, I did S-OFF my device with AlphaRevX and installed CMW... I just copied and old txt file with the word S-ON on it.
Any ideas? By the way, what does CID stand for?
Excellent tutorial
This is beyond fantastic. I have had my phone in Hboot-Fastboot with a boot loop for 4 days and counting. It was so bad to the point where my GF was almost ready to buy me a new Sensation 4G off kijiji!
Regardless this is great news, I will try it out the minute I am home from work.
FINGERS CROSSED!
-----UPDATE-----
I followed the instructions front to back. Archived all of the ROM contects, made deletion of Hboot file in rom. Changed cid numbers. Renamed the archive as PG32IMG.zip after formatting my SD card. Went to hboot on my DincS, and it said image not found. Found it odd since it worked yesterday when I used a differend PG32IMG batch, it failed but it made it past the reading cycle before the update.
Any thoughts?
Hi guys
I really need your help here. Please
I've been able to:
S-Off using alpharevx.
Install CWM.
Root my device.
And even flash it with a Saskatel Froyo ROM.
I downloaded the OPTUS, Vigin and Europe ROMS, and every time tried flashing I get.
Model ID incorrect.
Then I found this thread
http://forum.xda-developers.com/showthread.php?t=1145541
Explaining this issue. I
unziped the files,
removed the booter file,
modified android.txt and added the lines described.
However, when I try flashing the ROM, I get a CID incorrect!!!!!!!!!
I really want to get GB, how do I overcome this?
@aresguerrero, is it really needed to double post?
Just loaded all files as described in tutorial. I am getting CID incorrect.
Just to clarify my Dincs is stuck in a bootloop. I have no backups, no custom firmware.
This is what my phone is showing:
---AlphaRev---
VIVO PVT SHIP S-OFF RL
HBOOT-1.09.1000
RADIO- 3005.04.03.22_M
cMMC-boot
Fed 11 2011, 11:52:44
HBOOT
CID incorrect!
Update Fail!
@ Thumper0G
I get the same CID Incorrect, the only ROM I've been able to flash is the one from Saskatel.
Keep me updated, I've looked a lot trying to find a solution.
Bye
aresguerrero said:
@ Thumper0G
I get the same CID Incorrect, the only ROM I've been able to flash is the one from Saskatel.
Keep me updated, I've looked a lot trying to find a solution.
Bye
Click to expand...
Click to collapse
Ran the RUU file and lost my S-OFF. so basically now im completely fugged!!!
Thumper0G said:
Ran the RUU file and lost my S-OFF. so basically now im completely fugged!!!
Click to expand...
Click to collapse
You are in the same boat I have been for two weeks now. If only Bell were to release their Gingerbread update and all problems would be avoided .
ClaudiuJer said:
You are in the same boat I have been for two weeks now. If only Bell were to release their Gingerbread update and all problems would be avoided .
Click to expand...
Click to collapse
Well here is the problem. I am stuck in a boot loop. Even though the RUU.exe says that the update has installed and my android is ready to use, I am still in a bootloop.
Yes this is awesome that the phone updated for once. PROBLEM> NO S-OFF and BOOTLOOP is still going on...
I am sooooo stuck.
NOW, here's a question. Would my phone be ok to send in for service now that the S-OFF is gone and it's back to S-ON or is my warranty no good.
Can I make a goldcard even though my droid is unusable?
if not can I use my gf's Incredible S. its the same phone, and carrier.
I've used this ROM to get gingerbread 2.3.
aresguerrero said:
Hi guys
I downloaded the OPTUS, Vigin and Europe ROMS, and every time tried flashing I get.
Model ID incorrect.
Then I found this thread
http://forum.xda-developers.com/showthread.php?t=1145541
Explaining this issue. I
unziped the files,
removed the booter file,
modified android.txt and added the lines described.
However, when I try flashing the ROM, I get a CID incorrect!!!!!!!!!
I really want to get GB, how do I overcome this?
Click to expand...
Click to collapse
@ ClaudiuJer
It occurs to me that:
You can get an XTC clip and get rid of the S-ON (Hardware)
Then flash the Saskatel 2.2 ROM as I did.
Hope that helps...
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
mbinic said:
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
Click to expand...
Click to collapse
I just went through this a couple days ago with someone
go here and read pages 2-5 and see if you understand or still have questions read it all before moving on
http://forum.xda-developers.com/showthread.php?t=2593387&page=2
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
mbinic said:
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
Click to expand...
Click to collapse
yes after the conversion to .401 you will have a EU device and can update and flash all the new roms as they come out.
make note of the 2 links posted about changing your MID / CID their important steps in the whole process
http://forum.xda-developers.com/showthread.php?t=2535365
this guide by @nkk71 is a good source of information your just doing a few things differently
http://forum.xda-developers.com/showthread.php?t=2541082
OK, so part one is going mostly smoothly for now - unlocked bootloader, flashed TWRP, backed up (uploading for sharing) + saved partitions for rumrunner if I end up needing them (also uploading), had a few bootloops but managed to get ARHD 31.6 running. Now onto rumrunner...
I got S-OFF with rumrunner in the first try! Now to re-read and change CID and MID (4:40 AM, fingers crossed, heart pounding)
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
mbinic said:
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
Click to expand...
Click to collapse
Almost
1- change you MID to PN071000 using the tool
2- with SuperCID you cannot receive OTAs, so you need to change CID to European unbranded, there are several (this will affect the country/language options): http://forum.xda-developers.com/showpost.php?p=48195855&postcount=98 (instructions are also in that post)
so for example, if you wanted Eastern European languages you would need to set CID to HTC__032
3- since you're on hboot 1.55, you need to downgrade that separately to 1.44
4- you can leave the phone UNLOCKED, and even TAMPERED, but if you prefer to set them LOCKED and remove TAMPERED you can follow my guide.
5- run the RUU you mentioned
6- KEEP S-OFF!!
OTAs will not be affected by unlocked bootloader, or S-Off
let me know if you need more details
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
mbinic said:
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
Click to expand...
Click to collapse
yep, that works!
don't want to confuse you , but 1 2 and 3 can be run in any order, most important is to do run the ruu as last step, once the ruu has completed you should immediately receive OTAs.
remember, stay S-Off, consider it your "get out of jail" card, in case you ever want to change something again.
Thanks again I'll try it in a couple of hours and report my progress.
Edit:
OK, got CID HTC__032 and changed MID successfully. AROMA hung at 0.00%, but a restart helped like it was described in the post. Now onto HBOOT and RUU.
Edit 2:
Installed HBOOT 1.44 and the Guru Bootloader reset - removed tampered and set locked (why not ). Running RUU in a few minutes...
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
mbinic said:
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
Click to expand...
Click to collapse
Congrats mate
Can you also edit main thread title to include [SOLVED], thanks
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
mbinic said:
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
Click to expand...
Click to collapse
4.4 (hopefully 4.4.2) not out yet for most, only US Dev Edition, and has a few "bad habits" for the rest of the world... no need to change CIDs, it'll come soon enough....
ARHD 41.0 and MaximusHD are based on the US Dev Edition, not the WWE edition.
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
my htc
mbinic said:
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
Click to expand...
Click to collapse
hi friends first my english is not so good so excuse me i a have some mistakes, then i want to say i was reading your experience, i got the same version of htc one HTC_332 this is the cid for latin america this is what htc supports tell me by email, ok i got a little questions maybe u can help me
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
for last i want to thanks for the time you take to anwer me
Hello edulaffont,
edulaffont said:
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
Click to expand...
Click to collapse
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
first
mbinic said:
Hello edulaffont,
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
Click to expand...
Click to collapse
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
edulaffont said:
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
Click to expand...
Click to collapse
I also got that update as soon as I bought the phone, some time in October/November I think, it's old.
I didn't change the firmware when I was converting to WWE, a .401 version wasn't out yet.
I did change it last night though, and installed ARHD 51 (it gives me more options than stock) and everything went smoothly (I even did a dirty flash).
Anyway, I recommend you stick to the original instructions (use old ARHD for rumrunner), and when you're done converting to WWE, ran the RUU and everything works you can choose wheter you want to get the OTAs and stay stock (KitKat 4.4.2 OTA for WWE just came out, with new firmware), or root and install any ROM you wish