Hello friends
I have a HTC One M7, US factory unlocked 32 gigs model, initially it was running on stock ROM's but to get 4.4.2 OTA Kitkat with sense 5.5 i had gone completely stock, relocked my bootloader and used 4.3 RUU from Htc dev center. After flashing 4.3 RUU, i had got a prompt update to 4.4.2 OTA and it went smoothly. The phone is stock since then and few days back tried updating to Sense 6.0 but the phone tried updating OTA, showed me a red triangle and reported "system/app/google.apk has unexpected contents" and the update stopped.
Am totally clueless as to what is wrong with the phone now, how do i correct this error to get OTA update, i cant find the 4.4.2 RUU on htc site. Currently running on 4.19.1540.9 so can i again flash 4.3 RUU, then update OTA to 4.4.2 and then another OTA to sense 6.0? Or is there a short and easy way out?
Thanks
romeo7151 said:
Hello friends
I have a HTC One M7, US factory unlocked 32 gigs model, initially it was running on stock ROM's but to get 4.4.2 OTA Kitkat with sense 5.5 i had gone completely stock, relocked my bootloader and used 4.3 RUU from Htc dev center. After flashing 4.3 RUU, i had got a prompt update to 4.4.2 OTA and it went smoothly. The phone is stock since then and few days back tried updating to Sense 6.0 but the phone tried updating OTA, showed me a red triangle and reported "system/app/google.apk has unexpected contents" and the update stopped.
Am totally clueless as to what is wrong with the phone now, how do i correct this error to get OTA update, i cant find the 4.4.2 RUU on htc site. Currently running on 4.19.1540.9 so can i again flash 4.3 RUU, then update OTA to 4.4.2 and then another OTA to sense 6.0? Or is there a short and easy way out?
Thanks
Click to expand...
Click to collapse
please post the output of ''fastboot getvar all'' except imei and sn. There is a 4.19.1540.9 RUU so in theory, you should be able to run it and update to 5.11.1540
is your bootloader locked or unlocked?
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353887_signed_3-exe/
http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
Thanks for your help alray, posting the getvar all below. The bootloader is locked as of now showing re-locked.
c:\mini-sdk>fastboot getvar all
< waiting for device >
(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.19.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34TW904XXX
(bootloader) imei: 35443905990XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.101s
alray said:
please post the output of ''fastboot getvar all'' except imei and sn. There is a 4.19.1540.9 RUU so in theory, you should be able to run it and update to 5.11.1540
Click to expand...
Click to collapse
Something is off.
There is no Google.apk ...
Seocondly here is the checker file from OTA.. for eg.
apply_patch_check("/system/app/Gmail2.apk", "1320556b1253fba48ef13ca56a53c3bf1994069b", "73cf8dcc9241d5055c57317c92c1b54566206d4a") || abort("\"/system/app/Gmail2.apk\" has unexpected contents.");
set_progress(0.054699);
That seems to be doing some kind of a md5 check on Gmail2.apk before patching..
Maybe you need to re-run the RUU for 4.x.x.x (I have not been able to run it myself) and if incase it doesn't run, then S-oFF and go back to 3.x.x.x RUU, and then update away.
Last option will be restore a working nandroid of 5.x.x.x and install firmware.zip from 5.x.x.x OTA.. (I do not suggest it unless you absolutely have to.. good chances of things going bad.. even if you follow directions, specially without S-OFF)
---
ALSO...if you can get the exact file name, MAYBE we can get the ORIGINAL file from a working 4.4.2/Sense 5.5 firmware.
I am not suggesting this fix, but for more reading: http://forum.xda-developers.com/showthread.php?t=1945938 This is for Nexus 7
Thanks Sahil,
I did the OTA again to get the file name and got system/app/plusone.apk has unexpected contents. So this is where the problem lies in.
Can you tell why the 4.xx RUU are not working, any reason why it didnt work in your case. That was what i was planning to do. How do we change the system apps with stock ones? Read that thread, can we flash system.img? Is it safe? I would need to unlock the bootloader again for it, right?
SaHiLzZ said:
Something is off.
There is no Google.apk ...
Seocondly here is the checker file from OTA.. for eg.
apply_patch_check("/system/app/Gmail2.apk", "1320556b1253fba48ef13ca56a53c3bf1994069b", "73cf8dcc9241d5055c57317c92c1b54566206d4a") || abort("\"/system/app/Gmail2.apk\" has unexpected contents.");
set_progress(0.054699);
That seems to be doing some kind of a md5 check on Gmail2.apk before patching..
Maybe you need to re-run the RUU for 4.x.x.x (I have not been able to run it myself) and if incase it doesn't run, then S-oFF and go back to 3.x.x.x RUU, and then update away.
Last option will be restore a working nandroid of 5.x.x.x and install firmware.zip from 5.x.x.x OTA.. (I do not suggest it unless you absolutely have to.. good chances of things going bad.. even if you follow directions, specially without S-OFF)
---
ALSO...if you can get the exact file name, MAYBE we can get the ORIGINAL file from a working 4.4.2/Sense 5.5 firmware.
I am not suggesting this fix, but for more reading: http://forum.xda-developers.com/showthread.php?t=1945938 This is for Nexus 7
Click to expand...
Click to collapse
romeo7151 said:
Thanks Sahil,
I did the OTA again to get the file name and got system/app/plusone.apk has unexpected contents. So this is where the problem lies in.
Can you tell why the 4.xx RUU are not working, any reason why it didnt work in your case. That was what i was planning to do. How do we change the system apps with stock ones? Read that thread, can we flash system.img? Is it safe? I would need to unlock the bootloader again for it, right?
Click to expand...
Click to collapse
I am not sure why 4.x RUU are not working. You should try it on your computer however, as that will be the best bet.
You should also S-OFF before doing the OTA right now, as S-OFF will allow you to downgrade as a get out of jail card.
DO NOT FLASH SYSTEM.IMG... I just linked the thread for what the updater script is doing, do not follow anything from that thread. I REPEAT!!
Have you ever used Titanium backup or file explorer to delete apps from system partition?
Thanks bro, will try the RUU in a couple of days and update as to what happens. No clue on how to S-OFF but read a few threads on rev-one and firewater. Should i use firewater to S-OFF the device? Hboot is 1.56. As you say, will not flash the SYSTEM.IMG, not that adventurous though .
I have never ever used titanium backup or used root/file explorer to delete any system apps but did read that unlocking bootloader on HTC devices does delete a few system apps, maybe that is what's causing this issue or either it is just with this update, if those system files were missing, the phone should not have updated OTA to 4.4.2 Sense 5.5 when i had used 4.3 RUU and then did OTA.
SaHiLzZ said:
I am not sure why 4.x RUU are not working. You should try it on your computer however, as that will be the best bet.
You should also S-OFF before doing the OTA right now, as S-OFF will allow you to downgrade as a get out of jail card.
DO NOT FLASH SYSTEM.IMG... I just linked the thread for what the updater script is doing, do not follow anything from that thread. I REPEAT!!
Have you ever used Titanium backup or file explorer to delete apps from system partition?
Click to expand...
Click to collapse
romeo7151 said:
Thanks bro, will try the RUU in a couple of days and update as to what happens. No clue on how to S-OFF but read a few threads on rev-one and firewater. Should i use firewater to S-OFF the device? Hboot is 1.56. As you say, will not flash the SYSTEM.IMG, not that adventurous though .
Click to expand...
Click to collapse
use firewater, revone is for hboot 1.44 only.
did read that unlocking bootloader on HTC devices does delete a few system apps
Click to expand...
Click to collapse
unlocking bootloader with htcdev.com wipe /data including the sub-folders /data/storage/0 (sdcard) and /preload (/data/preload) where some HTC app are stored (flashlight, calculator, soundhound, weather animations etc etc. Some updates patches these files, if they are missing, the update will fail (MD5 check will fail) and report i.e ''unexpected content in /media/preload/calculator.apk''. Unlocking the bootloader doesn't delete file in /system, however its possible that some /system files were modified or deleted using root/custom kernel/s-off. Thats probably why you have a "unexpected content" (Md5 mismatch) of your /system/app/plusone.apk.
There is a nice post from nkk71 that explain everything in details: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
if those system files were missing, the phone should not have updated OTA to 4.4.2 Sense 5.5 when i had used 4.3 RUU and then did OTA.
Click to expand...
Click to collapse
Only specific files are patched during an ota update, so in theory its possible to do an ota update even if some files are missing/modified. If the updater-script of the ota doesn't check for those files (no patch to apply to those files) there is no reason for the installation to fail. So its possible that your plusone.apk was deleted/modified before that update.
and BTW plusone.apk seems to be Google+ for HTC One., will try to find the original file from te ota.zip I have on my computer.
edit: looks like plusone.apk was patched in 4.19.1540.4: so plusone.apk from 4.19.1540.4 or 4.19.1540.9 should do the job.
apply_patch_check("/system/app/PlusOne.apk", "eb47d88d7a485509637a9c8b2027952c7dfd2f73", "ee503ad46dd0d209d294121925e4ee05b3fb82d6") || abort("\"/system/app/PlusOne.apk\" has unexpected contents.");
Click to expand...
Click to collapse
then
assert(apply_patch("/system/app/PlusOne.apk", "-",
eb47d88d7a485509637a9c8b2027952c7dfd2f73, 22780041,
ee503ad46dd0d209d294121925e4ee05b3fb82d6, package_extract_file("patch/system/app/PlusOne.apk.p")));
Click to expand...
Click to collapse
---------- Post added at 05:10 PM ---------- Previous post was at 04:24 PM ----------
try this one, its from my 4.19.1540.9 backup. push it to /system/app and set permission to -rw-r--r--
try to update again and see if the script report any other "unexpected content" errors, if yes write them down and i'll send you the needed files.
Related
Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
(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.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:-
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
herwegan said:
@crushalot hey mate did you realize that there are now 4.19.xxx RUU's available on http://androidruu.com/?developer=M7# ?
for those who are interested: here's the link to the WWE 4.19.401.9 RUU
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
N3Gruj1989 said:
Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
Click to expand...
Click to collapse
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
Hi mb_guy, i have a twrp backup which i can restore, which could allow me to return to stock with superuser root access.
If i flash a stock recovery, will it remove my root access and receive future OTA? (if i am not mistaken, i tried flashing the stock recovery, and relocked the bootloader, but i just can't remove the superuser app :crying: )
Thanks.
below are my phone informations :
(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-ON
(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: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
mb_guy said:
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
Click to expand...
Click to collapse
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
yatin kumar said:
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
I googled HTC One stock recovery, but i didn't find a recovery for my HTC One build version, or are all the recovery.img the same?
Because I need a recovery.img for the 4.19.401.9 HTC_E11 (NL) version.
N3Gruj1989 said:
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
Click to expand...
Click to collapse
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Remove root by flashing stock firmware
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
ckpv5 said:
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Click to expand...
Click to collapse
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
N3Gruj1989 said:
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
Click to expand...
Click to collapse
You should have said this earlier. When you lost the some apps that reside in data/preload folder means you don't already have a proper stock, OTA most probably will be a fail attempt.
Flashing the recovery alone cannot guarantee a successful OTA update due to those missing apps.
The best option that you have is run the RUU unless you can find any nandroid backup for the current ROM.
For me, I will choose to run the RUU as that is always the best option when it is the right RUU for your device.
Make a backup to PC all your storage content in case you lose them by running the RUU (but unlikely you will lose them)
With the RUU ... the procedure is :
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
SiaoNang said:
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
Click to expand...
Click to collapse
If it is the firmware.zip alone, no .. it won't remove your root app.
When people say stock firmware it is always mean stock ROM.
To remove root, just simply select Full unroot in SuperSU settings. (asumming your rooting app is SuperSU as shown in that thread).
Thanks everyone for their help!
Everything worked fine, I'm back to stock now and just updated the OTA !
Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Flash a stock recovery... You'll probably find one in the thread you got your custom one from.
Then just relock bootloader with the command
fastboot oem lock
You can now update with no issues.
AmineOne said:
Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Click to expand...
Click to collapse
if you have unlocked your bootloader and rooted the phone, you'll probably have issue installing the update even if you restore the stock recovery, Like I said in the post you have linked, when you unlock bootloader, /data/preload get wiped. You need this folder and its content back in place to install ota updates. Also, if rooting or anything else you did, modified some /system files, the ota will not install. However, flash you stock recovery back and try the ota, if the ota fails with an image of a red triangle and an exclamation mark inside, then you'll need to restore some files (either /system files or /data/preload files) You have to flash the stock recovery version that match your current version. If you can post the output of fastboot getvar all (minus imei and serialno) we could help you find the recovery you need.
and btw, no need to relock bootloader like said above. Better to leave it unlocked so you'll not have to unlock it again and wipe /data/preload again
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
@alray I tried the update after flashing the stock recovery and relock the bootloader, and as you mentioned it shows the exclamation red mark... I will past the info getvar soon, big thanks
AmineOne said:
@alray I tried the update after flashing the stock recovery and relock the bootloader, and as you mentioned it shows the exclamation red mark... I will past the info getvar soon, big thanks
Click to expand...
Click to collapse
relocking bootloader was not required, better to re-unlock it now, or you'll have the same problem with the next ota.
try to reapply the update. when the phone boot in stock recovery and start to flash the ota, press and hold vol+ then power and release both. You'll see some command lines and you'll be able to know which file is causing the ota to abort.
look for something like: unexpected content or no such file or directory)
also post the getvar all
Hello again
This is the getvar :
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
@alray
I applied what you told me, (apply the update and look after errors)
her are what i get after that :
Finding update package...
Opening update package...
Verifing update package...
Installing update...
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "ORANG309") == "t"
Installation aborted.
I:Write host_mode:0 done
Is any body out there ?
Where did you get the update?
SaHiLzZ said:
Where did you get the update?
Click to expand...
Click to collapse
Download from Setting>Update
No more help
AmineOne said:
No more help
Click to expand...
Click to collapse
you can't manually install an OTA if you are S-ON, you need to "download and install" on the phone directly.
nkk71 said:
you can't manually install an OTA if you are S-ON, you need to "download and install" on the phone directly.
Click to expand...
Click to collapse
I do so ! as i told befor i download using automatic update on setting (with my phone)
AmineOne said:
I do so ! as i told befor i download using automatic update on setting (with my phone)
Click to expand...
Click to collapse
hmm, in that case I don't have any ideas.
some users say they had to relock bootloader, though i don't think that's necessary, as the US Dev Edition comes bootloader unlocked by default, and still receives OTAs just fine.
I guess you could try that.
AmineOne said:
Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Click to expand...
Click to collapse
The easy way is to use a RUU to get you phone back to Stock
then download and flash the update.
the more complicated way is to restore stock recovery and the missing files from unlocking the bootloader and then download the update.
Depending on your phones CID / MID some are able to just flash a Guru Reset and choose to install the stock recovery and say no to root and then take the OTA update.
As you already have TWRP why not just install the Stock unrooted 6.xx.xxx.x Rom ? >> http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
@nkk71
Thank you any way
Yes as alray told befor it's not necessary to lock the bootloader, my probleme I think is bigger cuz my version is Orange Spanish
Hope some one will help me soon
AmineOne said:
@nkk71
Thank you any way
Yes as alray told befor it's not necessary to lock the bootloader, my probleme I think is bigger cuz my version is Orange Spanish
Hope some one will help me soon
Click to expand...
Click to collapse
well, you could always go s-off and make things easier on yourself, but a question, what stock recovery are you using and where did you get it?
nkk71 said:
well, you could always go s-off and make things easier on yourself, but a question, what stock recovery are you using and where did you get it?
Click to expand...
Click to collapse
This one : Stock M7 GPE Recovery (i got it frome another web site i don't know if it's permitted to put external links in the Forum ?! )
AmineOne said:
This one : Stock M7 GPE Recovery (i got it frome another web site i don't know if it's permitted to put external links in the Forum ?! )
Click to expand...
Click to collapse
okay, that will not work, a GPE recovery, you need one for your phone. the easiest would be to extract it from the OTA
nkk71 said:
okay, that will not work, a GPE recovery, you need one for your phone. the easiest would be to extract it from the OTA
Click to expand...
Click to collapse
And how can i do that ? (i'm still novice don't know much)
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
hey xda,
trying to restore my M7 to stock for a warranty repair, but the link to download the Bell nandroid backup of the phone is down. it was HTC1guru but apparently it went down and came back as androidRUU, however all the backups are there except the one I need (but of course, right?). Could anyone please point me to the file I need? Nandroid or RUU is fine.
bbmaster123 said:
hey xda,
trying to restore my M7 to stock for a warranty repair, but the link to download the Bell nandroid backup of the phone is down. it was HTC1guru but apparently it went down and came back as androidRUU, however all the backups are there except the one I need (but of course, right?). Could anyone please point me to the file I need? Nandroid or RUU is fine.
Click to expand...
Click to collapse
We can't help you find the file you need if we don't know your phone details. Post the output of "fastboot getvar all" (remove imei and serialno before posting)
alray said:
We can't help you find the file you need if we don't know your phone details. Post the output of "fastboot getvar all" (remove imei and serialno before posting)
Click to expand...
Click to collapse
I didn't think the rest of the details mattered, but since you asked, here are the details. Original CID was BM__001 before I changed it to superCID
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3966mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
bbmaster123 said:
I didn't think the rest of the details mattered, but since you asked, here are the details. Original CID was BM__001 before I changed it to superCID
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) security: off
Click to expand...
Click to collapse
There is no RUU for Bell (x.xx.666.x), Only a 3.23.666.1 nandroid backup is available which is useless in your situation. After restoring that nandroid backup, your firmware will still be that leaked 7.15.401.1 version and will not match the 3.23.666.1 software version which will void the warranty. You'll also need to set your bootloader back to "LOCKED" and remove your "TAMPERED" flag which should be done on hboot 1.44 or 1.54 like explained in nkk71's guide.
alray said:
There is no RUU for Bell (x.xx.666.x), Only a 3.23.666.1 nandroid backup is available which is useless in your situation. After restoring that nandroid backup, your firmware will still be that leaked 7.15.401.1 version and will not match the 3.23.666.1 software version which will void the warranty. You'll also need to set your bootloader back to "LOCKED" and remove your "TAMPERED" flag which should be done on hboot 1.44 or 1.54 like explained in nkk71's guide.
Click to expand...
Click to collapse
thats fine, I can reflash my firmware. I know how to do all of this, I just need the file, but as I said, since the htc1guru server is down, I can't find it.
bbmaster123 said:
thats fine, I can reflash my firmware. I know how to do all of this, I just need the file, but as I said, since the htc1guru server is down, I can't find it.
Click to expand...
Click to collapse
But there is no 3.23.666.1 firmware uploaded anywhere, only a Nandroid backup (which does NOT include the firmware, only the software) so how will you reflash the stock 3.23.666.1 firmware over you 7.15.401.1 firmware?
For the nandroid backup, you'll have to wait for htc1guru.com to be back online.
alray said:
But there is no 3.23.666.1 firmware uploaded anywhere, only a Nandroid backup (which does NOT include the firmware, only the software) so how will you reflash the stock 3.23.666.1 firmware over you 7.15.401.1 firmware?
For the nandroid backup, you'll have to wait for htc1guru.com to be back online.
Click to expand...
Click to collapse
huh, I think I found a TWRP backup of the stock OS. Downloading now. Will check if it includes the firmware. its strange, it din't show up in a google search of of the ruu, but came up when I searched for 3.23.666.1. I will post the link if its the right file
bbmaster123 said:
huh, I think I found a TWRP backup of the stock OS. Downloading now. Will check if it includes the firmware. its strange, it din't show up in a google search of of the ruu, but came up when I searched for 3.23.666.1. I will post the link if its the right file
Click to expand...
Click to collapse
TWRP backups never includes the firmware. Only include /data partition (user data), /system partition (software aka Operating System) and /boot partition (kernel).
alray said:
TWRP backups never includes the firmware. Only include /data partition (user data), /system partition (software aka Operating System) and /boot partition (kernel).
Click to expand...
Click to collapse
yea, your right. now the hunt has changed from nandroid backup to firmware. I will scour and report my findings.
bbmaster123 said:
yea, your right. now the hunt has changed from nandroid backup to firmware. I will scour and report my findings.
Click to expand...
Click to collapse
so you'll need to find at least a firmware.zip and a nandroid backup of the same version, restoring the backup using the appropriate recovery and flashing the firmware.zip with fastboot with the phone booted in ruu mode. Don't ever think about using a firmware.zip from an ota update or you will brick your phone. Good luck.
alray said:
so you'll need to find at least a firmware.zip and a nandroid backup of the same version, restoring the backup using the appropriate recovery and flashing the firmware.zip with fastboot with the phone booted in ruu mode. Don't ever think about using a firmware.zip from an ota update or you will brick your phone. Good luck.
Click to expand...
Click to collapse
I believe I found it, but I want to be sure. Why would an OTA version of the firmware brick the phone? heres the link for the file I found
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/666/3.23.666.1.zip
bbmaster123 said:
I believe I found it, but I want to be sure. Why would an OTA version of the firmware brick the phone? heres the link for the file I found
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/666/3.23.666.1.zip
Click to expand...
Click to collapse
Im not sure if that is OTA or Full firmware, im not too upto speed with firmware packages, but to answer your question, OTA firmware just upgrades the original firmware on your device, so its not a complete firmware package (which is what you need), and as you dont have the original firmware, it would just brick.
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.
Seanie280672 said:
Im not sure if that is OTA or Full firmware, im not too upto speed with firmware packages, but to answer your question, OTA firmware just upgrades the original firmware on your device, so its not a complete firmware package (which is what you need), and as you dont have the original firmware, it would just brick.
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.
Click to expand...
Click to collapse
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader. I should probably make a new thread with instructions to return to stock bell and host post the nandroid and firmware. thanks for your help! now that I'm thinking about it, I should go back to all my previous threads and hit the thanks button for everyone who helped me!
bbmaster123 said:
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader. I should probably make a new thread with instructions to return to stock bell and host post the nandroid and firmware. thanks for your help! now that I'm thinking about it, I should go back to all my previous threads and hit the thanks button for everyone who helped me!
Click to expand...
Click to collapse
you need to go locked and s-on before the OTA's, if you go s-on after HBOOT 1.54 the tampered flag will come back and you'll have to get s-off again and start all over.
Have a look at post 2 by @alray he has a link in his signature by nkk71 of how to return to 100% stock which contains all the instructions
Seanie280672 said:
Could you not get away with using dev edition RUU and sending it back like that, dev edition devices come s-off and unlocked, the tampered flag is easy to remove, if they question it, deny any knowlege.
Click to expand...
Click to collapse
Afaik they come unlocked but not s-off. Anyway converting it to full dev edition might be the best solution at this point. Customer support often repair modded phones depending what is broken. For the purple camera for example, some users got their phone repaired under warranty even if the phone was not stock.
bbmaster123 said:
thats a good idea, but I got impatient and just flashed everything. turns out it works fine. now ill just run the stock ota updates from the settings menu and s-on and lock the bootloader.
Click to expand...
Click to collapse
You can't !
Your firmware is 7.15.401.1, To use ota update firmware must match the software version. The ota need to patch the 3.23.666.1 firmware not the 7.15.401.1 firmware.
unless you have flashed the 3.23.666.1 firmware then you should be fine. You must make sure that firmware file is the FULL firmware and not a firmware extracted from an ota update before flashing.
alray said:
Afaik they come unlocked but not s-off. Anyway converting it to full dev edition might be the best solution at this point. Customer support often repair modded phones depending what is broken. For the purple camera for example, some users got their phone repaired under warranty even if the phone was not stock.
You can't !
Your firmware is 7.15.401.1, To use ota update firmware must match the software version. The ota need to patch the 3.23.666.1 firmware not the 7.15.401.1 firmware.
unless you have flashed the 3.23.666.1 firmware then you should be fine. You must make sure that firmware file is the FULL firmware and not a firmware extracted from an ota update before flashing.
Click to expand...
Click to collapse
I already flashed the 3.23.666.1 firmware, and it worked. I already went through the first round of the update process, now its downloading the OTA for kitkat. still s-off right now. bootloader is still unlocked too.
bbmaster123 said:
I already flashed the 3.23.666.1 firmware, and it worked. I already went through the first round of the update process, now its downloading the OTA for kitkat. still s-off right now. bootloader is still unlocked too.
Click to expand...
Click to collapse
I'm looking forward to your post with all the links and instructions ... good job
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(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: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(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: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too
scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
deleted
Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk