Database Develop

[Q] [Help] Brick help needed [Solved!]

I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s

Use otg cable +USB mouse to control the phone
sent from my mobile device

update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?

Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?

medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.

You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/

SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?

What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.

SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!

[Q] Please Help

So I woke up today and decided I wanted to get a custom ROM on my HTC One. This sounded all good. I unlocked the bootloader and rooted the rom. All was fine until I tried to flash a custom rom. I had the ViperOne ROM ready to go but it would install and then get stuck on the loading. I presumed I would just have to wipe everything and then re-install the zip. This is where I messed up. I wiped the MicroSD in which the zip was originally on.
So now I am left with a device that has no OS. Basically a paperweight. From looking around I have found some topics that say that I just need to flash a RUU back onto the phone but something always fails and never works out.
As of right now, ADB is NOT working and the only way I can access the phone is through fastboot.
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
From the info above I went and downloaded "RUU Zip M7 Google Edition 4.4 3.58.1700.5" from htc1guru though when I went to install it, it failed. Putting me back at square 1.
Please help!!
Thanks in advance

DarkShock124 said:
So I woke up today and decided I wanted to get a custom ROM on my HTC One. This sounded all good. I unlocked the bootloader and rooted the rom. All was fine until I tried to flash a custom rom. I had the ViperOne ROM ready to go but it would install and then get stuck on the loading. I presumed I would just have to wipe everything and then re-install the zip. This is where I messed up. I wiped the MicroSD in which the zip was originally on.
So now I am left with a device that has no OS. Basically a paperweight. From looking around I have found some topics that say that I just need to flash a RUU back onto the phone but something always fails and never works out.
As of right now, ADB is NOT working and the only way I can access the phone is through fastboot.
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
From the info above I went and downloaded "RUU Zip M7 Google Edition 4.4 3.58.1700.5" from htc1guru though when I went to install it, it failed. Putting me back at square 1.
Please help!!
Thanks in advance
Click to expand...
Click to collapse
You will need to buy a USB OTG cable, which costs about $5. This is a microUSB to full USB cable. On a FAT32-formatted USB, transfer the ViperOne zip to the USB storage. Then, in TWRP recovery, choose the /usb otg directory. Then, flash the ViperOne zip from TWRP.
FYI, you cannot flash a Google Play RUU if you're S-ON. The phone needs to be S-OFF for that

raghav kapur said:
You will need to buy a USB OTG cable, which costs about $5. This is a microUSB to full USB cable. On a FAT32-formatted USB, transfer the ViperOne zip to the USB storage. Then, in TWRP recovery, choose the /usb otg directory. Then, flash the ViperOne zip from TWRP.
FYI, you cannot flash a Google Play RUU if you're S-ON. The phone needs to be S-OFF for that
Click to expand...
Click to collapse
Ok so i got the cable and flashed the ROM, now it is getting to the boot and just rebooting into TWRP.
The only error I got during the installation was the "set_metadata_recursive: some changes failed"

What version of twrp?
sent from my mobile device

SaHiLzZ said:
What version of twrp?
sent from my mobile device
Click to expand...
Click to collapse
Yeah that was the problem. The version was old and it was reported to have those issues. I flashed the newest version of the recovery and the installation went fine and I have my phone back now.
Thanks anyway

Device not found using adb

I have an htc one that is "tampered" and unlocked loaded with twrp. i have no os on the phone trying to push a custom rom using adb however no matter what i try cannot get the device to find ........ive tried uninstalling drivers and reinstalling them tried the universal naked drivers and still getting nothhing....my device is listed under android devices as my htc can someone give me some insight on what to do or get adb to recognize my phone?

Tommyboy77 said:
I have an htc one that is "tampered" and unlocked loaded with twrp. i have no os on the phone trying to push a custom rom using adb however no matter what i try cannot get the device to find ........ive tried uninstalling drivers and reinstalling them tried the universal naked drivers and still getting nothhing....my device is listed under android devices as my htc can someone give me some insight on what to do or get adb to recognize my phone?
Click to expand...
Click to collapse
what's your HBoot ver. ?
what's your PC OS , W7 or W8 ?
can you post your getvar all ? (without IMEI and S/N)

moha_moha20106 said:
what's your HBoot ver. ?
what's your PC OS , W7 or W8 ?
can you post your getvar all ? (without IMEI and S/N)
Click to expand...
Click to collapse
HBOOT 1.56.0000
Windows 7
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146194387
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(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.044s
Ive been going in circles for days now....I have a custom rom i want to flash because there is no os on the phone...it did boot into recovery fine when i had twrp on there.....but i tried to flash clockwork mod now it just hangs in a bootloop trying to go into recovery and cant get it to flash back to twrp.....if i can find out how to get this device seen i can get it working again....thanks for your help

[Q] How to get my HTC One up and running again?

Hi,
I wanna get an idea about the issue on my HTC One. I have a,
HTC One International version
Unlocked
S-On
Hboot: 1.54.0000
OS: 2.24.401.9
Earlier: TWRP 2.6.3.3
Now: TWRP 2.7.0.0
which rooted and I have been using various Sense based custom roms for about 6 months. After recent custom rom installation, my device didn't load the initial setup wizard. It was saying "service.htc.htcdialer failed". So what I did was I installed another custom rom. It also gave the same issue. After that I downloaded a Stock Zip file from here and flashed using these instructions. But I have no luck because it gave me an error like this during flashing process.
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
Currently, My device is loading into bootloader and that is it. Nothing loads when you turn the device on. Only the HTC logo and then restart. I also flashed TWRP 2.7.0.0 finally thinking that it might be more helpful than the Stock recovery.
I'm pulling my hair now and I wanna fix my device. Can anyone direct me to find the correct RUU or Zip file to flash?. Also please tell me how do I prepare my device to fix it?. This will be a great help.
Thanks you very much.
Dam.

im having the same problem. i can get to bootloader but i cant start my phone. its also boot looping. i found http://forum.xda-developers.com/showthread.php?t=2317985& but i dont know what .zip file im supposed to have or where to get it.

Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.

fenstre said:
Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.
Click to expand...
Click to collapse
sorry to jack your thread damithark
hey fenstre. so my problem is i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader. i also just ran the fastboot getvar all but im not sure what im looking for. ive tried factory resetting and everything else that you can do from the bootloader.

fenstre said:
Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.
Click to expand...
Click to collapse
This was caused because of a strange issue I encountered. After a reboot, I got a message saying my internal storage is encrypted and asked a password to decrypt. I didn't attempt any encryption and from what I found from google is that I need to do a data reset. So I did that and installed a Rom from TWRP and that was not starting up. It said "service.htc.htcdialer failed to start". So I had to then install a stock recovery and try flashing a RUU zip file. It also failed with this.
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
I have a these RUU files,
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4.exe
RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Guru_Reset_M7_2.24.401.8.zip
and these are the info,
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA36RW908595
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4250mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
How am I to proceed?.
Thanks.

redelmos said:
sorry to jack your thread damithark
hey fenstre. so my problem is i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader. i also just ran the fastboot getvar all but im not sure what im looking for. ive tried factory resetting and everything else that you can do from the bootloader.
Click to expand...
Click to collapse
It's alright mate. Hope you'll find an answer. :good:

So I red some threads recently and found an RUU that supports my CID number. Any help to continue?.

redelmos said:
i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader.
Click to expand...
Click to collapse
I think issues like that are common. You can wipe: cache/dalvik cache/data. You can also boot recovery and do a filesystem check on /system with this command: "e2fsck -f /dev/something/something", where you can find what "something" is by mounting /system and running "mount|grep system", then unmounting it. If none of that works, the kernel installer must have borked your existing CM install, and you'll need to reinstall.
damithark said:
So I red some threads recently and found an RUU that supports my CID number. Any help to continue?.
Click to expand...
Click to collapse
Good. I suggest googling it.

I think I found the issue. I can't flash any RUU that are available because my HBOOT version is 1.54. RUU file needs a earlier version of the HBOOT version (Eg: HBOOT 1.44). So to downgrade my HBOOT, I think I need to S-OFF. Because I'm in a boot loop, I can't S-OFF because it requires me to enable debugger mode. Is there a way to S-OFF using bootloader?. Please help me. I'm Stuck with this for 2 days now.
Thanks.

I really love to get some help on this one please.

I don't know why anyone doesn't helps me. I have a HTC One which is,
Loading to bootloader,
Have TWRP 2.7 installed,
Device fully Data Wiped,
In a bootloop,
ADB doesn't recognize my device.
Only fastboot does.
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What do I do to fix my phone?. I'm from Sri Lanka where mobile is mostly needed these days because it is the Festival season here. Any help will be greatly appreciated.
Thanks.

damithark said:
I don't know why anyone doesn't helps me. I have a HTC One which is,
Loading to bootloader,
Have TWRP 2.7 installed,
Device fully Data Wiped,
In a bootloop,
ADB doesn't recognize my device.
Only fastboot does.
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What do I do to fix my phone?. I'm from Sri Lanka where mobile is mostly needed these days because it is the Festival season here. Any help will be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Buy a USB OTG cable (very cheap, about $5)
Copy ARHD/any other rom of your choice to a USB
Plug in your USB OTG cable with the USB containing the rom attached to the cable
Mount USB OTG in the Mounts section (within TWRP)
Hit Install, scroll up to the root of the phone (NOT THE /sdcard)
There, choose storage or USB OTG (whatever in shows)
Flash the ROM and wipe in Aroma
Profit

i already told you go back to 2.6.3.3 or .4

nkk71 said:
i already told you go back to 2.6.3.3 or .4
Click to expand...
Click to collapse
I did and it worked. Now I have another issue,
So what I did was I sideloaded a Custom Rom (ViperOne_5.8.0).
Installed it.
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
It continuously happens every time the device restarts. Can't pass the initial screen.
What do I have to do now?.
Thanks a lot.for the help so far.

damithark said:
I did and it worked. Now I have another issue,
So what I did was I sideloaded a Custom Rom (ViperOne_5.8.0).
Installed it.
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
It continuously happens every time the device restarts. Can't pass the initial screen.
What do I have to do now?.
Thanks a lot.for the help so far.
Click to expand...
Click to collapse
Wipe all the partitions except Internal Storgae in the 'Wipe' section of TWRP and in the Aroma and then re-install the ROM. For some reason, the Aroma wipe doesn't work properly. I also had the same issue........
The wipe did the trick

damithark said:
I did and it worked. Now I have another issue,
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
Click to expand...
Click to collapse
that doesn't sound good
In booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Is it saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
hope not!!

raghav kapur said:
Wipe all the partitions except Internal Storgae in the 'Wipe' section of TWRP and in the Aroma and then re-install the ROM. For some reason, the Aroma wipe doesn't work properly. I also had the same issue........
The wipe did the trick
Click to expand...
Click to collapse
Thanks for the tip raghav. I did what you said and it doesn't work. Same issue appears saying "Process 'com.htc.htcdialer' isn't respoding".
and, reboots after a while. Do you think this is a hardware issue?.
Thanks for the help.

nkk71 said:
that doesn't sound good
In booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Is it saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
hope not!!
Click to expand...
Click to collapse
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.

damithark said:
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.
Click to expand...
Click to collapse
Very very strange. I was on the latest Kitkat firmware, S-OFF and SuperCID though. @nkk71 had suggested me to wipe when I had that issue. That solved my problem. However, ARHD ALWAYS worked for me. InsertCoin and ViperOne gave me that same error. And, my networking wasn't working at all either in ViperOne/InsertCoin. I flashed ARHD, which has a 100% success rate for me.
My suggestion: Flash ARHD 31.6, which SHOULD work
Then S-OFF through Rumrunner
Update to 4.19.401.11
Then SuperCID
After that, choose any ROM

damithark said:
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.
Click to expand...
Click to collapse
1- Remove IMEI and s/n from your post.
2- get a "thinner" ROM, for example: http://forum.xda-developers.com/showthread.php?t=2272945
then check the above information

Help!!! I erased OS completly of my HTC One M7 T Mobile with TWRP

I need help, I just got this phone and was unlocking bootloader and starting to root and then I was trying to erase cache and delvik and didnt see that system was also checked, so I accidentally erased the OS and I am struggling with the command line. My device is not being recognized when I type adb devices, I did manage to get fastboot getvar all info. I cant do adb push command and I dont know what rom to install, whether its stock or custom. As I said my bootloader is unlocked but The S is Off. I am going crazy tryna figure it out. I thought maybe I should update my recovery but Im stuck even on that since my device isnt being recognized. I read through a bunch of forums for the same issues but most are international or different carriers. This is the first time I really had an issue with unlocking and rooting. This command line is killing me. Someone please help

Boston5377 said:
I need help, I just got this phone and was unlocking bootloader and starting to root and then I was trying to erase cache and delvik and didnt see that system was also checked, so I accidentally erased the OS and I am struggling with the command line. My device is not being recognized when I type adb devices, I did manage to get fastboot getvar all info. I cant do adb push command and I dont know what rom to install, whether its stock or custom. As I said my bootloader is unlocked but The S is Off. I am going crazy tryna figure it out. I thought maybe I should update my recovery but Im stuck even on that since my device isnt being recognized. I read through a bunch of forums for the same issues but most are international or different carriers. This is the first time I really had an issue with unlocking and rooting. This command line is killing me. Someone please help
Click to expand...
Click to collapse
Post your getvar all. Please remove IMEI and serial number before posting.
Also which version of TWRP are you using?
Sent from my HTC One M9 using Tapatalk

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5fbd03bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.194s
I am using TWRP v2.6.0.1
Thanks for the reply.

Boston5377 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5fbd03bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.194s
I am using TWRP v2.6.0.1
Thanks for the reply.
Click to expand...
Click to collapse
OK first thing your TWRP is a very old version. You should update that first. If you hadn't wiped system flashing a rom with that twrp would have you in the same position with a soft brick anyway. Also the latest version allow MTP in recovery so you won't need to add push
Use this one for now http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.4.0-m7.img
Were you planning on flashing a custom rom. Or did you want to keep the stock rom?
Sent from my HTC One M9 using Tapatalk

I want to flash a custom rom. So then how do I flash the new TWRP?

Boston5377 said:
I want to flash a custom rom. So then how do I flash the new TWRP?
Click to expand...
Click to collapse
Same as you flashed the other twrp.
Download the .img copy it to your fastboot folder. Connect fastboot usb in the bootloader then in the fastboot command window type
Code:
fastboot erase cache
fastboot flash recovery "name of recovery".img
fastboot reboot-bootloader
Then from the bootloader menu select Recovery. You can check it's the new version as the top of the TWRP home screen.
Then go to "Mounts" and there should be an option to enable MTP. Activate it if it's not already. Then you should be able to access your internal storage on your PC as if it were booted to Android. Copy your chosen rom and flash Install it.
If you still can't get MTP or adb to work you may have a driver problem.
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My*HTC*..." -> install the latest in the list.
Sent from my HTC One M9 using Tapatalk

Holy Batman I am saved, Thank you Soooooo much

Boston5377 said:
Holy Batman I am saved, Thank you Soooooo much
Click to expand...
Click to collapse
Your welcome, glad you got it sorted. :good: :high-five:
Sent from my HTC One M9 using Tapatalk

Can I piggyback on this thread? I was running a ROM, did an "advanced wipe" in TWRP, erased everything (including "Internal Storage") and of course this erased the OS, so I used adb push to put the exact same ROM's flashable zip file back on the phone and tried re-flashing. But now I get stuck on the boot animation. More than half an hour.
Also TWRP is taking a long time to load now (3 minutes or so?). Did some partition get corrupt or do I just need to be patient and use a different technique?
Yes, I know TWRP 2.6.3.4 is out of date but honestly all I did is wipe things, the same combination of ROM and recovery was working before I touched it today!
S-OFF, unlocked, superCID etc. So I have options.
It's been quite awhile since I touched this phone - apologies if this is a newbish question..

You can always try exactly what I did. It worked because my TWRP was old. What have you got to lose? Just download from above link and type "fastboot flash recovery Name-of-file.img" and it should flash the new one on and go to mount then tap disable MTP and then press again to enable it, that reloads basically. Then plug it in and it should show on your pc, place rom in phones root and then exit and install rom. It was simple although your S is Off so there might be a different way.

Ok I'll give it a shot..