[Q] Need help, possible brick!? - One (M7) Q&A, Help & Troubleshooting

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:

Related

[SOLVED] Soft Bricked - Need Help!

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

HTC One boot loop, S-ON

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

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:

0 MB internal storage

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

HTC One M7 Stuck in a Boot Loop

Alright, I recently purchased a phone that was stuck at the screen with the download icon in the arrow circle (http://forum.xda-developers.com/album.php?albumid=11886). When it is like this is can not be put into hboot. I then somehow got the phone into a boot loop. I did wipe the cache and that did not fix the problem. I did a factory reset via hboot, and it sent me back to the screen I mentioned before (http://forum.xda-developers.com/album.php?albumid=11886). I've now gotten the phone back into boot looping so I can access hboot. Recovery does work and you can access all the options. This phone is basically a stock HTC One M7. Has not been rooted, is locked, and it S-ON. Any help would be appreciated.
Thank you!
Flash a RUU
jdgreat4 said:
Flash a RUU
Click to expand...
Click to collapse
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
CloudHD said:
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
Click to expand...
Click to collapse
post the output of "fastboot getvar all", remove your imei and serialno before posting it
alray said:
post the output of "fastboot getvar all", remove your imei and serialno before posting it
Click to expand...
Click to collapse
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
CloudHD said:
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
Click to expand...
Click to collapse
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
alray said:
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
Click to expand...
Click to collapse
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
CloudHD said:
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
Click to expand...
Click to collapse
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
alray said:
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CloudHD said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Danny201281 said:
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Click to expand...
Click to collapse
Followed your instructions. Everything went good. I did a factory reset and the phone actually ended up rebooting. It's now just sitting here, and seems to be stuck at the htc logo. Going to go ahead and follow the steps to unlock my bootloader then report back.
@Danny201281 Boot loader is now unlocked!
CloudHD said:
@Danny201281 Boot loader is now unlocked!
Click to expand...
Click to collapse
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Danny201281 said:
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Click to expand...
Click to collapse
Thank you! My friend wanted to ask about soff and root for his device
CloudHD said:
Thank you! My friend wanted to ask about soff and root for his device
Click to expand...
Click to collapse
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Danny201281 said:
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Click to expand...
Click to collapse
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
CloudHD said:
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
Click to expand...
Click to collapse
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Danny201281 said:
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Click to expand...
Click to collapse
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
CloudHD said:
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
Click to expand...
Click to collapse
Reboot Recovery and then copy over and install the rom :good:
When you format data it is like repartitioning the phone. All the partitions are gone until you reboot. That's the reason they won't mount
Danny201281 said:
Reboot Recovery and then copy over and install the rom :good:
Click to expand...
Click to collapse
Alright, Thank you very much!!!
Will update how it all wetn when finished.

Categories

Resources