HTC One boot loop, S-ON - One (M7) Q&A, Help & Troubleshooting

Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.

Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM

I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app

mayaakel said:
I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Didn't mean to thank you.. Using my phone to write this
Read the Q&As here to get your phone recognised
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
After that, install these files to a folder called htc one on your desktop.
http://koush.com/post/universal-adb-driver
Sent from my HTC One using XDA Premium 4 mobile app

Thanks will do
Sent from my Nexus 5 using XDA Free mobile app

raghav kapur said:
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM
Click to expand...
Click to collapse
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"

Torcidas1950 said:
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"
Click to expand...
Click to collapse
okay, let's stop using toolkits for a while and do it the old fashioned way, and start at the basics.
so first get this http://www.androidfilehost.com/?fid=23329332407585867
and extract the files into a simple folder, maybe something like C:\ADB
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).

nkk71 said:
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).
Click to expand...
Click to collapse
I get this:
(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: HT34xxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4183mV
(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

Torcidas1950 said:
I get this:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?

nkk71 said:
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?
Click to expand...
Click to collapse
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone

Torcidas1950 said:
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone
Click to expand...
Click to collapse
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later

nkk71 said:
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later
Click to expand...
Click to collapse
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help

Torcidas1950 said:
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help
Click to expand...
Click to collapse
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck

nkk71 said:
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck
Click to expand...
Click to collapse
How can I push the custom ROM zip file to the recovery so it can install it?

Torcidas1950 said:
How can I push the custom ROM zip file to the recovery so it can install it?
Click to expand...
Click to collapse
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.

nkk71 said:
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
when I type "adb devices" my HTC One doesn't show up

Torcidas1950 said:
when I type "adb devices" my HTC One doesn't show up
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2

nkk71 said:
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2
Click to expand...
Click to collapse
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.

Torcidas1950 said:
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.
Click to expand...
Click to collapse
sounds like a bad download, please check the MD5 on the ARHD.zip file

nkk71 said:
sounds like a bad download, please check the MD5 on the ARHD.zip file
Click to expand...
Click to collapse
Maybe I will try tomorrow, now I'm going to sleep

Related

[Q] Need help, possible brick!?

Hello,
I Flashed the Android Revolution ROM (International version) on my HTC One, had no problems whatsoever
(i used TWRP)
However, somehow i deleted my OS..
Now, i pushed the rom to my HTC One, and i can install the rom via TWRP.
However, i'm stuck at the HTC One boot logo.
Can anyone help
Im using the HTC One international version.
Btw, i erased the cache and flashed the boot.img via cmd, still not getting anything.
Nickkrommenie said:
Hello,
I Flashed the Android Revolution ROM (International version) on my HTC One, had no problems whatsoever
(i used TWRP)
However, somehow i deleted my OS..
Now, i pushed the rom to my HTC One, and i can install the rom via TWRP.
However, i'm stuck at the HTC One boot logo.
Can anyone help
Im using the HTC One international version.
Btw, i erased the cache and flashed the boot.img via cmd, still not getting anything.
Click to expand...
Click to collapse
Did you check the download is not corrupt? Check the MD5 sum, sounds like a bad download.
No need to flash boot.img as this comes as part of the ROM, but you can (within recovery) erase cache and Dalvik.
Still sound like a bad download IMHO.
nkk71 said:
Did you check the download is not corrupt? Check the MD5 sum, sounds like a bad download.
No need to flash boot.img as this comes as part of the ROM, but you can (within recovery) erase cache and Dalvik.
Still sound like a bad download IMHO.
Click to expand...
Click to collapse
How can i check the MD5 sum?
And if it's a bad download, do i just need to re-download the ROM? / Flash another rom
Nickkrommenie said:
How can i check the MD5 sum?
And if it's a bad download, do i just need to re-download the ROM? / Flash another rom
Click to expand...
Click to collapse
Here's a simple program that will do the job: www.WinMD5.com
The original MD5 is usually mentioned in the OP, or the download section. once you compare that to the one you downloaded, HAPPY FLASHING.
Remember to hit the Thanks button if I helped
nkk71 said:
Here's a simple program that will do the job: www.WinMD5.com
The original MD5 is usually mentioned in the OP, or the download section. once you compare that to the one you downloaded, HAPPY FLASHING.
Remember to hit the Thanks button if I helped
Click to expand...
Click to collapse
Nice, unplugged my HTC and plugged it in 15 minutes later, and ADB doesnt recognise my phone..
I typed adb devices and all i get is: list of devices attached.
Nothing more
Never mind, PC does recognise phone now.
However, i tried another ROM. pushed it onto my phone and flashed it.
However, now i´m stuck at the Insertcoin bootlogo =/
Im totally stuck here.
Nickkrommenie said:
Never mind, PC does recognise phone now.
However, i tried another ROM. pushed it onto my phone and flashed it.
However, now i´m stuck at the Insertcoin bootlogo =/
Im totally stuck here.
Click to expand...
Click to collapse
Are you checking the MD5 sums? Also can you post a "fastboot getvar all" (remove IMEI and s/n).
nkk71 said:
Are you checking the MD5 sums? Also can you post a "fastboot getvar all" (remove IMEI and s/n).
Click to expand...
Click to collapse
I will post a fastboot getvar all when i get home.
could this maybe be a problem with the memory of the HTC One? The rom just doesn't boot.(gets stuck at homescreen, and tried different roms). even tried the boot.img method but that didn't work either..
EDIT: This is what i get :
(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.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXX
(bootloader) imei: XXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3696mV
(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!
So, to sum up things:
I flashed a custom rom, no problems at all.
When i tried to wipe the data of my phone, i accidently wiped my OS.
However, my HTC gets recognised by my W7 pc, and i have no problem pushing Custom ROMS to my HTC (bootloader and recovery are accessible).
However, when i flash a custom rom, the phone gets stuck at the HTC boot-logo
I tried the fastboot erase-cache, then flash the boot.img and installed the ROM etc,
I tried that in every order possible.
P.s i checked the MD5 sums
Nickkrommenie said:
So, to sum up things:
I flashed a custom rom, no problems at all.
When i tried to wipe the data of my phone, i accidently wiped my OS.
However, my HTC gets recognised by my W7 pc, and i have no problem pushing Custom ROMS to my HTC (bootloader and recovery are accessible).
However, when i flash a custom rom, the phone gets stuck at the HTC boot-logo
I tried the fastboot erase-cache, then flash the boot.img and installed the ROM etc,
I tried that in every order possible.
P.s i checked the MD5 sums
Click to expand...
Click to collapse
Strange indeed! So there are only two things I can think of:
1- It's a hardware defect; I've read of 1 incident (again 1) where they guy actually to the phone back to the shop and they confirmed it was a defective memory board. (for now let's assume this is NOT your case)
2- you said "i accidently wiped my OS", which I assume you did by formatting something (probably /system) in TWRP, which could have messed or corrupted your partitions. have you tried different recoveries?
Here's what I'm thinking: flash a different recovery, format pretty much everything, adb push the ROM again, and hope it works.
So if you're up to it:
1- Download the following CWM recovery (that way I can follow you as it's the same one on my phone at the moment):
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
2- flash it in bootloader:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY and confirm you're on attached screen, and we'll proceed from there...
nkk71 said:
Strange indeed! So there are only two things I can think of:
1- It's a hardware defect; I've read of 1 incident (again 1) where they guy actually to the phone back to the shop and they confirmed it was a defective memory board. (for now let's assume this is NOT your case)
2- you said "i accidently wiped my OS", which I assume you did by formatting something (probably /system) in TWRP, which could have messed or corrupted your partitions. have you tried different recoveries?
Here's what I'm thinking: flash a different recovery, format pretty much everything, adb push the ROM again, and hope it works.
So if you're up to it:
1- Download the following CWM recovery (that way I can follow you as it's the same one on my phone at the moment):
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
2- flash it in bootloader:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY and confirm you're on attached screen, and we'll proceed from there...
Click to expand...
Click to collapse
Okaj, i am at the exact same screen at this moment
Nickkrommenie said:
Okaj, i am at the exact same screen at this moment
Click to expand...
Click to collapse
Okay, now go to "mounts and storage"
start formatting:
- format /system
- format /data
- format /cache
- format /sdcard
- format /data and /data/media (/sdcard)
***go back***
adb push <name of rom>.zip /data/media/
- install zip
and flash it
nkk71 said:
Okay, now go to "mounts and storage"
start formatting:
- format /system
- format /data
- format /cache
- format /sdcard
- format /data and /data/media (/sdcard)
***go back***
adb push <name of rom>.zip /data/media/
- install zip
and flash it
Click to expand...
Click to collapse
Did everything, however when i wanted to push the rom to my phone, adb doesnt recognise my phone...
EDIT: I figured it out, however when i try to push the ROM to the phone, CMD says : protocol failure..
Nickkrommenie said:
Did everything, however when i wanted to push the rom to my phone, adb doesnt recognise my phone...
Click to expand...
Click to collapse
reboot phone: go to "advanced" and select "reboot recovery"
and also reboot PC
Don't forget to unplug phone and later replug after reboot. then confirm adb is working again.
EDIT: and while you're there, wipe dalvik
nkk71 said:
reboot phone: go to "advanced" and select "reboot recovery"
and also reboot PC
Don't forget to unplug phone and later replug after reboot. then confirm adb is working again.
EDIT: and while you're there, wipe dalvik
Click to expand...
Click to collapse
Did that, when i plug my phone into the computer you can here the "connected tune" from windows.
However, 5 seconds after i wanted to push the rom, you can hear the "disconnected tune" and it just says protocol failure.
Nickkrommenie said:
Did that, when i plug my phone into the computer you can here the "connected tune" from windows.
However, 5 seconds after i wanted to push the rom, you can hear the "disconnected tune" and it just says protocol failure.
Click to expand...
Click to collapse
silly question, but is the phone charged enough? also try a different USB port. I know this is a bit of trial and error to get adb to work sometimes. I remember you having this problem before no?
Did you update drivers and adb?
nkk71 said:
silly question, but is the phone charged enough? also try a different USB port. I know this is a bit of trial and error to get adb to work sometimes. I remember you having this problem before no?
Did you update drivers and adb?
Click to expand...
Click to collapse
Yes the phone was charged enough, "sideloaded" the ROM and installed it. Now i just have to wait and hope for the ROM to boot.
EDIT: ROM Doesn't boot, just reboots in recovery after a while
Nickkrommenie said:
Yes the phone was charged enough, "sideloaded" the ROM and installed it. Now i just have to wait and hope for the ROM to boot.
Click to expand...
Click to collapse
keep me posted, I'm F5'ing this thread like a hawk :cyclops:
nkk71 said:
keep me posted, I'm F5'ing this thread like a hawk :cyclops:
Click to expand...
Click to collapse
First of all, even when i wont be able to fix this phone. I would like to thank you for your support and time!
Nickkrommenie said:
First of all, even when i wont be able to fix this phone. I would like to thank you for your support and time!
Click to expand...
Click to collapse
"even when i wont be able to fix this phone" let's keep that an IF, I'm not ready to give up just yet fingers still crossed :fingers-crossed:

My HTC One Dead Dead dead

Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app
alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023
Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot
nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?
alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!
Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive:

Weaksauce vs rumrunner [SOLVED]

I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n), and what ROM are you running?
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3884mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Pretty sure rumrunner won't work on 1.57. Either Firewater or sunshine
chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
@nateboi81 is right, your only options are:
a) sunshine (costs $25) on stock rom
or
b) firewater (free) on rooted ROM (and possibly bulletproof kernel)
if firewater gives you "whelp this sucks, etc" error then only sunshine will work
chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
I s-off my rooted htc one hboot 1.57 using firewater. Must be on custom rom I think. Download link in case you need it, other links didn't work for me;
Firewater
- adb reboot <-- Important
- adb wait-for-device push firewater /data/local/tmp <--- When the phone restarts enter this
- adb shell
- su
- chmod 755 /data/local/tmp/firewater
- /data/local/tmp/firewater
Wait for prompt and type Yes, must be capital 'Y'
Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident. I will just turn off the system updates on my phone and delete the update so it doesn't keep bugging me.
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
chris9486 said:
Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident.
Click to expand...
Click to collapse
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
chris9486 said:
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
Click to expand...
Click to collapse
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
I thought about doing that but I am reluctant to fiddle about too much now. I'm being super cautious with all things technology wise. I lost a hard drive last week and then the backup of it two days later when I tried to put it on a new drive. Through no fault of my own and it's costing £540 for it to be recovered by a professional company. I don't want to f-up anything else because I can't afford another phone. My contract is up in Jan so I'll just stay on this till I can upgrade. My phone hasn't prompted me to upgrade ota again yet. So it's not a necessity to return to stock.
chris9486 said:
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
Click to expand...
Click to collapse
I wasn't offended at all, just wondering what should be written differently.
chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
Click to expand...
Click to collapse
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).
nkk71 said:
I wasn't offended at all, just wondering what should be written differently.
Click to expand...
Click to collapse
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
nkk71 said:
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).
Click to expand...
Click to collapse
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
I am downloading ARHD and I am ready to flash it, I will try to s-off with firewater. If it doesn't work, I will just keep ARHD on and be fine till I can upgrade to a new phone. Not sure which one yet. Torn between Z2 and M8.
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
Click to expand...
Click to collapse
Can I ask, is this the correct ruu for my phone mid and cid?
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:
chris9486 said:
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Click to expand...
Click to collapse
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
chris9486 said:
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
Click to expand...
Click to collapse
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
chris9486 said:
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
Click to expand...
Click to collapse
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
chris9486 said:
Can I ask, is this the correct ruu for my phone mid and cid?
Click to expand...
Click to collapse
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
chris9486 said:
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:
Click to expand...
Click to collapse
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
then enter RECOVERY
nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
Click to expand...
Click to collapse
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.
chris9486 said:
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.
Click to expand...
Click to collapse
I already answered above
nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
then enter RECOVERY
Click to expand...
Click to collapse
I've never checked md5 in my life of using computers and the internet. I am an idiot I know.
ADB was working on fastboot USB in the bootloader yesterday. I didn't enter recovery once yesterday.
When I try to go to recovery (cwm) it just flashes for a second then reboots.
I will try the force reboot but not confident.
Do I try the force reboot when the phone is off, in the boot loop or in the bootloader. Because all three just send me back to the bootloader after about 10 seconds and none cause the phone to reboot.
nkk71 said:
I already answered above
Click to expand...
Click to collapse
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.
chris9486 said:
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.
Click to expand...
Click to collapse
please change your recovery to twrp 2.6.3.3 as mentioned below:
A) Having Problems? Rule #1: check MD5 on all your downloads; one single corrupt download can keep you trying for hours on end for nothing!
https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt
on Mac, Linux, and Android terminals it's already built in:
Mac: in terminal, just type md5 <name of file>
----> MD5 (<name of file>) = 12345678901234567890123456789012
Linux: in terminal, just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Android: in "adb shell", just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ , http://implbits.com/hashtab.aspx , http://www.pc-tools.net/win32/md5sums/ or any other one of your choosing.
C) Problems installing a ROM (in particular 4.4+ versions, and getting permission/set_metadata errors)
for M7_U/UL models, get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
Note: at the time of this writing these are the most reliable versions, even the 2.7.x.x series seem to still have problems
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY and install the ROM​

[Q] How do I get my phone operable again?

Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.
dirkgently68 said:
Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.
Click to expand...
Click to collapse
post the output of "fastboot getvar all' (exclude imei and serialno)
what recovery are you using? What version number?
dirkgently68 said:
Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.
Click to expand...
Click to collapse
you'll most likely have to format data and push the file to the phone again. This will wipe the entire phone same as a RUU
alray said:
post the output of "fastboot getvar all' (exclude imei and serialno)
what recovery are you using? What version number?
Click to expand...
Click to collapse
Fastboot getvar all returns this :-
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.12.161.8
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: VODAP001
battery-status: good
battery-voltage: 4315mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Recovery is TWRP v2.8.0.2
Thanks for your response!
dirkgently68 said:
Fastboot getvar all returns this :-
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.12.161.8
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: VODAP001
battery-status: good
battery-voltage: 4315mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Recovery is TWRP v2.8.0.2
Thanks for your response!
Click to expand...
Click to collapse
Afaik ARHD must be installed using twrp 2.6.3.3 (higher versions of twrp are not compatible, or at least, they are not all compatible)
flash twrp 2.6.3.3
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then in twrp selsect "install", browse your phone storage to find your ARHD zip file, select it and then swipe to flash.
If this fail again, format data like cisa said above, but you'll have to push the rom to your phone storage again.
alray said:
Afaik ARHD must be installed using twrp 2.6.3.3 (higher versions of twrp are not compatible, or at least, they are not all compatible)
flash twrp 2.6.3.3
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then in twrp selsect "install", browse your phone storage to find your ARHD zip file, select it and then swipe to flash.
If this fail again, format data like cisa said above, but you'll have to push the rom to your phone storage again.
Click to expand...
Click to collapse
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.
dirkgently68 said:
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.
Click to expand...
Click to collapse
What was the error code in twrp?
What is your adb version?
Do you have latest HTC drivers installed?
Are you using a usb 2.0 ports? Maybe try another usb port/cable.
Have you checked MD5 value of your rom/recovery files?
dirkgently68 said:
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.
Click to expand...
Click to collapse
After you done wipe/format data. Did you reboot the phone to recovery?
You have to do this to write the new file system.
If it's still failing after reboot. Disable HTC sync or better still uninstall it if you don't use it.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Thanks to all of you who responded, it turns out I've got 6 different versions of ADB on my PC due to various toolkits and things I've downloaded for my different devices, I also only have USB 3 ports on this machine but when I changed ADB version it worked, so again thanks to you all :good:

[Q] ADB can't find phone

So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44) as that is needed to update the firmware however it cannot connect to my phone either (same adb problem)
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables. I've tried uninstalling and reinstalled different HTC drivers, I also tried installing the google usb drivers.
I need helps
Cofffey said:
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in
Click to expand...
Click to collapse
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
To achieve s-off on hboot 1.44 use Revone
as that is needed to update the firmware
Click to expand...
Click to collapse
S-OFF is only needed if you flash a custom firmware.
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables.
Click to expand...
Click to collapse
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps[/QUOTE]
alray said:
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
To achieve s-off on hboot 1.44 use Revone
S-OFF is only needed if you flash a custom firmware.
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps
Click to expand...
Click to collapse
[/QUOTE]
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(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.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Cofffey said:
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(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.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Click to expand...
Click to collapse
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
alray said:
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
Click to expand...
Click to collapse
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Cofffey said:
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Click to expand...
Click to collapse
you are s-off now?
alray said:
you are s-off now?
Click to expand...
Click to collapse
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Cofffey said:
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Click to expand...
Click to collapse
Change your CID to GOOGL001:
boot in bootlaoder / fastboot usb mode
using fastboot enter these commands:
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
Then confirm your cid is now GOOGL001:
Code:
fastboot oem readcid
output must be "GOOGL001"
reboot in ruu mode:
Code:
fastboot oem rebootRUU
flash this firmware, not the one you have linked above:
Code:
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot reboot-bootloader
then reflash twrp:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery, push the GPE rom to your phone and flash it. Reboot and your phone should boot in the 5.1 rom (first boot can take up to 10-15 mins, will be stuck at htc splash screen)
Dont forget to backup your important files before, the firmware flash will wipe your phone.
alray said:
Wait, I'll make some modification to the firmware so it can be flashed on your phone and I'll send it to you in a few minutes.
Click to expand...
Click to collapse
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Cofffey said:
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Click to expand...
Click to collapse
see edited post above. (#8)
alray said:
see edited post above. (#8)
Click to expand...
Click to collapse
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Cofffey said:
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Click to expand...
Click to collapse
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
alray said:
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
Click to expand...
Click to collapse
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Cofffey said:
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Click to expand...
Click to collapse
If you need some of elementalX features then yes flash it, you can always revert back to the previous kernel that comes with the rom by extracting it from the rom.zip and flashing it using fastboot:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
ElementalX kernel must be flashed in recovery.

Categories

Resources