Related
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 everyone!
I unlocked using HTCDEV my One (M7-UL , Europe version) with Hboot 1.57 and 4.4.2 with S-ON. After rooting and putting a custom recovery, I received an OTA update to upgrade to 4.4.3.
My question is, Can I upgrade as it or my device will brick ("Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable")? I have read from HTC that if you upgrade an OTA being unlocked, it may fail...
Then:
1) May I relock boot and put a stock recovery in order to upgrade? If so, How does it work?
2) Or maybe I can run Sunshine in my device (i tested and it seems to work, I stopped in paypal step) to get S-OFF and then obtain this RUU and flash it?
Thx in advance!
To receive the ota you need to put the stock recovery back and copy over some of the apps that get deleted when you unlock the bootloader. It's a lot of stuffing around to be honest. Why not just install a custom Rom that uses 4.4.3. They are better than stock roms anyways
But I'm actually receiving this OTA; I'm hesitating to press install button being unlocked...
Tell me examples of these ROMS. Are they 100% compatible with all HTC ONE stock staff, (infrared , beats audio...)?.
Thx
It will let you download an ota if you are on a stock Rom. But if you have a custom recovery or you haven't re added the apps that were deleted when you unlocked it won't install. It won't brick your phone or anything. It just won't install. Maximums and Android revolution are two off the top of my head. Both work fine. Why don't you just experiment a little. Back up your current Rom and try a few others. If you don't like them u can always restore the backup
Thx. I'll try.
One more question, do you recommend me to run Sunshine in 4.4.2 stock rom to gain S-OFF before installing MaximusHD ROM?
and how much is secure doing S-OFF with this tool?
Sunshine does work best on stock roms. It's quick and easy and does compatibility tests to make sure it Will work on your phone. It does cost $25 but we'll worth it if you ask me
Sunshined Done!
Now I'm going to installing MaximusHD, and possible later, GPE (that requires being S-OFF first).
Any good guide explaining GPE<->SENSE (stock or custom)?
Thx
I have an unlocked and rooted HTC One M7, which I just updated to the latest version of android via an OTA update.
I used the process I always use for this, by reverting back to the stock recovery, then doing the update.
Even though the update completed, the initial boot after the update won't complete anymore. I am stuck at the HTC One Boot-logo.
I know that it usually takes longer to boot after an update, for the first time. However I have waited 60+ minutes now and it still did not move on.
Some more detailed information:
- Unlocked bootloader
- S-OFF
- H-Boot: 1.61.0000
- Radio: 4T.35.3218.16
- Version-Main before update: 7.18.161.2 (This is also the stock recovery I pulled and flashed before doing the OTA)
- Version-Main after update: 7.18.161.21
- CID: VODAP110
- Variant m7_ul unlocked / international
What I have tried:
1st As mentioned above, re-flashing stock recovery, update -> No boot
2nd Recovery from an older nandroid backup, made on the previous version, so 7.18.161.2. After recovering, my device worked fine again, like before the update. HOWEVER: The system version (inside the OS, aswell as adb and bootloader) still showed 7.18.161.21, which should be the version AFTER the update. It still tells me that I need to update my phone though.
3rd Since then I have tried to re-flash the stock recovery, this time the one for 7.18.161.21, since it showed me I was on this version. Again, the update completed without any hickup, but it is now stuck at boot again.
PhilDrummer said:
I have an unlocked and rooted HTC One M7, which I just updated to the latest version of android via an OTA update.
I used the process I always use for this, by reverting back to the stock recovery, then doing the update.
Even though the update completed, the initial boot after the update won't complete anymore. I am stuck at the HTC One Boot-logo.
I know that it usually takes longer to boot after an update, for the first time. However I have waited 60+ minutes now and it still did not move on.
Some more detailed information:
- Unlocked bootloader
- S-OFF
- H-Boot: 1.61.0000
- Radio: 4T.35.3218.16
- Version-Main before update: 7.18.161.2 (This is also the stock recovery I pulled and flashed before doing the OTA)
- Version-Main after update: 7.18.161.21
- CID: VODAP110
- Variant m7_ul unlocked / international
What I have tried:
1st As mentioned above, re-flashing stock recovery, update -> No boot
2nd Recovery from an older nandroid backup, made on the previous version, so 7.18.161.2. After recovering, my device worked fine again, like before the update. HOWEVER: The system version (inside the OS, aswell as adb and bootloader) still showed 7.18.161.21, which should be the version AFTER the update. It still tells me that I need to update my phone though.
3rd Since then I have tried to re-flash the stock recovery, this time the one for 7.18.161.21, since it showed me I was on this version. Again, the update completed without any hickup, but it is now stuck at boot again.
Click to expand...
Click to collapse
You are confusing software and firmware version. When installing an ota update, both the software and firmware are updated. Nandroid backups doenst include the firmware, flashing one will only restore the software. So you are restoring a .2 software on a . 21 firmware.
Anyway you have soff just flash the latest ruu available for your phone and then update it
alray said:
You are confusing software and firmware version. When installing an ota update, both the software and firmware are updated. Nandroid backups doenst include the firmware, flashing one will only restore the software. So you are restoring a .2 software on a . 21 firmware.
Anyway you have soff just flash the latest ruu available for your phone and then update it
Click to expand...
Click to collapse
I have tried finding the correct RUU, but I am getting a little confused with the available ones. When selecting the RUU, is only the variant of the phone important (so unlocked in my case) or do I have to match everything, as in CID, Carrier etc.? Because I cannot seem to find one that has matching information, except for the variant.
PhilDrummer said:
I have tried finding the correct RUU, but I am getting a little confused with the available ones. When selecting the RUU, is only the variant of the phone important (so unlocked in my case) or do I have to match everything, as in CID, Carrier etc.? Because I cannot seem to find one that has matching information, except for the variant.
Click to expand...
Click to collapse
7.18.161.2 is the first ruu posted in this thread
alray said:
7.18.161.2 is the first ruu posted in this thread
Click to expand...
Click to collapse
Wow, sorry I somehow didn't manage to find that :angel:
Thaks a lot!
Btw, since you said the firmware is not included in a Nandroid backup, if I create one now, do the whole procedure and if something fails, re-flash the nandroid, should everything still be working fine just as it is now? I'm guessing yes, right?
Also: If I now flash the ruu, deleting all data etc in the process, and then update, I won't have any option of re-aquiring all my data/settings either, right?
So in the end effect, this update will basically "flush" my phone
Same problem
Hi
I experienced the same problem while updating from 7.18.161.2 to 7.18.161.21. My bootloader was unlocked l, S-on and flashed stock recovery before I did the OTA. This procedure was working fine since a long time. Unfortunately this time I got stuck at the HTC boot logo, same as OP.
After flashing the RUU, locking the bootloader (this I guess was the important step) and do the OTA again, it finally worked. Too bad I lost all my precious data. Yeye backup I know
Im really aware of unlocking my bootloader again and have the same problem the next time they might release an update.
Now my question is, did HTC or my Carrier (Swisscom) changed anything in the update procedure?
Regards
red1337
red1337 said:
Hi
I experienced the same problem while updating from 7.18.161.2 to 7.18.161.21. My bootloader was unlocked l, S-on and flashed stock recovery before I did the OTA. This procedure was working fine since a long time. Unfortunately this time I got stuck at the HTC boot logo, same as OP.
After flashing the RUU, locking the bootloader (this I guess was the important step) and do the OTA again, it finally worked. Too bad I lost all my precious data. Yeye backup I know
Im really aware of unlocking my bootloader again and have the same problem the next time they might release an update.
Now my question is, did HTC or my Carrier (Swisscom) changed anything in the update procedure?
Regards
red1337
Click to expand...
Click to collapse
They will probably not have anymore updates but to install one you need:
stock recovery of the same firmware version or from the ota update version
stock /system partition (any missing/modified/corrupted files on this partition will makes the ota install fail)
stock /data/preload (any missing/modified/corrupted files on this partition will makes the ota install fail, unlocking the bootloader wipes everything in this folder)
More details here:http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
tw39515 said:
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
Click to expand...
Click to collapse
Welcome back to HTC
It really depends on what you plan to do with your M9.
If you plan on using custom roms then yes unlock and install TWRP. Root is not required to flash roms.
Sunshine does not root or unlock but removes secure write (S-Off) which allows you to install different firmware's etc.
With S-on you can only move forward with firmware's. Lots of people complain about the 25.00, But its well worth it.
If you are not concerned about the cost, then unlock, twrp, flash superSu, and install sunshine and S-off then your free to do anything.
backup if you like but there is a thread with stock backups etc...
hope this helps
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
will do viperone had issues on initial firmware so i flashed the latest ruu, sunshine is next. thanks for the advice.
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
umangilu said:
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
Click to expand...
Click to collapse
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
kc6wke said:
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
Click to expand...
Click to collapse
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Miguel_Lancaster said:
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Click to expand...
Click to collapse
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
kc6wke said:
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
Click to expand...
Click to collapse
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Miguel_Lancaster said:
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Click to expand...
Click to collapse
The RUU will not relock bootloader or rewrite S-On. To accept OTA, you need to have stock unmodified device.
You could run the RUU again or just unroot and flash stock recovery. The OTA will not wipe the device but the RUU will.
Hope this helps.
kc6wke said:
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
Click to expand...
Click to collapse
Thanks for this! Im having trouble with my computer and have been looking for a ruu zip all day lol. Will give this a shot on my TMOUS S-Off M9 tomorrow so I can jump to my next device.
Hi Experts,
Kindly bear my ignorance and answer the following questions.I tried enough to find solution but cannot risk since this is not my personal phone. I have T-Mobile HTC one M9 with S-OFF,Bootloader Unlocked,Rooted and in Kitkat Sense 2.7.531.6. I am having problem with the phone that i cannot turn on Mobile data and there is no option for network reset settings. I dont have any OS backup. I have downloaded Nougat RUU from HTC website. As i read in the forum,no update is available for my rooted phone and have to use any custom OS.My questions are
(i) If i flash with Nougat RRU will my bootloader be relocked and S-OFF will be S-ON. I have obtained unlock.bin from HTCdev so incase if my bootloader is relocked can i use the same unlock.bin for unlocking again.
(ii) I need to use a software which requires root permission.I saw TWRP supports HTC one M9 and can that be used to root Nougat? any successful root for nougat. Suggestion pls.
(iii) In case after upgrading to Nougat, If i want to downgrade is Nandroid backup enough or need any additional things ?
(iv) Do Updating ROM updates Kernel too.(Really Sorry for this since i saw my software while installing, updates kernel which i have no idea)
(v) Finally if anyone have 2.7.531.6 T-Mobile ROM Kindly Share.