Related
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:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
So I got cyanogenmod for my phone, never really had an android so thought id have a play around and I needed it for mirroring on the screen in my car, but I HATE it! So i followed some online tutorials to get it back to stock, now my phone is stuck in the bootloader saying its tamerped and relocked, I have downloaded some apparent .ruu files, however, when following online tutorials there is no .exe in the file? Just a Meta-Inf folder, a system folder and a boot.img ... I just want my old phone back! Sorry if this is nooby, didn't no where else to ask. Thanks for your help!!
uyfgfar said:
So I got cyanogenmod for my phone, never really had an android so thought id have a play around and I needed it for mirroring on the screen in my car, but I HATE it! So i followed some online tutorials to get it back to stock, now my phone is stuck in the bootloader saying its tamerped and relocked, I have downloaded some apparent .ruu files, however, when following online tutorials there is no .exe in the file? Just a Meta-Inf folder, a system folder and a boot.img ... I just want my old phone back! Sorry if this is nooby, didn't no where else to ask. Thanks for your help!!
Click to expand...
Click to collapse
Relax. Now there are a few ROMs which are exactly the same as the stock HTC rom, but with more features. The ROM is based on HTC Sense 5.5 and KitKat, the same which you would see on ur One.
Unrooting and converting ur phone completely to complete stock is an unnecessary headache, which u can avoid by just flashing a Sense ROM. If, for some reason, your purpose is to unroot the phone, then, well, I can help u.
Reply in this thread whether ur fine with a Sense ROM or u want 2 go complete stock
raghav kapur said:
Relax. Now there are a few ROMs which are exactly the same as the stock HTC rom, but with more features. The ROM is based on HTC Sense 5.5 and KitKat, the same which you would see on ur One.
Unrooting and converting ur phone completely to complete stock is an unnecessary headache, which u can avoid by just flashing a Sense ROM. If, for some reason, your purpose is to unroot the phone, then, well, I can help u.
Reply in this thread whether ur fine with a Sense ROM or u want 2 go complete stock
Click to expand...
Click to collapse
Hi mate, thanks for the quick reply. I want to go back to complete stock if that's okay
uyfgfar said:
Hi mate, thanks for the quick reply. I want to go back to complete stock if that's okay
Click to expand...
Click to collapse
Ok. Now I will need a little more info abt ur device. Put ur phone in fastboot mode in the bootloader. Open the fastboot/adb folder on ur PC. Open command prompt. Type "fastboot getvar all" without the quotation marks. Post the output on this thread and delete IMEI number and serial number.
uyfgfar said:
So I got cyanogenmod for my phone, never really had an android so thought id have a play around and I needed it for mirroring on the screen in my car, but I HATE it! So i followed some online tutorials to get it back to stock, now my phone is stuck in the bootloader saying its tamerped and relocked, I have downloaded some apparent .ruu files, however, when following online tutorials there is no .exe in the file? Just a Meta-Inf folder, a system folder and a boot.img ... I just want my old phone back! Sorry if this is nooby, didn't no where else to ask. Thanks for your help!!
Click to expand...
Click to collapse
You need to be a bit careful, before you end up doing something really wrong:
"Just a Meta-Inf folder, a system folder and a boot.img" -> that's a custom/stock ROM.zip flashable through custom recovery (TWRP or CWM), it is NOT a ruu.
start by posting a "fastboot getvar all" (excluding IMEI and s/n), and do you need to go back to full stock, or is a custom ROM OK too?
nkk71 said:
You need to be a bit careful, before you end up doing something really wrong:
"Just a Meta-Inf folder, a system folder and a boot.img" -> that's a custom/stock ROM.zip flashable through custom recovery (TWRP or CWM), it is NOT a ruu.
start by posting a "fastboot getvar all" (excluding IMEI and s/n), and do you need to go back to full stock, or is a custom ROM OK too?
Click to expand...
Click to collapse
This is directed at both of you, if it is much easier to do I could get a custom ROM? but I would want it to run the same if not better than the original, if you can suggest a route to go? I will get the command prompt return for you both now
uyfgfar said:
This is directed at both of you, if it is much easier to do I could get a custom ROM? but I would want it to run the same if not better than the original, if you can suggest a route to go? I will get the command prompt return for you both now
Click to expand...
Click to collapse
Flashing a Sense based Custom ROM is MUCH better and easier than RUUing the phone. Its the EXACT stock experience, but with much more tweaks, which are optional of course.
raghav kapur said:
Flashing a Sense based Custom ROM is MUCH better and easier than RUUing the phone. Its the EXACT stock experience, but with much more tweaks, which are optional of course.
Click to expand...
Click to collapse
YES! Okay let's do that then! But I am currently stuck on the cyanogemod boot screen! Why is everything going wrong
uyfgfar said:
This is directed at both of you, if it is much easier to do I could get a custom ROM? but I would want it to run the same if not better than the original, if you can suggest a route to go? I will get the command prompt return for you both now
Click to expand...
Click to collapse
As @raghav kapur said, custom ROMs can be very tweaked or very close to stock, here an index thread of ROMs (and other stuff):
http://forum.xda-developers.com/showthread.php?t=2438026
I'm personally using ARHD 52.0 which is stock but improved, the other ROMs are all very good too, you just need to see what options you want. There is no "best" ROM, so don't even ask (or your thread will be closed). It's all personal choice!!
nkk71 said:
As @raghav kapur said, custom ROMs can be very tweaked or very close to stock, here an index thread of ROMs (and other stuff):
http://forum.xda-developers.com/showthread.php?t=2438026
I'm personally using ARHD 52.0 which is stock but improved, the other ROMs are all very good too, you just need to see what options you want. There is no "best" ROM, so don't even ask (or your thread will be closed). It's all personal choice!!
Click to expand...
Click to collapse
Pretty sure I have that ROM downloaded already. Right, now I have to find out how to get off the cyanogen boot logo? any tips?
uyfgfar said:
Pretty sure I have that ROM downloaded already. Right, now I have to find out how to get off the cyanogen boot logo? any tips?
Click to expand...
Click to collapse
Press and hold POWER + VOLDOWN (under a bright light, i am not kidding!!), after 4 or 5 seconds the buttons will start blinking, then after 20 to 30 seconds, the phone should reboot.... let go of POWER, but keep holding VOLDOWN, that will get you to bootloader, and we can proceed from there.
(you may need to try 2 or 3 times)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BSW901469
(bootloader) imei: 359405054858699
(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: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
There you go guys that's my getvar
uyfgfar said:
YES! Okay let's do that then! But I am currently stuck on the cyanogemod boot screen! Why is everything going wrong
Click to expand...
Click to collapse
1) Ya, ok. First u'll have to unlock the bootloader again.
2) Go to the Android Development page, which will give u a list of ROMs. Download any one which you like
3) You will most likely have a proper booting Cyanogenmod after the bootloader unlock. If not, you will need to use ADB sideload from CWM/TWRP. Tutorial is mentioned here:
http://forum.xda-developers.com/showthread.php?t=2559200
4) If you have a proper booting CM(Cyanogenmod), then transfer the Sense ROM which you downloaded to ur Internal Storage. If its still not booting, adb sideload the ROM zip to the internal storage from the link ive sent
5) Wipe the data, cache, dalvik cache and system in CWM/TWRP. Flash the ROM zip which u downloaded. Choose the wipe option in the Aroma installer. Let it install
6) Profit
raghav kapur said:
1) Ya, ok. First u'll have to unlock the bootloader again.
2) Go to the Android Development page, which will give u a list of ROMs. Download any one which you like
3) You will most likely have a proper booting Cyanogenmod after the bootloader unlock. If not, you will need to use ADB sideload from CWM/TWRP. Tutorial is mentioned here:
http://forum.xda-developers.com/showthread.php?t=2559200
4) If you have a proper booting CM(Cyanogenmod), then transfer the Sense ROM which you downloaded to ur Internal Storage. If its still not booting, adb sideload the ROM zip to the internal storage from the link ive sent
5) Wipe the data, cache, dalvik cache and system in CWM/TWRP. Flash the ROM zip which u downloaded. Choose the wipe option in the Aroma installer. Let it install
6) Profit
Click to expand...
Click to collapse
I will unlock the bootloader and let you know if the cyanogen mod boots up if not, can you please explain in dummy-talk step 4 and 5?
raghav kapur said:
1) Ya, ok. First u'll have to unlock the bootloader again.
2) Go to the Android Development page, which will give u a list of ROMs. Download any one which you like
3) You will most likely have a proper booting Cyanogenmod after the bootloader unlock. If not, you will need to use ADB sideload from CWM/TWRP. Tutorial is mentioned here:
http://forum.xda-developers.com/showthread.php?t=2559200
4) If you have a proper booting CM(Cyanogenmod), then transfer the Sense ROM which you downloaded to ur Internal Storage. If its still not booting, adb sideload the ROM zip to the internal storage from the link ive sent
5) Wipe the data, cache, dalvik cache and system in CWM/TWRP. Flash the ROM zip which u downloaded. Choose the wipe option in the Aroma installer. Let it install
6) Profit
Click to expand...
Click to collapse
NOTHING. It's not booting up at all. I don't want to lose my phone but reading these tutorials is making me flustered because I dont knwo what the hell i'm doing.
uyfgfar said:
NOTHING. It's not booting up at all. I don't want to lose my phone but reading these tutorials is making me flustered because I dont knwo what the hell i'm doing.
Click to expand...
Click to collapse
ok. I assume you have TWRP 2.6.3.3
Now, first, on your PC, download the Android SDK and run the program. Start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
Tell me when ur done
raghav kapur said:
ok. I assume you have TWRP 2.6.3.3
Now, first, on your PC, download the Android SDK and run the program. Start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
Tell me when ur done
Click to expand...
Click to collapse
I dont know what TWRP 2.6.3.3 is maet
And i've installed both packages on the SDK now
uyfgfar said:
I dont know what TWRP 2.6.3.3 is maet
And i've installed both packages on the SDK now
Click to expand...
Click to collapse
Ok. U need a custom recovery.
http://techerrata.com/browse/twrp2/m7
Click on: openrecovery-twrp-2.7.0.0-m7.img
Download, save it to the adb/fastboot folder on ur laptop
Tell me when done
raghav kapur said:
Ok. U need a custom recovery.
http://techerrata.com/browse/twrp2/m7
Click on: openrecovery-twrp-2.7.0.0-m7.img
Download, save it to the adb/fastboot folder on ur laptop
Tell me when done
Click to expand...
Click to collapse
okay, i've downloaded that and saved it in the fastboot folder
uyfgfar said:
okay, i've downloaded that and saved it in the fastboot folder
Click to expand...
Click to collapse
now open command prompt in the fastboot folder and type (without quotation):
"fastboot flash recovery xx"
"xx" indicates the img file. So drag the img file from the fastboot folder to command prompt. That will show its name and directory. Hit enter
Howdy fellas. So im pretty hooped here. First of all let it be said i am a total noob and this has solidified my standing as a noob. Bought a used M7 (Rogers), came rooted BL unlocked, s-on, running cm 11. I wanted to install ARHD 83.1 Thought hey why not start from scratch, unroot flash stock RUU etc. So i made a backup of the Cm11 rom just incase in twrp 2.8.3.0. Relocked BL, then google Rogers M7 RUU , downloaded a 4.4, sense 5.5 one and ran it. Got an error message about 3 min in from windows explorer saying htc.fastboot.exe has stopped, everything closed and my phone just rebooted back to fastboot. SO i thought i better restore my backup. Went to unlock bootloader, hit yes and my phone was booting into cm 11... stuck at boot logo for an hour till it got quite warm. So i hard reset it, went into recovery to restore backup and voila, I have 0 MB internal storage with no files at all. Can someone please help? Ill even donate if you can help me get my phone back
Many thanks
butthurtlocker said:
Howdy fellas. So im pretty hooped here. First of all let it be said i am a total noob and this has solidified my standing as a noob. Bought a used M7 (Rogers), came rooted BL unlocked, s-on, running cm 11. I wanted to install ARHD 83.1 Thought hey why not start from scratch, unroot flash stock RUU etc. So i made a backup of the Cm11 rom just incase in twrp 2.8.3.0. Relocked BL, then google Rogers M7 RUU , downloaded a 4.4, sense 5.5 one and ran it. Got an error message about 3 min in from windows explorer saying htc.fastboot.exe has stopped, everything closed and my phone just rebooted back to fastboot. SO i thought i better restore my backup. Went to unlock bootloader, hit yes and my phone was booting into cm 11... stuck at boot logo for an hour till it got quite warm. So i hard reset it, went into recovery to restore backup and voila, I have 0 MB internal storage with no files at all. Can someone please help? Ill even donate if you can help me get my phone back
Many thanks
Click to expand...
Click to collapse
looks like your data partition is corrupted. This should be easy to fix but first post the output of "fastboot getvar all" except your IMEI and SERIALNO.
BTW do you prefer to go back to stock rom or CM?
alray said:
looks like your data partition is corrupted. This should be easy to fix but first post the output of "fastboot getvar all" except your IMEI and SERIALNO.
BTW do you prefer to go back to stock rom or CM?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4259mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I much prefer stock! Thanks so much for the reply too i hope i can get this going somehow
butthurtlocker said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) security: on
I much prefer stock! Thanks so much for the reply too i hope i can get this going somehow
Click to expand...
Click to collapse
Sorry for late reply, we have some serious power outages here in Quebec (damn freezing rain!)
Download TWRP 2.6.3.3 and save it to your adb/fastboot folder on your computer
With your phone connected to your computer and booted in bootlloader/fastboot usb mode, 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-bootloader
Boot in recovery mode (TWRP), select Wipe, Advanced Wipe, then select everything and "Swipe to wipe". When completed, go back in the main menu, select Wipe then "Format Data". When format data is completed reboot the recovery.
When rebooted in recovery, select "backup" then select "boot" only and swipe to backup, go back in the main menu
Download this nandroid backup and save it to your desktop.
Extract the backup zip files, put all the files in a folder and name that folder "MYBACKUP"
move that folder in the same folder where you have adb and fastboot on your computer
with your phone still in twrp main menu, adb push the backup to your phone:
Code:
adb push MYBACKUP /sdcard/TWRP/BACKUPS/[COLOR="Red"]Your_Serial_Number[/COLOR]/MYBACKUP
(replace text in red by your phone's serial number. You can find your serial number in your "fastboot getvar all")
This will take a while and your command prompt will be unresponsive during the transfer. When the command prompt is responsive again, then the transfer is complete.
In twrp select "restore", select "MYBACKUP", select all partitions then "swipe to restore"
reboot phone and confirm everything is working fine
alray said:
Sorry for late reply, we have some serious power outages here in Quebec (damn freezing rain!)
Download TWRP 2.6.3.3 and save it to your adb/fastboot folder on your computer
With your phone connected to your computer and booted in bootlloader/fastboot usb mode, 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-bootloader
Boot in recovery mode (TWRP), select Wipe, Advanced Wipe, then select everything and "Swipe to wipe". When completed, go back in the main menu, select Wipe then "Format Data". When format data is completed reboot the recovery.
When rebooted in recovery, select "backup" then select "boot" only and swipe to backup, go back in the main menu
Download this nandroid backup and save it to your desktop.
Extract the backup zip files, put all the files in a folder and name that folder "MYBACKUP"
move that folder in the same folder where you have adb and fastboot on your computer
with your phone still in twrp main menu, adb push the backup to your phone:
Code:
adb push MYBACKUP /sdcard/TWRP/BACKUPS/[COLOR="Red"]Your_Serial_Number[/COLOR]/MYBACKUP
(replace text in red by your phone's serial number. You can find your serial number in your "fastboot getvar all")
This will take a while and your command prompt will be unresponsive during the transfer. When the command prompt is responsive again, then the transfer is complete.
In twrp select "restore", select "MYBACKUP", select all partitions then "swipe to restore"
reboot phone and confirm everything is working fine
Click to expand...
Click to collapse
Wow man, you did it. It works! Thanks so much. You got a paypal i can donate to? Im happy to throw a few bucks your way. One last question, Im wondering if the radio/firmware that nandroid is running is new enough that i can install a rom like ARHD 84 or insert coin etc? Or Do i need to update it somehow? And if so how would i go about doing that? your step by step was amazing by the way,
butthurtlocker said:
Wow man, you did it. It works! Thanks so much.
Click to expand...
Click to collapse
You're welcome!
You got a paypal i can donate to? Im happy to throw a few bucks your way.
Click to expand...
Click to collapse
If you feel that I deserve it, you can use the "donate to me" button below my avatar
One last question, Im wondering if the radio/firmware that nandroid is running is new enough that i can install a rom like ARHD 84 or insert coin etc? Or Do i need to update it somehow?
Click to expand...
Click to collapse
I think it should be good with those roms but it wouldn't hurt to update it. 3.22.631.1 is a pretty old firmware.
And if so how would i go about doing that?
Click to expand...
Click to collapse
Well the easiest way would be to flash the stock recovery back and take all ota updates to latest version. Otherwise you could use the 4.19.631.9 and then take the remaining ota updates.
your step by step was amazing by the way
Click to expand...
Click to collapse
Thanks :highfive:
alray said:
You're welcome!
If you feel that I deserve it, you can use the "donate to me" button below my avatar
I think it should be good with those roms but it wouldn't hurt to update it. 3.22.631.1 is a pretty old firmware.
Well the easiest way would be to flash the stock recovery back and take all ota updates to latest version. Otherwise you could use the 4.19.631.9 and then take the remaining ota updates.
Thanks :highfive:
Click to expand...
Click to collapse
y
In either case, could you step ny step me into how to do either? As in how to take stock recovery then otas as well as the new actual firmware. Would i need s-off for either? Sorry to ask so much but im just a bit overwhelmed by all this being new to it. And yeah im totes gonma slang you some coin when im home from work
butthurtlocker said:
y
In either case, could you step ny step me into how to do either? As in how to take stock recovery then otas as well as the new actual firmware. Would i need s-off for either? Sorry to ask so much but im just a bit overwhelmed by all this being new to it. And yeah im totes gonma slang you some coin when im home from work
Click to expand...
Click to collapse
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
alray said:
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
Click to expand...
Click to collapse
Thanks man, trying now. Just donated
NOTE- i could only update to 4.4.2, Sense 6. My radio now reads 4T.27.3218.14, Hboot 1.57. This doesnt match the newer version number! IS there any thing else i could do to further update my firmware?
alray said:
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
Click to expand...
Click to collapse
Hope you got my donation! Thanks again for the help. I do have one additional questions however. So i did what you said flashed that stock recovery, then update as far as my OTAS would go. then re flashed TWRP so i could flash ARHD. But im wanting to re flash stock recovery now! So i see my Hboot has changed to 1.57. Could you link me to the new proper stock recovery for my updated device?
butthurtlocker said:
Hope you got my donation! Thanks again for the help. I do have one additional questions however. So i did what you said flashed that stock recovery, then update as far as my OTAS would go. then re flashed TWRP so i could flash ARHD. But im wanting to re flash stock recovery now! So i see my Hboot has changed to 1.57. Could you link me to the new proper stock recovery for my updated device?
Click to expand...
Click to collapse
Don't reflash the stock recovery if you are using a custom rom like arhd, keep twrp recovery.
Stock recovery is not useful at all when using custom roms, only needed for stock roms.
And I need to know your main version to direct you to the correct stock recovery version
Code:
fastboot getvar version-main
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Well... There is one thing you could do.
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Click to expand...
Click to collapse
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
2.Flash a custom recovery.
You flash a custom recovery like this using fastboot.
Code:
fastboot flash recovery <recoveryName>.img
3.Use TWRP to copy the ROM zip file to your internal storage.
4.Do a nandroid backup.
5.Do an advanced wipe (Wipe data, system, cache and dalvik cache partitions).
6.Do a factory reset (Wipe Data/Factory reset).
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
7.Flash your preferred ROM.
8.Tell me if it worked and enjoy!
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!".
Click to expand...
Click to collapse
This screen is the stock recovery main page.
Volume up and power work, and give 5 fails to mount the sd card.
Click to expand...
Click to collapse
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Click to expand...
Click to collapse
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
Is there anything else I can do with it? or is it just a paperweight now?
Click to expand...
Click to collapse
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant
Click to expand...
Click to collapse
Yes rogers are M7_UL too.
so you can just go ahead and root your phone then flash a ROM of your choice.
Click to expand...
Click to collapse
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
-Windows computer (WIndows 8.1 is fine).
Click to expand...
Click to collapse
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
Click to expand...
Click to collapse
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
alray said:
This screen is the stock recovery main page.
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
Yes rogers are M7_UL too.
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
Click to expand...
Click to collapse
The last HTC device that lasted 3 years with me was the One X (my AT&T M7 either got bricked or had battery issue) and I never tried to get it S-OFF'ed since I really did no't see any use for it back in the day plus its screen was having problems anyway. This is new knowledge for me thanks!
and to the OP, if you need more help the quote button is your friend.
Good luck!
The Android Manual said:
The last HTC device that lasted 3 years with me was the One X
Click to expand...
Click to collapse
Wow mine (Tegra version) only lasted 13 months, had the infamous wifi issue (repaired myself) , overheat issue and motherboard finally died. I was very reluctant to buy htc again but finally I'm very satisfied with my M7.
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
squidstings said:
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
Click to expand...
Click to collapse
You can try the Roger's RUU in this post. You will need to follow the instructions in the OP. I believe in your case, since there is no 6.xx version for Roger's you can go directly to the Lollipop version.
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
Click to expand...
Click to collapse
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
squidstings said:
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
Click to expand...
Click to collapse
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
alray said:
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
Click to expand...
Click to collapse
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
squidstings said:
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM? is one custom and the other carrier generated?). I managed to get the identifier token last night, but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
I downloaded the ruu from the link on XDA but the .zip won't extract.
squidstings said:
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM?
Click to expand...
Click to collapse
A RUU stands for Rom Update Utility. Its an official file from HTC that flashes many partitions like the system partition (the rom/OS), the recovery partition, bootloader, radio partition, touch drivers, IR drivers...... well all partitions that are not specific to your phone and that will make it stock again. The only partition that are not flashed when using a RUU are those containing unique info about your phone like the MFG partition containing your IMEI number, Serial number, Date of manufactures etc.
A rom is only the /system partition flashed using a custom recovery. So when you flash a ROM (eiither custom or stock) you only flash the system partition and all other are kept like they was before the flash.
but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
Click to expand...
Click to collapse
You don't need usb debugging when flashing a RUU. USB debuging is only needed to use ADB commands when booted in the OS. A RUU is flashed using FASTBOOT commands when booted in the bootloader.
squidstings said:
I downloaded the ruu from the link on XDA but the .zip won't extract.
Click to expand...
Click to collapse
This is explained in the same post from where you have downloaded the file.... You might want to read the OP of the thread you are downloading files from :good: Not trying to be rude btw but lack of reading can sometime makes the situation worst. so just for you here it is again: The ruu are encrypted so they can't be extracted or opened and don't need to be, only flash it on your phone.
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them
Click to expand...
Click to collapse
and instruction how to flash the ruu are posted just below these warnings, just click on the "show more" button.
---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------
@squidstings
Might be easier to just unlock the bootloader, flash a recovery and then a rom like suggested at post #2
Youv said you already have your identifier token, go ahead and submit it to htcdev.com/bootloader (must create and account first). They will reply with an e-mail containing a file named Unlock_code.bin. Download and save the file in the same folder where you have adb and fastboot installed on your computer.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.[/QUOTE]
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
C:\Android>
I did read everything. got a bit confused by different methods and files suggested (maybe just different wording for the same proceedure?). I've been looking for ROMs and RUUs all day. after I've fixed this phone (hopefully) i want to root my m7.
squidstings said:
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Click to expand...
Click to collapse
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
alray said:
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
Click to expand...
Click to collapse
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
squidstings said:
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
Click to expand...
Click to collapse
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
mb_guy said:
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
Click to expand...
Click to collapse
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
squidstings said:
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
Click to expand...
Click to collapse
Ok, let me try again.
If you want to flash a rom,
1) unlocked bootloader (you have)
2) Flash custom recovery like twrp (I don't see that you have done this) so may be easier to go the ruu route.
3) Use custom recovery to install rom. I like the arhd ones
If you want to flash the RUU
1) relock the bootloader
2) flash the ruu, once this is done and the phone rebooted and running it will be at 7.17.631.7, go to settings about and check for system updates. You should receive an OTA which is 7.17.631.35. Install it.
3) You can leave the phone like this, or re-unlock the bootloader and flash a custom recovery like twrp. This will give you the ability to do nandroid backups, root the phone or install custom roms if you want.
Either method should work, the choice is yours
Hope this is clearer.