Hello, and thank you in advance for reading and offering your help.
I have a HTC One M7 that I tried to root with SuperSU following a video on youtube. It worked the first time, but wasn't rooted and the SuperSU app didnt work, so I got the updated version, tossed it in, flashed(after following the exact same previous steps), and now the phone is stuck in a loop of turning on and off. I CAN reach my TWERP menu, and the Sprint technician i spoke with today told me to get a ROM(I got VenomOne's), and then plug my phone up after taking it to recovery mode, hit mount, and then just flash it in. The issue is: When i plug my phone into my laptop, it does no mount. It is not my USB Cord, or my phone. Its something to do with the firmware or something, who knows! But I really need some help, and would appreciate anything you can do for me, XDA!
PS: Recovery files non-existent. I and he tried, but they just aren't there. I think I wiped em.
SoftbrickedHTC1 said:
Hello, and thank you in advance for reading and offering your help.
I have a HTC One M7 that I tried to root with SuperSU following a video on youtube. It worked the first time, but wasn't rooted and the SuperSU app didnt work, so I got the updated version, tossed it in, flashed(after following the exact same previous steps), and now the phone is stuck in a loop of turning on and off. I CAN reach my TWERP menu, and the Sprint technician i spoke with today told me to get a ROM(I got VenomOne's), and then plug my phone up after taking it to recovery mode, hit mount, and then just flash it in. The issue is: When i plug my phone into my laptop, it does no mount. It is not my USB Cord, or my phone. Its something to do with the firmware or something, who knows! But I really need some help, and would appreciate anything you can do for me, XDA!
PS: Recovery files non-existent. I and he tried, but they just aren't there. I think I wiped em.
Click to expand...
Click to collapse
post the output of "fastboot getvar all" remove your IMEI/MEID/SERIALNO before posting
what is your twrp version?
What version of Supersu is installed?
alray said:
post the output of "fastboot getvar all" remove your IMEI/MEID/SERIALNO before posting
what is your twrp version?
What version of Supersu is installed?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3768mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
TWRP Version: 2.6.3.0
SuperSU-V2.46.zip
SoftbrickedHTC1 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3768mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
TWRP Version: 2.6.3.0
SuperSU-V2.46.zip
Click to expand...
Click to collapse
You could simply relock your bootloader and flash the 6.23.651.6 ruu.exe to fix the bootloop issue.
Then unlock it again and root using Verizon TWRP 2.8.6.0 which should have the up-to-date Supersu binaries.
How would I do that? I am not super tech savvy. Thanks for your response! I appreciate it greatly!
Update: Also now, when I try to start my phone, i get the HTC One screen, and then it goes straight to TWRP after. Also, why would I use Verizon TWRP? Would that mess anything up? I have Sprint.
Update2: I relocked my bootloader, and I am installing the RUU. I get an error that tells me to make sure my phone is connected via USB(this is part of the mounting issue I assume). Also, now my boot screen says tampered, relocked, and security warning. Please help! Thanks!
Anyone have any other idea?
Related
Hey guys! So, I got a pop up on my phone last week for the 4.4.2 update However, I seem to be unable to install it. I get booted into twrp, so I try to install it from there, but it says flash failed. I am completely hopeless with things like this (wasn't me who rooted my phone etc). Any help would be very appreciated and apologies for my stupid question.
fsmn said:
Hey guys! So, I got a pop up on my phone last week for the 4.4.2 update However, I seem to be unable to install it. I get booted into twrp, so I try to install it from there, but it says flash failed. I am completely hopeless with things like this (wasn't me who rooted my phone etc). Any help would be very appreciated and apologies for my stupid question.
Click to expand...
Click to collapse
you need stock recovery to install ota. Find the stock recovery you need and flash it like any recovery
Code:
fastboot flash recovery <name_of_file>.img
fastboot reboot
and try to install the ota again.
alray said:
you need stock recovery to install ota. Find the stock recovery you need and flash it like any recovery
Code:
fastboot flash recovery <name_of_file>.img
fastboot reboot
and try to install the ota again.
Click to expand...
Click to collapse
How do I figure out which stock reovery I need?
fsmn said:
How do I figure out which stock reovery I need?
Click to expand...
Click to collapse
post the output of fastboot getvar all minus IMEI/sn
Hi there.
I like fiddling and wanted to build some BLE apps and hence required Android 4.3 or higher. We were seriously slow with the updates here in South Africa and I decided to root and load stock HTC 4.3 and later 4.4. My phone does however want to do OTA updates on 4.4 (even though other M7 users here don't have it yet, only received 4.3 about a month ago, which was when I flashed 4.4). I understand 4.4.2 for the M7 is out and would like to keep with the HTC stock updates. I do however experience your exact same issue and have read previously that I need a stock Recovery.
My question is exactly the same as yours. How do I know which Recovery to download and where do I download it from. Finding ROMs is easy and so is custom Recoveries (like TWRP), but not sure about finding the stock Recovery.
Thanks guys!
---------- Post added at 03:42 PM ---------- Previous post was at 03:29 PM ----------
Wow, that reply was so quick, it was even before my addition to the question
Here is the printout:
(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.62.401.1
(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: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3955mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
Thank you for the assistance!
The Stock recovery needs to match your current "version-main", so in your case a 3.63.x.x , if you can match all 4 numbers that's best but for sure the first two.
alray said:
post the output of fastboot getvar all minus IMEI/sn
Click to expand...
Click to collapse
(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.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Recovery for stock_3.62.401.1
https://www.dropbox.com/s/i9v6ungs3dw1low/stock_3.62.401.1.img
bored_stupid said:
Recovery for stock_3.62.401.1
*link*
Click to expand...
Click to collapse
Thank you!
Let me know how you get on
bored_stupid said:
Let me know how you get on
Click to expand...
Click to collapse
I FINALLY got it to work (yes, totally hopeless)! Yay! Thank you both for the help!
Thats great news. could edit main thread title to include [SOLVED], thanks
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
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
Hi,
Like an idiot, I forgot to take a backup before I flashed CM to my M7. At first, it hung on the loading screen, but after a factory wipe in TWRP, it at least booted. Unfortunately, my touch screen doesn't work, so I can't actually *do* anything. I don't fully know what all I can do with just TWRP, ADB, and Fastboot, and I'd rather not shell out for a new phone. Any advice?
lieronet said:
Hi,
Like an idiot, I forgot to take a backup before I flashed CM to my M7. At first, it hung on the loading screen, but after a factory wipe in TWRP, it at least booted. Unfortunately, my touch screen doesn't work, so I can't actually *do* anything. I don't fully know what all I can do with just TWRP, ADB, and Fastboot, and I'd rather not shell out for a new phone. Any advice?
Click to expand...
Click to collapse
Firstly, if it hangs at the loading screen, wiping it is kinda silly. AS far as im not mistaken, wiping in TWRP will also wipe the OS. So, currently, u don't have a full OS on the phone.
In TWRP 2.7.0.0, you can use an external mouse via USB OTG. So, buy a USB OTG cable, plug in a mouse. then perform a WIPE BEFORE FLASHING THE ROM. So wipe first, then flash CM, then reboot. If it still gets stuck, ask for help. But don't wipe. Im hoping that u didn't wipe the Internal SD card...........
Thanks for the reply. My touchscreen works in Recovery, but not in the OS. I assume this means I don't need to buy the adapter you mentioned? Anyway, I do not believe I wiped the SD card. I am having trouble flashing cyanogenmod through Fastboot. Which partition should I be flashing it to? I apologize for my very basic questions, but I'm in a bit over my head here.
lieronet said:
Thanks for the reply. My touchscreen works in Recovery, but not in the OS. I assume this means I don't need to buy the adapter you mentioned? Anyway, I do not believe I wiped the SD card. I am having trouble flashing cyanogenmod through Fastboot. Which partition should I be flashing it to? I apologize for my very basic questions, but I'm in a bit over my head here.
Click to expand...
Click to collapse
you don't flash a rom from fastboot
flash it from recovery (TWRP)
---------- Post added at 05:56 PM ---------- Previous post was at 05:48 PM ----------
clsA said:
you don't flash a rom from fastboot
flash it from recovery (TWRP)
Click to expand...
Click to collapse
more information is needed if you really want help
post fastboot getvar all (minus serial no and imei)
post the link to the CM you flashed
post what recovery your using
do you have s-off
clsA said:
more information is needed if you really want help
post fastboot getvar all (minus serial no and imei)
post the link to the CM you flashed
post what recovery your using
do you have s-off
Click to expand...
Click to collapse
getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(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: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
loaded CM 10.1-20130512-CPUFREQ-m7, which is probably ancient. Got it from ROM manager.
Using CWM Recovery 6.0.4.3 right now
I do not have s-off, which is weird because I had it previously.
I appreciate the help.
lieronet said:
getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(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: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
loaded CM 10.1-20130512-CPUFREQ-m7, which is probably ancient. Got it from ROM manager.
Using CWM Recovery 6.0.4.3 right now
I do not have s-off, which is weird because I had it previously.
I appreciate the help.
Click to expand...
Click to collapse
yep your on the new AT&T Firmware
you can flash the RUU and try to get it back or look for the new version of CM
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Hello Everyone,
I am new to the whole custom rom thing, so I tried something simple on my HTC One (M7). The Install program that is new from Cyanogenmod. It was all looking fine and it installed (I think) in the end, after a few restarts, I was left with the blue cyanogenmod icon, a blue arrow going around it and white text beneath saying cryanogenmod. This went on for 4 hours. I thought this cant be normal and tried to restart the phone. It all worked, but when it was booting normally again, nothing changed, still the icon with the arrow circling it. So that wasn't all how I wanted it to be. I went in the recovery mode and I got there fine, but I noticed some things that were strange, for example, it told me, that it could not mount /data.
All I really want now is either the Stock Android that came with the HTC or the Cyanogenmod Version working, either way I have no idea on how to continue, I hope you can help me.
Thank you
Jonah
jonahmoeller said:
Hello Everyone,
I am new to the whole custom rom thing, so I tried something simple on my HTC One (M7). The Install program that is new from Cyanogenmod. It was all looking fine and it installed (I think) in the end, after a few restarts, I was left with the blue cyanogenmod icon, a blue arrow going around it and white text beneath saying cryanogenmod. This went on for 4 hours. I thought this cant be normal and tried to restart the phone. It all worked, but when it was booting normally again, nothing changed, still the icon with the arrow circling it. So that wasn't all how I wanted it to be. I went in the recovery mode and I got there fine, but I noticed some things that were strange, for example, it told me, that it could not mount /data.
All I really want now is either the Stock Android that came with the HTC or the Cyanogenmod Version working, either way I have no idea on how to continue, I hope you can help me.
Thank you
Jonah
Click to expand...
Click to collapse
What custom recovery and version were you using?
Which Cyanogenmod were you flashing and where did you get it?
Did you check the MD5 of the files downloaded?
Can you post a fastboot getvar all except remove the imei and serialno?
What custom recovery and version were you using?
ClockworkMod Recover v6.0.4.8
Which Cyanogenmod were you flashing and where did you get it?
It didn't specify anywhere on their homepage, all it said it was using the last stable version, since I did this two days ago it should be I face the latest they have for the Htc One
Did you check the MD5 of the files downloaded?
I did in face and it all checked out fine
Can you post a fastboot getvar all except remove the imei and serialno?
(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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(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
all: Done!
finished. total time: 0.119s
Thanks for the quick replay @majmoz
jonahmoeller said:
What custom recovery and version were you using?
ClockworkMod Recover v6.0.4.8
Which Cyanogenmod were you flashing and where did you get it?
It didn't specify anywhere on their homepage, all it said it was using the last stable version, since I did this two days ago it should be I face the latest they have for the Htc One
Did you check the MD5 of the files downloaded?
I did in face and it all checked out fine
Can you post a fastboot getvar all except remove the imei and serialno?
(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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(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
all: Done!
finished. total time: 0.119s
Thanks for the quick replay @majmoz
Click to expand...
Click to collapse
have you tried to flash the rom using a custom recovery instead of using the installer?
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
use the recovery version specified in the above link.