Hello,
I recently dropped my HTC One S into a glass of water. It kept on working so I thought I'd got away with it, but then a few hours later it rebooted and now won't boot beyond the white "HTC" screen before rebooting again. I've tried drying it out but it's still doing it.
The phone had not been modded or rooted before, I just used the stock HTC OS which came with it. I can get to the bootloader screen and have tried various things to get it working but nothing seems to have worked. I've anyone can point me in the right direction (or tell me I've no chance) I'd be very grateful. I've done the following:
Tried the stock recovery, gave the same reboot loop.
Tried the "clear storage" and "factory reset" options, same reboot loop.
Connected with USB Fastboot - seems fine and I can see the device from my laptop
Unlocked the bootloader - I now have *** UNLOCKED *** at the top of the screen
Flashed a custom recovery (I've tried CWM and TWRP, various versions) - seemed fine and Fastboot suggested that the flash had worked, but when I try to load it I get the same reboot loop. The only difference is that I now have some red text on the HTC screen when starting recovery: "This build is for development purpose only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
I'm at a loss as to what to try or where to look now. I saw one post which suggested that the stock ROM may be detecting the invalid recovery and trying to overwrite it, and others that suggest using an RUU to get the phone back to original state, but I can't seem to see one which matches the info I get from "fastboot getvar all". My thinking is that if the recovery doesn't even work then something is wrong with the phone itself, but is there a way I can tell what the phone is doing or any logs I can see? As Fastboot doesn't have access to files in storage I can't tell if there's anything there.
The phone's info (from fastboot getvar all) is below, and if anyone can suggest anything I'd be very grateful.
Thanks,
James
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.771.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24SW409116
(bootloader) imei: 359901047356445
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
From what you describe, it surely sounds like a HW fault. Reflashing will not fix it. You can always try (in the unlikely case that the flash memory was somehow rewritten), but as you already have tried it, it means your phone is most probably bricked. Sorry.
Some expert may want to confirm my conclusion.
As a last resort, I would take the phone apart, and leave it like that for a day or two, to make sure any remaining moisture has a change to evaporate - and then re-assemble. It is possible that some of it could be shorting an address line or something? More likely something is corroded beyond repair.
EDIT: It may be possible that the hboot was damaged / rewritten but the flash memory is still intact. That may be fixable, but quite difficult. It means purposedly "bricking" the device further and manually registering device nodes in Linux and directly writing into them.... I think I saw a guide somewhere. This will not be easy for the average user, and there only a slim chance it will actually work.
Thanks. That's pretty much what I thought but thought I'd ask in case someone had any bright ideas. I've already ordered a new phone which should get here tomorrow, so I don't really want to spend hours trying to get it working when it's probably bricked anyway.
Related
Right now I can not turn my phone on, it just gets stuck in the htc quietly brilliant "This build is for development purpses only" red text screen every time I reboot it.
I have TWRP v2.4.3.0 installed and working, bootload is unlocked, I don't know what to do next. Could anyone be kind enough to give me a clear set of instructions ("flash rom" isn't helping - would help a lot if you mentioned which rom and how to flash it and whether to reset factory settings/clear cache). all I want to do is to get past the htc quietly brilliant screen, no matter how. Help please.
Info about my phone below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:***************
(bootloader) imei: *********
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's pretty easy. All you have to is to follow the instructions over here.
rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
I think the root of my problem may be finding a custom rom compatible with hboot 1.13..
Every rom i try to install fails (trickdroid, viperones), is there any way i can update hboot first?
rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
Helloooooo?
I'm stuck, it's not like I didn't try installing roms before.
They're failing because I have hboot 1.13 and I can't find ANY roms that are compatible with 1.13.
I also can't download an RUU, because no RUU is available for my carrier/version (CID: ROGERS001)
that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3
rugmankc said:
that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3
Click to expand...
Click to collapse
I'm S4, and I managed to fix it... never got viperones to work though, first i did the superCID process and downloaded a t-mobile ruu, and then tried to custom rom viperones which didn't work ended up working with aokp, so thanks anyways, how do I close this thread
Get different twrp. Many people have problems flashing roms with 2.4.3.0 version.
Sent from my HTC One S using xda app-developers app
Glad you got it. Mod may close it. Since you asked.
Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>
Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon
Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.
I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!
Yesterday I went through the process of unlocking my bootloader, rooting the phone and then S-OFF via Sunshine. After completing these steps, I attempted to flash a RUU (http://forum.xda-developers.com/one-e8/development/ruu-sprint-htc-one-e8-1-22-651-1-stock-t2952981) - the reason for this being I am attempting to unlock my SIM for use on another carrier. So, I was able to successfully flash the RUU via fastboot commands (followed these instructions: https://www.youtube.com/watch?feature=player_embedded&v=ybu7fZa41so) and then rebooted the device. Upon rebooting the device, I was able to use the phone for 10 seconds or so before it automatically reboot itself. This happened several times before the bootloop stopped and I was able to use the phone just fine. Thinking everything was working, I proceeded to the next step in unlocking my SIM (outlined here: http://forum.xda-developers.com/one...51-1-stock-t2952981/post57116360#post57116360) which was to flash a zip (found here: http://forum.xda-developers.com/atta...1&d=1417208962). Upon flashing the zip, I was unable to successfully reboot the phone. Instead, I am only able to access the bootloader and TWRP recovery.
I am currently at a loss for what to do. One issue is that I may have attempted to flash the RUU and subsequently the zip while my phone was low battery (roughly <15%; I've read this can cause issues but I'm not 100% sure). I am currently charging my phone in hopes that this may solve the issue but I am not entirely optimistic.
I realize that I am an idiot for not having a stock rooted TWRP backup - I actually did create one (albeit on my internal storage) which was subsequently deleted when flashing the RUU. I have not been able to find a stock rooted backup of the Sprint HTC One E8 (perhaps I am not looking in the right places), could anyone help me find this? Or should I try to flash the RUU linked above again (am I wrong in assuming this would serve as a custom recovery)?
I am concerned that I may have bricked my phone...so any help at all would be appreciated.
Hope I can help. First the good news- you have not bricked your phone. Now the (not so) bad news- you are in a bit of a mess but will be able to come out with a functional phone.
It sounds like you have a Sprint phone and tried to flash another RUU.
I need to know exact model number of your phone, MID, CID stock ROM etc and what RUU you had tried to use.
The easiest way would be to find a stock RUU that your phone had come with, rename it to 0PAIJMG.zip and put in the root of an external micro sd and reboot the phone in bootloader and let the phone reinstall the original RUU (as you have already done once).
Before, you try to flash another RUU make sure you have superCID and have modified MID as well ( there are plenty of discussion on this in this forum).
Alright, so after a day of tinkering with things I think I may have resolved the issue (but not achieved my goal of unlocking the SIM).
I ended up getting superCID, and flashing the current RUU for the Sprint HTC One from HTC's website. The phone is now up and running on 2.32.651.7. I did this by downloading the .exe. file straight from HTC's website and following the utility instructions. I was previously trying to manually flash 1.22.651.1.
So my phone is up and running, however I would still like to unlock the SIM. I am following the instructions in the link I provided in my previous post (http://forum.xda-developers.com/one-...0#post57116360) but am somewhat hesitant to re-flash the 1.22.651.1 RUU as instructed in the guide considering what I just went through. I know that I would be able to just revert back to my current RUU which is stable, but I'm not inclined to go through with the process if it is just a dead-end. Would I be able to go through with the instructions (specifically everything including flashing the zip file from http://forum.xda-developers.com/atta...1&d=1417208962 and onwards) and still be able to successfully unlock the SIM from the 2.32.651.7 RUU? Or do you think it specifically requires the 1.22.651.1 RUU to work?
I'm not familiar with MID or why I need to modify it, could you elaborate or should I just look into other forum posts?
As for my phone info, here you go: (I used the command fastboot getvar all; not sure if this is what you wanted)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.32.651.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4AASP00761
(bootloader) imei: 990004299346803
(bootloader) imei2: Not Support
(bootloader) meid: 99000429934680
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ50000
(bootloader) cidnum: 11111111
(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: d0c41a5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OK so I'm pretty sure what is causing problems is the step outlined here - "flash the attached zip http://forum.xda-developers.com/atta...1&d=1417208962". Apparently the file is supposed to grant write access to modify an APK file and allow the phone to be rooted, however, whenever I flash the zip file from TWRP recovery, I am no longer able to boot into my OS...instead I boot straight to recovery. Not sure why this is - any help would be appreciated!
hi everyone, first time poster, got stuck with soft bricked m8s.
1. can not unlock, tried many tokens from htcdev and for m8 and for other supported phones, but every time it`s offers yes or no option.. power button... it`s switches off, vibrates and boots up to htc logo. when i go back to fastboot it`s says relocked.
2. i have no RUU mode, after fastboot oem rebootRUU phone just restarts to system and stops at htc logo. no silver screen or anything like that.
how much i understand my only option (i hope there is another option) is to download RUU to sd card and hboot flash it from sd card, but as i understand, my firmware or OS is 2.21.401.1 and i cannot go lower, and i can not find online RUU i need.
i believe i need something like this ?
0PKVIMG_M[email protected]60201_20.05_018_F_release_496316_signed_2_4
i downloaded this file numerous time from one place i found, but it seems corrupted at source, it wont let me to copy it to sd card, cannot even extract rom.zip
htc_fastboot flash zip ruu.zip says its too large and any other ruu signature fail.
i found some places online which selling this download, but since my knowledge is not that strong, i am not sure even i am buying right one or not wasting money and time.
would appreciate if someone would upload or direct to right ruu.
software status modified
Relocked
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main: 2.21.401.1
version-misc: PVT SHIP S-ON
serialno: xxxxxxxx
imei: xxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8ql_ul
platform: hTCBmsm8939
modelid: 0PKV10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0b9a12e3
hbootpreupdate: 11
gencheckpt: 0
mfg-name: 0001
do i have any other options, like force-downgrade main version, get another RUU or even RUUmode back, Unlock somehow so i could just use any rom, or anything from here..
thank you in advance for any suggestions.
forgot to mention, every time i plug wall charger or micro usb from PC , phone shows battery for 2 seconds and self starts boot loader , i can not even see those green things filling battery or % of charge.
is it hardware issue or still software does it ?