Database Develop

[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

[Q] Stuck on tampered relocked, not sure how to revert back to stock

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

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

How to install the Lollipop OTA on a rooted M7 with a stock rom and custom recovery

THIS IS A GUIDE ON HOW TO INSTALL THE LOLLIPOP OTA UPDATE ON A ROOTED INTERNATIONAL HTC ONE M7 WITH A CUSTOM RECOVERY AND A STOCK HTC SENSE ROM
Disclaimer: I am making this guide to help you if I can. I am doing that because I have spent more than 10 hours trying to upgrade my phone; and because I am new at this, I soft bricked my phone. I did unbrick it and install lollipop eventually but I am making this for the people like me, so that you don’t make the same mistakes. Oh, and, never tick “system” when doing a wipe trough TWRP recovery XD With that said, I am not a pro, but I have learned a lot trough trial and error; so, follow the instructions carefully and be patient!!! I am not responsible if something goes horrendously wrong, good luck! Also, sorry for the weird formatting, I am very new to that as well.
Hey everybody, as you probably know, HTC has started rolling out Lollipop to M7s.
If you are like me and love to have control over your phone and its customization, you probably rooted your device and installed a custom recovery to have more options like full system backups...
Well, now that the update is out, you might have tried to upgrade following the on screen instructions for the OTA (Over The Air) update and found out it can’t be done just like that. I am here to tell you, don’t worry, don’t bang your head against the table, there is a way, and it is simple. This is a collection of some of the things that I have learned in the previous two days:
You will need a couple of things:
*Your International HTC One M7
You can be S-OFF OR S-On
*The Android SDK
Your alternative would be the Minimal ADB and Fastboot because that’s the part of the sdk we will be using for this. I recommend the SDK if you don’t quite now what you are doing because I will be explaining how to use that, otherwise, feel free to use the Minimal ADB and Fastboot. But, if you are going to use the Minimal ADB and Fastboot don’t forget to create a desktop shortcut, it will make things easier later.
*The OTA zip itself
We will need this to get the stock recovery image, I will explain why soon.
*Your htcdev.com account
We will need it to unlock your boot loader later because in order to complete this, you will
temporarily relock your bootloader.
*Your phones drivers ( If you do install the drivers I linked, you should probably uninstall HTC sync,
just to be on the safe side)
*Your PC (I will write for Windows because that’s what I have)
THE LINKS TO EVERYTHING YOU NEED:
-The Tools:
Android SDK (Android Sutdio): http://developer.android.com/sdk/index.html
Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
-The phone drivers:
https://www.youtube.com/watch?v=afrvSGiMAtk (This video is really good, it shows you how you can get the drivers to work so that adb recognizes your phone even in recovery, it is useful for side loading and stuff... I recommend doing this just to be safe, you can install HTC sync later if you want)
Ok, let’s begin:
1. Download the OTA zip file on to your phone as you normaly would, but don’t click install. Instead, copy the file to a folder on your desktop (name the folder what you want).
2. Right click the zip and click “Extract to .......” (with the ..... being the name of the OTA file)
3. In there, there will be another zip file called “firmware.zip”
4. Extract that one, we will use it to get the stock recovery. Why do we need the stock recovery if the custom one is better? We need it to install the OTA update because of the way that OTA files are made and the way that the stock recovery works. The stock recovery is made to do two things, preform a factory reset and to install OTA updates. The OTA update zips are made to be only installed trough the stock recovery. I don’t know why, but that’s what I found out, simple as that.
5. Now, Copy that recovery.img file back in to the main folder on your desktop (you don't need the OTA zip on your computer anymore, if you want delete it)
6. In order to apply the OTA update file, you will need to temporaroly relock your bootloader and flash the stock recovery. To do that:
1) Boot your phone in to the bootloader by holding Vol Down + Power
2) Navigate with the volume keys and click the power button to select. Select the “fastboot mode” it should show up red and say fastboot. (fastboot usb if connected to pc)
3) Connect the phone to the PC via USB 2.0 (USB 3.0 might not work)
4) Go to folder where you installed Android SDK and go in to the “platform-tools” folder and while holding shift right click in the empty space of the folder and click open command window here .
5) Type in “fastboot devices” (witouth the quote marks) this will make sure your PC sees your phone.
If a radnom set of numbers appears and by it fastboot or something like that, you are good, if not check the connection and the drivers. I will link to how to get drivers to work because there are known issues when using windows 8/8.1
6) Next thing is to copy the recovery file from the desktop folder in to the platform-tools folder.
7) Type in “fastboot flash recovery recovery.img”
8) Type in “fastboot reboot-bootloader”
9) Type in “fastboot oem lock” (This will lock the bootloader, we will unlock it again later)
7. Boot your phone up and normaly install the OTA update.
8. To reinstall the custom recovery, just download the latest TWRP or Clockworkmoad recovery for the M7 and copy it in to the platform tools folder. Boot the phone in to fastboot again and type in “fastboot flash recovery ****.img” (wher **** is the name of your custom recovery image)
9. To unlock your bootloader, do the same as you did the first tame you did it, follow the htcdev.com instructions. If you still have the unlock token, just put it in to the platform-tools folder. Boot in to fastboot and type in “fastboot flash unlocktoken Unlock_code.bin”
If for any reason you get into a boot loop, just reboot into recovery trough the bootloader and wipe cache and dalvik cache
That’s it, you should now have a rooted HTC One M7 running stock Lollipop sense.
And, some sugestions:
-Keep the stock recovery somewhere if you ever need it again. I say this because when I was searching for the stock recovery image, people were saying to download one from the internet but to be careful... That would be much more complicated because there is no guaranty that the recovery you download is right for your exact phone! This is the simplest way, and it is guarantied to work because in the OTA zip for your phone is the recovery that is made to work on your phone!
-Keep the unlocktoken in order to easily unlock your bootloader if you ever need to relock it again, it just saves you time.

MrSolution98 said:
THIS IS A GUIDE ON HOW TO INSTALL THE LOLLIPOP OTA UPDATE ON A ROOTED INTERNATIONAL HTC ONE M7 WITH A CUSTOM RECOVERY AND A STOCK HTC SENSE ROM
Disclaimer: I am making this guide to help you if I can. I am doing that because I have spent more than 10 hours trying to upgrade my phone; and because I am new at this, I soft bricked my phone. I did unbrick it and install lollipop eventually but I am making this for the people like me, so that you don’t make the same mistakes. Oh, and, never tick “system” when doing a wipe trough TWRP recovery XD With that said, I am not a pro, but I have learned a lot trough trial and error; so, follow the instructions carefully and be patient!!! I am not responsible if something goes horrendously wrong, good luck! Also, sorry for the weird formatting, I am very new to that as well.
Hey everybody, as you probably know, HTC has started rolling out Lollipop to M7s.
If you are like me and love to have control over your phone and its customization, you probably rooted your device and installed a custom recovery to have more options like full system backups...
Well, now that the update is out, you might have tried to upgrade following the on screen instructions for the OTA (Over The Air) update and found out it can’t be done just like that. I am here to tell you, don’t worry, don’t bang your head against the table, there is a way, and it is simple. This is a collection of some of the things that I have learned in the previous two days:
You will need a couple of things:
*Your International HTC One M7
You can be S-OFF OR S-On
*The Android SDK
Your alternative would be the Minimal ADB and Fastboot because that’s the part of the sdk we will be using for this. I recommend the SDK if you don’t quite now what you are doing because I will be explaining how to use that, otherwise, feel free to use the Minimal ADB and Fastboot. But, if you are going to use the Minimal ADB and Fastboot don’t forget to create a desktop shortcut, it will make things easier later.
*The OTA zip itself
We will need this to get the stock recovery image, I will explain why soon.
*Your htcdev.com account
We will need it to unlock your boot loader later because in order to complete this, you will
temporarily relock your bootloader.
*Your phones drivers ( If you do install the drivers I linked, you should probably uninstall HTC sync,
just to be on the safe side)
*Your PC (I will write for Windows because that’s what I have)
THE LINKS TO EVERYTHING YOU NEED:
-The Tools:
Android SDK (Android Sutdio): http://developer.android.com/sdk/index.html
Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
-The phone drivers:
https://www.youtube.com/watch?v=afrvSGiMAtk (This video is really good, it shows you how you can get the drivers to work so that adb recognizes your phone even in recovery, it is useful for side loading and stuff... I recommend doing this just to be safe, you can install HTC sync later if you want)
Ok, let’s begin:
1. Download the OTA zip file on to your phone as you normaly would, but don’t click install. Instead, copy the file to a folder on your desktop (name the folder what you want).
2. Right click the zip and click “Extract to .......” (with the ..... being the name of the OTA file)
3. In there, there will be another zip file called “firmware.zip”
4. Extract that one, we will use it to get the stock recovery. Why do we need the stock recovery if the custom one is better? We need it to install the OTA update because of the way that OTA files are made and the way that the stock recovery works. The stock recovery is made to do two things, preform a factory reset and to install OTA updates. The OTA update zips are made to be only installed trough the stock recovery. I don’t know why, but that’s what I found out, simple as that.
5. Now, Copy that recovery.img file back in to the main folder on your desktop (you don't need the OTA zip on your computer anymore, if you want delete it)
6. In order to apply the OTA update file, you will need to temporaroly relock your bootloader and flash the stock recovery. To do that:
1) Boot your phone in to the bootloader by holding Vol Down + Power
2) Navigate with the volume keys and click the power button to select. Select the “fastboot mode” it should show up red and say fastboot. (fastboot usb if connected to pc)
3) Connect the phone to the PC via USB 2.0 (USB 3.0 might not work)
4) Go to folder where you installed Android SDK and go in to the “platform-tools” folder and while holding shift right click in the empty space of the folder and click open command window here .
5) Type in “fastboot devices” (witouth the quote marks) this will make sure your PC sees your phone.
If a radnom set of numbers appears and by it fastboot or something like that, you are good, if not check the connection and the drivers. I will link to how to get drivers to work because there are known issues when using windows 8/8.1
6) Next thing is to copy the recovery file from the desktop folder in to the platform-tools folder.
7) Type in “fastboot flash recovery recovery.img”
8) Type in “fastboot reboot-bootloader”
9) Type in “fastboot oem lock” (This will lock the bootloader, we will unlock it again later)
7. Boot your phone up and normaly install the OTA update.
8. To reinstall the custom recovery, just download the latest TWRP or Clockworkmoad recovery for the M7 and copy it in to the platform tools folder. Boot the phone in to fastboot again and type in “fastboot flash recovery ****.img” (wher **** is the name of your custom recovery image)
9. To unlock your bootloader, do the same as you did the first tame you did it, follow the htcdev.com instructions. If you still have the unlock token, just put it in to the platform-tools folder. Boot in to fastboot and type in “fastboot flash unlocktoken Unlock_code.bin”
If for any reason you get into a boot loop, just reboot into recovery trough the bootloader and wipe cache and dalvik cache
That’s it, you should now have a rooted HTC One M7 running stock Lollipop sense.
And, some sugestions:
-Keep the stock recovery somewhere if you ever need it again. I say this because when I was searching for the stock recovery image, people were saying to download one from the internet but to be careful... That would be much more complicated because there is no guaranty that the recovery you download is right for your exact phone! This is the simplest way, and it is guarantied to work because in the OTA zip for your phone is the recovery that is made to work on your phone!
-Keep the unlocktoken in order to easily unlock your bootloader if you ever need to relock it again, it just saves you time.
Click to expand...
Click to collapse
You sir are a genius. I was just about to throw the phone and laptop out the window. 3 days of getting nowhere and then i found this. Thank you. Just have a question. What will happen now with further updates? HTC have only released 5.0 as far as i know but 5.1 has been rolled out to some already? Will future updates go back to normal?

:good:
Really interesting. Thanks

stef6692 said:
You sir are a genius. I was just about to throw the phone and laptop out the window. 3 days of getting nowhere and then i found this. Thank you. Just have a question. What will happen now with further updates? HTC have only released 5.0 as far as i know but 5.1 has been rolled out to some already? Will future updates go back to normal?
Click to expand...
Click to collapse
Hey, thank you! It really means a lot! I know the struggle of thinking you broke your very expensive smart phone... I soft bricked my phone after this by wiping everything trough the recovery because I didn't read what i checked on the wipe list... My phone is working now, I installed an aosp lollipop rom because I didn't like that htc stuck with sense 6 when releasing lollipop for the M7... I just felt it didn't have all the features I was looking for. To answer your question: go to this website (just copy it to a new window in your browser and delete the spaces; I can't post outside links yet...) http : // androidcommunity.com/ htc-one-m7-could-be-updated-to-android-5-1-20150323/

martin1984 said:
:good:
Really interesting. Thanks
Click to expand...
Click to collapse
Thank you. Glad I could help!

keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?

ljy1 said:
keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?
Click to expand...
Click to collapse
You have flashed a custom kernel. YOu have to restore your rom to 100% stock,

ljy1 said:
keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?
Click to expand...
Click to collapse
I think @alray is right. Do you have the OTA zip file? Because if you do, I think you can fix this problem by flashing the firmware.zip that is located in the ota zip. @alray am I correct? This came to mind because I had to do that when I was installing a new rom, it needed to have the stock firmware. If you do, and this is correct, come back to this thread and I will do my best to help you

MrSolution98 said:
I think @alray is right. Do you have the OTA zip file? Because if you do, I think you can fix this problem by flashing the firmware.zip that is located in the ota zip. @alray am I correct? This came to mind because I had to do that when I was installing a new rom, it needed to have the stock firmware. If you do, and this is correct, come back to this thread and I will do my best to help you
Click to expand...
Click to collapse
Flashing the stock firmware won't change anything to /system. He must restore the stock rom because his custom kernel made some changes in /system.

alray said:
Flashing the stock firmware won't change anything to /system. He must restore the stock rom because his custom kernel made some changes in /system.
Click to expand...
Click to collapse
Hmmm :silly: @alray Maybe he could try the Android Revolution Rom, it is basically stock lollipop sense. I have tried it as well as the original software, didn't run into any differences or problems... Maybe that would be easier than trying to find the original software for his specific phone... I managed to sideload this rom using twrp when my phone was soft bricked... So, I think flashing the rom won't be a problem if he has a working phone. But, also, I think he will have to flash the firmware.zip to install this rom, that's what I was talking about earlier,

MrSolution98 said:
Hmmm :silly: @alray Maybe he could try the Android Revolution Rom, it is basically stock lollipop sense. I have tried it as well as the original software, didn't run into any differences or problems... Maybe that would be easier than trying to find the original software for his specific phone...
Click to expand...
Click to collapse
It might be really easy to find the original rom for his phone, its all depend what version he is currently on. I agree that if he can't find it, using a custom rom like arhd is good alternative. We can help him find the required files (if they exist) but he will first need to post the output of "fastboot getvar all"

alray said:
It might be really easy to find the original rom for his phone, its all depend what version he is currently on. I agree that if he can't find it, using a custom rom like arhd is good alternative. We can help him find the required files (if they exist) but he will first need to post the output of "fastboot getvar all"
Click to expand...
Click to collapse
Okay, and thanks for the replies! I am relatively new to this and want to learn something from this If and when he does do that, we will continue this
Also, I don't know about finding the software for his specific phone being easy... Could you explain? @alray When I was looking for the software for my phone I read about the CID number having to mach up and that the phones, even though they are from the same variant, they are different for different parts of the world... I couldn't even manage to find the recovery.img that worked on my phone... That's why I think I was lucky to have the ota zip on my computer... I found the stock recovery and the firmware zip which I needed later on... From all that, I kinda got the impression that finding the exact software is not impossible but hard if you don't understand what exactly you are looking for... That's why I would recommend arhd if you just want the stock experience but don't want to mess around too much.

Goofed during recovery replacement
Alray, I accidentally flashed boot instead of recovery in an attempt to get the LP OTA going. I can't find a replacement to get it working again. I used a Guru Reset zip, but after the first reboot, it took me to a jacked boot img. What can I do. I really just want AT&T Lollipop.
C:\Users\markm_000\Dropbox\Apps\HTCOne>fastboot.exe
(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:
(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: 4312mV
(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

mmccurdy said:
Alray, I accidentally flashed boot instead of recovery in an attempt to get the LP OTA going. I can't find a replacement to get it working again. I used a Guru Reset zip, but after the first reboot, it took me to a jacked boot img. What can I do. I really just want AT&T Lollipop.
C:\Users\markm_000\Dropbox\Apps\HTCOne>fastboot.exe
(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:
(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: 4312mV
(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
Lock your bootloader and run the RUU from this post.

Was desperate for a quick fix
majmoz said:
Lock your bootloader and run the RUU from this post.
Click to expand...
Click to collapse
Thanks. In the meantime, I only found salvation by installing a generic rom, S-OFF'ing, changing the CID/MID, and using the developer RUU. I couldn't find the RUU for my particulars.. I should probably switch back to S-ON unless there's a good reason to leave it.

can u help me
after i received lollipop update in my brother M7 DUAL SIM
i successfully downloaded it , and when i press install now the phone reboot to bootloader and nothing happens
i tried this more than one time and every time it take me to bootloader
can u help me ....
i tried ur method but nothing change
TAMPERED
RELOCKED
security warning
M7CDUG PVT SHIP S-ON RL
HBOOT-2.49.0000
RADIO-U3.15.3509.12
phone never rooted
and i have no recovery " when i try to enter recovery from bootloader nothing happen

Possibly a stupid question, but:
Will this wipe the user data from the phone? I don't see why reverting to stock would do that, but doesn't using the HTCDevs to unlock the bootloader wipe the phone?
Thanks!

toycar69 said:
Possibly a stupid question, but:
Will this wipe the user data from the phone? I don't see why reverting to stock would do that, but doesn't using the HTCDevs to unlock the bootloader wipe the phone?
Thanks!
Click to expand...
Click to collapse
What is your situation and your goal exactly? You might not need to follow this guide.
Yes unlocking the bootloader wipe the phone

Hi Alray,
my current situation is I have an HTC M7, S-OFF and rooted, running stock ROM on Android 4.4.4 and TWRP recovery. I've been holding back, but now I'd like to try the stock Lollipop upgrade. I have no modifications to the system partition, except the SuperSU binary.
Is it possible for me to just flash the stock recovery and run the OTA then?
Thanks!

toycar69 said:
Hi Alray,
my current situation is I have an HTC M7, S-OFF and rooted, running stock ROM on Android 4.4.4 and TWRP recovery. I've been holding back, but now I'd like to try the stock Lollipop upgrade. I have no modifications to the system partition, except the SuperSU binary.
Is it possible for me to just flash the stock recovery and run the OTA then?
Thanks!
Click to expand...
Click to collapse
I would indeed try to do this first as it will only take you 5 minutes to flash the stock recovery back. If the ota fails (red triangle) then its because something isn't 100% stock and you'll have to flash a lollipop RUU.