Develop Bugs

:S Phone cannot boot :/

My friend has just unlocked his bootloader using HTC Dev, this has left it S-ON, so he installed cwm, made a nandroid, then began flashing rom's, he flashed the boot.img separate via fastboot due to the s-on, yet aosp rom's just get stuck on the boot animation, and any sense rom, (including the backup) just boot straight to recovery :/ He's asked me for help but I'm at a loss to explain this :S
we have tried reflashing an RUU but it just complained about it being the wrong version even though there is no other version it could be
Any ideas?
Thanks in advance

Relock the bootloader, then root using the ace advanced kit. You will may find a link to it in xda or if you search for glevitan. The hack kit was removed from xda.
Sent from a dream.

l.m.prowse said:
My friend has just unlocked his bootloader using HTC Dev, this has left it S-ON, so he installed cwm, made a nandroid, then began flashing rom's, he flashed the boot.img separate via fastboot due to the s-on, yet aosp rom's just get stuck on the boot animation, and any sense rom, (including the backup) just boot straight to recovery :/ He's asked me for help but I'm at a loss to explain this :S
we have tried reflashing an RUU but it just complained about it being the wrong version even though there is no other version it could be
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
you have to flash the boot.img in fastboot commands if you have unlocked the bootloader with HTCDEV. Do that, and the you will have a working phone.
HTCDEV is useless, I would suggest that u relock the bootloader and then use the Hack Kit....:good:

Teichopsia said:
Relock the bootloader, then root using the ace advanced kit. You will may find a link to it in xda or if you search for glevitan. The hack kit was removed from xda.
Sent from a dream.
Click to expand...
Click to collapse
glevitan said:
you have to flash the boot.img in fastboot commands if you have unlocked the bootloader with HTCDEV. Do that, and the you will have a working phone.
HTCDEV is useless, I would suggest that u relock the bootloader and then use the Hack Kit....:good:
Click to expand...
Click to collapse
We cannot get the phone to boot into a rom, therefore the hack kit is useless, it requires the phone to boot, and we've relocked and everything, it just refuses to boot any roms (yes we have been flashing the boot.img's via fastboot

l.m.prowse said:
We cannot get the phone to boot into a rom, therefore the hack kit is useless, it requires the phone to boot, and we've relocked and everything, it just refuses to boot any roms (yes we have been flashing the boot.img's via fastboot
Click to expand...
Click to collapse
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.

Teichopsia said:
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.
Click to expand...
Click to collapse
His advice was to use the hack kit, which we cannot do without a booting OS, which we currently do not have, which is the reason I posted here.

Teichopsia said:
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.
Click to expand...
Click to collapse
From what I've gathered, he's in a bootloop, unlocked with HTCDEV and has tried to flash the backed up boot.img via fastboot.
In this specific situation how is the hack kit any use to him if he can't get past the splash screen?
Perhaps double check the locations and files you're pushing/flashing and "fastboot erase cache" before and after.
I'm sure you've probably tried this already but it's the only other things I can think of causing the loop.

sprogurt said:
From what I've gathered, he's in a bootloop, unlocked with HTCDEV and has tried to flash the backed up boot.img via fastboot.
In this specific situation how is the hack kit any use to him if he can't get past the splash screen?
Perhaps double check the locations and files you're pushing/flashing and "fastboot erase cache" before and after.
I'm sure you've probably tried this already but it's the only other things I can think of causing the loop.
Click to expand...
Click to collapse
Yeah we've tried all of that :/ I can't think of any reason its doing it. It's the same as I do on my HOX, never had a single problem with it :/

l.m.prowse said:
Yeah we've tried all of that :/ I can't think of any reason its doing it. It's the same as I do on my HOX, never had a single problem with it :/
Click to expand...
Click to collapse
Ok, in order to flash a RUU you will have to relock your bootloader. The main version error is due to the unlocked bootloader.
If you still have CWM, before relocking the bootloader u can try to flash a custom rom and then flash the boot.img in fastboot (but doing a wipe first) If that is not working, then you gotta flash a RUU but wil only work if you relock the bootloader....:good:

glevitan said:
Ok, in order to flash a RUU you will have to relock your bootloader. The main version error is due to the unlocked bootloader.
If you still have CWM, before relocking the bootloader u can try to flash a custom rom and then flash the boot.img in fastboot (but doing a wipe first) If that is not working, then you gotta flash a RUU but wil only work if you relock the bootloader....:good:
Click to expand...
Click to collapse
We relocked the bootloader, and the RUU still said it was the wrong version, the image on the device is 1.13 whereas the ruu is 1.12.405.1, there is no 1.13 ruu :/

l.m.prowse said:
We relocked the bootloader, and the RUU still said it was the wrong version, the image on the device is 1.13 whereas the ruu is 1.12.405.1, there is no 1.13 ruu :/
Click to expand...
Click to collapse
ok, do the following, what CID number does the phone have?
boot in hboot, choose fastboot and then plug the phone (you should see fastboot usb in red). Now open a CMD as admin in the PC and type fastboot getvar all. Get the INFOcidnum...and paste it here...

glevitan said:
ok, do the following, what CID number does the phone have?
boot in hboot, choose fastboot and then plug the phone (you should see fastboot usb in red). Now open a CMD as admin in the PC and type fastboot getvar all. Get the INFOcidnum...and paste it here...
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.0.0
(bootloader) serialno: SH0CFRX04874
(bootloader) imei: 352668046527618
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3882mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
That's everything it displayed

same problem
I have the same problem. I use bootloader from htc.dev, forgot to backup and i am stuck on fastboot mode. I have cwm but i succesfully instal miui rom, but i cant to use phone, because HTC logo dont move i follow you suggestions. I hope u can help me too.
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.31.405.6
INFOserialno: SH11ZRX02646
INFOimei: 356299049533530
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4194mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.005s

HD Desire stuck at boot, recovery mode will not load

Hi Everyone,
Running JellyTime (4.2) on my phone, but it all of the sudden does boot anymore. It just gets stuck on the JellyTime boot screen. When I try to boot the phone into recovery mode ( 4EXT Recovery), the phone vibrates three times and has a blank screen, with the amber LED continuously blinking. Is there any hope for this phone? Is there a way to maybe boot it via Windows? Or is the hardware dead or faulty now? Any help would be appreciated.
I've taken out the battery, SD, SIM card. But when I boot the phone with even just the battery inside the result is the same.
Cheers,
raczyk

try to reflash recovery from fastboot, and then everything else. and learn to use search

t0mas_ said:
try to reflash recovery from fastboot, and then everything else. and learn to use search
Click to expand...
Click to collapse
Thanks for the suggestion t0mas. Does the reflash have to be a RUU file? Perhaps one from here?http://shipped-roms.com/index.php?category=android&model=Ace

it doesnt have to be, but it can be. be careful not to flash froyo!

Thanks for the tip, from that website it would be a froyo, my telephone it Telus branded. Connecting the phone to my computer via USB does recognize a "HTC Android Interface", but when trying to control the phone from my PC using various fastboot packages, the phone does not respond. Is there particular fastboot tool you guys use?

raczyk said:
Thanks for the tip, from that website it would be a froyo, my telephone it Telus branded. Connecting the phone to my computer via USB does recognize a "HTC Android Interface", but when trying to control the phone from my PC using various fastboot packages, the phone does not respond. Is there particular fastboot tool you guys use?
Click to expand...
Click to collapse
I'm not sure but you might have to install the HTC usb drivers but don't install HTC Sync. You could then use fastboot to get the phone's CID and match it with the correct GB rom.
I have a Desire HD that I purchased used and it was running a stock Telus GB rom.

audit13 said:
I'm not sure but you might have to install the HTC usb drivers but don't install HTC Sync. You could then use fastboot to get the phone's CID and match it with the correct GB rom.
I have a Desire HD that I purchased used and it was running a stock Telus GB rom.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT12*****56 recovery
I've installed the "Universal_Naked_Driver_0.72" found on these forums, followed by "Minimal ADB and Fastboot." I can onlly get the adb.exe to work not fastboot.exe. Also the number above is that the CID? And how does one cross reference with a correct GB rom?
Edit: Just made some progress and managed to boot it into FastBoot using:
C:\Program Files\Minimal ADB and Fastboot>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT12*****56 fastboot

raczyk said:
C:\Program Files\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT12*****56 recovery
I've installed the "Universal_Naked_Driver_0.72" found on these forums, followed by "Minimal ADB and Fastboot." I can onlly get the adb.exe to work not fastboot.exe. Also the number above is that the CID? And how does one cross reference with a correct GB rom?
Click to expand...
Click to collapse
Can you boot into the the HBoot screen using the volume down and power button? If you can, select fastboot from the menu. Then type fastboot getvar all and it will return the following info:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.17.14.11_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.20.502.52
INFOserialno: HT11XTZ01021
INFOimei: 3xxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9814000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4206mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
This post might help too: http://forum.xda-developers.com/showthread.php?t=2317536

audit13 said:
Can you boot into the the HBoot screen using the volume down and power button? If you can, select fastboot from the menu. Then type fastboot getvar all and it will return the following info:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.17.14.11_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.20.502.52
INFOserialno: HT11XTZ01021
INFOimei: 3xxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9814000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4206mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
This post might help too: http://forum.xda-developers.com/showthread.php?t=2317536
Click to expand...
Click to collapse
Yeah I can navigate Fastboot via phone, just don't now what image to laod onto it now. I have the following options: Bootloader, reboot, reboot botolaoder, power down. Currently I have the SD card and SIM card taken out of the phone. What image should I load onto it? From here it suggest the following "fastboot flash recovery your_recovery_image.img." . img? I've always used .zip images the past such as "cm-JellyTime_42_R10.zip"
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.2425
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HT12PTZ0****
(bootloader) imei: 355761*********
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9814000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4204mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d4fa0f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.031s

If you flash using a custom recovery such as cwm or 4ext, the file extension is .zip. When flashing through fastboot, the images would have a .img file.
Since you already had 4ext on your phone, did you try re-flashing 4ext to see if it will boot in recovery mode?
Edit: since you cid is now all 1s, you'll have to find a way to pull the cid from another source such as the radio file.

audit13 said:
If you flash using a custom recovery such as cwm or 4ext, the file extension is .zip. When flashing through fastboot, the images would have a .img file.
Since you already had 4ext on your phone, did you try re-flashing 4ext to see if it will boot in recovery mode?
Edit: since you cid is now all 1s, you'll have to find a way to pull the cid from another source such as the radio file.
Click to expand...
Click to collapse
The phone does boot into 4ext recovery mode, i just can't install the .zip image. Do I need the cid to reflash with a .img image?
From fastboot here is the info, believe all I need is an .img image file. Any suggestions, please?
ACEPVT ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot

After playing around with the phone.. I've loaded recovery from fastboot.. previously I've also wiped to default settings and cleared cache.. this time from fastboot I've selected for the phone to fastboot.. and the phone has booted.. Will try to flash with an updated jelly time mod.

raczyk said:
After playing around with the phone.. I've loaded recovery from fastboot.. previously I've also wiped to default settings and cleared cache.. this time from fastboot I've selected for the phone to fastboot.. and the phone has booted.. Will try to flash with an updated jelly time mod.
Click to expand...
Click to collapse
I tried Carbon rom and it's worked well for me. Glad you got it working.

HTC DESIRE HD RUU update result bricked phone logo screen HELP

Hi guys!!
I really need your help. after unsuccessful attempt to update my HDT with ruu file (dont know which one) it ended up with white screen. i thought no big deal. i ll fix that but after numerous attempts to return stock i realize that something that i do is not right so help me please.
my HD is locked and first i tried to unlock bootloader on htcdev but my hboot 2.00.027 is no longer support as htcdev claims. it needs to be updated.
This is the RUU file that according to my knowledge matches the requirements of my phone but oviously not.
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
i tried with it flash from sd card - it comes to do you want to update? pressed vol.buton +. update in progress and that stuck for over a hour.
tried via computer and usb cabel. after running exe file it stuck on rebooting in bootloader.
tried flash over adb and fastboot command via cmd. fastboot devices shows that phone is connected but it stuck on next command fastboot erase cache.
here are the characteristic of the phone.
ACE PVT SHIP S-ON RL
HBOOT 2.00.0027
MICROP - 0438
RADIO 26.14.04.28_M
eMMc - boot
Sep 7 2011,19:06:24
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.1
(bootloader) serialno: SH198RX00810
(bootloader) imei: 3xxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.000s
C:\android>
PLEASE HELP ME TO FIND THE RIGHT RUU or any other method that would work.
bear in mind iam unrooted.
What am i supposed to do to fix my phone? any clue?
via RUU or .... ............

If your aiming for a stock rom, Just create a goldcard and try flashing your stock rom.
You can extract the rom.zip file in ruu by
The process:
- Download a RUU from anywhere (you already have one)
- Open/Run the .exe You'll get something like this
- Click the Start button
- Select the Run command and type in: %temp%
- Search for a folder that has a bunch of characters and looks somewhat like this: {XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX} just keep on searching in each folder, if you have patience you'll find it.
- And inside that folder should be another folder that looks the same, and has the format above.
- Find a zip file called rom.zip -
-Rename the rom.zip to PD98IMG.zip
If you already created a goldcard. put the PD98IMG.zip in the root of your sd card
Go to bootloader and pressing -volume and power button.
Rom zip will automatically detected and you will be ask to update.
Hope it helps "newbie here" :fingers-crossed:

Iam not aiming on stock. actually i dont care. i just want my phone back working.
i dont have a goldcard. can i make one with unrooted and locked phone?
i tried with flash from sd card extracted rom and renamed as PD98IMG - it comes to do you want to update? pressed vol.buton up than shows update in progress and stuck for over a hour.
doesent work
thanks for effort

Its easy to create a goldcard, any sd card will do.
Links is http://forum.xda-developers.com/showthread.php?t=970157
if you cannot get your cid just use the attach file goldcard.img below
i dont know if it would work, but since you haven't find any solution yet, you could at least try.
Hope it helps your phone...:fingers-crossed:

charles66 said:
Iam not aiming on stock. actually i dont care. i just want my phone back working.
i dont have a goldcard. can i make one with unrooted and locked phone?
i tried with flash from sd card extracted rom and renamed as PD98IMG - it comes to do you want to update? pressed vol.buton up than shows update in progress and stuck for over a hour.
doesent work
thanks for effort
Click to expand...
Click to collapse
Have you tried with a different sdcard? have you also checked the md5sum or the RUU? maybe you can flash it in fastboot (read the guide in my signature to find out how)

glevitan said:
Have you tried with a different sdcard? have you also checked the md5sum or the RUU? maybe you can flash it in fastboot (read the guide in my signature to find out how)
Click to expand...
Click to collapse
i tried with a other sd card.
i also checked ms5sum - it matches.
i tried flash it from fastboot.
result - negativ.
with sd card it comes do you want to update? yes. and than stuck on updating on a first stage on bootloader and stuck there.
i tried with a goldcard. result the same as with regular sd card.
please read all my tread. i need to fix my phone.

[Q] Stuck on HTC logo after flashing custom rom

I have an HTC Desire HD.
I unlocked it
s-off
rooted
flashed with cwm recovery
installed from ZIP file on SDCARD
rebooted
stuck on HTC logo regardless of what I attempt.
I have no idea where to go from here.
Any ideas?
Thanks

did you made full wipe?

What ROM?....which version of cwm? These are important factors

ClockworkMod Recovery v 5.8.1.5
I have tried different ROMs, all end up with the same scenario
cm-10.1-20130301-unofficial -ace
cm-JellyTime_R17.zip
I hope this answer helps you help me

Can you access boot loader? If so , go to it and post results of "fastboot getvar all". Maybe running an ruu will get u back on track.

Yest, bootloader is accessible and I attempted an RUU and ended up with the same result.
I will post the results of getvar all when I get home, stuck in traffic now
Thanks
-----------------------------------------
Here is the result of getvar all:-
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.13.0.0
INFOserialno: SH12CRX01945
INFOimei: 356299049756800
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__Y13
INFObattery-status: good
INFObattery-voltage: 4172mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.031s

Is this were it stops?
No one has any idea to what it could be, no need for an absolute solution, a mere possible or a reflection as to what I could have done wrong would be appreciated.

LOL
What can i say to you?
As you stated on very first post of yours where you mentioned that your device is S-OFF? then why "INFOsecurity: on" ??
Simply flash any custom rom then extract boot.img from that custom rom .zip file and flash it through fastboot using command "fastboot flash boot boot.img"
Afterwards it should boot normally. Recovery has no issue nor given rom as you've mentioned on your post. Just requires boot.img to be flashed as your device is S-ON! not S-OFF.

I read a little sarcasm in that LOL
Thanks for the valuable info, I will attempt that as soon as I get home.
I will give feedback as to how successful my attempt has been.

I have attempted the proposed solution and I got the following error:
failed (remote: signature verify fail)
I read that could have to do with the fact that my bootloader is locked again. I did run a while back fastbood oem lock.
oem unlock returns an error.
So I attempted with the htcdev unlock code.bin again and unlocked it.
I ran the boot.img as instructed again and this time it was a success although it gave me a scare with the 4 reboots it performed
Thanks for the help, the tip from dr.patron99 was very helpful.

help: bricked htc one m7 ?

Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.

redmapleleaf said:
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
Click to expand...
Click to collapse
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.

Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
redmapleleaf said:
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Click to expand...
Click to collapse

Update: all problems are fixed, the phone is returned to its stock state completely. Here is what I did.
1. Change the CID to T-MOB010 by using "fastboot oem writecid T-MOB010
2. with CID=T-MOB010 and model number MID=PN0713000 I look up the RUU exe that support those two parameters and download it from htc1guru.com
3. down grade my hboot from 1.54 to 1.44 by flashing a hboot.zip file
4. put the phone in fastboot mode and run the RUU exe . After it is done the phone is back to stock rom.
That's it. Hope these steps could help some sorry soul out there. This HTC root/unroot is NOT FUN at all! If you happen to read this HTC, please make your bootloader idiot proof. Otherwise we will just go with your competitor whoever has a better bootloader.
redmapleleaf said:
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
Click to expand...
Click to collapse