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
Related
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Torcidas1950 said:
PLEASE RESPOND
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
Click to expand...
Click to collapse
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery. And how do I do that?
Torcidas1950 said:
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery.
Click to expand...
Click to collapse
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
And how do I do that?
Click to expand...
Click to collapse
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
iElvis said:
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
Click to expand...
Click to collapse
alray said:
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Click to expand...
Click to collapse
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Torcidas1950 said:
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
post your "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(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: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Torcidas1950 said:
Here it is:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
nkk71 said:
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
Click to expand...
Click to collapse
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
1- If you are 100% stock then Settings -> About should also show your correct version number
2- you rooted the phone, so that may or may not have changed some system files, so OTA may not work
3- once S-Off stay S-Off, my personal opinion
In my humble opinion, three choices really, when it comes to "modding" or not your phone:
A) stay stock and don't mess with it to get OTAs
B) you cannot achieve S-OFF (due to newer hboots, or device problems) -> fine live with an unlocked bootloader, and accept the fact that you cannot install OTAs .... you can however "download and install later" the OTA, then pull it to your phone, and use the signed firmware.zip in it
C) you can achieve S-OFF and want to mod your phone -> then do it, get S-Off and enjoy the freedom (but don't flash things not meant for your phone!! this goes for S-On too)
Of course you're going to say that "but S-Off is dangerous", it's a double edged sword... sometimes you are able save your phone thanks to S-Off, and sometimes you can brick it completely.
But then again, you can easily brick an S-On phone too (especially one that is modded), and much more difficult to save than an S-Off phone.
^^ All that is my personal opinion, and I'm not suggesting you S-Off, but if you want to mod your phone (whether S-On or S-Off), you need to be aware of what may, or may not, go wrong, and have done some reading and research
Good Luck
Well, its not worth it. I wont risk bricking my phone again
Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
Torcidas1950 said:
Well, its not worth it. I wont risk bricking my phone again
Click to expand...
Click to collapse
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
nkk71 said:
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
Click to expand...
Click to collapse
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Torcidas1950 said:
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Click to expand...
Click to collapse
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
nkk71 said:
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
Click to expand...
Click to collapse
Well, I am not planing to unplug the cable haha.. well if someone else knows please tell, the update is coming soon so I would like to know, but if its risky, there is no way I'm doing it
Torcidas1950 said:
but if its risky, there is no way I'm doing it
Click to expand...
Click to collapse
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
nkk71 said:
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
Click to expand...
Click to collapse
So, yesterday the OTA was finally released, and today I have flashed stock recovery... Now waiting for the OTA notification to come
Sent from my HTC One using XDA Free mobile app
hello guys,
i did a deep search, but nothing found about it, or found but did not understood, so i will ask you. if in my stock recovery it also says (TAMPER), will be possibly to instal OTA?
L.E. - rest is like the title of the topic - Unlocked, S-ON, tampered..
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.
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
Some info about the phone:
S-ON
TWRP ver 2.6
rooted
can access recovery
don't need anything on the phone
I'm looking for a solution to get this phone going again.. any solution. I'd prefer to be on stock ROM. I'd love some help on this. I'm here.
post your fastboot getvar all please
2dayquestion said:
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
don't need anything on the phone
Click to expand...
Click to collapse
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
alray said:
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
Click to expand...
Click to collapse
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
post the ouput of fastboot getvar all
Seanie280672 said:
post your fastboot getvar all please
Click to expand...
Click to collapse
(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: 1.00.000.0
(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: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(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
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
yatindroid said:
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
Click to expand...
Click to collapse
The factory reset isn't working. It still hangs. I did the initial backup through TWRP. Will Titanium backup be compatible with that backup?
Now the phone is currently locked, no OS.Should I flash another ROM?
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The OS is set to 1.000.000. I used some **** utility that reset it. I started clicking things... lol
One thing I'm wondering is since this phone is S-ON, will I be able to even flash a ROM? Could that be the reason that the TWRP restore function isn't working? As far as I know... SON would prevent system files from being written.. correct me if I'm wrong
..downloading that file as I write this
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
2dayquestion said:
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
Click to expand...
Click to collapse
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Seanie280672 said:
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Click to expand...
Click to collapse
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
2dayquestion said:
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
Click to expand...
Click to collapse
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Seanie280672 said:
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Click to expand...
Click to collapse
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
2dayquestion said:
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
Click to expand...
Click to collapse
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Seanie280672 said:
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Click to expand...
Click to collapse
That may have been the issue. Thanks for your time. Another 'thanks' is in order. Cheers
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
majmoz said:
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
Click to expand...
Click to collapse
Seanie280672 said:
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
Click to expand...
Click to collapse
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
snebojsa said:
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
Click to expand...
Click to collapse
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Seanie280672 said:
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
snebojsa said:
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
Click to expand...
Click to collapse
I can tell by your cid, mid and hboot version
Seanie280672 said:
I can tell by your cid, mid and hboot version
Click to expand...
Click to collapse
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
snebojsa said:
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
Click to expand...
Click to collapse
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Seanie280672 said:
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Click to expand...
Click to collapse
Yes, I see it, thanks for informations :good:
Same issue and confused (more than usual)
My version main is empty as well and I can't figure it out.
build.prop/ro.aa.romver=1.54.401.5
Downloads\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 12312313123
(bootloader) imei: 12345613456123
(bootloader) meid: 123456123456
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
UNLOCKED
M7_WLS PVT HIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO -1.01.20.0512
OpenDSP -v32-120.284.0909
OS-
Currently running ViperOne 6.2.1. Tried 7.0 last night but things were a bit funky and didn't have enough time to sort 'em all out. Thought firmware might be an issue, and it seems a bigger issue than I originally thought.
Any and all help appreciated
Version-main empty is TWRP issue, you have to re-flash firmware and flash fixed twrp version. I moved from M7 to M8 so I forgot where to find those files, you have to search it.
On M8 I had the same problem, flashing firmware and fixed twrp solved it. Also, when tried latest Viper rom I was on old firmware and had some odd issues, but since flashed new firmware everything is fine.
Hope I helped you.
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
toad6386 said:
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
clsA said:
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
Click to expand...
Click to collapse
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
toad6386 said:
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
Click to expand...
Click to collapse
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
clsA said:
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
Click to expand...
Click to collapse
Hey, no worries. You've helped. I didn't make it clear I Sprint. I'm more used to the 3VO forum where there wasn't hardly anything BUT Sprint. I suppose that's what confuses me about this one, with all the variants. Thanks again! :thumbup:
Sent from my HTCONE using XDA Free mobile app
Hi guys.
I really trust xda forums and that's why I come here whenever I need help. You always save the day guys and I want to thank you for that.
So a while ago I've unlocked the boot loader, flashed cwm recovery via fast boot and rooted my device. I'm still on a stock Rom though.
Now I want to upgrade to lollipop manually, my plan is to download the official Rom from HTC's website connect my device to the pc with a usb cable then install it on my phone.. From what I understand I should flash back the stock recovery then relock the boot loader and restore the contents of a folder (i don't remember what folder though). Where can I find the stock Rom img file I should flash? (And the folder contents that i'm supposed to restore) also if I relock the boot loader will the upgrade proceed if it still shows "tampered"?
Please guys help what am I supposed to do before upgrading??
monrokhoury said:
Hi guys.
I really trust xda forums and that's why I come here whenever I need help. You ashtrays save the day guys and I want to thank you for that.
So a while ago I've unlocked the boot loader, flashed cwm recovery via fast boot and rooted my device. I'm still on a stock Rom though.
Now I want to upgrade to lollipop manually, my plan is to download the official Rom from HTC's website connect my device to the pc with a usb cable then install it on my phone.. From what I understand I should flash back the stock recovery then relock the boot loader and restore the contents of a folder (i don't remember what folder though). Where can I find the stock Rom img file I should flash? (And the folder contents that i'm supposed to restore) also if I relock the boot loader will the upgrade proceed if it still shows "tampered"?
Please guys help what am I supposed to do before upgrading??
Click to expand...
Click to collapse
You need to restore the preload data. This gets wiped when you unlock the bootloader and it will cause the OTA to fail. Relocking isn't necessary for installing ota's you just need Stock Rom and Recovery. A GuruReset is usually the way to go.
If your talking about flashing the RUU then you will need to relock the bootloader if your s-on but that's it. Missing preload data, rooted rom's and custom recovery will not effect the RUU install. It will just flash stock over the top of it all. Your phone will be wiped though so backup any data you want to keep. :good:
If you need more help finding the correct software post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting
Danny201281 said:
You need to restore the preload data. This gets wiped when you unlock the bootloader and it will cause the OTA to fail. Relocking isn't necessary for installing ota's you just need Stock Rom and Recovery. A GuruReset is usually the way to go.
If your talking about flashing the RUU then you will need to relock the bootloader if your s-on but that's it. Missing preload data, rooted rom's and custom recovery will not effect the RUU install. It will just flash stock over the top of it all. Your phone will be wiped though so backup any data you want to keep. :good:
If you need more help finding the correct software post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting
Click to expand...
Click to collapse
done, here's what that returned:
D:\Program Files\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.111
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode:y SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
thanks for helping me find the software. I need to know how to restore the preloade data. I know how to flash the stock recovery but I don't have it. I gotta admit btw that I don't know what ruu is.
monrokhoury said:
done, here's what that returned:
D:\Program Files\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.111
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode:y SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
thanks for helping me find the software. I need to know how to restore the preloade data. I know how to flash the stock recovery but I don't have it. I gotta admit btw that I don't know what ruu is.
Click to expand...
Click to collapse
Ok thanks you don't need to worry about an RUU because there isn't one for your Device.
Do you know how to use a nandroid backup? There is a Stock TWRP nandroid and the recovery you need in this thread here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good: you can use this to restore your Device back so you can get OTA updates
Danny201281 said:
Ok thanks you don't need to worry about an RUU because there isn't one for your Device.
Do you know how to use a nandroid backup? There is a Stock TWRP nandroid and the recovery you need in this thread here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good: you can use this to restore your Device back so you can get OTA updates
Click to expand...
Click to collapse
I have cwm recovery on my phone, can I use it to flash the nanodroid backup? or do I have to flash twrp recovery?
and after flashing the nanodroid backup I just have to flash the stock recovery and then upgrade?
which one is the nanodroid backup I need to flash? is it this one:
" TWRP Backup: https://yadi.sk/d/rQzZ9i0CdmstQ "
or this:
"6.09.401.111 Firmware with Hboot 1.57.000 https://yadi.sk/d/n7BAQ8vpdqPSS "
??
and do I need to worry about the radio file in your link?
thanxx for your help man!
Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man
monrokhoury said:
Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man
Click to expand...
Click to collapse
If you can find a download for just the preload data then yes that would be easier. I'll see if I can find something.
Otherwise you want the TWRP backup from that thread and you will need to flash TWRP recovery to restore it. And just to clarify you can't flash the nandroid backup like a normal Rom. You will need to unzip it and copy the folder in to your TWRP backups folder then use the restore option in twrp
The radio file is not such a big issue it will be the same radio you already have anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
monrokhoury said:
Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man
Click to expand...
Click to collapse
Preload data this is the closest I can find. It may or may not work so try at your own risk.
http://goo.gl/XvLuE0
This is the preload data from 6.09.401.12 which is the lte version of your Device. The preload data may well be the same as the only difference is that 1 device has lte enabled and the other (your Device does not) :good:
Danny201281 said:
If you can find a download for just the preload data then yes that would be easier. I'll see if I can find something.
Otherwise you want the TWRP backup from that thread and you will need to flash TWRP recovery to restore it. And just to clarify you can't flash the nandroid backup like a normal Rom. You will need to unzip it and copy the folder in to your TWRP backups folder then use the restore option in twrp
The radio file is not such a big issue it will be the same radio you already have anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Preload data this is the closest I can find. It may or may not work so try at your own risk.
http://goo.gl/XvLuE0
This is the preload data from 6.09.401.12 which is the lte version of your Device. The preload data may well be the same as the only difference is that 1 device has lte enabled and the other (your Device does not) :good:
Click to expand...
Click to collapse
Man, you're the best
monrokhoury said:
Man, you're the best
Click to expand...
Click to collapse
There is no data / preload folder in the backup either, are you sure you need it for this particular device ?
you can download the TWRP backup and extract it then open each individual file, like the system file with winrar, like ive done, this is the system folder from the backup, (see pict below)
Seanie280672 said:
There is no data / preload folder in the backup either, are you sure you need it for this particular device ?
you can download the TWRP backup and extract it then open each individual file, like the system file with winrar, like ive done, this is the system folder from the backup, (see pict below)
Click to expand...
Click to collapse
so this backup won't allow me to restore the preload contents? is there anyway to restore it? or should I forget about ota updates?
monrokhoury said:
so this backup won't allow me to restore the preload contents? is there anyway to restore it? or should I forget about ota updates?
Click to expand...
Click to collapse
no this backup doesnt appear to contain the data/preload contents, but thats why I said have you tried to update ?, is the update available to you yet ? maybe the M7_U is different to the UL and doesnt require this folder, or you could try as Danny stated earlier and use the UL ones he linked you too. :good:
Seanie280672 said:
no this backup doesnt appear to contain the data/preload contents, but thats why I said have you tried to update ?, is the update available to you yet ? maybe the M7_U is different to the UL and doesnt require this folder, or you could try as Danny stated earlier and use the UL ones he linked you too. :good:
Click to expand...
Click to collapse
I want to update manually by downloading the update file from HTC's website and then following these instructions to upgrade:
Performing the ROM Update:
1. Download and save the HTC One™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
I found them here.
Danny said that manually restoring the contents might not work.. if I restore them and then try upgrading can it brick the phone? and how can I restore them anyway?
thaaaanx
monrokhoury said:
I want to update manually by downloading the update file from HTC's website and then following these instructions to upgrade:
Danny said that manually restoring the contents might not work.. if I restore them and then try upgrading can it brick the phone? and how can I restore them anyway?
thaaaanx
Click to expand...
Click to collapse
Not too sure about restoring the contents manually, I have done it myself before, but on a different HTC One SV a couple of years ago in order to update, but I did have a hell of a game doing it, even came down to creating the data and preload folders in system on my phone myself andf setting the correct premissions and then placing each file in there manually, I really wouldnt like to say if it would work for your device or not.
On a different note, which update files have you found, could you supply a link please, and I thought you had to be s-off to manually update regardless ?
Seanie280672 said:
Not too sure about restoring the contents manually, I have done it myself before, but on a different HTC One SV a couple of years ago in order to update, but I did have a hell of a game doing it, even came down to creating the data and preload folders in system on my phone myself andf setting the correct premissions and then placing each file in there manually, I really wouldnt like to say if it would work for your device or not.
On a different note, which update files have you found, could you supply a link please, and I thought you had to be s-off to manually update regardless ?
Click to expand...
Click to collapse
no you don't need to s-off cause you'll be updating using HTC sync manager.
here's a link:
http://www.htc.com/us/support/rom-downloads.html
let's say I'm considering flashing maximushd Rom, I have flashed twrp recovery 2.8.4.0, now I just have to do a full wipe using it and then flash the Rom?
monrokhoury said:
no you don't need to s-off cause you'll be updating using HTC sync manager.
here's a link:
http://www.htc.com/us/support/rom-downloads.html
let's say I'm considering flashing maximushd Rom, I have flashed twrp recovery 2.8.4.0, now I just have to do a full wipe using it and then flash the Rom?
Click to expand...
Click to collapse
There is no lollipop update on that page for your phone, only the dev edition M7, but yes to MHD Rom, and if you get s-off you can flash the matching firmware too.
Seanie280672 said:
There is no lollipop update on that page for your phone, only the dev edition M7, but yes to MHD Rom, and if you get s-off you can flash the matching firmware too.
Click to expand...
Click to collapse
" Unlocked/Developer
Device Name Latest ROM # Details and Instructions Link
HTC One (M8) 4.16.1540.8
View
Download
HTC One 7.17.1540.7
View
Download
HTC One max 3.23.1540.1 N/A
Download"
mine is an unlocked m7.
is switching s-off and flashing the firmware a must? bc some members told me that they just flashed the Rom using twrp recovery and everything went fine.. do you confirm?
monrokhoury said:
" Unlocked/Developer
Device Name Latest ROM # Details and Instructions Link
HTC One (M8) 4.16.1540.8
View
Download
HTC One 7.17.1540.7
View
Download
HTC One max 3.23.1540.1 N/A
Download"
mine is an unlocked m7.
is switching s-off and flashing the firmware a must? bc some members told me that they just flashed the Rom using twrp recovery and everything went fine.. do you confirm?
Click to expand...
Click to collapse
No flashing the firmware isn't required, although it's recommended, you should be ok just to flash the Rom, it's just the same as flashing a custom Rom.
As for unlocked its a different type of unlocked, confusing I know, yours is just network unlocked, that ruu / ota is dev edition, unlocked bootloader and s-off unlocked from the factory, have a look at the version number, the 3rd set of digits is what matters, that's 1540 dev, your output on page 1 states 401 international edition.
Seanie280672 said:
No flashing the firmware isn't required, although it's recommended, you should be ok just to flash the Rom, it's just the same as flashing a custom Rom.
As for unlocked its a different type of unlocked, confusing I know, yours is just network unlocked, that ruu / ota is dev edition, unlocked bootloader and s-off unlocked from the factory, have a look at the version number, the 3rd set of digits is what matters, that's 1540 dev, your output on page 1 states 401 international edition.
Click to expand...
Click to collapse
thanks for explaining that man you're amazing you saved me a lot of time.. I guess I'll download and flash mhd though I gotta ask, why is flashing the firmware recommended?
and is mhd a good Rom in your opinion?
Anyway I made a full nanodroid backup using twrp so that I can roll back if I don't like the results.. that'll work right?
thaaaaanx again
monrokhoury said:
thanks for explaining that man you're amazing you saved me a lot of time.. I guess I'll download and flash mhd though I gotta ask, why is flashing the firmware recommended?
and is mhd a good Rom in your opinion?
Anyway I made a full nanodroid backup using twrp so that I can roll back if I don't like the results.. that'll work right?
thaaaaanx again
Click to expand...
Click to collapse
Nandroid is always recommended and a good idea, I use mhd myself, they are all very much the same at the moment to be honest, the differences between them are very minimal, and matching firmware to the Rom version is always recommended to save a potential problems.
---------- Post added at 09:35 AM ---------- Previous post was at 09:26 AM ----------
Just to add, when the official SIGNED - (that's important) 401 firmware comes out and is available you will be able to flash that, at the moment it's unsigned and will brick your phone. You'll just need to relock your boot loader first as your s-on, then flash it like any other firmware, then re-unlock your bootloader and reflash a custom recovery.
Seanie280672 said:
Nandroid is always recommended and a good idea, I use mhd myself, they are all very much the same at the moment to be honest, the differences between them are very minimal, and matching firmware to the Rom version is always recommended to save a potential problems.
---------- Post added at 09:35 AM ---------- Previous post was at 09:26 AM ----------
Just to add, when the official SIGNED - (that's important) 401 firmware comes out and is available you will be able to flash that, at the moment it's unsigned and will brick your phone. You'll just need to relock your boot loader first as your s-on, then flash it like any other firmware, then re-unlock your bootloader and reflash a custom recovery.
Click to expand...
Click to collapse
I hear you, abd I won't need to restore the preload contents that got quoted when I unlocked the boot loader?