Develop Bugs

get HTC Desire with cracked Amoled in ADB

Hello,
I got a HTC Desire with cracked Amoled (DIgitizer ist working, can unlock blind) but I dont now which launcher is installed or which rom ist installed, I got it in Fastboot blind...
But I want to get it in ADB to get Screencast working does someone know how to boot the HTC Desire with turned on ADB or how to turn it on blind?

Settings> Applications>Development
Usb debugging must be enabled.
Then, install PC adb drivers, and you're done.

Hello,
and you can do this blind, while not knowing which ROM,Launcher or wtf is on the phone?
It should be stock cause of the ringtone, but I dont now which launcher and where I am actually

It's not impossible, but hard.
What rom is supposed to be installed on the phone?
Touchscreen works, doesn't it?

Hello,
yes Touchscreen seems to work! Cause I can unlock!
Unlocking the Screen, press the Vol+ Button to see if unlocked (it makes sounds then) and then pressing the "menü" Button and blind pressing settings but don't know how to be sure where I am

Ok. So here's what we'll do. You will take your phone, and keep it parallel to the images below, and move your finger on the screen exactly as the red markers show you. It's the only thing I could think of.
1. Unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing to do here.
2. Press Menu, and press in the red marked area to enter settings.
3. Move you finger across the screen exactly as the arrow shows.
4. Press on the marked section of the screen. You should enter Applications menu.
5.Press on the marked section. (Development)
6. Tick USB Debugging by pressing the marked section.
7. See if "adb devices" returnes anything.
If this doesn't work the first time, try 2 more times, then we'll try with a Froyo sense.

Hello,
Thanks man! But I have a smarter way I just have to get access to the phones data partition!
then I can modify the settings.db file which contains a value called "adb_enabled"...
Only thing I can reach is Hboot mode and Fastboot mode ..
This is what I get from "fastboot getvar all"
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.93.0001
(bootloader) version-baseband: 5.11.05.27
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 2.12.110.4
(bootloader) serialno: NEVERMIND
(bootloader) imei: NEVERMIND
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-365c78d6
(bootloader) hbootpreupdate: 11
all: Done!

Look what I found:
http://forum.xda-developers.com/showthread.php?t=1030107
Maybe you can access the phone, but I think you still need USB Debugging enabled. You do have root access right?

abaaaabbbb63 said:
Ok. So here's what we'll do. You will take your phone, and keep it parallel to the images below, and move your finger on the screen exactly as the red markers show you. It's the only thing I could think of.
Click to expand...
Click to collapse
Thanks!! It actually worked!

Hi,
it worked for you?
I did not get it to work, anyway I ordered a new Display now

You will replace it manually?
Good luck.

Hi,
yes I allready replaced many Screen at iPhones and other Phones
Regards

[Q] How to Solve a BOOTLOOP ?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hello
I have an HTC dezire Z and it stuck after power on at the BOOTLOADER screen , as you can see on the Picture .
and i want to know if there is anyway to solve this problem
i flashed it with this room [RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed] it was successful and i start using it normally but when i restart it , it stuck again on this screen
i know that the phone is working but there is something wrong with the boot sequence
i want to repair this phone to give it to my little brother
please Help

You have a S-ON Device, so you have to extract the boot.img from the zip file. Then enter fastboot modus on the phone and open fastboot in the command line on your pc, you also have to connect the phone via usb to the pc. Copy the boot.img to the folder where fastboot is.
Run "fastboot devices" and check if your device is listed.
Then run the command "fastboot flash boot boot.img", now the phone should boot.

akamarukiba said:
You have a S-ON Device, so you have to extract the boot.img from the zip file. Then enter fastboot modus on the phone and open fastboot in the command line on your pc, you also have to connect the phone via usb to the pc. Copy the boot.img to the folder where fastboot is.
Run "fastboot devices" and check if your device is listed.
Then run the command "fastboot flash boot boot.img", now the phone should boot.
Click to expand...
Click to collapse
thanks for your help ,
the problem is when i turn-on the phone it stuck on the BOOT screen as in the picture , AND the UP and DOWN button don't work at all
when i boot in the recovery mode ( power-on + down button ) i have the same problem the UP and DOWN keys don't work at all
the only way a can start the phone with is to plug it to the computer to execute FASTBOOT and type in the command line "FASTBOOT REBOOT" and it starts normally .
i followed the instruction carefully in http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD to get S-OFF and ROOT and ENG HBOOT with Gfree and i have a ROOTED device , and i installed clockwork recovery and a newer ROM (aosp-4.2.2) .
but the problem is always here , it's abnormal why my phone is not booting normally even if i flashed all things that can be flashed ???
View attachment 2445883
as you can see here
the Vol up and Down button are working normally expect in the BOOT Mode , i have tried to go to the recovery using ROM Manager App and it works by choosing " Reboot in recovery " , i have ClockworkMod Recovery v6.0.4.5 installed ,i did a test key to check if it's a hardware issue related to the keys, and am sure it's not due to that . keys are respnding perfectly .
if you have any suggestion or solution to that problem ????
i think it's related to the boot process :s

i typed "fastboot oem partition_test all" in the command line and i got :
C:\HTC>fastboot oem partition_test all
...
(bootloader) Testing Partition[merge_emmc]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[misc]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[hboot]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[sp1]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[wifi]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[recovery]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[boot]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[mfg]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[sp2]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[pdata]...
(bootloader) Can not allocate heap for flash_block_test
OKAY [ 0.139s]
finished. total time: 0.141s
=============================================================
and for "fastboot oem check_emmc_mid"
C:\HTC>fastboot oem check_emmc_mid
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.009s
==============================================================
and also for "fastboot oem boot"
C:\HTC>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is HTC__102
(bootloader) setting->cid::HTC__102
(bootloader) serial number: SH0BMRT05576
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =465
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.13.04.19_M androidboot
(bootloader) .cid=HTC__102 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-GER androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BMRT05576 androidboot.bootloader=0.84.2000 no_console_suspe
(bootloader) nd=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:493018 msec
FAILED (status read failed (Too many links))
finished. total time: 7.807s

Which radio do you have installed? I do not know if it is the problem, but it might be.
I am using this one: Vision_Radio_12.62.60.27_26.13.04.19
It workes well with Flinnys CM 10.1 Build 25 test4 and Nevergones CM 11.
Instruction and Radioimages are here:
http://forum.xda-developers.com/showthread.php?t=970809

akamarukiba said:
Which radio do you have installed? I do not know if it is the problem, but it might be.
I am using this one: Vision_Radio_12.62.60.27_26.13.04.19
It workes well with Flinnys CM 10.1 Build 25 test4 and Nevergones CM 11.
Instruction and Radioimages are here:
http://forum.xda-developers.com/showthread.php?t=970809
Click to expand...
Click to collapse
i have the same radio Radio_12.62.60.27_26.13.04.19

HLOOX said:
[...] and i installed clockwork recovery and a newer ROM (aosp-4.2.2) [...]ClockworkMod Recovery v6.0.4.5 installed
Click to expand...
Click to collapse
Sorry, I do not have any good ideas left, these are my last ideas, but I think they will not solve the problem.
Which AOSP-Rom are you using? Did you searched for similar issues with that rom, have you tried another rom yet? (Like the offical CM 7.2 for Vision?)
And you are using a ported ClockworkMod Recovery by NeverGone, I have not tested it yet, and I do not think it causes the problem, but there might me unkown issues with flashing. You could try the official one to flash the Rom.
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-vision.img

am using AOSP - Jelly Bean 4.2.2 - Build 16 ,
it's not caused by the ROM or by the ClockworkMod Recovery , because this problem appeared when i were using the phone with his original shipped ROM .
and to solve the problem i first tried to RUU shipped ROM file , the problem consist .
the problem was here bofore i flashed anything , i flashed the HBOOT and RADIO and changed the ROM to solve the problem but noting works with me to solve this problem .

I have a solution that you Should try...
You need to download proper RUU ... the android 2.2 PC10.img thing...I don't remember the name..
No doubt you will return to stock ...but after re root 100% it will solve your problem!!
Sent from my T05A using xda app-developers app

mohnish.killer said:
I have a solution that you Should try...
You need to download proper RUU ... the android 2.2 PC10.img thing...I don't remember the name..
No doubt you will return to stock ...but after re root 100% it will solve your problem!!
Sent from my T05A using xda app-developers app
Click to expand...
Click to collapse
thank you mohnish.killer , i have already try this solution with this original shipped rom
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_ 12.56.60.25_26.10.04.03_M_release_199043_signed
am familiar with HTC devices and i know a lot about flashing and rooting and i know how to solve many problems and i have never faced like this problem .
before this problem my HTC was running under Gingerbread StockRom ,i shut it down before i sleep one night and in the next morning i tried to turn it on but it stuck on the boatlooder screen .
the first thing i did is to try solve the problem with an original shipped ROM (RUU) ,the instalation was successful but it didnt work .
the second thing is to flash only BOOT.IMG with fastboot using a Stok boot , the flashing was successfull but the problem is always here.
the last thing i did is to root the device with the ENG-HBOOT and install jelly bean 4.2.2 and ClockworkMod Recovery ,but i still have the problem.
my little brother is using the phone now , i show him how to start the phone with the computer and the command fastboot reboot
and am still confused with this problem , there is something freak with that phone

I don't know from where did you get that image for gingerbread stock anyways.... Just give the android 2.2 image another shot !
Sent from my HTC Vision using xda app-developers app

Nearly Bricked, Please Help

The phone is a VZW HTC One. I have S-off with Hboot 1.55, bootloader unlocked and I was rooted prior to the flashing of TIKTAK going sideways. Now I can ADB when i'm in recovery and I can flash new recovery mods. I know this means that I'm not completely done for.
When I let the phone try to boot without going into the boot loader it sits at the green HTC screen with the red distribution statement. In this state it tries to make an MTP connection with windows but it doesn't install the drivers properly.
I don't seem to have an internal file structure. I tried downloading HTC1guru's nandroid backup but TWRP doesn't recognize it in either its zipped form or extracted. CWM doesn't seem to recognize any file system at all. I have to use someone elses backup because I was dumb and didn't move my backup off the device before dropping a bomb in the file system.
TWRP is asking for a password that I don't know (and didn't set) every time it opens
I also tried RUU but I never get to the silver HTC screen.
I'm at a loss as to how to proceed. Any thoughts would be most appreciated. I'm pretty handy in the IT world but this is my first time flashing a custom ROM, it may be the last. Thanks in advance.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000428178272
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Just do the 2.10.605.1 ruu (found in santods rom/radio/kernel thread), then " fastboot erase cache ", then " fastboot flash recovery name_of_recovery.img ". From there you can flash a rom, or just flash superuser and be stock rooted.

I can't get the phone into RUU. any reboot that doesn't go to recovery or fastboot just hangs on the green HTC screen.
>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: read fifo failed, retry
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 17
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 2.156s]
finished. total time: 2.156s

Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk

Any luck?
jbeavis19 said:
Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
JBeavis, I am in a very similar situation to the one you are in. Have you had any luck with fixing it or getting a warranty repair?
Thanks!

I'm also in a similar situation
One critical difference between the HTC One and the thunderbolt... no SDCard. Which would not be a big deal had I not wiped the phone with no backup (stupid I know) before loading a new rom image to replace it. Now I can't get ADB to recognize my phone in CWM recovery. No sideload. Nothing. I do have S-off and CWM 6.0.4.7 installed successfully. If anybody has any advice I'd really appreciate it.

@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.

Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!

eicos said:
Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!
Click to expand...
Click to collapse
Did you try the repair process regardless with the right mount point?
These are the Verizon HTC one mounts
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes @Gizmoe, the command fails with "could not stat /dev/block/mmcblk0p37 --- no such file or directory". Any other ideas? I appreciate your help.

Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.

I gave up and warrantied the phone and now it has 4.4.2 on it so no rooting until ther is a method that works and I'm not sure I'll try another custom rom any time soon.
@Gizmoe, thanks for the suggestion, that is an approach that I didn't try, I thought I went through them all.

Gizmoe said:
Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.
Click to expand...
Click to collapse
Thanks @Gizmoe, I had the same error with fastboot oem rebootRUU as the op. I am 99.999% sure the EMMC got fried somehow. Probably I hard booted the phone at a bad time during the installation or something - or maybe it was just ready to die. In any case I also have warrantied the phone. Replacement to arrive tomorrow. Here's hoping it doesn't have 4.4.2, though it probably will. @mike1986., do you have any light to shed on this topic?

Gizmoe said:
@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.
Click to expand...
Click to collapse
I got my phone to a state where I could push a rom down to it using that fix. Thanks for the help! (I've created an entirely different thread detailing my new problem) http://forum.xda-developers.com/showthread.php?t=2657211

M8, Grrrrrrr !!!!!!

While the M8 is a nice device, I hate it. This device has caused me no end of problems..
Every time I try to flash anything, it kills it, boot loops, stuck at HTC logo, etc... I've never had so much trouble with any device, even changing simple settings seems to do the same.
Changing the dpi - Stuck at HTC Logo...
Installed Xposed (Not using ART) - Stuck at HTC Logo...
Restore Nandroid Backup - Stuck at..... blah blah blah...
So I'm trying to get back to stock and then maybe start again. If I try to flash my stock recovery backup, it then won't boot into recovery it just goes back to HBoot, I've tried downloading Stock Recoveries, but I'm not sure if it's the right one. I've tried zipping the recovery into the 0P6BIMG.zip and flashing it through HBoot, but this doesn't work. My version-main is missing so, I can't check it with the one in the android-info.txt. I think it's something to do with Firewater S-Off.
I'm stuck, anybody else having similar problems...
Thanks ...John...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT44MWM08826
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s

I see that you're S-OFF, but is your bootloader still unlocked? There's a method of unlocking/locking the hboot without HTCDev if you're S-OFF. You could try running a RUU exe then unlocking your bootloader again. S-OFF will stay through the RUU.

decayer177 said:
I see that you're S-OFF, but is your bootloader still unlocked? There's a method of unlocking/locking the hboot without HTCDev if you're S-OFF. You could try running a RUU exe then unlocking your bootloader again. S-OFF will stay through the RUU.
Click to expand...
Click to collapse
I can't see it being firewater problem cause there is so many users including myself with no problems. But I had unlocked my boot loader before I s off'd with firewater

M8,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yeah, My bootloader is still unlocked. I had used HTC Dev before using firewater too.. I think the problem was there before I'd S-Off'd, so I don't think Firewater caused that, but I had read that some people had missing a version-main after using it...
I had thought about flashing an RUU, as this has usually been the answer in the past, but I could only find them for the Verizon and T-Mobile US versions. As far as I'm aware they haven't released one for the international version..
I was thinking about converting to the GPE edition. Hopefully replacing the HBoot and recovery in the process, but would I still need to know the version-main..
:fingers-crossed:
Thanks ...John...

Missing version-main is a TWRP 2.7 problem.

j0hn0n1 said:
Yeah, My bootloader is still unlocked. I had used HTC Dev before using firewater too.. I think the problem was there before I'd S-Off'd, so I don't think Firewater caused that, but I had read that some people had missing a version-main after using it...
I had thought about flashing an RUU, as this has usually been the answer in the past, but I could only find them for the Verizon and T-Mobile US versions. As far as I'm aware they haven't released one for the international version..
I was thinking about converting to the GPE edition. Hopefully replacing the HBoot and recovery in the process, but would I still need to know the version-main..
:fingers-crossed:
Thanks ...John...
Click to expand...
Click to collapse
By the looks of things you only did S-OFF, rooted perhaps, custom recovery(Hence missing main-version) but you haven't converted to any other device and/or went with SuperCID? Did you do an OTA update to the newest 2.xx.xxx.x firmware? If not then perhaps you're device is still on the 1.54.61.5 version.
You can grab a nandroid backup + stock recovery from the COLLECTION of Stock backup's thread. ORANG001 is in there. Assuming of course you either did an OTA(When you bought the phone back in the early days) or bought it before the 2.xx.xxx.x update, chances are that your version number that you're looking for is 1.54.61.5 so that settles that issue then.

Yeah, I unlocked the boot loader with HTC Dev, then S'Off'd, rooted it and then installed a custom recovery almost straight after getting the phone. I then flashed ViperROM so I definitely didn't do any OTA's.
I didn't bother with SuperCID at the time because I didn't need it, I was just flashing ROMs, mostly. Then I stated noticing that almost every ROM that I'd flash would just hang at the HTC logo.
I managed to to restore the stock rom from my backups, but the recovery wouldn't take, although this is just a backup of the custom recovery that I first flashed. I had tried the orang001 backup from the collection of stock backups, and that wouldn't work either, and the same with the custom recoveries from the same page..
If I flash Philz recovery though, this works every time... TWRP I had some trouble with, but got it working eventually.. I just can't seem to get a stock recovery to work, no matter what..
Thanks ...John...

Need help with My M8

hi
i installed leneage OS on my device few months back then used it few days then left it in my drawer , a few days back when i started my phone i saw a vertical colored lines on screen and i can barley see what came to my mind is that a software issue so what did i do is went to recovery did a full wipe (system as well) and that is my mistake , screen became worse in i cant see any thing except lines still im able to boot into bootloader , fastboot etc..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 6(s)
My Device status now is Unlocked TWRP recovery and No OS
thanks in advance

Cutrus said:
hi
i installed leneage OS on my device few months back then used it few days then left it in my drawer , a few days back when i started my phone i saw a vertical colored lines on screen and i can barley see what came to my mind is that a software issue so what did i do is went to recovery did a full wipe (system as well) and that is my mistake , screen became worse in i cant see any thing except lines still im able to boot into bootloader , fastboot etc..
My Device status now is Unlocked TWRP recovery and No OS
thanks in advance
Click to expand...
Click to collapse
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?

Saleen28 said:
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?
Click to expand...
Click to collapse
Yes they are , i reflashed the os at the beginning same results

Saleen28 said:
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?
Click to expand...
Click to collapse
uploaded a picture

Seems like hardware issue imo.
Your M8 is blue - have you changed the unibody or it was just a blue model?
Also - was your drawer a dry place? Maybe some moisture somehow got into it.

Saleen28 said:
Seems like hardware issue imo.
Your M8 is blue - have you changed the unibody or it was just a blue model?
Also - was your drawer a dry place? Maybe some moisture somehow got into it.
Click to expand...
Click to collapse
Yes blue , I've store it in his original box in a dry place

I'd flash a ruu as a last line of defense if it's a software thing.
If that doesn't help then it's a hardware problem, probably the screen. If you're lucky then reconnecting the screen ribbon might fix it, if not - you need a screen replacement.

Saleen28 said:
I'd flash a ruu as a last line of defense if it's a software thing.
If that doesn't help then it's a hardware problem, probably the screen. If you're lucky then reconnecting the screen ribbon might fix it, if not - you need a screen replacement.
Click to expand...
Click to collapse
Tried to flash a RUU halted at this message when i flash the RUU
fail43 main version check fail
Didn't figure out how to pass it

Cutrus said:
Tried to flash a RUU halted at this message when i flash the RUU
fail43 main version check fail
Didn't figure out how to pass it
Click to expand...
Click to collapse
This error tells that you're trying to flash a ruu that is lower than your current firmware. Try this one - https://androidfilehost.com/?fid=24369303960687057
Also a short guide I've found, just in case
ckpv5 said:
For S-On
fastboot oem lock (to relock bootloader)
fastboot reboot-bootloader (reboot to bootloader after relock)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Click to expand...
Click to collapse