Related
OK, so I got a HTC One yesterday. Checking the development status here I decided not to bother with stock a single day and went straight ahead to prepare it for custom ROMs. While I was at it I decided to go for S-OFF as well so i would be able to flash radios in the future.
I think something went wrong, the status is: phone boots into (stock) system allright, but it will not establish a WiFi connection at all (it worked prior to S-OFFing), when I move the slider from disable to enable it says "Turning on..." and is grayed out but it is stuck there for infinity. Switching Bluetooth on and off works, but due to this glitch I fear that somehow my radio partition got corrupted (if I recall that is usually where S-OFF flags etc are stored).
Here is exactly how I proceeded: I got the revone command line tool and moonshine tool in the newest versions.
First I used revone according to the steps outlined on XDA, which worked and displayed an S-OFF in the bootloader header. To my understanding this only gave me S-OFF, so then I proceded with moonshine to install unsecure bootloader, superuser.apk and su. This tool also ran through as described without a glitch and rebooted me into the bootloader showing the custom moonshine S-OFF header. I then used the One-in-all-tool to install a custom recovery (TWRP in this case). This also worked great.
Then I was getting ready to put on a custom ROM and tried to hook the device to my PC via USB as a mass storage to copy over the custom ROMs I downloaded. At first boot HTC Tell jumped up and claimed it "fixed something because it noticed it was not as expected". I fgured this was to be expected, with the device S-OFFed and stock ROM still on it but gave it no 2nd thought. I checked and S-OFF stuck even through this.
Copying the ROMs as planned would not work, I can browse the /mnt/sdcard contents and also read files from there, but no matter how and when I try to write anything it fails with an error (device is disconnected or not ready). I then tried to sideload a filemanager with SMB client feature so I could transfer the ROMs through my local WiFi but then I noticed the glitch with the WiFi which could not be resolved even with reboots and clearing cache/dalvik cache throuch recovery.
What is my best bet now? Try to rollback the moonshine S-OFF and reinstall the original bootloader which was backed up? Just install a custom ROMs and assume all is good and it will straighten itself out? Flash the original RUU stock ROM, therefore prolly going back to stock and re-doing the entire S-OFF process? Any ideas on how to further diagnose what (if anything) is wrong? Is it all possible to roll back to a completely stock base by flashing the RUU through TWRP?
You didn't need to use Moonshine, you could've just flashed CWM/TWRP and flashed the SuperSU package to get root access. As you're S-OFF I would flash an RUU to get back to a stock state (you'll keep S-OFF) and then try to re-root using the normal methods.
What software build are you on at the moment?
Thank you for your quick reply.
FYI, I am on PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed. That was ther software / radio version installed when it came out of the box.
However, as per advice from the guys in moonshine IRC channel I have re-flashed the boot.backup-img moonshine created when it ran and the problem with WiFi seems to be gone. I will play around a bit more, but it could be the issue is resolved (although I fail to understand eactly why).
Sounds like the custom HBOOT could be the issue
Yes, I have just now understood how HBOOT and the bootloader / boot.img are two separate things.
I think my reasoning for using both tools was kind of: "well, instructions for moonshine say it needs a HTCDEV unlocked device to run, and then will install su / superuser.apk in one swoop, yet revone will S-OFF / unlock my phone without hopping through the HTCDEV hoops, so hell, I will just use revone to S-OFF / unlock and then moonshine to S-OFF again and get su / superuser.apk conveniently..." The facepalm in this might be obvious to the hardcore / experienced coders / developers here but it made sense for my layman brain (at least at that late time of night...).
The question at hand is resolved though, the device behaves just fine as of now.
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Walter_White said:
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Click to expand...
Click to collapse
Not all of that stuff can be flashed in recovery. Some partitions like hboot have to be flashed in rebootRUU mode. You can return to stock that way, but running a RUU is simpler and usually safer (provided you have the right RUU).
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
WARNING: i'm the second owner of the phone. For warranty I would have had to send the phone to HTC. I suspect the HTC warranty won't apply to me anyhow. I suggest that in this situation, people just get the phone fixed on warranty if they have that option
First Steps:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ? (SEE UPDATE BELOW)
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ? (SEE UPDATE BELOW)
Thanks in advance !
same issue
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
LRail said:
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
So far:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ?
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ?
Q3) If I eventually decide to install the Developer Edition firmware.. will the phone be effectively be a Dev phone ? (OTA updates... factory recovery/locked bootloader... no ID issues in the future..)
Thanks in advance !
P.S. For pure curiousity.... Am I correct in believing that revone can't clear the "tamper" flag and lock the bootloader with the custom recovery ?
Click to expand...
Click to collapse
double post
omgkush said:
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
Click to expand...
Click to collapse
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
LRail said:
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Click to expand...
Click to collapse
Tampered will come back the second you flash a recovery. Best to stay S-OFF
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
ysl00 said:
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
Click to expand...
Click to collapse
Thanks for the heads up. If I get a bunch of free time I may just test that after doing a new full backup.
Not sure about the Rogers 4.3 OTA.
I'm running currently the phone with Developer Edition ROM+CID and can confirm that it's 4.3 OTA updates hboot to 1.55.
After the update my phone is still s-off.
I have previously rolled back to an older hboot via a firmware flash.
Since the phone is still S-OFF, I assume I can do that again if needed.
EddyOS said:
Tampered will come back the second you flash a recovery. Best to stay S-OFF
Click to expand...
Click to collapse
Thanks For the reply Eddy.
Recovery flashing sets the tampered flag even if it's a factory recovery from an OTA being flashed ?
I agree on the S-OFF normally.
This was a test to see if I could get it back to full stock for warranty if needed, and S-OFF would not be acceptable in that case.
please help!
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
millarrjm said:
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
Click to expand...
Click to collapse
Esposition said:
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
Click to expand...
Click to collapse
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
re.
LRail said:
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I tried that. CWM version 6.+ doesn't save to the backup folder anymore. And won't read a restore I put in it either... Ie. The rogers off the bugzylawson site.
bklam said:
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
Click to expand...
Click to collapse
Hello bklam,
Sorry, I missed your question.
No. I used CWM only to restore the "Whampahoofus"' nandroid backup.
That backup is "almost" 100% stock. Unfortunately it contains a custom recovery and won't (in my experience) work for normal OTA updates.
To solve this I decided to extract the factory firmware from one of the old Rogers OTA ("unrar" will extact the files from the OTA), and flash that.
To flash it I used the quick instructions in the 1st post of this thread-->http://forum.xda-developers.com/showthread.php?t=2182823
(I believe there were more details instructions on firmware.zip flashing in another thread but I can't find it at the moment)
Note to other readers: There can be confusion about the word "firmware". Some people use it describe the Rom.
In this case, I'm referring to the hboot, boot and recovery images in a single special file called firmware.zip. I believe in some cases it can also include the radio software too.
If I ever get a chance to get this 100% tested and figured out, I'll post a step by step method.
At this point it's just a overview of what I tried, and looking for other members advice.
Unfortunately, as you can see from my posts, it didn't work 100% for me. It gave me the stock Rogers HTC One Rom/software with OTA updates, but the bootloader still had the tampered flag.
Check out ysl00's post above. He/She evidently had it working 100% without the tamper flag.
Not sure if Rogers has a 4.3 OTA yet, but that might fix the flag since it includes a firmware update along with the OS update.
Post back with your results !
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
figured it out.
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
millarrjm said:
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
Click to expand...
Click to collapse
Sorry about that. No I didn't see it until just now. I guess thats the problem with having 20 browser tabs open at once. hehe
millarrjm said:
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
Click to expand...
Click to collapse
Good to hear. I read your post. I thought..."Is he using a root file manager ?" then read your next post….
I was also going to suggest a guaranteed way to determine where the CWM backups are being stored on a phone.
This way it doesn't matter which version of CWM, which phone or if the back directory exists yet.
Simply create a test backup and see where it goes. Then copy the Nandroid backup that you want to restore, there.
I should mention that I'm currently running my phone as a Developer Edition (Brightstar) 4.3 with OTAs, S-OFF, and unlocked.
It's works perfectly. Only the Carrier ID (CID) needed to be changed. The MID is the same.
I assume that a brightstar RUU will work on it now, even if the phone was locked and S-ON.
I have a few more things I want to tweak on it, then I'll likely make a backup and try restore it to stock rogers again so that I can create a clear how-to.
What's interesting, is that the Developer Edition OS seems to be the same as the Rogers Edition OS (without the rogers apps which can be uninstalled).
The only reason I think it might be a better choice is that the Dev Edition should get OTA updates earlier than the Rogers Edition.
I tried the custom Viper Rom 2.6.x but couldn't get an LTE connection. I suspect that was due to APN settings, but I didn't confirm that.
Anyone got the Viper Rom fully working on a Roger HTC M7 ?
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Esposition said:
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Click to expand...
Click to collapse
The OTAs don't work with custom recovery. You need the factory recovery
Hi guys,
need your help.
2 days ago my phone (HTC One M7_UL) said there is a great update for me - new Sence 6.0 and etc. (about 700 - 800 MB total). I agreed to update it, but, probably battery wasn't charge so I get a phone with just a black screen.
After two days of tryings to recover it I did it - I download from this forum a ROM and successfully wrote it on device.
Sence 6.0 is looking great, but my question is:
previously there was an option 'Check for software updates', but now I can't see it in 'Settings-About'. Did I do smth wrong? Cause now I have my phone as 'Unlocked, Tampered' with S-on. Will I be able to get OTA updates?
Please, help me, it's my first android smartphone, I will be appreciated.
Thanks a lot.
Hmld said:
Hi guys,
need your help.
2 days ago my phone (HTC One M7_UL) said there is a great update for me - new Sence 6.0 and etc. (about 700 - 800 MB total). I agreed to update it, but, probably battery wasn't charge so I get a phone with just a black screen.
After two days of tryings to recover it I did it - I download from this forum a ROM and successfully wrote it on device.
Sence 6.0 is looking great, but my question is:
previously there was an option 'Check for software updates', but now I can't see it in 'Settings-About'. Did I do smth wrong? Cause now I have my phone as 'Unlocked, Tampered' with S-on. Will I be able to get OTA updates?
Please, help me, it's my first android smartphone, I will be appreciated.
Thanks a lot.
Click to expand...
Click to collapse
Did you install the odex version? On mine, in the Settings -> About at the top it states Software updates! The odex version is pure stock and will be able to receive the OTA providing you have the stock recovery and boot.img installed. The de-odex version is not able to receive OTA updates and I am guessing it doesn't have Software updates on it's menu. If you installed the wrong one just download and install the odex version.
majmoz said:
Did you install the odex version? On mine, in the Settings -> About at the top it states Software updates! The odex version is pure stock and will be able to receive the OTA providing you have the stock recovery and boot.img installed. The de-odex version is not able to receive OTA updates and I am guessing it doesn't have Software updates on it's menu. If you installed the wrong one just download and install the odex version.
Click to expand...
Click to collapse
Hi, thank for reply
Yes, I installed odex version. I am not interested in custom ROMs, just want to restore my phone to it's stock version, so that I could load OTAs.
My phone is unlocked, s-on, tampered (after I was trying to return it to life)
When I go About -> Software Information - only I can see :
1) Android version (4.4.2)
2) HTC Sence version (6.0)
3) Software number (Android Revolution HD71.1 by mike 1986)
4) HTC SDK API level (6.20)
And button 'More'
But now button 'Check for updates'
Also, I tried to install from htc1guru Reset ROM. Installed it. I had Sence 5.5 and Android 4.3. There I had 'Check for updates' button - but after pressing it - it said there are no updates.
What should I do to be able to get OTAs?
Thanks a lot
Follow this thread to gain 100% stock.
http://forum.xda-developers.com/showthread.php?t=2358738
Hmld said:
Hi, thank for reply
Yes, I installed odex version. I am not interested in custom ROMs, just want to restore my phone to it's stock version, so that I could load OTAs.
My phone is unlocked, s-on, tampered (after I was trying to return it to life)
When I go About -> Software Information - only I can see :
1) Android version (4.4.2)
2) HTC Sence version (6.0)
3) Software number (Android Revolution HD71.1 by mike 1986)
4) HTC SDK API level (6.20)
And button 'More'
But now button 'Check for updates'
What should I do to be able to get OTAs?
Thanks a lot
Click to expand...
Click to collapse
It looks like you still have ARHD71.1 on your phone. Go to this site and follow Method #1. Flash 4.19.401.11 version and select stock radio and recovery in aroma. After you have the stock recovery and rom back on your phone your last step will be to relock your bootloader with the command: fastboot oem lock Then you should be able to receive the Sense 6 OTA.
majmoz said:
It looks like you still have ARHD71.1 on your phone. Go to this site and follow Method #1. Flash 4.19.401.11 version and select stock radio and recovery in aroma. After you have the stock recovery and rom back on your phone your last step will be to relock your bootloader with the command: fastboot oem lock Then you should be able to receive the Sense 6 OTA.
Click to expand...
Click to collapse
I tried, now it has Android 4.4.2, Sense 5.5. But when I tap on 'Check for updates' - it says 'There are no updates available for your phone'
Michiel0912 said:
Follow this thread to gain 100% stock.
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Try this method.
I'd rather try THIS method, think it is easier because you do not have to re-root phone after flash ruu.zip. Yesterday I successfully revert back to 100% stock with that method.
Originally Posted by snebojsa
Another question: you sad that the order of doing things is:
1. Get rid of tampered ad lock bootloader
2. Then flash ruu.zip
In THIS thread by Crushalot sad that first you have to flash ruu.zip THEN get rid of tampered and lock bootloader. What is the right order, or that is irrelevant?
Click to expand...
Click to collapse
if you are following my RUU.EXE or RUU.ZIP method, then you need to 1st remove tampered and set locked.
why? because once you flash the ruu.zip, it will overwrite custom recovery (needed for the adb commands / bootloader reset tool) with the stock recovery, which doesn't allow adb commands or bootloader reset tool.
after a successful ruu flash, everything will be 100% stock.
to double check, bootup once to make sure the phone is booting OK, and everything was wiped,
but, if you intend on going S-ON do not take OTAs, go back to bootloader and S-ON (as always, I do not recommend it)
Click to expand...
Click to collapse
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?
I have S-off and a custom recovery. If I want to update to the latest software (.7), what do I have to do? I'm guessing I only need to flash a stock recovery, lock my bootloader, and take the OTA but I want to make sure this update doesn't S-On, as it is security based. Also, since I'm S-Off, do I actually have to lock my bootloader? It's sorta a PITA to unlock again.
Interested to know the answer to this myself.
sauprankul said:
I have S-off and a custom recovery. If I want to update to the latest software (.7), what do I have to do? I'm guessing I only need to flash a stock recovery, lock my bootloader, and take the OTA but I want to make sure this update doesn't S-On, as it is security based. Also, since I'm S-Off, do I actually have to lock my bootloader? It's sorta a PITA to unlock again.
Click to expand...
Click to collapse
I tried to take the OTA on my stock rooted ROM and it wouldn't boot. My guess is root or xposed caused the issue as I've heard (after the fact) that the system partition needs to be stock. While HTC used to make OTAs that would switch s-off back to s-on, I haven't heard of them doing that recently (by recently, I mean ever on the m7). I don't think you need to relock to take the OTA, but I wasn't successful, so maybe that was the reason.
I successfully took the update with no data loss and all applications kept (s-off) by running the Xposed uninstaller zip from recovery, unrooting via superSU, and flashing the stock recovery_signed.img included in the zip in this thread. Then accepting the update, after update reapplying all these things worked flawlessly.
Joshlul said:
I successfully took the update with no data loss and all applications kept (s-off) by running the Xposed uninstaller zip from recovery, unrooting via superSU, and flashing the stock recovery_signed.img included in the zip in this thread. Then accepting the update, after update reapplying all these things worked flawlessly.
Click to expand...
Click to collapse
so looks like S-Off people just have to 1) unroot, 2) remove Xposed and 3)flash the stock recovery to take the OTA update. Will do!
sauprankul said:
so looks like S-Off people just have to 1) unroot, 2) remove Xposed and 3)flash the stock recovery to take the OTA update. Will do!
Click to expand...
Click to collapse
Unless you're me and try to do it rooted. Then, after your phone won't boot, you have to try to run the RUU and find it doesn't work right on Windows 10 (at least for me the window would just disappear/crash after accepting the licensing agreement). Then you have to find an old Windows 7 laptop. Try the latest HTC Sync and find it doesn't work. Use the "naked" adb driver which gives fastboot access, but then get error 170 when running the RUU. So, uninstall HTC Sync and find an old copy of the HTC Drivers on your hard drive. Install that and then run the RUU to go back to stock. Wait for the phone to boot, then finally take the OTA. :crying:
I'm going to update my guide to include the HTC Drivers that finally worked for me.
coal686 said:
Unless you're me and try to do it rooted. Then, after your phone won't boot, you have to try to run the RUU and find it doesn't work right on Windows 10 (at least for me the window would just disappear/crash after accepting the licensing agreement). Then you have to find an old Windows 7 laptop. Try the latest HTC Sync and find it doesn't work. Use the "naked" adb driver which gives fastboot access, but then get error 170 when running the RUU. So, uninstall HTC Sync and find an old copy of the HTC Drivers on your hard drive. Install that and then run the RUU to go back to stock. Wait for the phone to boot, then finally take the OTA. :crying:
I'm going to update my guide to include the HTC Drivers that finally worked for me.
Click to expand...
Click to collapse
Thanks for taking one for the team, coal.
Joshlul said:
unrooting via superSU.
Click to expand...
Click to collapse
I'm actually unable to do this. It just gets stuck on "Uninstalling, please wait."
I uninstalled all of my root apps, no cigar.
How do I unroot my phone if I can't do it via the app?
EDIT: disregard, I'm an idiot. Don't disable superuser before uninstalling it - SU requires root to uninstall itself LOL
EDIT 2: Also, I remember installing a custom kernel at some point. I should probably reflash the stock rom just in case (dirty of course).
EDIT 3: Aaand we have bootup! yay. Hopefully this update has more goodies than just the stagefright fix. I was thinking this would fix the mediaserver drain. I'll update this post if it does.