Database Develop

[GUIDE] Install any Gingerbread RUU on Canadian IS!

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...

Sensation Xl bricked

Hi. I have a htc sensation xl, and i did unlock the bootloader after that i installed CWM and a custrom rom... it worked a few day but one day my phone simply died, it switched off when i was brawsing the web, and now it only comes on shows the htc logo and vibrates 6 times fast... and ramanis that way!
I can get into bootloader and fast boot but i canot enter recovery... i did flash recovery again using adb but the same...
i have tryed to flash a ruu but at the end i get a error 155 and the phone remains the same...? any ideas what my phone has?
Sorry for my bad english!

When you installing RUU, phone must be in fastboot mode and bootloader must be locked.
Possible that damaged the memory (RAM) on the motherboard.
Try flash RUU for you country like i said. We will see.

sorry for my question... how do i lock the bootloader? and where do i find a ruu for cid HTC__Y13

slave2anubis said:
sorry for my question... how do i lock the bootloader? and where do i find a ruu for cid HTC__Y13
Click to expand...
Click to collapse
Put phone in fastboot mode.
PHP:
Power + Vol down
Connect to PC.
Go to SDK Android Tools.
PHP:
*:\Program Files\Android\android-sdk\platform-tools
PHP:
shift + right click=Open cmd
In cmd type:
PHP:
fastboot oem lock
In this topic:
[ROM]Runnymede Shipped ROM Collection

well i did what you sad, the bootloader says "relocked" i am tryng to download a ruu for sensation xl europe i hope i cand flash it...
if not i read here on the forum that i can modify a file inside the ruu and make it accept a diferent cid...

slave2anubis said:
well i did what you sad, the bootloader says "relocked" i am tryng to download a ruu for sensation xl europe i hope i cand flash it...
if not i read here on the forum that i can modify a file inside the ruu and make it accept a diferent cid...
Click to expand...
Click to collapse
Yep but you need to make S-OFF.
Europe CID
PHP:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__304
cidnum: HTC__032
Than will be work

well that is kinda not posibile at the moment is that right? hope the ruu will work and restore my phone to former glory, if that fails do you have any ideea what i can try to make it run?

slave2anubis said:
well that is kinda not posibile at the moment is that right? hope the ruu will work and restore my phone to former glory, if that fails do you have any ideea what i can try to make it run?
Click to expand...
Click to collapse
Your CID is from Europe. Than EU RUU will be working.
S-OFF is avible not Radio S-OFF but is working nice to install without checking CID/SuperCID

well i did install the ruu and it worked this time, now my phone is kikig strong! thanx again for the support!

slave2anubis said:
well i did install the ruu and it worked this time, now my phone is kikig strong! thanx again for the support!
Click to expand...
Click to collapse
Nice to hear

htc sensation xl
i have unlocked the bootloader and installed 4ext , twrp recovery and whats next

HTC desire C back to stock help please

Hi i am trying to get my phone HTC desire C back to stock from Slim-Sense-v1 i downloaded CID getter from the playstore and found i have htc_001 but cant seem to find the latest ruu for it anywhere
tried the various methods on these forums however non have been successful i managed to unlock and flash using Desire_C_All-In-One_Kit_v1.0 so im a complete noob to these but would greatful if some kind chap would be able to help me .

wub901 said:
Hi i am trying to get my phone HTC desire C back to stock from Slim-Sense-v1 i downloaded CID getter from the playstore and found i have htc_001 but cant seem to find the latest ruu for it anywhere
tried the various methods on these forums however non have been successful i managed to unlock and flash using Desire_C_All-In-One_Kit_v1.0 so im a complete noob to these but would greatful if some kind chap would be able to help me .
Click to expand...
Click to collapse
www.htcruu.com - look for Golf
Thats where you can find everything you need.

been there done that
yep ive been there downloaded two ruu,s and tried all the steps mentioned from about 4 tutorials and still no luck
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
are the two i tried but they didnt work tried flash the system.img but that was too big according to cmd prompt

wub901 said:
yep ive been there downloaded two ruu,s and tried all the steps mentioned from about 4 tutorials and still no luck
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
are the two i tried but they didnt work tried flash the system.img but that was too big according to cmd prompt
Click to expand...
Click to collapse
Install it from pc.
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app

hutchinson epgoice
SO im g uessing nobody knows how to return this phone to stock ?

wub901 said:
SO im g uessing nobody knows how to return this phone to stock ?
Click to expand...
Click to collapse
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app

PopaStefanx said:
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
Click to expand...
Click to collapse
Erm i h ave s on as there isnt a way to turn it off i have tried using the tutorials i have tried installing boot.img rocovery.img which goes fine but when i try to install the system.img through adb it tells me the files is too large
i have tried relocking the bootloader which works and using RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_1 0.11.98.09_1.06.98.13M2_release_265825_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10. 11.98.09H_1.06.98.13M2_release_295101_signed
and they both tell me that they are the wrong version and give me an error

PopaStefanx said:
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
Click to expand...
Click to collapse
Clearly Mr Spark here should read deeper into the forum for this device, ^__^ No S-Off im afraid.
wub901 said:
Erm i h ave s on as there isnt a way to turn it off i have tried using the tutorials i have tried installing boot.img rocovery.img which goes fine but when i try to install the system.img through adb it tells me the files is too large
i have tried relocking the bootloader which works and using RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_1 0.11.98.09_1.06.98.13M2_release_265825_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10. 11.98.09H_1.06.98.13M2_release_295101_signed
and they both tell me that they are the wrong version and give me an error
Click to expand...
Click to collapse
I found that happened with me, have you tried to let it run through the standard way of installing the software instead if using CMD based commands?

a reasonably intelligent reply would be nice seeing as i have tried installing t he ruu from a pc seeing as its an exe file!

wub901 said:
a reasonably intelligent reply would be nice seeing as i have tried installing t he ruu from a pc seeing as its an exe file!
Click to expand...
Click to collapse
Hey a little respect here.... I can understand that trying to restore to stock and it not going your way it can be stressful and frustrating.
When troubleshooting , you have to make sure you do everything to try and find the resolution
Im sorry bud, but when it comes to restoring to stock, we are a bit unlucky at the moment, some devices will go back, some wont.
Why do you want to go back to stock?

because i am trying to sell the phone i have tried the guide you have mentioned i have tried fastboot boot.img and recovery.img and relocking bootloader and then running the ruu and get a wrong version error i have tried changing from slim sense v1 to nameless and then unlocking bootloader and reflashing the boot & recovery.img and still not joy.
i have tried fastboot flashing the system.img but get that it is too large the ruu,s that i have used are RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
i got this phone from phones4u my hboot is 128.0000 and my radio is 1.06.98.13M2

error 130 model id error
ok so tried installing recovery.img worked
using nameless rom v7
removed supersu
relocked bootloader following fkofilee,s guide and get error 130 model id error from both ruu files

wub901 said:
because i am trying to sell the phone i have tried the guide you have mentioned i have tried fastboot boot.img and recovery.img and relocking bootloader and then running the ruu and get a wrong version error i have tried changing from slim sense v1 to nameless and then unlocking bootloader and reflashing the boot & recovery.img and still not joy.
i have tried fastboot flashing the system.img but get that it is too large the ruu,s that i have used are RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
i got this phone from phones4u my hboot is 128.0000 and my radio is 1.06.98.13M2
Click to expand...
Click to collapse
who are you trying to sell it too?

to a shop who most probably wont buy it with a custom rom on it

wub901 said:
to a shop who most probably wont buy it with a custom rom on it
Click to expand...
Click to collapse
They will, they mostly wont check ha, my advice to you is (After having the same problem) Install a Custom Rom That Isnt Like Nameless Or Has A Custom boot Animation That Appears To Obvious.

Yeah thats an idea but its not really solving my problem of getting it back to stock is it ?
anyway i was having a google and thought i may work putting the rom file on the sd card and renaming the zip to PL01IMG.zip well hboot read the file and checked it then gave me a model id error so is there anyway i can change the model id in to ruu zip to match the phone ?

wub901 said:
Yeah thats an idea but its not really solving my problem of getting it back to stock is it ?
anyway i was having a google and thought i may work putting the rom file on the sd card and renaming the zip to PL01IMG.zip well hboot read the file and checked it then gave me a model id error so is there anyway i can change the model id in to ruu zip to match the phone ?
Click to expand...
Click to collapse
If the cid doesn't match it won't let you do it and there's no way of changing it. There is another way tho you could extract the Rom.zip from the ruu get the system and boot img and use the android kitchen to build it into a flashable zip then use cwm to flash back to stock then just flash back the stock recovery.
Sent from my HTC Desire C using xda app-developers app

andrewtjb said:
If the cid doesn't match it won't let you do it and there's no way of changing it. There is another way tho you could extract the Rom.zip from the ruu get the system and boot img and use the android kitchen to build it into a flashable zip then use cwm to flash back to stock then just flash back the stock recovery.
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
ok the cid id HTC_001 which is in the android-info.txt of the rom
modelid: PL0110000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__016
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__A48
hbootpreupdate:13
mainver: 1.45.401.4
DelFat:1
DelCache: 1
but there must be a way to change to model id of the zip file to match the phone surely as for android litchen il give that a go what would be good is if we had a stock ROM we could just flash through CWM then just flash the boot and recovery .

wub901 said:
ok the cid id HTC_001 which is in the android-info.txt of the rom
modelid: PL0110000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__016
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__A48
hbootpreupdate:13
mainver: 1.45.401.4
DelFat:1
DelCache: 1
but there must be a way to change to model id of the zip file to match the phone surely as for android litchen il give that a go what would be good is if we had a stock ROM we could just flash through CWM then just flash the boot and recovery .
Click to expand...
Click to collapse
Not That simple my friend, sorry , ive tried to do everything to my old desire C , and it didnt work.

oh guys,come on, i say somebody should make a backup on CWM,of his original stock,upload it on the net,and everybody who wants a original stock can get it
Sent from my HTC Desire C using xda premium

[Q] can i flash KITKAT update for S-ON

Hi all, i have Unlocked HTC ONE, and didn't receive the OTA KITKAT update , cause my phone form UAE HTC__J15 (mea)
i don't need to loose my warranty, but i need to flash the KITKAT update manually
any way to do it without root, S-off or UNLOCKED
thank you very much

moha_moha20106 said:
Hi all, i have Unlocked HTC ONE, and didn't receive the OTA KITKAT update , cause my phone form UAE HTC__J15 (mea)
i don't need to loose my warranty, but i need to flash the KITKAT update manually
any way to do it without root, S-off or UNLOCKED
thank you very much
Click to expand...
Click to collapse
1- on the M7, HTC__J15 is just another unbranded international WWE edition (.401.)
2- post your "fastboot getvar all" (excluding IMEI and s/n) (because you could have a PN071000 or PN0711000 model)
3- what ROM are you on

nkk71 said:
1- on the M7, HTC__J15 is just another unbranded international WWE edition (.401.)
2- post your "fastboot getvar all" (excluding IMEI and s/n) (because you could have a PN071000 or PN0711000 model)
3- what ROM are you on
Click to expand...
Click to collapse
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno: ************
INFOimei: **********
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3916mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bb768ae1
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.046s

moha_moha20106 said:
C:\ADB>fastboot getvar all
INFOversion-bootloader: 1.55.0000
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
finished. total time: 0.046s
Click to expand...
Click to collapse
1- please edit your post and remove IMEI
2- it's just a standard .401. UL edition
3- what ROM are you on
4- what ROM do you want to be on
5- have you considered S-Off, or is that something you do not want to attempt
EDIT: and what recovery do you have?

nkk71 said:
1- please edit your post and remove IMEI
2- it's just a standard .401. UL edition
3- what ROM are you on
4- what ROM do you want to be on
5- have you considered S-Off, or is that something you do not want to attempt
EDIT: and what recovery do you have?
Click to expand...
Click to collapse
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM

moha_moha20106 said:
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM
Click to expand...
Click to collapse
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.

nkk71 said:
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.
Click to expand...
Click to collapse
Bro, the updates are coming from the HTC MEA region. The MEA region hasn't rolled out the update. So, its impossible to officially get the update. Even though its an unbranded one, the J_15 wont get it unless MEA rolls it out

nkk71 said:
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.
Click to expand...
Click to collapse
yes i was mean Unlocked (unbranded), and my bootloader is still LOCKED
i was found this post http://forum.xda-developers.com/showthread.php?t=2224752
and i don't know what the different between Odexed and De-Odexed , what it's mean
thank you

moha_moha20106 said:
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM
Click to expand...
Click to collapse
Officially, without rooting or any similar procedure, its sadly impossible. I live in Dubai. Im on ARHD 52. Couldn't wait for the delay
HTC MEA facebook page says update will arrive 'very soon'. Im guessing 2-3 weeks more sadly

raghav kapur said:
Officially, without rooting or any similar procedure, its sadly impossible. I live in Dubai. Im on ARHD 52. Couldn't wait for the delay
HTC MEA facebook page says update will arrive 'very soon'. Im guessing 2-3 weeks more sadly
Click to expand...
Click to collapse
welcome dear, i hate waiting for the OTA update, about months waiting, they are announced for this update about last Nov. 2013, they was told us about this update : The HTC ONE Users can receive this OTA update in the first week of the new year, now it's 14-Mar and no update for MEA users
hate them all

moha_moha20106 said:
yes i was mean Unlocked (unbranded), and my bootloader is still LOCKED
i was found this post http://forum.xda-developers.com/showthread.php?t=2224752
and i don't know what the different between Odexed and De-Odexed , what it's mean
thank you
Click to expand...
Click to collapse
No don't do that!!
raghav kapur said:
Bro, the updates are coming from the HTC MEA region. The MEA region hasn't rolled out the update. So, its impossible to officially get the update. Even though its an unbranded one, the J_15 wont get it unless MEA rolls it out
Click to expand...
Click to collapse
Yes bro, I do think I understand that, but, looky here:
Code:
[B][COLOR="Blue"]modelid: PN0710000[/COLOR][/B]
cidnum: HTC__001
[B][COLOR="Blue"]cidnum: HTC__J15[/COLOR][/B]
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
[B][COLOR="Blue"]mainver: 4.19.401.8[/COLOR][/B]
btype:1
aareport:1
hbootpreupdate:3
and yes, that's the official OTA, which can be applied manually using stock recovery if coming from 3.62.401.1 (without unlocking or anything).
BUT: if that's not the update HTC is going to push for J15, then any OTAs after that will very likely no longer work.
so OP, if you want my personal opinion, just wait for it to be released officially.

nkk71 said:
No don't do that!!
Yes bro, I do think I understand that, but, looky here:
Code:
[B][COLOR="Blue"]modelid: PN0710000[/COLOR][/B]
cidnum: HTC__001
[B][COLOR="Blue"]cidnum: HTC__J15[/COLOR][/B]
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
[B][COLOR="Blue"]mainver: 4.19.401.8[/COLOR][/B]
btype:1
aareport:1
hbootpreupdate:3
and yes, that's the official OTA, which can be applied manually using stock recovery if coming from 3.62.401.1 (without unlocking or anything).
BUT: if that's not the update HTC is going to push for J15, then any OTAs after that will very likely no longer work.
so OP, if you want my personal opinion, just wait for it to be released officially.
Click to expand...
Click to collapse
Ok Bro, sadly to wait...
thanks so much

[Q] RUU ver. 7.21.707.35

I would like to request for anyone who has a link for the RUU with the following details:
version-main: 7.21.707.35
modelid: PN0714000
cidnum: HTC__044
I already tried to search here at xda but kept on finding a lower version. please help. thanks in advance!

fvx12 said:
I would like to request for anyone who has a link for the RUU with the following details:
version-main: 7.21.707.35
modelid: PN0714000
cidnum: HTC__044
I already tried to search here at xda but kept on finding a lower version. please help. thanks in advance!
Click to expand...
Click to collapse
There is no RUU for this version yet (maybe never, who knows)
You'll have to achieve s-off and flash the 7.21.707.21 ruu or use custom roms

thanks for the reply.
im planning to install 'Android_Revolution_HD-One_92.0_4a9d05' to my device. is it compatible with my htc one?

fvx12 said:
thanks for the reply.
im planning to install 'Android_Revolution_HD-One_92.0_4a9d05' to my device. is it compatible with my htc one?
Click to expand...
Click to collapse
Yes it should work fine, just make sure you flash it using a recent twrp version (2.6.3.3 or above)

Thanks alray, i am now able to use my phone after several days.