This may or may not be n00b question!
I have never had any trouble rooting/installing roms on my previous devices, but with my HTC One, I can't figure out what has been giving me all of these bootloops since coming to baad's rom.
I have tried installing this rom, through its various versions, but ever since coming to 2.6 and above (2.7.0 and 3.0.0) I have managed to get a bootloop when installing something from Insertcoin Market, as well as when restarting from the boot menu. To resolve this, I just install the rom once more via recovery, but it's a pain.
I have tried both TWRP 2.6.3.3 and 2.7.4.05.05, but neither seem to resolve the issue. I haven't noticed this to be a recurring problem with any other users, and those that have had bootloops, their solutions do not apply to my case.
I have done both dirty and clean flashes, so I can't pinpoint the issue.
Anyone have any similar issues?
I appreciate all of the help!
I bought the phone in used condition, so I'm thinking there might have been something the previous owner used that is conflicting with my current setup?
Is my best bet to revert back to stock (rom, firmware, and kernel) and try to replicate the issues?
So if you instaall the ROM and setup the basic things - you get a bootloop after reboot?
Can you post fastboot getvar all (no IMEI/Serial) here?
davebugyi said:
So if you instaall the ROM and setup the basic things - you get a bootloop after reboot?
Can you post fastboot getvar all (no IMEI/Serial) here?
Click to expand...
Click to collapse
Yes, after reboots; I also get a bootloop when trying to install InsertCoin Market mods.
Thanks for taking a look; this is what comes up:
C:\Users\wildcat>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
C:\Users\wildcat>
Well, Only things coming to my mind:
Check download with MD5 if it is not corrupted.
I also updated the Radio - Mine is 4T.27.xxxx (yours - 4A.19.3263.13) - might worth to update it to the latest - search for firmwares in development thread.
Some Aroma setting is not currently ported good, thus causing bootloop - check the latest ROM from SVN.
davebugyi said:
Well, Only things coming to my mind:
Check download with MD5 if it is not corrupted.
I also updated the Radio - Mine is 4T.27.xxxx (yours - 4A.19.3263.13) - might worth to update it to the latest - search for firmwares in development thread.
Some Aroma setting is not currently ported good, thus causing bootloop - check the latest ROM from SVN.
Click to expand...
Click to collapse
Thank you! Will try some of these solutions sometime today. Will update if it was successful.
Related
Hi all,
I've been banging my head for quite some time on why I haven't received any of the OTA updates. I'm still on 4.2.2 and seeing my friends, with different variants of course, getting KitKat... pisses me off
As you can see I'm S-on and was wondering if I really need to go through the hassle of S-Off.
Can anyone here offer a simple walkthrough or a link to download a relevant OTA or Stock ROM that could start getting me OTA updates?
In the searches I've done I couldn't find an OTA I could manually flash since none of the OTAs base versions is 2.24.401.9. Signature fail every time.
adb and fastboot fully functional.
I didn't flash any recovery or other img yet. Fresh out of the box.
Here are my device details:
(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: HT37BW900798
(bootloader) imei: Mod edit removed IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(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
all: Done!
Help will be greatly appreciated.
Thanks,
Ita
itaita22 said:
Hi all,
I've been banging my head for quite some time on why I haven't received any of the OTA updates. I'm still on 4.2.2 and seeing my friends, with different variants of course, getting KitKat... pisses me off
As you can see I'm S-on and was wondering if I really need to go through the hassle of S-Off.
Can anyone here offer a simple walkthrough or a link to download a relevant OTA or Stock ROM that could start getting me OTA updates?
In the searches I've done I couldn't find an OTA I could manually flash since none of the OTAs base versions is 2.24.401.9. Signature fail every time.
adb and fastboot fully functional.
I didn't flash any recovery or other img yet. Fresh out of the box.
Here are my device details:
(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: HT37BW900798
(bootloader) imei: Mod edit removed IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(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
all: Done!
Help will be greatly appreciated.
Thanks,
Ita
Click to expand...
Click to collapse
No idea why people want stock OTA...
Unlock bootloader, install TWRP, flash whatever rom you want. No need for s-off.
Simple as 1, 2, 3.
Moderator Information,
I have removed your IMEI number. This is personal information and you shouldn't post it on line.
Ghost
I have exactly the same problem. HTC One is unrooted (or whatever HTC's expression for root is), but it doesnt want to update to last version 4.4.2, which is already available for my version 3.62.401.1.
If anyhone has an idea how to get OTA for 4.4.2, please let us know.
Why not just flash ARHD 5.1...4.19.401.8.
You will have the latest rom, identical to the stock Rom, but slicker, faster and better. When HTC decide to update that Rom, ARHD will be the first to offer it. No waiting for it to become available for you country/network or variant.
Sent from my HTC One using XDA Premium HD app
cr1960 said:
No idea why people want stock OTA...
Unlock bootloader, install TWRP, flash whatever rom you want. No need for s-off.
Simple as 1, 2, 3.
Click to expand...
Click to collapse
Well, thanks.
I wish to have stock OTA so I won't need to chase after stable releases, battery drain issues, or other wonderful scenarios I know you guys handle daily.
On that matter, installing another stock will put me on track for OTA updates? Are there other factors that could prevent it?
Appreciate the help.
itaita22 said:
Well, thanks.
I wish to have stock OTA so I won't need to chase after stable releases, battery drain issues, or other wonderful scenarios I know you guys handle daily.
On that matter, installing another stock will put me on track for OTA updates? Are there other factors that could prevent it?
Appreciate the help.
Click to expand...
Click to collapse
That's fine - to each his own. My experience has been that you get great stability and even better battery (using custom kernels) with custom roms, but hey, that's just me
You'll just have to wait for your carrier to send the OTA - you can't force it.
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
EDIT: Well this is awkward. After posting this thread I found the solution. If anyone in the future has the same problems as me, just flash one of these
http://forum.xda-developers.com/showthread.php?t=2406330
Apparently that was all that was needed.
Hello xda community,
First off, I apologize. I know questions like these get asked hundreds of times but after spending 3 days straight of digging through forum threads and making very little progress I've decided to just ask.
So I tried installing a custom rom on my HTC One. I did exactly what I usually do when flashing a new rom on my nexus 7. I had an unlocked device with the latest twrp recovery. I did an advanced wipe (which included internal storage), then I did an adb sideload to flash the rom. I must have done something wrong because the flashing didn't work and ever since then I've been trying to get back to stock rom.
I've tried running both the 3.04.651.2 RUU and the 4.06.651.4 RUU posted by O.M.J and neither worked. I've tried flashing the Guru Reset M7 Sprint 3.04.651.2 rom found on htc1guru. Twrp said the flashing was successful yet when I booted up the device it would get to the lockscreen and when I tried to unlock it, it would just show the HTC logo. After that it would endlessly reboot itself over and over. I've tried flashing the Android Revolution HD 31.6 rom and I got the same problems as when I tried to flash the htc1guru stock rom.
I can get into both the bootloader and twrp recovery without any problems so I figure not all hope is lost. Below is info about my phone. As you can see the version-main number is missing, though I don't know how important that is.
Code:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
I'm not sure if it's significant, but I did manage to flash that custom rom today. It's the Slim-m7spr-4.4.2.build.5 rom. I booted up the phone just fine (this is probably the only successful thing I've done so far).
Anyway, like I said I'm trying to get back to stock and I would appreciate any and all help. Thanks guys.
Hi guys, I am having some major issues with my HTC one phone. I was trying to install a rom (ViperOne), but that failed. I thought I knew what I was doing so I didn't wipe cache, etc. I went back into TWRP and tried to restore from backup (I had previously made a backup), but no backups were found! Since then, I've been trying many things. I just want to go back to a stock, fresh install of android. I am a noob at this and have no idea what to do next.
What I can do:
- Fastboot.
- ADB.
- Reach TWRP recovery, and flash other recoveries.
What I cannot do:
- Install other roms via TWRP.
When I try to install a .zip rom, here is the error that occurs:
E: Error executing updater binary in zip '/sdcard'.
Error flashing zip '/sdcard/cm-11/20141129-NIGHTLY.zip'
Updating partition details...
FAILED
Click to expand...
Click to collapse
I'm very angry about this and I hope I do not have to buy a new phone.
Any help is GREATLY appreciated.
OfficialBlox said:
Hi guys, I am having some major issues with my HTC one phone. I was trying to install a rom (ViperOne), but that failed. I thought I knew what I was doing so I didn't wipe cache, etc. I went back into TWRP and tried to restore from backup (I had previously made a backup), but no backups were found! Since then, I've been trying many things. I just want to go back to a stock, fresh install of android. I am a noob at this and have no idea what to do next.
What I can do:
- Fastboot.
- ADB.
- Reach TWRP recovery, and flash other recoveries.
What I cannot do:
- Install other roms via TWRP.
When I try to install a .zip rom, here is the error that occurs:
I'm very angry about this and I hope I do not have to buy a new phone.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
Three questions, just three.
Are you S-ON?
What fastboot/OS version are you running if any?
Code:
fastboot getvar all
What version of TWRP/CWM are you running?
DennisBold said:
Three questions, just three.
Are you S-ON?
What fastboot/OS version are you running if any?
Code:
fastboot getvar all
What version of TWRP/CWM are you running?
Click to expand...
Click to collapse
S-ON: I'm pretty sure. How can I verify this?
Fastboot version: How do I check this? EDIT: Bootloader version seems to be 0.5.
TWRP version: 2.5.0.0
Thanks for the quick reply
OfficialBlox said:
S-ON: I'm pretty sure. How can I verify this?
Fastboot version: How do I check this? EDIT: Bootloader version seems to be 0.5.
TWRP version: 2.5.0.0
Thanks for the quick reply
Click to expand...
Click to collapse
...ah, I see you missed the command.
If you run this using fastboot:
Code:
fastboot getvar all
It'll spit out all the necessary information.
Do you want to upgrade to TWRP 2.7.1.1+? Just go for the latest. It generally has a pretty good chance of working.
DennisBold said:
...ah, I see you missed the command.
If you run this using fastboot:
Code:
fastboot getvar all
It'll spit out all the necessary information.
Do you want to upgrade to TWRP 2.7.1.1+? Just go for the latest. It generally has a pretty good chance of working.
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(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: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
I will upgrade to that TWRP version right now and see how it goes. Will post back in a few minutes.
OfficialBlox said:
Code:
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main: 1.27.531.11
(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) security: on
Click to expand...
Click to collapse
You are S-ON, you're currently running 1.27.531.11. And you really need to go back and edit out your IMEI and SERIALNO.
S-ON means you can flash an RUU containing the same or higher version of the current software, you can't go back. To be on the safe side the download link below contains the RUU for the same version you currently have.
An RUU will restore your device to an out of the box condition with all the default software provided by HTC.
http://www.htc1guru.com/?wpfb_dl=82
OMG.
Got it working after like 15 hours. Would just like to thank you so much, was a simple fix. Whoever else stumbles upon this thread, consider updating your TWRP to the latest version.
OfficialBlox said:
OMG.
Got it working after like 15 hours. Would just like to thank you so much, was a simple fix. Whoever else stumbles upon this thread, consider updating your TWRP to the latest version.
Click to expand...
Click to collapse
Sorry for using all capitals... in advanced!
PLEASE REMOVE YOUR SERIALNO AND IMEI FROM YOUR POST (#5)!
Someone could clone your IMEI and do far worse things using that. So please go back and edit it out. Or plain delete the fastboot output.
OfficialBlox said:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(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: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
Click to expand...
Click to collapse
(removed some things)
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
kayohbe said:
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
Click to expand...
Click to collapse
Please, post the output of "fastboot getvar all" (don't post your imei and serialno).
Sent from my HTC One using XDA Labs
fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
I recognize this is my own mistake as a result of being short sighted and not careful enough with my actions. Also, i'm willing to take any amount of time necessary to learn whatever skills may be required to resolve this issue (how to utilize certain tools properly, specific programming languages etc.)
kayohbe 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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
alray said:
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
Click to expand...
Click to collapse
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
kayohbe said:
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
Click to expand...
Click to collapse
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
alray said:
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
kayohbe said:
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
Click to expand...
Click to collapse
No its to late, try the RUU.
Seems good [:=
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
kayohbe said:
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
Click to expand...
Click to collapse
no problem. Update your phone to the latest version before unlocking and rooting. The latest one is .52
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
kayohbe said:
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
Click to expand...
Click to collapse
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
alray said:
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
Click to expand...
Click to collapse
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
kayohbe said:
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
Click to expand...
Click to collapse
I played the game for 2-3 days at launch and it was easy to spoof a fake gps location to cheat. To do that I also had to hide the fact the I was using "mock location" from the developer options using an Xposed module or the game would detect it. I guess its also really easy to hide the fact the you are using a custom rom/root from pokémon go using the same method... Not tried but im sure it can be done.
I assume it was easy prior to the current update - they've cracked down on 'spoof players' about a week or so ago
Help for HTC - M7
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
1191 said:
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
Click to expand...
Click to collapse
Yes you've download the right file.
Instructions how to flash: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(see post #1)