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..
Related
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.
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 !!
First, off, awesome NOOB video, and after watching it I can safely say I've done my due diligence. I have scoured our internet and several parallel earth internets with no luck in finding a solution. If any of you can give me a hand, I'd really appreciate it.
Phone Specs:
HTC Rezound
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-V14.6.0.7708.00.0507
eMCC-BOOT
Sep 20 2012,17:40:22
SDK tools: "Pulled from the SDK of February 13, 2013"
PROBLEM: Cannot revert to stock rom by
1) using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
2) or flashing from Amon Ra or TWRP (can't mount eMCC/data)
3) or uploading PH98IMG.zip to SD card and letting Hboot handle the heavy lifting (sticks at HTC boot up screen on reboot)
4) or using "fastboot oem rebootRUU" followed by "fastboot flash zip PH98IMG.zip" gets
sending 'zip' (624366 KB)...
OKAY [ 55.743s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 142.046s
BACKGROUND: I'm obviously a noob, but the only way to learn is by digging in. Here's the progression that's led me to this point:
1) Learned to unlock bootloader
2) Installed cm-10.1-20130629-NIGHTLY-vigor (officially unsupported by available for Rezound from CyanogenMOD's website)
3) Noticed instability so I wiped everything (x3) and tried to revert to stock. Couldn't make any progress, especially since the RUU exe crashes on both Win7 systems I have.
4) To get functionality for work, switched to cm-10.1.0.1-vigor.
5) Still have stability issues, so I'm trying yet again to revert. Current results of attempts are listed above under "PROBLEMS"
Note1: Per Scott's suggestion over either at Phandroid or ScottsRoms (can't remember I've been so many different places), I've modified the android-info.txt in PH98IMG.zip as follows, making sure the version number is higher than the current from CID Getter:
"modelid: PH9810000
cidnum: VZW__001
mainver: 4.09.605.2
hbootpreupdate:12
DelCache:1
DelFat:1
"
Note 2: MD5s check out.
Note 3: Before my first installation of CyanogenMOD's latest nightly, adb worked fine and would list my phone. After CyanogenMOD's latest nightly, adb does succeed in starting daemon and lists what it think is my phone, but instead of listing a phone it lists a blank space and returns to the command prompt. if I try adb reboot, it returns error: device not found. BUT fastboot still works fine.
Appendix 1: fastboot getvar all returns:
C:\Users\Josh\Desktop\Root Project\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (seem odd to anyone else that there's no number there?)
(bootloader) serialno: ******
(bootloader) imei:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.499s
Appendix 2: The sequence I've been following trying to get the thing to accept the stock rom is below...and I've tried small variations variations when what's below fails miserably.
1. Load TWRP or Amon Ra recovery
2. Wipe, wipe, wipe!
3. Reboot bootloader
4. fastboot flash recovery recovery_signed.img (have treated as interchangeable in sequence with step 5)
5. fastboot flash boot boot_signed.img (have treated as interchangeable in sequence with step 4)
6. (used this, also from Scott, before I started manually editing the android-info.txt in the image zip) fastboot flash zip SetMainVersionLOW.zip (to make sure the main version is lower than the stock ROM version--otherwise it'll think you're upgrading to a lower version and won't run)
7. fastboot oem lock
8. This step varies. I've tried
a. fastboot oem rebootRUU then fastboot flash zip PH98IMG.zip
b. fastboot boot TWRP or Amon Ra recovery, then flashing PH98IMG.zip from there
c. dropping PH98IMG.zip on the SD card and letting Hboot handle the heavy lifting
I take it you didn't take a back up of your previous rom before installing CM10.1?
mjones73 said:
I take it you didn't take a back up of your previous rom before installing CM10.1?
Click to expand...
Click to collapse
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
JoshManning said:
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
Click to expand...
Click to collapse
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
mjones73 said:
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
Click to expand...
Click to collapse
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
You already have the latest firmware on your phone, that doesn't get touched when you do a rom install.
Thank you, Matt! I'm downloading the ROM right now. Will post results once it's down.
SOLVED
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
kc6wke said:
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
Click to expand...
Click to collapse
Makes perfect sense. Rocking along now nicely thanks to you. Seriously, can I send you an Amazon card or something?
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
You're welcome, kc6wke covered question 1, for number 2, I knew you couldn't RUU cause you are on the latest firmware and s-on, it's not possible to downgrade firmware unless you're s-off. Your only option really was to install a different rom so I gave you a stock rooted one.
Matt, I've got an additional question if you have time. Any idea why my attempts to root the new ROM aren't taking hold? The phone is running just fine off the ROM you directed me to. After installation, I booted into Amon RA 3.16, installed superuser and su, and rebooted. Nothing. SUChecker returns "su declined / not found"
Actually nevermind. SUChecker is returning a false negative. Apologies, and thanks again!
The one I gave you was already rooted, no need to do that.
mjones73 said:
The one I gave you was already rooted, no need to do that.
Click to expand...
Click to collapse
I now remember your saying that. Thank you so much for your help. I really appreciate it.
Josh,
I may be wrong but I think that the iemi is sensitive info so you might want to delete that from your original post. Maybe delete your serial number as well just in case.
btw... my phone doesn't show a mainver either, never got an answer as to why not, but it works fine.
Thanks! Done and done.
well he was a noob, but then he just became just like the rest of them
how did he uploaded the rom in Amon Ra.
band001 said:
how did he uploaded the rom in Amon Ra.
Click to expand...
Click to collapse
Depends, are you s-on or s-off?
mjones73 said:
Depends, are you s-on or s-off?
Click to expand...
Click to collapse
s-off
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
band001 said:
s-off
Click to expand...
Click to collapse
Sorry but i am s-on not s-off yet. trying to get info on how to also if this does not work.
Hey guys, So I got a new phone and I was looking to unroot this one.
Currecntly my device is
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
What is the easiest way to return to stock.
I found Guru_Reset_M7_3.62.401.1.zip
But I was unsure if that was the correct one.
Thanks
derik123derik123 said:
Hey guys, So I got a new phone and I was looking to unroot this one.
Currecntly my device is
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
What is the easiest way to return to stock.
I found Guru_Reset_M7_3.62.401.1.zip
But I was unsure if that was the correct one.
Thanks
Click to expand...
Click to collapse
not enough info
their are 2 good guides for returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
and
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
not enough info
their are 2 good guides for returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
and
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
What other information do you need?
The second would not work because I am s-on.
derik123derik123 said:
What other information do you need?
The second would not work because I am s-on.
Click to expand...
Click to collapse
fastboot getvar all (minus your serial no and IEMI)
clsA said:
fastboot getvar all (minus your serial no and IEMI)
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
How would I go about getting this device back to stock.
Thank you for your support.
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if you want the easy s-off with revone use this android 4.1.2 RUU instead
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
Sent from my HTC One using Tapatalk
clsA said:
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply,
The link above takes to Cingular US, is that what I want? Its an ATT phone.
derik123derik123 said:
Thanks for the reply,
The link above takes to Cingular US, is that what I want? Its an ATT phone.
Click to expand...
Click to collapse
yep those are the AT&T RUU
clsA said:
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if you want the easy s-off with revone use this android 4.1.2 RUU instead
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is there a more up to date version this program can flash? like our phone's are 4.3 out of the box is there a 4.3 ruu?
rummrunner is a good sorce? we've talked about my device im getting it fixed tomorrow. so all i need to do is unlock the bootloader agian, and use rum runner to get s off?
vividblu2020 said:
is there a more up to date version this program can flash? like our phone's are 4.3 out of the box is there a 4.3 ruu?
rummrunner is a good sorce? we've talked about my device im getting it fixed tomorrow. so all i need to do is unlock the bootloader agian, and use rum runner to get s off?
Click to expand...
Click to collapse
The top link is the most current AT&T Ruu android 4.3
clsA said:
The top link is the most current AT&T Ruu android 4.3
Click to expand...
Click to collapse
flash those with rum runner?
vividblu2020 said:
flash those with rum runner?
Click to expand...
Click to collapse
you don't flash it .. it's an executable file that resets your phone to factory, out of the box condition. It most likely will fail on your windows 8.1 PC because of no fastboot driver support for your phone (yet)
Rumrunner is a method to gain s-off on your phone nothing more, nothing less
clsA said:
yep those are the AT&T RUU
Click to expand...
Click to collapse
I downloaded it and ran it. My phone is stuck on the HTC logo and the RUU said it could not update my rom please get the correct something or another.Going to let my phone sit at the HTC logo and see if it starts.
That ruu did have a error recovery steps, I'll try that.
Any insight?
EDIT: rebooted the phone and It's running like normal(Nothing was deleted etc..)
derik123derik123 said:
I downloaded it and ran it. My phone is stuck on the HTC logo and the RUU said it could not update my rom please get the correct something or another.Going to let my phone sit at the HTC logo and see if it starts.
That ruu did have a error recovery steps, I'll try that.
Any insight?
EDIT: rebooted the phone and It's running like normal(Nothing was deleted etc..)
Click to expand...
Click to collapse
what is your OS ?
do you have htc drivers installed
did you lock the bootloader ?
fastboot oem lock
did you follow the instructions here >> http://www.htc.com/us/support/htc-one-att/news/
clsA said:
what is your OS ?
do you have htc drivers installed
did you lock the bootloader ?
fastboot oem lock
did you follow the instructions here >> http://www.htc.com/us/support/htc-one-att/news/
Click to expand...
Click to collapse
drivers are installed.
This is what fastboot says.
HTML:
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
Ran the ruu again. This is what I get.
http://imgur.com/a/CSs6P
Followed instructions on that page as well.
derik123derik123 said:
drivers are installed.
This is what fastboot says.
HTML:
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
Ran the ruu again. This is what I get.
http://imgur.com/a/CSs6P
Followed instructions on that page as well.
Click to expand...
Click to collapse
lock the bootloader
fastboot oem lock
then run the RUU
do you want the instructions for RUU flashing the rom.zip
clsA said:
lock the bootloader
fastboot oem lock
then run the RUU
Click to expand...
Click to collapse
Yup.. That's it. It had to be something simple. Thanks alot for your help! you're awesome!
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.