Sorry for starting a new thread. I've looked but can't seem to find a straightforward answer. Sorry still noob.
I have a problem with my HTC Sensation Z710e- the Camera is not working
Solution: Send it to HTC since it is still under warranty.
Issue:
I am on S-ON, with HBOOT version 1.23.000, with a custom ROM. (Why I got S-ON with a custom ROM inside? Long story, believe me.)
Now, my Bootloader Screen says:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.23.0000
eMMc-boot
Dec. 26, 2011, 12:14:25
I have the following information:
Model number: HTC Sensation Z710e
Android version: 2.3.5
Software Number: Elegancia_1.4.5
Kernel version: 2.6.35.13-gc35910f
[email protected]#1
SMP PREEMPT Fri Sep 23 17:21:03 CST 2011
Baseband Version: 11.65.3504.00U_11.19.3504.29_2
Build Number: 2.08.401.1 CL168617 release-keys
ClockworkMod Recovery v.5.0.2.0
CID = HTC__J15
MID = PG5813000
First question:
"Will I be able to flash a Stock ROM so I can send it back for repairs?"
Second question:
Does anybody know what is the stock ROM for my phone based on the following information:
CID = HTC__J15
MID = PG5813000
Bought in Dubai, United Arab Emirates
Made in Taiwan
btw, would writing my IMEI compromise my phone security in any way?
I've tried the following ROMs and I got [ ERROR ]140: Bootloader Version Error, on all of them..
RUU_Pyramid_HTC_ARA_1.34.415.1_Radio_10.43a.9007.0 0U_10.51.9007.27_M3_release_197242_signed.exe
RUU_Pyramid_hTC_Asia_TW_1.35.709.1_Radio_10.43a.90 07.00U_10.51.9007.27_M3_release_198188_signed.exe
RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed.exe
I tried both in Bootloader and Lockscreen when I flash the RUU. [ ERROR ] 155 if its on Lockscreen. And yes, I've tried to flash when I was unlocked and then when I relock.
Third question:
Will I be able to remove the ***RELOCKED*** from the bootloader screen so that there will be no issues with warranty? How?
Or do I just bring my phone back to HTC and get it over with?
Thanks in advanced for the answers and sorry for the bother.
In this thread you can read how to S-ON it back. I would definitely S-ON it and flash official firmware+ROM before going to service. Considering RUU version, honestly I do not know, but I would try one of those:
RUU_Pyramid_hTC_Asia_TW_1.35.709.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198188_signed.exe
RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed.exe
Stock ROMs collection can be found here (link from this thread).
Is it possible to flash ASBS v3.0 ROM and HBoot 2.15 on my branded phone (*) ?
Should I change CID to HTC__001 or 11111111 ?
(*)
HTC One S
T-MOB101
HBOOT-1.14.0002
RADIO-1.09es.50.02.07_2
Android version : 4.0.4
HTC Sense version : 4.1
Software number : 2.38.111.10
Baseband version : 1.09es.50.02.07_2_10.09d.50.04L
Build number : 2.38.111.10 CL97613 release-keys
Bootloader unlocked
Rooted with SuperSU
ROM Stock
iangelo said:
Is it possible to flash ASBS v3.0 ROM and HBoot 2.15 on my branded phone (*) ?
Should I change CID to HTC__001 or 11111111 ?
(*)
HTC One S
T-MOB101
HBOOT-1.14.0002
RADIO-1.09es.50.02.07_2
Android version : 4.0.4
HTC Sense version : 4.1
Software number : 2.38.111.10
Baseband version : 1.09es.50.02.07_2_10.09d.50.04L
Build number : 2.38.111.10 CL97613 release-keys
Bootloader unlocked
Rooted with SuperSU
ROM Stock
Click to expand...
Click to collapse
Yes, you will need to flash wifi fix if available. If not then you will have no wifi at all.
Qs5 said:
Yes, you will need to flash wifi fix if available. If not then you will have no wifi at all.
Click to expand...
Click to collapse
Which Wifi fix ? You mean the wifi partitions ?
These are included in the Update firmware, aren't they ?
And what about CID ? Should I change it to HTC__001 or 11111111, or it doesn' t matter ?
Hi,
I have to take my phone back to warranty due to camera problems and I have to get it back to stock.
I have: CID HTC_102
HBOOT: 3.01.000
Android 4.1.1
ROM: ViperC2 3.1.3
Baseband version: 16.22.20.03U_16.11.20.24_M
Build number: 3.19.401.101
The problem is that I cant use the RUU: RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe since this is older that what I currently have.
I can also get the OTA zips fro http://forum.xda-developers.com/showthread.php?t=2200930 but I do not know how to install OTA zip in a way as RUU to get it back to stok.
Please help!
Cheers,
MR
hi - I'm referring to the firmware, not an RUU or OTA.
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.
Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.
sandys1 said:
Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.
Click to expand...
Click to collapse
The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.
Brightstar 5.13.1540.2:
Kernel: 3.4.10-gefd4656
hboot: 2.18.0000
radio: 1.34a.32.45.21_10.142.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.020
sbl1: 001.138.004
sbl2: 001.138.009
sbl3: 001.138.007
T-Mobile 5.08.111.2:
Kernel: 3.4.10-g08ef01e
hboot: 2.15.0000
radio: 1.31a.32.45.16_2_10.141.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.019
sbl1: 001.138.003
sbl2: 001.138.007
sbl3: 001.138.005
twistedddx said:
The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.
Click to expand...
Click to collapse
Thanks for that !
Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
Thanks again...
sandys1 said:
Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
.
Click to expand...
Click to collapse
Ensure s-off and supercid first.
You could create your own unofficial firmware.zip like Turge did that includes some img's that the OTA you are installing may be missing. I think the following will be easiest though.
Ensure 3.17/3.18 complete firmware or better as base is installed on phone, eg 3.18 RUU or previously updating to 3.xx/5.xx officially with HTC OTA. This can be skipped if you are certain you have already installed this or Turges 5.08.111.2 firmware.
Download T-Mobile 3.17.111.1 OTA (or similar complete 3.17/3.18):
http://fotadl.htc.com/OTA_EVITA_UL_...129.32.34a_release_300591m6ejdlmoq874n7fw.zip
Open zip, extract firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot
If this step is not done you run a higher risk of the device being bricked in the update.
I would suggest reboot to ensure firmware is completely written to device before moving to next firmware.zip package.
Download Brightstar 5.13.1540.2 OTA:
http://fotadl.htc.com/OTA_EVITA_UL_....17.1540.4_release_342737ulobjpm2t4w05mnr.zip
Open zip, extract firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot
NOTE: HTC official firmware.zip includes boot.img and recovery.img. You will need to reinstall custom recovery and your installed ROMs matching boot.img.
NOTE #2: CM install scripts do not include hboot 2.18 (it includes 2.14, 2.15, 2.16 and 2.17). You would need to hand edit the updater-script for such ROM's to get them to install.
NOTE #3: The above instructions account only for the software versions listed above. Do not assume these instructions can be used for past or future firmware.zip files obtained from past/future OTA. You must always account for the fact OTA expects your phone to already be functional with a particular previous software version. OTA firmware.zip typically does not include files that are expected to already be installed on the device. Updating from unexpected software versions will likely end in a bricked phone. Whereas RUU files contain complete firmware.zip.
What is the reason for wanting the "latest" firmware? I haven't been following CM11 closely (so maybe I'm missing something here), but in general the AOSP ROMs don't require the "latest" firmware, its just the Sense 5 ROMs that act wonky if your firmware (probably radio in particular) is outdated.
So unless I'm missing something, it seems like you are going through a lot of extra work and risk of bricking the phone for no real reason. If you don't do the steps exactly right as twistedddx listed them, you run a high risk of instantly bricking the device (and the only way back is JTAG). In particular, if you don't update the hboot modules correctly (sbl1, 2, and 3 all need to be compatible), its a brick.
I agree with Redpoint, there's absolutely no benefit to flashing this firmware, only risk, unnecessary risk.
Sent from my Evita
sandys1 said:
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.
Click to expand...
Click to collapse
2.15 is not technically a firmware number. Its just been often posted here "2.15 firmware" as a sort of shorthand for "the firmware modules that came with hboot 2.15". Each module has different numbers (tz, sbl1, etc.), as twistedddx posted in Post #2 above. Checking the number for each module is the only way to check for what is "latest".
Hello
Does anyone tell me which file is good for my s-on phone ? [http://androidruu.com/?developer=Ville]
HBOOT 2.15.0000
RADIO 1.11.50.05.28
CID HTC_032
Baseband version: 1.11.50.05.28_10.27.50.08L
I tried RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 but i received "FAILED <remote:42 custom id check fail>
By the way does someone could send me signed boot.img for JB ROM (my universal extractor make corrupted files ) ?