After doing a OTA upgrade from GB to HC my Flyer ended up with an error. It was s-off before this and working fine. I can not run ADB commands, boot up, run revolution, install from sd card, run recovery, htc unlock or fastboot commands. It only boots into fastboot and installing an RUU also ends in an error. Some fastboot commands is working but whatever I do I get Signature error, Bootloader error or FAILED (remote: signature verify fail). My getvar looks like this:
C:\Data\Android\Adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.10.0000
INFOversion-baseband: 3809.05.04.10_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.55.1114.31
INFOserialno: HT15SJN00865
INFOimei: 355195000000017
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4140000
INFOcidnum: HTC__Y13
INFObattery-status: good
INFObattery-voltage: 3843mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader:
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.031s
Can someone please give me a hand?
run the hc soff ruu posted in development by globatron. should do the trick .
Already tried that. It starts with: Run revolutionary and I cannot do that. I am at S-ON now. If I try to just run the RUU it fails!
Other things I can try?
if you were s off prior to attempting to upgrade you should not have been able to change the hboot version via standard update and you would be left with a gb s off hboot and a hc system. looking back at your post it appears you have a s on hc hboot but a system that wont boot. When you try to run the globatron soff ruu it would fail becasue you are s on. I am guesing since your system has been updated to hc when you attempt to run your stock ruu you are failing because the misc version is older in the ruu you are attempting.
I am kinda guesing here as to my understanding if you were s off prior you should still be s off, but maybe try to htc dev unlock. then flash recovery to your device. once recovery is installed you should be able to change you misc version following steps listed in globatrons downgrade from hc leak thread. After you change the misc version you would need to relock your hboot then attempt the stock ruu again.
try extracting the zip from the ruu and run these commands:
fastboot oem lock
fastboot erase cache
fastboot rebootruu
fastboot flash zip (filename)
Run the Honeycomb RUU, then proceed with the downgrade instructions.
I have tried all that and none of it is working. Some of it runs, but ends with an error like Signature error, Bootloader error or FAILED (remote: signature verify fail). I guess I'm stuck with a brick?
globatron said:
Run the Honeycomb RUU, then proceed with the downgrade instructions.
Click to expand...
Click to collapse
Finally. I found the correct RUU to download and then the installation finished without errors. Thanx alot !!
Related
Please pay special attention to the "health warnings" This is NOT a general user procedure.
WIFI and WIFI + 3G flyer
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
C:\tools>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.11.0006
INFOversion-baseband: 3821.08.00.26_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.10.405.1
INFOserialno: HT15AT403150
INFOimei: 354672040203497
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__Y13
INFObattery-status: good
INFObattery-voltage: 3843mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 60a0efb2
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.025s
Much appreciated
try rebooting to android BrumBrum74, it looks like it's done, you have the new radio and VersionMain
I was not able to apply the point "Yes" in the unlock menu so i flashed a RUU and am back on Ship S-Off.
Scabes24 said:
Much appreciated
Click to expand...
Click to collapse
NP mate, I should have done that from the start tbh.
nickiberli said:
I was not able to apply the point "Yes" in the unlock menu so i flashed a RUU and am back on Ship S-Off.
Click to expand...
Click to collapse
on which hboot nickiberli?
globatron said:
try rebooting to android BrumBrum74, it looks like it's done, you have the new radio and VersionMain
Click to expand...
Click to collapse
Stuck on the white screen with green htc letters.
I was on S-OFF revolution way and managed to flash the rom before following your steps. Was stuck on the same place then before flashing the hboot.
BrumBrum74 said:
Stuck on the white screen with green htc letters.
Click to expand...
Click to collapse
BrumBrum, install teamviewer and send me the details in a PM.
I really can't tell what way things are and this way takes too much time.
After unlocking bootloader - can i runn ruu simply ? Or unlock and then run rru and then flash new Hboot ? will this do ?
Also help me how to run DD command??
globatron said:
BrumBrum, install teamviewer and send me the details in a PM.
I really can't tell what way things are and this way takes too much time.
Click to expand...
Click to collapse
Thanks.
PM sent.
Can anyone, who installed the new hboot and the new rom type "mount" in adb shell and post the output here?
thx
BrumBrum74 said:
Thanks.
PM sent.
Click to expand...
Click to collapse
Thanks so much for these instructions. Seem to be having exactly the same issues as Brumbrum74. If either of you guys could share what you do to resolve it when you're done, that'd be ace.
Thanks.
error to 12
12 Run the following commands
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
log:
sending 'zip' (529282 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
I downloaded the file 3 times rom.zip.
------
info HTC FLYER
*UNLOKED*
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0850
RADIO-3821.08.00.26_M
Neaw - a couple of us have this issue. The OP is checking it out on Brumbrum76's machine now
Mh, until now only globatron was lucky with this method? Strange...
@globatron
In which state (ROM, hboot, S-OFF, ...) was your Flyer before you make the update to HC?
This method failed (like everyone else.).
If I download a RUU and run it and install it, will it go back to normal hboot like it was before? Or am I stuck until some fixes this?
Edit: And most importantly, will it boot?
I flashed the 2.00 flyer 3g RUU and it worked. Now i can get S-off again with revolutionary.
I got into the screen where it shows "HTC" on a black background.. then I downloaded a wifi ruu. I ran it, and when it tries to update it fails. Is there anyway to reboot into recovery or get a RUU working? I have to leave somewhere and need my Flyer - all help is greatly appreciated.
Go in to fastboot and run the RUU on the PC.
it worked for me like this..
Hi,
I really need help with my bricked Flyer.
I tried to install honeycomb on my Flyer followed the process described in the link below:
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Now, I ended up with a working CM, new and UNLOCKED bootloader, and new radio, S-ON **but** device turns on to white HTC screen and stays on that state.
I tried to revert to genuine GB rom followed the process on this post:
http://forum.xda-developers.com/showthread.php?t=1257909
And now current device state is:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT- 1.11.0006
MICROP- 0850
RADIO- 3821.08.00.26_M
eMMC-boot
I tried to RUU fastboot method using rom.img from RUU_Flyer_HC_S_HTC_WWE_3.10.405
And ended up with error 132 (signature issue)
I also tried to flash PG41IMG.zip (pulled out of RUU_Flyer_HC_S_HTC_WWE_3.10.405) using goldcard without success- same signature issue (wrong product ID)
Curent state- no ADB, no CM, only fast boot works...
I would appreciate any help getting back to a working Flyer.
Thanks!
motman said:
Hi,
I really need help with my bricked Flyer.
I tried to install honeycomb on my Flyer followed the process described in the link below:
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Now, I ended up with a working CM, new and UNLOCKED bootloader, and new radio, S-ON **but** device turns on to white HTC screen and stays on that state.
I tried to revert to genuine GB rom followed the process on this post:
http://forum.xda-developers.com/showthread.php?t=1257909
And now current device state is:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT- 1.11.0006
MICROP- 0850
RADIO- 3821.08.00.26_M
eMMC-boot
I tried to RUU fastboot method using rom.img from RUU_Flyer_HC_S_HTC_WWE_3.10.405
And ended up with error 132 (signature issue)
I also tried to flash PG41IMG.zip (pulled out of RUU_Flyer_HC_S_HTC_WWE_3.10.405) using goldcard without success- same signature issue (wrong product ID)
Curent state- no ADB, no CM, only fast boot works...
I would appreciate any help getting back to a working Flyer.
Thanks!
Click to expand...
Click to collapse
if you have RELOCKED, You can try your original PG41IMG.zip (GB) with Goldcard
Yeah, I made a goldcard but the problem is that the base version installed on my Fiyer is Wifi_1.36.1540.32 and I can not find this version's RUU file anyware... Am I scr**ed? or is there any way to get this RUU file?
motman said:
Yeah, I made a goldcard but the problem is that the base version installed on my Fiyer is Wifi_1.36.1540.32 and I can not find this version's RUU file anyware... Am I scr**ed? or is there any way to get this RUU file?
Click to expand...
Click to collapse
It seems you made your goldcard incorrect.
I created a new goldcard and confirmed that I made it correctly, copied 41IMG.zip from another WIFI rom but still no go... I'm getting CID incorrect error on HBOOT
motman said:
I created a new goldcard and confirmed that I made it correctly, copied 41IMG.zip from another WIFI rom but still no go... I'm getting CID incorrect error on HBOOT
Click to expand...
Click to collapse
have you branding Version? if yes: it can be image name is different. For example on my Flyer: IMG41DIAG.zip
No, this Flyer was purchased unbranded in BestBuy- US. I guess that the only free solution will be with 1.36.1540.32 RUU version which can not be found anywhere :-(
motman said:
No, this Flyer was purchased unbranded in BestBuy- US. I guess that the only free solution will be with 1.36.1540.32 RUU version which can not be found anywhere :-(
Click to expand...
Click to collapse
You can control your cid with
fastboot getvar cid
viera77 said:
You can control your cid with
fastboot getvar cid
Click to expand...
Click to collapse
Thanks!
I'll try fastboot getvar cid option next week and post my results.
OK, here are the results:
'fastboot getvar all' command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0006
(bootloader) version-baseband: 3821.08.00.26_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0850
(bootloader) version-main: 1.36.1540.32
(bootloader) serialno: HT15JJN00515
(bootloader) imei: 35519**********
(bootloader) product: flyer
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4140000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3674mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 60a0efb2
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Now, running this command:
fastboot oem writecid 11111111
Gives me the following error:
(bootloader) [ERR] Command error !
OKAY [ 0.016s]
finished. total time: 0.016s
What should I do next?
I'm echoing your cry for help. I'm in EXACTLY the same position. SOMEONE PLEASE HELP!
Managed to upgrade to HoneyComb
I managed to unbrick my flyer by redo all HoneyComb process using the link in my first post.
All of this could not happen without using the unlock_code.bin file I originally received from HTC to unlock the bootloader again! I used 'fastboot flash unlocktoken Unlock_code.bin' command then flashed the new CM recovery menu then HC custom rom zip file via CM.
The only step I could not bypass is S-ON due to a newer Hboot version (1.11.0006) which is not supported by Revolutionary yet.
I can live with that although I'm not able to downgrade to stock rom, my CID is still BS_US001. I wish I knew how to revert to the older supported Hboot in order to S-OFF.
I hope that helps.
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
s-on is required for unlocking bootloader, s-off will go to disclaimer screen but wont respond if yes is selected, it will only say ***unlock*** (which it must, but it wont be truly unlocked, your phone needs to respond when selecting yes and MUST restart, if you need to remove battery, it wont be unlocked.
***Problem***: now I had s-off and ***LOCKED*** so I ran fastboot oem writesecureflag 3 to get s-on, unlocked through htcdev and heres the big problem:
Now:
***UNLOCKED***
HBOOT 1.49.0007 S-ON (RH - i think)
Cant change CID, flash recovery, doesnt read PG86IMG files, cant flash anything through fastboot, cant run RUU because of error 132 (signature error).
After trying to change CID with:
fastboot oem writecid HTC__621
Result =
gave a few errors
cidnum = 0202 ...???
Have hboot 1.49.0007, can unlock relock bootloader, have functioning ICS rom
fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.20.401.2
INFOserialno: HT23NV200556
INFOimei: 352647050653635
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG863****
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 5785mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.510s
so please help... any1...
cybergurken said:
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
Click to expand...
Click to collapse
You should not have done that.
Also, if you are S-Off that is really all that matters. There is not really any reason to unlock the Bootloader. If you were S-Off and wanted to have an unlocked bootloader you should have just found a hboot like the revolutionary one or engineering and flashed PG86IMG.zip and that would have given you Unlocked and S-Off.
For the most part, you never want to do the fastboot oem writesecureflag 3.
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Thnx 4 responding
mnomaanw said:
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Click to expand...
Click to collapse
Hi, no offence taken...
However, Im still a newbie @ all of this, however, I might be wrong but 3 q's
1. Why would it hang on the "yes" option
2. If I pull out baattery, it says ***unlocked*** but I have no access to recovery, even after custom recovery flash in fastboot, it cant/wont/doesnt boot into recvoery @ all, ref. "my other posts", why would that happen
3. What is the real difference between unlocking bootloader, and s-oof, I have read many posts and I figured getting both would be on the safe side...
and lastly, xd, why would a bootloader not read/detect a PG86IMG file, that is also another problem,
Once again, tnks very much
Hi i need some help about "HTC Desire X PROTO" s-off,is it possiable???
my info is here
Code:
****UNLOCKED*****
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
emmc-boot
apr 22 2013,14:28:51:0
http://forum.xda-developers.com/showthread.php?t=2630531
xpirt
xpirt said:
http://forum.xda-developers.com/showthread.php?t=2630531
xpirt
Click to expand...
Click to collapse
Thanks for your Replay,But it can not help me,Actually My phone is not fully power ON,it is Only on Boot Screen,i can use only Fastboot.
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.20.0000
INFOversion-baseband: 1.10.40.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.00.000.0
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT2A1LY11239
INFOimei: 358835041573301
INFOmeid:
INFOproduct: proto
INFOplatform: HBOOT-8225
INFOmodelid: PM6610000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-f3c065d3
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.010s
How is it possible to have two different hboot
Post #1 :
HBOOT-1.25.0002
RADIO-1.15.40.04
Post #3 :
INFOversion-bootloader: 1.20.0000
INFOversion-baseband: 1.10.40.23
How to help without a proper/correct info ?
If it is 1.20.0000 you can simply solve your problem with a RUU.
ckpv5 said:
How is it possible to have two different hboot
Post #1 :
HBOOT-1.25.0002
RADIO-1.15.40.04
Post #3 :
INFOversion-bootloader: 1.20.0000
INFOversion-baseband: 1.10.40.23
How to help without a proper/correct info ?
If it is 1.20.0000 you can simply solve your problem with a RUU.
Click to expand...
Click to collapse
SORRY IT WAS MISTAKE FROM MY SIDE,THE ACTUAL IS
Code:
****UNLOCKED*****
PROTO PVT SHIP S-ON RL
HBOOT-1.20.0000
RADIO- 1.10.40.23
emmc-boot
apr 22 2013,14:28:51:0
ITS THE CURRENT POSITIN OF MY PHONE BUT BEFORE IT WAS
Code:
****UNLOCKED*****
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
emmc-boot
apr 22 2013,14:28:51:0
Actually it was caused after JTAG Rpairer,it was wrking well,i was trying to reapier IMEI and S-OFF with JTAG BOX,but now its only on BOOT Screen,i tr different types of RUU it always give me error "158" or "155".i try the following RUU
Code:
PM66IMG_PROTO_DUG_ICS_40A_HTCCN_CHS_CU_1.00.1402.8_R_Radio_10.11.45D.02_2M_10.20.45.26U_release_293272_signed
ruu_proto_u_ics_40a_htc_asia_wwe_1.14.707.1_radio_10.18.40.05u_1.09.45.201_release_284720_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed
APPLE-LINKS said:
i tr different types of RUU it always give me error "158" or "155".
Click to expand...
Click to collapse
Error 155 usually means the bootloader is not relocked before run the RUU.
For your case, you only can use the ruu_proto_u_ics_40a_htc_asia_wwe_1.14.707.1_radio_10.18.40.05u_1.09.45.201_release_284720_signed.exe because your hboot now is 1.20.0000 and CID HTC__044
So, what you need to do is :
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
ckpv5 said:
Error 155 usually means the bootloader is not relocked before run the RUU.
For your case, you only can use the ruu_proto_u_ics_40a_htc_asia_wwe_1.14.707.1_radio_10.18.40.05u_1.09.45.201_release_284720_signed.exe because your hboot now is 1.20.0000 and CID HTC__044
So, what you need to do is :
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Click to expand...
Click to collapse
sorry for avian mistake,actually i could not post the full info afterJTAG repair,actually i reset cid to super cid,plz if you dont mind again give a look to my situation,what things are necessary to me.
thanks
Code:
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.20.0000
INFOversion-baseband: 1.10.40.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT2A1LY11239
INFOimei: 353335041573307
INFOmeid:
INFOproduct: proto
INFOplatform: HBOOT-8225
INFOmodelid: PM6610000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-f3c065d3
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.016s
APPLE-LINKS said:
i reset cid to super cid,plz if you dont mind again give a look to my situation,what things are necessary to me.
thanks
Click to expand...
Click to collapse
Even better with SuperCID, follow the same step as described above.
Most important is your hboot is 1.20.0000 and that's the only RUU available (two RUU actually, the other one is 1.14.401.1). And to run RUU the bootloader must be relocked.
Since it is SuperCID, it should run without CID matching to android-info.txt
Give it a try and follow the steps that I mentioned above and let me know the outcome.
When you need to unlock again, you need to reapply new unlock_code.bin
With SuperCID, if I'm not wrong you also can try the other RUU with a higher version hboot - RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe as it will update your hboot to 1.18.0000
Another option to have a working phone is :
Install TWRP recovery (or any recovery) for ICS, then install a custom ROM based on ICS and fastboot flash the ICS boot.img
Your problem now is actually is the hboot is a lower version which is ICS but you have a JB ROM so it can't boot. It will boot when all the boot.img, ROM and recovery are all ICS.
ckpv5 said:
Even better with SuperCID, follow the same step as described above.
Most important is your hboot is 1.20.0000 and that's the only RUU available (two RUU actually, the other one is 1.14.401.1). And to run RUU the bootloader must be relocked.
Since it is SuperCID, it should run without CID matching to android-info.txt
Give it a try and follow the steps that I mentioned above and let me know the outcome.
When you need to unlock again, you need to reapply new unlock_code.bin
With SuperCID, if I'm not wrong you also can try the other RUU with a higher version hboot - RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe as it will update your hboot to 1.18.0000
Another option to have a working phone is :
Install TWRP recovery (or any recovery) for ICS, then install a custom ROM based on ICS and fastboot flash the ICS boot.img
Your problem now is actually is the hboot is a lower version which is ICS but you have a JB ROM so it can't boot. It will boot when all the boot.img, ROM and recovery are all ICS.
Click to expand...
Click to collapse
Thanks for Your Kind INFO Now its working well,all-thing are going OK,do i need you Unlock Bootloader agian,or no need it?
APPLE-LINKS said:
Thanks for Your Kind INFO Now its working well,all-thing are going OK,do i need you Unlock Bootloader agian,or no need it?
Click to expand...
Click to collapse
Great :good::good:
To unlock bootloader again is your personal choice. You only need that if you need to install custom ROM, or root it and for whatever reason you may have. If you are happy with what you have, no need to do it.
Can you edit your title to (SOLVED) Desire X hboot problem instead of Desire X S-Off ?
HBoot Problem
My HBoot-1.20.0000
How i turn my hboot into1.25....................Please help
i do not understand how i do it.....
ridwone01 said:
My HBoot-1.20.0000
How i turn my hboot into1.25....................Please help
i do not understand how i do it.....
Click to expand...
Click to collapse
make sure u have stable internet connection.
from your phone, go to Settings -> About -> Update, check for update and wait till it finished and reboot.
Hi guys, I am by no means a noob but here's what happened. Maybe someone experienced can help me with this.
I was running the CM11 lastest nightly with the latest TWRP, S-ON when I decided I needed to go back to stock. So I locked the bootloader using fastboot oem lock after rebooting to the bootloader and since my phone was last on 3.24.531, that's the RUU I flashed (I remember now I didn't run it as administrator the first time). The RUU failed and it said that some partitions basically couldn't be flashed. Not the radio, but the userdata and system for example couldn't be flashed. It was able to flash boot though. I kept trying the RUU multiple times. At first it would keep failing the same way, but now I am stuck on the black HTC logo with the 4 triangles in the corners. I kept getting error 155 even though my bootloader is clearly relocked. Every time I reboot the phone manually it goes to the black HTC screen, and I have to insert and remove the USB cable in order to get to the bootloader RUU mode screen, but there's no option for fastboot. I can, however, seemingly unlock the bootloader and lock at my will and also flash recoveries (I still have my Unlock_code.bin and it does get accepted), but I can't get to them.
Now I have yet another problem, I can't charge the phone because I was about to try this RUU instead (5.14.531.1): http://www.htc.com/us/support/htc-one-t-mobile/news/ but now I get error 120. Any idea how I can get this thing to charge and how I can fix my problem once I get it charged more again? Thanks guys I'm kind of desperate here...
EDIT: Maybe another idea would be to format the partitions manually then re-run the RUU, because I was on CM11 4.4.4 and I was trying to reinstall the 4.3 T-Mobile RUU, and maybe they were confusingly formatted for the RUU? Idk.
Okay when I go to RUU mode looking at the bootloader screen and plug this thing into a charger, FASTBOOT AC lights up, but I can't tell if the phone is charging...is that one way to charge it?
EDIT2:fastboot getvar all output:
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.03
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA34xxxxxxxx
INFOimei: 35xxxxxxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 4051mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-412e361e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.048s
Alright, I solved it. Solutions were:
1. YES, fastboot ac does mean that the phone is charging
2. I ran the 5.14.531.1 RUU as administrator, and it worked. Cleared up all the triangles and flashed all the partitions successfully. All good.