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?
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
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Scrufdog said:
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Click to expand...
Click to collapse
delete the cache after flash stock recovery ? fastboot erase cache
dawexxl said:
delete the cache after flash stock recovery ? fastboot erase cache
Click to expand...
Click to collapse
did that, didnt help, but thx
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Scrufdog said:
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Click to expand...
Click to collapse
If you're S-off, no.
You might want to take a look at the thread in the link below. It pretty much covers what you have to do to take the OTA. Since you're S-off, why not install the firmware for the latest update and then flash a ROM based off the latest update? Much simpler than having to go through all the steps you're going through.
http://forum.xda-developers.com/showthread.php?t=2888993
yeah, i was trying to update via methods that were a couple weeks old, which of course are old.... lol
I installed the latest ROM from sprint, then install ViperOne on top of it, going through the install right now. Wifi is working so I guess the firmware updated correctly.
Thanks
It is solved! For the answer look at my post below
Hello guys,
phone HTC one M8 Harman Kardon Edition
Happens that in my urge to unlock my phone sim lock I firstly changed the MID to unlocked SIM Dev edition MID and CID to SuperCID, well that went great until I was dumb enough to try to flash a Dev edition RUU to the phone and then i lost my TWRP recovery and everything went haywire. cause now i try to flash Recovery through fastboot and it suceeds but the phone gets stuck in entering recovery, Im not able to flash a Sprint RUU for HK because 1. i havent found one and 2. it probably wont load because of the MID which is 0P6B1200 if im correct.
please help me either load the Custom recovery so i can have access to adb, or any other way to fix it.
thank you!!
if someone could please give me any ideas, or contact anyone who could help me, it would be greatly apreciated, i can pay up to 20 usd through paypal if anyone can help me!!!
Change your MID back to Sprint and run the Sprint HK RUU...should be good to go.
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
thank you but no
Sarvesh.huddedar said:
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
Click to expand...
Click to collapse
I dont know what is going on but i did that already, even trying the new recovery image, and it gets stuck in the Entering Recovery... step
"Fastboot erase cache" and make sure you are flashing the correct version of twrp(change the MID back to the original one, this is dangerous if there is hardware difference across the 2 MIDs)
Guys all off your help was greatly apreciated but there was something wrong
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Hey
jseb14 said:
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Click to expand...
Click to collapse
Where do you type the "su ...." command into?
Hello,
I am new to xda forum and expecting a helping hand from fellow members, here's the scenario, I have a sprint htc one which was working fine a few days ago before i decided to act smart .
It was rooted when i purchased it so i thought of flashing a new custom rom into it.I tried flashing (HTC_One_-_MaximusHD_53.0.0) and this one (NuSenSeveN-LP-m7-Sprint_v4.02_050715) and ended up being stuck at green HTC logo, even though the physical buttons are performing their respective functions when pressed but the screen shows just the htc one logo and nothing else.
It is unlocked, tampered and s-on and i have twrp recovery on board, hboot 1.57.0000
WHAT I HAVE ALREADY TRIED AND FAILED:
1) tried rum runner to turn s-off because i though may b because of s-on the roms are not being flashed properly but it says adb device not found
2) tried flashing Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0 but stuck at handsfree activation, even though i deleted htcwizard.apk.
Now the bottom line is, I am unable to use my device and in desperate need of your help.
Please respond, awaiting to put my hand back on the device.
Thank You
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Sloth said:
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Click to expand...
Click to collapse
Hey thanks for the response, I am not tech geek so I have no idea how to flash the latest RUU can you please be more specific about how to perform the above mentioned process or can you have a chat on hangouts as I have altready added you on it.
Thanks alot
Try to flash ruu which could be found on other posts do u know how to boot into the bootloader?
problem solved
Update: thanks to @Sloth I have fixed the problem, if anyone out there who owns a sprint htc one and have messed up his phone by flashing an incompatible rom the way i did, first relock your bootloader if you are s-on and then simply download RUU file from htc official website, make sure its for sprint variant.
Once the bootloader is relocked simply run ruu.exe file that you have downloaded and you are done.
Note: if the ruu setup says that you phone is not connected or gets stuck, boot into recovery and perform factory, after that re-try running ruu.
Thanks Sloth, and thanks xda members
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.