Develop Bugs

[Q] [q] need help with htc desire (gsm)

My HTC Desire is stuck at the HTC welcome screen,
Things i've tried:
1. HBoot Clear Storage
2. Fastboot Erase Cache & Recovery
3. Installed a new Clockwork Recovery via Fastboot
4. Tried Accessing system.img & boot.img
NON of the Above works,
Alpharev & Revolutionary wants to find the phone in Debugging mode, which would be okay if it could boot into the OS, but doesn't
Can't Create a GoldCard because psas Goldcard Generator site isn't working anymore
This is the little information i've gathered on it so far
From Hboot:
*** UNLOCKED ***
BRAVO PVT1 SHIP S-ON
HBOOT-1.03.0003
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Dec 21 2011,20:44:09
From Fastboot Getvar all:
version: 0.5
version-bootloader: 1.03.0003
version-baseband: 5.11.05.27
version-cpld: None
version-microp: 031d
version-main: 2.35.0.0
serialno: HT071PL00121
product: bravo
platform: HBOOT-8x50
modelid: PB9920000
cidnum: HTC__001
battery-status: good
battery-voltage: 4109mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 229eea55
hbootpreupdate: 11
From RUU Setup:
Image Version: 2.35.0.0
DOES ANYONE KNOW WHAT ELSE I SHOULD DO?

Flash 2.3 RUU. There are many tutorials out here. Look for them.
Sent from my HTC One using Tapatalk 4 Beta

Breakages said:
My HTC Desire is stuck at the HTC welcome screen,
Things i've tried:
1. HBoot Clear Storage
2. Fastboot Erase Cache & Recovery
3. Installed a new Clockwork Recovery via Fastboot
4. Tried Accessing system.img & boot.img
NON of the Above works,
Alpharev & Revolutionary wants to find the phone in Debugging mode, which would be okay if it could boot into the OS, but doesn't
Can't Create a GoldCard because psas Goldcard Generator site isn't working anymore
This is the little information i've gathered on it so far
From Hboot:
*** UNLOCKED ***
BRAVO PVT1 SHIP S-ON
HBOOT-1.03.0003
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Dec 21 2011,20:44:09
From Fastboot Getvar all:
version: 0.5
version-bootloader: 1.03.0003
version-baseband: 5.11.05.27
version-cpld: None
version-microp: 031d
version-main: 2.35.0.0
serialno: HT071PL00121
product: bravo
platform: HBOOT-8x50
modelid: PB9920000
cidnum: HTC__001
battery-status: good
battery-voltage: 4109mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 229eea55
hbootpreupdate: 11
From RUU Setup:
Image Version: 2.35.0.0
DOES ANYONE KNOW WHAT ELSE I SHOULD DO?
Click to expand...
Click to collapse
You will have to downgrade your hboot. That version won't work with revolutionary.

abaaaabbbb63 said:
You will have to downgrade your hboot. That version won't work with revolutionary.
Click to expand...
Click to collapse
Downgrade how?
i've searched for ways to do that but can't find one
now i seem to have gone too far
i tried:
fastboot oem rebootRUU
fastboot flash zip [Desire-Stock-2.3-Upgrade].zip
i got a
FAILED (remote: 51 partition update fail)
and tried doing it again
now i get
FAILED (remote: 12 signature verify fail)
and it's stuck with this screen

Breakages said:
Downgrade how?
i've searched for ways to do that but can't find one
now i seem to have gone too far
i tried:
fastboot oem rebootRUU
fastboot flash zip [Desire-Stock-2.3-Upgrade].zip
i got a
FAILED (remote: 51 partition update fail)
and tried doing it again
now i get
FAILED (remote: 12 signature verify fail)
and it's stuck with this screen
Click to expand...
Click to collapse
Why did you..?!.. Never mind..
You know, if you googled "Downgrade 1.03 hboot", the first result would have been this guide:
http://forum.xda-developers.com/showthread.php?p=24039156
How do you people look for things these days, and not find anything?

abaaaabbbb63 said:
Why did you..?!.. Never mind..
You know, if you googled "Downgrade 1.03 hboot", the first result would have been this guide:
http://forum.xda-developers.com/showthread.php?p=24039156
How do you people look for things these days, and not find anything?
Click to expand...
Click to collapse
Yep, i tried that this morning, Didn't work,
something told me to try the RUU Updater again, it was going great until it told me there was an Error Recovery so it was going to help me recover it, after asking me to remove the battery which i did and insert it back after 3 seconds (WHICH I DID)
NOW THE PHONE IS HARD BRICKED, I MEAN TOTALLY DEAD, IT DOESN'T RESPOND, POWER ON? NOTHING, CONNECT VIA USB, NOTHING

Breakages said:
NOW THE PHONE IS HARD BRICKED, I MEAN TOTALLY DEAD, IT DOESN'T RESPOND, POWER ON? NOTHING, CONNECT VIA USB, NOTHING
Click to expand...
Click to collapse
Oh god.. That's not good.
Does it show a led, or something, when plugged in?
Take your battery out, press the power button for 10 seconds, plug the battery back in, then try to boot.
Or put your phone in the freezer for 5 minutes with the battery taken out, then try to boot.
If none of these work, then say goodbye to your Desire. You'll have to either get a new phone, or replace the motherboard.

I've tried the first one and it didn't work, tried the freezer, nothing worked too, i guess i'd have to go get the board flashed
Sent from my Nexus 7 using xda app-developers app

Sorry bro
Breakages said:
I've tried the first one and it didn't work, tried the freezer, nothing worked too, i guess i'd have to go get the board flashed
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You will need somone who solder some cables and plug it to riffbox(its a jtag tool for repairing dead boots)

[Stuck] Boot loop

Hi,
I need help with booting loop.
After trying to root and flash custom ROM I can't do anything.
I was using EasyAceRootTool to unlock a boot loader and to get Root access in custom ROM.
After going into recovery I wiped everything and installed cm-7-20130301-NIGHTLY-ace.zip without errors.
After rebooting I see only white screen.
I tried wipe and install again and again...was reading a lot of threads and did everything what I found. Still nothing.. (or I did in wrong way)
I've tried maybe 5 different RUU - all the time errors.
This is what I can see in fastboot:
**UNLOCKED**
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
RECOVERY:
ClockworkMOD v5.8.1.5
in the bottom I can see:
E:Can't open / cache/recovery/log
E:Can't mount / cache/recovery/last_log
E:Can't open / cache/recovery/last_log
fastboot getvar all:
version: 0.5
version-bootloader: 2.00.0029
version-baseband: 26.14.04.28_M
version-cpld: None
version-microp: 0438
version-main: 3.13.0.0
serialno: MB141RX12271
imei: 356299047527468
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4199mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: fcef1579
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
Thanks.

Gedaz said:
Hi,
I need help with booting loop.
After trying to root and flash custom ROM I can't do anything.
I was using EasyAceRootTool to unlock a boot loader and to get Root access in custom ROM.
After going into recovery I wiped everything and installed cm-7-20130301-NIGHTLY-ace.zip without errors.
After rebooting I see only white screen.
I tried wipe and install again and again...was reading a lot of threads and did everything what I found. Still nothing.. (or I did in wrong way)
I've tried maybe 5 different RUU - all the time errors.
This is what I can see in fastboot:
**UNLOCKED**
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
RECOVERY:
ClockworkMOD v5.8.1.5
in the bottom I can see:
E:Can't open / cache/recovery/log
E:Can't mount / cache/recovery/last_log
E:Can't open / cache/recovery/last_log
fastboot getvar all:
version: 0.5
version-bootloader: 2.00.0029
version-baseband: 26.14.04.28_M
version-cpld: None
version-microp: 0438
version-main: 3.13.0.0
serialno: MB141RX12271
imei:
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4199mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: fcef1579
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
Thanks.
Click to expand...
Click to collapse
You need to flash boot.img in fastboot. Boot.img can be found in the rom zip files that you flashed earlier.
Sent from my Desire HD using xda premium

yumm91 said:
You need to flash boot.img in fastboot. Boot.img can be found in the rom zip files that you flashed earlier.
Click to expand...
Click to collapse
fastboot flash img boot.img
sending 'img' (2982 KB)...
OKAY [ 0.516s]
writing 'img'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.001s
Doesn't work ...

If memory serves, you will need to downgrade your hboot first before you can flash a boot.img.
Sent from my Desire HD using xda app-developers app

romuloxiii said:
If memory serves, you will need to downgrade your hboot first before you can flash a boot.img.
Click to expand...
Click to collapse
Thanks for answers,
well I'm not sure how to do this
I have downloaded this RUU
OTA_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R-1.84.661.1_R_release_194023aok9iw7hmtj4lilk.zip, Renamed it to PD98IMG.zip and flashed in
fastboot oem rebootRUU
fastboot flash zip OTA_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R-1.84.661.1_R_release_194023aok9iw7hmtj4lilk.zip
and still nothing,
fastboot flash zip OTA_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R-1.84.661.1_R_release_194023aok9iw7hmtj4lilk.zip
sending 'zip' (102227 KB)...
OKAY [ 17.309s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.653s
please correct me if I did everything wrong

My mistake was
fastboot flash zip boot.img,
after typing
fastboot flash boot boot.img
I got WORKING cm-7.2.0-ace.zip ROM
So far so good :fingers-crossed:
But, I have strange touchscreen behavior it touches not where I'm pressing but like 20mm to the left and none of the 4 buttons are working.
I've tried to download and install same ROM like 10 times but still the same.
On CM11 and CM10 I have only black screen.
Any ideas ?

Now I have CM-10 with touch screen problem.
I found out that for some ROM's I need to boot boot.img manually in fastboot mode because I'm S-on.
I have only touch screen problem now. I don't believe it's hardware problem because before everything it was working really well.
(I found some threads about it as well, but cleaning Dalvik cache or permission fixing didn't help.)
I really need help in here, thanks.

Gedaz said:
Now I have CM-10 with touch screen problem.
I found out that for some ROM's I need to boot boot.img manually in fastboot mode because I'm S-on.
I have only touch screen problem now. I don't believe it's hardware problem because before everything it was working really well.
(I found some threads about it as well, but cleaning Dalvik cache or permission fixing didn't help.)
I really need help in here, thanks.
Click to expand...
Click to collapse
are you already have tried flashing boot.img from fastboot...?
fastboot flash boot boot.img

JJeamy said:
are you already have tried flashing boot.img from fastboot...?
fastboot flash boot boot.img
Click to expand...
Click to collapse
I have solved booting problem like I said.
Before did flash zip boot.img instead of flash boot boot.img.
I don't know what to do with touchscreen, looks like all left side is not working and on the right side I have 2-3cm error to the left side...
Is it possible to get some kind of touch screen driver or video driver zip file to flash from recovery to try restore default value of touch screen ?.
I've flashed
lordmodUEv8.9-CFS-b7-2WCR-TUN.zip kernel from recovery but on the phone I still can see:
Kernel version
2.6.35.14-cyanogenmod-g295e82f
I can navigate on the phone only through androidscreencast.jnlp
Thanks.

Gedaz said:
I have solved booting problem like I said.
Before did flash zip boot.img instead of flash boot boot.img.
I don't know what to do with touchscreen, looks like all left side is not working and on the right side I have 2-3cm error to the left side...
Is it possible to get some kind of touch screen driver or video driver zip file to flash from recovery to try restore default value of touch screen ?.
I've flashed
lordmodUEv8.9-CFS-b7-2WCR-TUN.zip kernel from recovery but on the phone I still can see:
Kernel version
2.6.35.14-cyanogenmod-g295e82f
I can navigate on the phone only through androidscreencast.jnlp
Thanks.
Click to expand...
Click to collapse
i'm not sure is..but what i guest it's looks like a rom problem/bug indeed..
maybe you can try another rom that you sure that is not have major bug indeed..
try like carboon rom for JB and svhd rom for ICS,
but because the phone still s-on..then you must always flashing boot.img (from the rom.zip itself) manual too from fastboot after installing every any new custom rom..
hopefully this can help..

[Q] Stuck in bootloader with Security warning.

I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*ALSO I am currently on InsertKoin ROM* <--That might change something
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John

I've been S-Off since day one so double check everything but this will get you in the right direction. You need to S-off and unlock, flash an RUU and then relock (to remove the red text warning). Going back to S-on I understand is pretty dangerous and appears to be unnecessary. Go to this thread and start with the 3rd tutorial to re-S-off. If you can get S-off'd the rest should be pretty easy.

jman036 said:
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
Click to expand...
Click to collapse
That should be early enough to use Firewater on. Let me know if you run into problems because I can help via team viewer.

@pmterp & @dottat Thanks for the reply and that sounds like a good idea but I have to push the file via adb. I cannot get there because I am stuck in the fastboot section. So I don't think firewater or anything that uses adb will work.

Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
You can go into ruu mode while s-on, but need a signed ruu. Last signed ruu we had was 2.x
Sent from my HTC6500LVWBLU using XDA Free mobile app

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.

jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
That is RUU mode and will accept an RUU file to flash at this point. I believe Uzephi is correct that the RUU you flash must be signed (which I think is the same as encrypted). I'm not sure where you would find them but I'm sure Google will be your friend on that. Be careful what version you flash because I think it can cause problems if you move down. I'm not sure how open he is to helping via PM (he's super helpful but also very busy) but if it were me I'd reach out via PM to @santod040 and ask for advice. He's a highly skilled dev who's been with this device a long time.

I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.

tflogic said:
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
Click to expand...
Click to collapse
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Click to expand...
Click to collapse
Dang really? I thought they would be since they both have "signed" in the filenames.
HSM_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_5.28.605.2_HSM_Radio_1.13.41.0702_NV_VZW_4.64_002_release_387332_signed.zip
Click to expand...
Click to collapse
Any idea what to do then?

tflogic said:
Dang really? I thought they would be since they both have "signed" in the filenames.
Any idea what to do then?
Click to expand...
Click to collapse
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have one of each ?
---------- Post added at 10:58 PM ---------- Previous post was at 10:55 PM ----------
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340

dottat said:
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
Click to expand...
Click to collapse
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?

tflogic said:
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
Click to expand...
Click to collapse
If installed drivers are correct htc sync will see the phone. I just responded to your post in a different thread. Can you try that first before we troubleshoot drivers?

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.

Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I cant seem to find any RUU files that match my phone!
dottat said:
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Click to expand...
Click to collapse
Well I made it one step further with it recognizing that I have a phone connected but said "no software available."
I think if I can find a signed RUU file then I can fix this. I just have to find it.....

See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
Click to expand...
Click to collapse
Well I tried this and sadly I can send it but it always gets signature check fail. :/ (I ran it twice also)

[Q] Pls help - HTC One X stuck on quietly brilliant screen and won't restore

Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal

koolvirgo said:
Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal
Click to expand...
Click to collapse
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version

Thant said:
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version
Click to expand...
Click to collapse
Hi,
Thanks pal ! Here is the output of fastboot getvar version-main
version-main: 0.0.0.178434
thanks,
Kunal

Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal

koolvirgo said:
Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal
Click to expand...
Click to collapse
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want

Thant said:
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want
Click to expand...
Click to collapse
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal
Click to expand...
Click to collapse
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same

Thant said:
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same
Click to expand...
Click to collapse
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal

koolvirgo said:
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal
Click to expand...
Click to collapse
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???

Thant said:
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???
Click to expand...
Click to collapse
Yes, I did both !!

koolvirgo said:
Yes, I did both !!
Click to expand...
Click to collapse
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?

I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
INFOversion: 0.5a
INFOversion-bootloader: 1.72.0000
INFOversion-baseband: 5.1204.167.31
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.18.401.4
INFOserialno: HT23NW107620
INFOimei: 359188041361783
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 3660mV
INFOdevpower: 3
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
Click to expand...
Click to collapse
What I have to do?? Thanks for the help you are saving me!!

lollerz46 said:
I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
What I have to do?? Thanks for the help you are saving me!!
Click to expand...
Click to collapse
Okay I solved my problem, my issue was the boot.img that was different from the one inside the custom rom! Hope this helps

Thant said:
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?
Click to expand...
Click to collapse
It says Endeavoru XE

koolvirgo said:
It says Endeavoru XE
Click to expand...
Click to collapse
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU

Thant said:
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU
Click to expand...
Click to collapse
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal

koolvirgo said:
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal
Click to expand...
Click to collapse
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot

Thant said:
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot
Click to expand...
Click to collapse
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal
Click to expand...
Click to collapse
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment

Thant said:
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment
Click to expand...
Click to collapse
Hi Thant,
Before trying what you suggested (for manual update) I tried the ICS RUU once again. It went through fine this time not sure why, then I did an OTA upgrade and now I'm on Android 4.0.4 hboot 1.12 (same as before but on 2.17.720.2). There are no more OTA updates available, though HTC india website says there is one available for 3.14.720.24 which is JB version and should automatically update my hboot which I can then hopefully use to update to 4.4 ROM. Do you think what I think is going to work ?
But I can't find the OTA firmware for 3.14.720.24. There was one available here but no more.
There's one here but not sure about the authenticity of this.
I have downloaded the firmware zip you shared but it seems the file is corrupt.
Thanks,
Kunal

[Q] Stuck in fastboot and no connections in ADB

Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi

ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.

riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?

Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app

elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?

PLS can anyone help me ? :crying:

themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?

FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.

FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..