Touch only working in TWRP - no response on any ROM - HTC One Mini 2

Dear beloved XDA community,
I was deep downunder with my personal life the past half year and likely lost a lot friends as well as access to the project my heart still beats for: AIMSICD. My secret dream is to continue work there this year.
My issue: In an attempt to slowly crawl my way back into the Android world, I am currently tinkering with a phone of a friend of mine, who had messed up his ROM. After a full wipe and a fresh instal of the unofficial LineageOS 14.1, it appears that the touch screen does not respond on any ROM that I try - but in recovery mode on TWRP everything works fine. Therefore, I guess that no connector cables are broken. But I am out of ideas and it never happened to me that no ROM detects the touch, yet TWRP does. What is your suggestion to solve this? Added information about this unlocked, but S-ON phone:
[email protected]:~$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(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: ea702fb0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Click to expand...
Click to collapse
Sending some love and inner peace to everyone who still knows me!

SecUpwN said:
Dear beloved XDA community,
I was deep downunder with my personal life the past half year and likely lost a lot friends as well as access to the project my heart still beats for: AIMSICD. My secret dream is to continue work there this year.
My issue: In an attempt to slowly crawl my way back into the Android world, I am currently tinkering with a phone of a friend of mine, who had messed up his ROM. After a full wipe and a fresh instal of the unofficial LineageOS 14.1, it appears that the touch screen does not respond on any ROM that I try - but in recovery mode on TWRP everything works fine. Therefore, I guess that no connector cables are broken. But I am out of ideas and it never happened to me that no ROM detects the touch, yet TWRP does. What is your suggestion to solve this? Added information about this unlocked, but S-ON phone:
Sending some love and inner peace to everyone who still knows me!
Click to expand...
Click to collapse
seems like a simple bad flash.
download the ROM again (just in case) and dont forget to Fully wipe your device from Recovery (Data, Dalvik and Cache!) and them install the LineageOS again.

Thank you for taking the time to answer, @kativiti. No, the strange thing is that no matter which custom OS has been installed, touch does not work - except for when I install the stock ROM. I now finally achieved S-OFF and Super-CID on the HTC One Mini 2 using SunShine in order to upgrade the firmware and everything, then did a full wipe of everything and installed Lineage OS 14.1 again. Same result. I wonder why the stock ROM is detecting touch correctly, but nothing else is?

UPDATE: I've just installed NomostroPop and touch works perfectly! So this really must be a driver Issue, I'm hoping that @nightcore500 updates his unofficial LineageOS 14.1 with the Himax touchscreen driver.

Which build of TWRP do you use?
And does your device feature the Himax touchscreen?
TWRP 3.0.2 by @nightcore500 does not yet support the Himax touchscreen (LOS 14.1 does!), so I assume you are on an older build, as this would contradict your experience.
Flashing LOS 14 with TWRP 2.x might cause problems and could be the reason.

Thanks for chiming in, @stkl. The problem has been identified and is about to be solved.

Related

please help! htc one possible boot loop of death.

edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !
Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.
hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom
another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>
Deleted
garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this
garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.
Deleted
when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.
sorry didnt read your reply, well it didnt initialise so no s off anyway
garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us
im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option
right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now
guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me

HTC One Charging Problems.

I have had my HTC One for over 6 months now and have very few complaints.
Around 3 months ago (completely stock phone) the phone stopped charging all together, except for occasionally charging when powered off, and even then on a cycle (strong orange light, weak orange light, no light). At the same time USB stopped working, the phone had dents in it so I didn't want to risk my warranty and decided to fix it myself. I pushed a custom recovery(fastboot was working occasionally) and purchased a USB-OTG cable which my phone recognized.
So at this stage the phone detected AC and USB in fastboot, AC when powered OFF and USB-OTG in recovery.
I installed a ViperOne ROM(I think one of the first releases at that stage), yet the problem persisted.
I went through over 10 combinations of ROMs, Recoveries and Kernels until finally, through sheer luck, the problem was solved.
I did a NANDROID back-up and soon forgot the problem ever occurred. Now 3 or more months later the problem has mysteriously reappeared after no further modifications of any sort. I have unfortunately lost the NANDROID back-up and cannot rediscover the solution to my problem. I have now downloaded every major ROM and Kernel on XDA, tried them all, in different orders, with different recoveries. NO LUCK.
I have read every result I can find through searches related to my problem, all suggest returning it for a motherboard replacement. I would rather find a solution which doesn't leave me without my phone. My current situation is a phone that charges in fastboot through AC, not ideal.
Any help or advice would be much appreciated, Caleb.
EDIT: I believe the solution ROM was insertcoin-m7-6.0-4 and an elementalx or bulletproof kernel.
Details :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34AW907110
(bootloader) imei: 355859050600535
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3835mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
try doing a warrenty exchange through your carrier, that might help.
calebvenner said:
I have had my HTC One for over 6 months now and have very few complaints.
Around 3 months ago (completely stock phone) the phone stopped charging all together, except for occasionally charging when powered off, and even then on a cycle (strong orange light, weak orange light, no light). At the same time USB stopped working, the phone had dents in it so I didn't want to risk my warranty and decided to fix it myself. I pushed a custom recovery(fastboot was working occasionally) and purchased a USB-OTG cable which my phone recognized.
So at this stage the phone detected AC and USB in fastboot, AC when powered OFF and USB-OTG in recovery.
I installed a ViperOne ROM(I think one of the first releases at that stage), yet the problem persisted.
I went through over 10 combinations of ROMs, Recoveries and Kernels until finally, through sheer luck, the problem was solved.
I did a NANDROID back-up and soon forgot the problem ever occurred. Now 3 or more months later the problem has mysteriously reappeared after no further modifications of any sort. I have unfortunately lost the NANDROID back-up and cannot rediscover the solution to my problem. I have now downloaded every major ROM and Kernel on XDA, tried them all, in different orders, with different recoveries. NO LUCK.
I have read every result I can find through searches related to my problem, all suggest returning it for a motherboard replacement. I would rather find a solution which doesn't leave me without my phone. My current situation is a phone that charges in fastboot through AC, not ideal.
Any help or advice would be much appreciated, Caleb.
EDIT: I believe the solution ROM was insertcoin-m7-6.0-4 and an elementalx or bulletproof kernel.
Click to expand...
Click to collapse
atlzonly89 said:
try doing a warrenty exchange through your carrier, that might help.
Click to expand...
Click to collapse
Well, if it comes to that I will have to. This post is more about trying to gain some understanding as to what the problem is.

[Q] Bootloop - Green HTC logo, sometimes Android

Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(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.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA
Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)
nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.
Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck
There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.

[Q] M7 no service/meid unknown/boot loop

Phone Info:
SPRINT HTC ONE M7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: #my number#
(bootloader) imei: #my number#
(bootloader) meid: #my number#
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Symptoms:
No Service
Doesnt show my Basband num, IMEI, MEID, NetWork, IP in UI (but it shows up when i Run "Fastboot getvar all".
Progress com.htc.htcdialer isn't responding.
Boot loops every 5-7 min.
What I did:
Last weeks i bricked my sch-i500 so even though I have Verizon I went out to buy HTC one on sprint (hoping i cant make it work on Verizon).
So i unlocked BootLoader and Rooted the device. Yet for some reason SU wasn't working right - i didnt have root rights.
So i decided to Mod flash it. Made a backup in TWRP, wiped: dalvik, cache, data. and successfully flashed Android Revolution HD 53.0.
But I guess not. Because once i rebooted my screen tripped pink right before the boot animation and never loaded into UI.
I restarted it and gave it another 10 min of loading time - nothing.
I wiped after the previous ROM and flashed Venom ROM, ViperOne 6.2.0.
This one took long to boot up as well but once it did it would just show HTC logo screen upon screen unlock.
I gave it time and it actually brings up the "get started page" 5 min in - problem is it would reboot 1 min after.
After i flashed kernel.
Newest version of Gapps.
Tried LiquidSmooth Rom - that would boot me up but didn't solve my issue plus it didn't have google play and other apps.
I even tried going back to the recovery. It would SPRINT it back into stock yet have the acquired issues since i installed the mod: show HTC logo screen once it entered the UI and the rest of bs
I managed to get the get started page and run through it real quick before it rebooted.
But it had no service, and all those issues i stated above.
Now i came back to ViperOne and once the logo screen flashed to "get started" i ran through it real quick and now thats where im at. But it restarts. And has initial issues.
My Plan:
I researched and came to conclusion that i need to flash the radio.
But before i see i need to flash the Firmware.
In order to flash the firmware i need to Get S-OFF.
Ran RumRunnerr, FireWater, MoonShine they all crash at one point or another.
So Im stuck and idk what to do. Unable to go stock or fix the present. Any ideas?
Screens:
{
"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"
}
Other Comments:
Im kinda new to this. had a few successful Roots but when it came to mods I bricked two phones now.
Level of knowledge 4/10. Have basic Terminology down.
ShoutOut: ViperOne is beast. Love it - if it would work. But Venom Team did an outstanding job. :good:
Oh and btw my HTC ONE is Blue lol.. hope that helps x)
TimFUSE said:
Phone Info:
SPRINT HTC ONE M7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: #my number#
(bootloader) imei: #my number#
(bootloader) meid: #my number#
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Symptoms:
No Service
Doesnt show my Basband num, IMEI, MEID, NetWork, IP in UI (but it shows up when i Run "Fastboot getvar all".
Progress com.htc.htcdialer isn't responding.
Boot loops every 5-7 min.
What I did:
Last weeks i bricked my sch-i500 so even though I have Verizon I went out to buy HTC one on sprint (hoping i cant make it work on Verizon).
So i unlocked BootLoader and Rooted the device. Yet for some reason SU wasn't working right - i didnt have root rights.
So i decided to Mod flash it. Made a backup in TWRP, wiped: dalvik, cache, data. and successfully flashed Android Revolution HD 53.0.
But I guess not. Because once i rebooted my screen tripped pink right before the boot animation and never loaded into UI.
I restarted it and gave it another 10 min of loading time - nothing.
I wiped after the previous ROM and flashed Venom ROM, ViperOne 6.2.0.
This one took long to boot up as well but once it did it would just show HTC logo screen upon screen unlock.
I gave it time and it actually brings up the "get started page" 5 min in - problem is it would reboot 1 min after.
After i flashed kernel.
Newest version of Gapps.
Tried LiquidSmooth Rom - that would boot me up but didn't solve my issue plus it didn't have google play and other apps.
I even tried going back to the recovery. It would SPRINT it back into stock yet have the acquired issues since i installed the mod: show HTC logo screen once it entered the UI and the rest of bs
I managed to get the get started page and run through it real quick before it rebooted.
But it had no service, and all those issues i stated above.
Now i came back to ViperOne and once the logo screen flashed to "get started" i ran through it real quick and now thats where im at. But it restarts. And has initial issues.
My Plan:
I researched and came to conclusion that i need to flash the radio.
But before i see i need to flash the Firmware.
In order to flash the firmware i need to Get S-OFF.
Ran RumRunnerr, FireWater, MoonShine they all crash at one point or another.
So Im stuck and idk what to do. Unable to go stock or fix the present. Any ideas?
Screens:
Other Comments:
Im kinda new to this. had a few successful Roots but when it came to mods I bricked two phones now.
Level of knowledge 4/10. Have basic Terminology down.
ShoutOut: ViperOne is beast. Love it - if it would work. But Venom Team did an outstanding job. :good:
Oh and btw my HTC ONE is Blue lol.. hope that helps x)
Click to expand...
Click to collapse
okay qiute a lot of work you did there... i personally recommend mooshine s-off.. i also didnt get s-off in rumrunner and firewater kept crashing... try moonshine on a windows 7 pc, it'll work for sure... and after that run RUU of your preferred choice of base band and it should fix your problem...:fingers-crossed:
praveensk.rcb said:
okay qiute a lot of work you did there... i personally recommend mooshine s-off.. i also didnt get s-off in rumrunner and firewater kept crashing... try moonshine on a windows 7 pc, it'll work for sure... and after that run RUU of your preferred choice of base band and it should fix your problem...:fingers-crossed:
Click to expand...
Click to collapse
yea.. i forgot to write moonshine in there
I've tried all them bottles out there and none of em buzz me up right.
TimFUSE said:
yea.. i forgot to write moonshine in there
I've tried all them bottles out there and none of em buzz me up right.
Click to expand...
Click to collapse
are you trying it in windows 7 pc or in windows 8.1... because in windows 8.1 there is no driver support and there is chances of bricking the phone...:fingers-crossed:
praveensk.rcb said:
are you trying it in windows 7 pc or in windows 8.1... because in windows 8.1 there is no driver support and there is chances of bricking the phone...:fingers-crossed:
Click to expand...
Click to collapse
It doesnt matter .. i am able to do everything on win8.1 pc as i am in win7. All you have to do is find and install correct drivers if they dont install automatically.
Although attempting S-OFF methods were done on win7 PC.
But in any case I appreciate your input because i started getting a feeling that no-one replies to new posts now.
Apart from that you pushed me to go out and research more and i found a simple method that took me back to stock in about 20 min.
This post saved my crying soul.. thank you - O.M.J
And thank you - praveensk.rcb. You're a good friend :fingers-crossed:
Important note
If anyone will find the method above helpful - something to keep in mind - it wipes your internal storage.
So if you have somth on your internal SDCard that you dont wanna loose - u know what to do.
TimFUSE said:
Important note
If anyone will find the method above helpful - something to keep in mind - it wipes your internal storage.
So if you have somth on your internal SDCard that you dont wanna loose - u know what to do.
Click to expand...
Click to collapse
its ok timFUSE... glad your phone is up and running...:highfive::victory:
praveensk.rcb said:
its ok timFUSE... glad your phone is up and running...:highfive::victory:
Click to expand...
Click to collapse
I also found out what the problem was.
My TWRP was not designed for Sprint HTC One.
Sprint requires its own TWRP to flash properly.
So now i ROMed into ViperOne 6.2.0 :highfive:
Need Help!
Hey guys i'm getting an active cmdline over flow on my Sprint Htc One that i sim unlocked to use on a GSM network. Sadly along with that i'm constantly dropping and reconnecting to the network.
It appears that my mmcblk0p19 seems to be corrupted.
So my question is can anyone who has a Sprint Htc One PN072 pull the misc partition from their phone and upload it so that i may compare and fix mine?
in custom recovery, do the following adb commands:
adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
adb pull /tmp/mmcblk0p19_bak.img
Any assistance will be greatly appreciated
relic626 said:
Hey guys i'm getting an active cmdline over flow on my Sprint Htc One that i sim unlocked to use on a GSM network. Sadly along with that i'm constantly dropping and reconnecting to the network.
It appears that my mmcblk0p19 seems to be corrupted.
So my question is can anyone who has a Sprint Htc One PN072 pull the misc partition from their phone and upload it so that i may compare and fix mine?
in custom recovery, do the following adb commands:
adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
adb pull /tmp/mmcblk0p19_bak.img
Any assistance will be greatly appreciated
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showpost.php?p=42351491 :fingers-crossed:
Thanks but.....
praveensk.rcb said:
try this http://forum.xda-developers.com/showpost.php?p=42351491 :fingers-crossed:
Click to expand...
Click to collapse
Seems legit but like i said my mmcblk0p19 appears to be corrupted here's a SS of the fist page of code.
Keep in mind i have no idea of how it's supposed to look.
https://www.dropbox.com/s/rmfk256r1wtl8fm/Screenshot 2014-05-16 22.45.07.png
Problems. Lots of Problems.
TimFUSE said:
I also found out what the problem was.
My TWRP was not designed for Sprint HTC One.
Sprint requires its own TWRP to flash properly.
So now i ROMed into ViperOne 6.2.0 :highfive:
Click to expand...
Click to collapse
I had no signal on my ROM after fixing a bunch of other issues, Now my HTC is relocked, tampered, and i get the "unfortunately qualcomm enhanced location service has stopped" error after I get past the lockscreen. I really need help the sooner the better thank you in advanced!!
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: *****************
(bootloader) meid: ***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

[Q] Cannot install any ROM's at all, but can access bootloader.

Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.
I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.

Categories

Resources