Related
I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...
sofakng said:
I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...
Click to expand...
Click to collapse
actually what are you trying to achieve?
Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?
sofakng said:
Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?
Click to expand...
Click to collapse
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock
matt95 said:
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock
Click to expand...
Click to collapse
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...
sofakng said:
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...
Click to expand...
Click to collapse
it worked in your case the stock recovery always gives that symbol there's nothing wrong with it
Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!
sofakng said:
Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!
Click to expand...
Click to collapse
Try getting the .zip one and do a fastboot version. Works for me.
tozfeekum said:
I'm trying to return my HTC developer edition back to stock
and I am running the RUU via terminal:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip.
I've tried running it immediately as suggested in other threads but that hasn't worked.
Does anyone know what's going on here:
ending 'zip' (1004418 KB)...
OKAY [ 34.434s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 165.173s
EDIT:
I got this working by running fastboot erase cache
Click to expand...
Click to collapse
I'm not sure if you're also experiencing the recovery partition missing, like in my thread.
http://forum.xda-developers.com/showthread.php?t=2267008
Hmmmm, maybe that's my problem?
I've just flashed the ZIP, and everything looked like it worked fine... (I received the "please flush image" message and I re-ran the flash and it then completely successfully)
However, when I select [Recovery] from HBOOT, the screen flashes for a second, and then it returns to the HBOOT again. It does seem like the recovery partition is missing...?
Here is my fastboot log: http://pastebin.com/KQJjE78a
EDIT: When I unlocked my bootloader (fastboot flash unlocktoken), and then tried to enter recovery, it went back into clockwork recovery!!
The RUU/ZIP is absolutely, positively, not overwriting my recovery... (which is also why the bootloader still says "tampered" as well, because the entire stock image is not being 100% restored)
I have the same exact problem with my one dev edition.Hope someone can figure this out
Sent from my HTC One using xda premium
Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us
sofakng said:
Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us
Click to expand...
Click to collapse
you succeeded in installing the recovery then?
matt95 said:
you succeeded in installing the recovery then?
Click to expand...
Click to collapse
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...
sofakng said:
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...
Click to expand...
Click to collapse
the stock one i mean..? where did you get it? from a nandroid backup or from the RUU itself?
The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium
martyotaku said:
The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.
sofakng said:
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.
Click to expand...
Click to collapse
Did you do the fastboot erase cache?
The way I got it back to stock recovery was doing this.
When I had CWM, I attempted to fastboot a different recovery using this.
http://forum.xda-developers.com/showthread.php?t=2158763&highlight=recovery+img
It installed but it never worked as the phone could not enter. Then I just fastboot the factory zip and it some how overriden the faulty recovery and it worked.
I'm not home now and hate using this app lol I'll post it when I get home ...but it's from dev mikes post
edit here is what i used from this link http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt
I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
since your S-On you can't use the RUU's and I'm pretty sure those system.img files are not signed; they are just dumps in img format so even if they weren't too big they still wouldn't work.
mthomas1262 said:
I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt
Click to expand...
Click to collapse
ipfreelytech said:
I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.
dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
mthomas1262 said:
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.
Click to expand...
Click to collapse
ipfreelytech said:
dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
Click to expand...
Click to collapse
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?
sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
mthomas1262 said:
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?
Click to expand...
Click to collapse
ipfreelytech said:
sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
Click to expand...
Click to collapse
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers
Here you go:
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
extract the zip, then copy the folder to your recovery's backup location. I made it with CWM.
If your using CWM you can use the command adb push 2013-11-28.07.23.56 /data/media/clockworkmod/backup/GPE/
then restore it from the menu
Here's a link to the untouched firmware.zip from the OTA:
https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
flash that zip from fastboot.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 firmware.zip
fastboot reboot
should be good to go then. You'll have stock /system and stock recovery so future OTA should work.
mthomas1262 said:
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers
Click to expand...
Click to collapse
I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. Last night I discovered the stock recovery image and loaded that successfully (wanting a stock experience now). This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!
s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
The_Doctor_Who said:
I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. I wanted a totally stock experience. Last night I discovered the stock recovery image and loaded that successfully. This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!
Click to expand...
Click to collapse
ipfreelytech said:
s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
Click to expand...
Click to collapse
It did come in the GPE box, so I hope he didn't go that much out of the way to lie! lol It is the official GPE.
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.
there is no legit RUU for GPE! The conversion RUU only works with s-off because it is not properly signed!
flash this CWM: http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
after flashing fastboot erase cache
select reboot bootloader on your phone. then select recovery.
then continue with restoring my nandroid and then flashing the firmware in RUU mode.
The_Doctor_Who said:
It did come in the GPE box, so I hope he didn't go that much out of the way to lie!
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.
Click to expand...
Click to collapse
looking great - enjoying me some kit-kat right now! thanks a ton!
Awesome. So I take it my nandroid plus the firmware zip worked for you?
mthomas1262 said:
looking great - enjoying me some kit-kat right now! thanks a ton!
Click to expand...
Click to collapse
ipfreelytech said:
Awesome. So I take it my nandroid plus the firmware zip worked for you?
Click to expand...
Click to collapse
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!
That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.
Ok - at least I know what my issue was before. I attempted to install SuperSU.zip 1.8, installs fine, but when I go into regular boot get boot looping again. Looks like I'll need to wait for an update to SuperSU.zip - if someone with authority can post in the SuperSU thread that might be really helpful.
Thanks!
good eye. I have fixed the link. here's the right one: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
The purpose of the firmware.zip is to get all your firmware on the correct version as well as writing the stock recovery so that future OTA will work without issue [assuming of course you don't screw with /system by deleting apk you don't use or editing files].
you flash it using fastboot after rebooting to ruu mode. re-read my post.
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
mthomas1262 said:
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!
Click to expand...
Click to collapse
---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------
fastboot getvar all
paste the results here with imei and serial redacted.
The_Doctor_Who said:
That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.
Click to expand...
Click to collapse
I greatly appreciate the help (and apologize for stepping on the toes of the OP).
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
ipfreelytech said:
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
Click to expand...
Click to collapse
I got the installer from:
download (dot) chainfire (dot) eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
(can't post URLs yet)
I haven't tried to get s-off, on on the 1.54 version so that makes things a little harder, I've seen some posts about it.
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.
It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?
dukocuk said:
It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?
Click to expand...
Click to collapse
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)
alray said:
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)
Click to expand...
Click to collapse
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
dukocuk said:
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse
What happens when you try to unlock the bootloader?
alray said:
What happens when you try to unlock the bootloader?
Click to expand...
Click to collapse
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.
dukocuk said:
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.
Click to expand...
Click to collapse
do you have a custom recovery installed ?
if so, the only way you can unlock the bootloader is to flash the stock firmware to put stock recovery back on, you cant lock or relock the bootloader with custom software on your phone.
Stock firmware here: https://www.androidfilehost.com/?fid=95832962473395871
i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.
dukocuk said:
i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.
Click to expand...
Click to collapse
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?
Seanie280672 said:
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?
Click to expand...
Click to collapse
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.
dukocuk said:
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.
Click to expand...
Click to collapse
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.
Seanie280672 said:
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.
Click to expand...
Click to collapse
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?
dukocuk said:
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?
Click to expand...
Click to collapse
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.
Seanie280672 said:
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.
Click to expand...
Click to collapse
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions, did read the guides but didnt get the idea fully.
dukocuk said:
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions.
Click to expand...
Click to collapse
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.
Seanie280672 said:
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.
Click to expand...
Click to collapse
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???
dukocuk said:
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???
Click to expand...
Click to collapse
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.
Seanie280672 said:
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.
Click to expand...
Click to collapse
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone? That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?
dukocuk said:
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone?
Click to expand...
Click to collapse
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
dukocuk said:
That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?
Click to expand...
Click to collapse
bin that firmware file, you wont need it again.
Seanie280672 said:
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
bin that firmware file, you wont need it again.
Click to expand...
Click to collapse
Thank, i followed the guide you made for that person, it helped me out too.
I appreciate it.
Hi,
I've kind of soft bricked my phone. Good thing is still able to fastboot as my PC detects it via USB.
I am new to Android rooting, flashing etc.
I had android Lollipop before I messed up phone. I've downloaded Nandroid backup and RUU for Indian version of HTC One 802d from other threads on XDA.
I am not sure of process to use that Nandroid backup. I've CWM recovery but don't have root access. Bootloader iss unlocked.
For other thing i.e. RUU that I downloaded is a zip file. But for some strange reason I'm not able to extract it on windows 7. It says compressed zip folder is invalid. I also downloaded Chinese RUU which is again zip and doesn't extarct, gives same error.
I am new to all this though I've some knowledge about computers and gadgets.
Please help me on how to get back my phone working may by Nandroid or RUU or anything else.
Please let me know if any details or information is needed.
Greatly appreciate any help in this regard. Thank you!
Hi,
Can someone please help me with this? :crying:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
donkeykong1 said:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
Click to expand...
Click to collapse
Thanks a lot for your reply!
Okay I get a point about RUU.zip not opening. I was trying it at first place cause I saw it some video that he opens it and then runs a setup file in it which opens windows wizard which then guides step by step to flash RUU from GUI.
Yes, my phone is S-On and I've been doing quite a lot reading since past couple of days and understading things better with every reading.
Now, I need further help. I'll first briefly explain how I messed up my phone. I had android L with Sense 6 in my cellphone before I started playing with it and decided to root. After watching few tutorials I first unlocked Bootloader then flashed cwm recovery. After that I took a backup from cwm and then installed SuperSu.zip from cwm recovery and rebooted phone normally. It started but SuperSu installed earlier was stopping regularly throwing error messages. I also downloaded rootChecker app and it showed that I didn't have root access.
Here, I slightly panicked as this is first time I was playing around with it. I rebooted my phone, went to cwm recovery and tried restoring back up that I took earlier as said above. But I didn't have root access and since then my phone went in bootloop and not starting.
My PC detects it when I connect in fastboot USB and i am able to execute fastboot commands.
=======================================================================================
Now, I,ll explain steps I am following to get my phone working :
1) I downloaded few RUU zip latest being from here --> http://www.mediafire.com/download/k...1_09B_release_391798_signed+by+jamesjerss.zip
2) Downloaded stock recovery for KITKAT from other xda thread --> http://forum.xda-developers.com/showthread.php?t=2617159
3) flashed this stock recovery then relocked my phone. fastboot oem lock.
4) executed fastboot oem rebootRUU
5) executed fastboot flash zip ruu.zip with the ruu zip downloaded in step 1 above
but it fails with version check failed , some error like this don't remember exact wording of it. I can get you that if needed by trying one more time.
Also, I can provide other information like getvar all and hboot version etc if required but kindly help me get out of this. Really appreciate your help.
I just want to highlight one more thing that I visited HTC care centre yesterday and without looking much at device just by looking at bootloader and cwm recovery he said that OS is corrupt and I'll need to replace mother board which costs half the price of phone. I don't believe him. It is just soft bricked and am able to connect in fastboot USB.
Please guide me on how to proceed further ahead.
Thank you once again!
<<Just getting you the output after running flash zip>>
C:\Users\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboo
t flash zip ruukkn.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1344718 KB)...
OKAY [ 75.112s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 190.871s
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot ?
donkeykong1 said:
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot
Click to expand...
Click to collapse
Lol. He certainly seems to be one.
Below is result of getvar all -->
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: 2.04.30.0316
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.720.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: A1000037A674B4
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it ?
donkeykong1 said:
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it
Click to expand...
Click to collapse
he he I won't do that definitely.
But earlier yesterday I had tried with Lollipop RUU downloaded from -->
androidfilehost.com/?fid=24052804347774374
but that too failed with similar signature verify fail.
What should I do?
<<<<<<<<<<<<<<Just to point out>>>>>>>>>>>>>>>>>>>>>>>>>>
Lollipop RUU that I downloaded is like PN07IMG_M7C_DWG_L50_SENSE60_MR_hTC_Asia_India_]7.17 .720.6_Radio_1237.29.35.0903 release_426120_signed.zip whereas from getvar results shared above it shows version like --> bootloader) version-main: 7.17.720.15
does it make a difference? if yes, that's the latest RUU I can find online.
How can I proceed in this scenario?
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
donkeykong1 said:
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
Click to expand...
Click to collapse
Okay but what after flashing TWRP recovery? How will it help?
yogeshchaudhari21 said:
Okay but what after flashing TWRP recovery? How will it help?
Click to expand...
Click to collapse
We'll find a TWRP nandroid backup and restore it [emoji6]
donkeykong1 said:
We'll find a TWRP nandroid backup and restore it [emoji6]
Click to expand...
Click to collapse
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
yogeshchaudhari21 said:
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob [emoji14] , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
Click to expand...
Click to collapse
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
donkeykong1 said:
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
Click to expand...
Click to collapse
Oh sure! I'll be waiting.
I do have a cwm recovery although it's not touch version but that doesn't matter I guess.
Really appreciate your support. Thanks!
I'm back. did you flash the recovery yet?
donkeykong1 said:
I'm back. did you flash the recovery yet?
Click to expand...
Click to collapse
Hey hi!
Yes, I did.
yogeshchaudhari21 said:
Hey hi!
Yes, I did.
Click to expand...
Click to collapse
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
donkeykong1 said:
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
Click to expand...
Click to collapse
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
yogeshchaudhari21 said:
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
Click to expand...
Click to collapse
Did you unlock your bootloader again?
donkeykong1 said:
Did you unlock your bootloader again?
Click to expand...
Click to collapse
Yes I did unlock and then flashed recovery. I've been doing it quite a few times since yesterday so got used to it. This is something strange happening.