Related
With todays rumored start of the OTA for the Dinc I have a question as to how to go about things. When the leaked 2.2 came out I flashed my radio and updated to the leaked 2.2, had the typical problems everyone else did but instead of going through all of the fixes went back to stock 2.1. So I'm back to firmware 2.1-update1 baseband 1.000.03.04.06. My question is this. Unrevoked posted a tweet last night/early this morning saying to be sure to use Unrevoked Forever before any OTAs. So, at risk of goofing something up what steps do I need to take to be ready for the OTA?
Root using Unrevoked 3.1
Use Unrevoked Forever
Wait for OTA
Sound about right? But if I do those things will I be able to apply the OTA without issue? Or is the general idea to not apply 2.2 until Unrevoked has come out with a modified 2.2 OTA. I'm honestly not too worried about root as I know that Unrevoked will eventually, if not soon after the update, come out with something for rooting 2.2.
Also, if I do these things and return to Stock, S-ON will be there still, can I then take the update normally without issue, then simply wait on Unrevoked to root 2.2? So many things going on, not sure which way to go.
I looked over the forums and didn't see any similar questions being asked, so if I missed something please disregard.
You need to have s-off before you apply the 2.2 OTA update or you will loose Root perm until they figure out a way to reroot. If you have S-off even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system.
I got this information from http://unrevoked.com/rootwiki/doku.php/public/forever I take no credit for it.
The steps you described will enable you to root after the OTA update. Just make sure that you have the latest radio before you update.
Keep in mind that there is currently no way to revert from s-off at the moment so if your goal is to have a 2.2 factory image, just sit tight and wait for the update.
Sent from my rooted Dinc using XDA App
Hatman41 said:
You need to have s-off before you apply the 2.2 OTA update or you will loose Root perm until they figure out a way to reroot. If you have S-off even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system.
I got this information from http://unrevoked.com/rootwiki/doku.php/public/forever I take no credit for it.
Click to expand...
Click to collapse
OK, forgive the stupid question. It's early, I didn't sleep, so I NEED to run Unrevoked Forever, period, before the OTA, otherwise I'm at the mercy of someone discovering a root method for 2.2, which may or may not take forever, yea?
Yes that is what I have read that the 2.2 OTA will plug up the current root process just like it did for the EVO.
If you want root, you install unrevoked forever.
If you are worried about being able to revert to stock image for warranty reasons or otherwise, check Berzerker7's post in the development thread to downgrade. According to him you will have stock and VZW techs dont have a way for checking for s-off
Sent from my rooted Dinc using XDA App.
Hatman41 said:
Yes that is what I have read that the 2.2 OTA will plug up the current root process just like it did for the EVO.
Click to expand...
Click to collapse
OK so here's what I've got so far, and thanks for the help =)
•Run Unrevoked 3.1
•Run Unrevoked Forever
•Reflash back to Stock 2.1
•Apply official OTA
•Apply custom recovery
•Install su
Sound right?
I just found this about the OTA http://forum.xda-developers.com/showpost.php?p=7728407&postcount=3386
Assuming you are on 2.1 with clockwork and s-off: http://forum.xda-developers.com/showpost.php?p=7660617&postcount=5
Sent from my ADR6300 using XDA App
So could I follow the steps I outlined before and be ok?
•Run Unrevoked 3.1
•Run Unrevoked Forever
•Reflash back to Stock 2.1
•Apply official OTA
•Apply custom recovery
•Install su
Yes you should be fine if you do that.
Hatman41 said:
Yes you should be fine if you do that.
Click to expand...
Click to collapse
OK, thanks a lot for the help guys. I feel better going into this now =)
Now all we need is the OTA.
I am a bit confused. I am urnning radio 2.15 (latest) with SkyRaider 2.5.2 and Clockwork recovery and S-OFF.
How do i go about getting stock radio and stock ROM? Also, can the stock rom be rooted or no when flashing OTA?
Thanks!
rulevoid said:
I am a bit confused. I am urnning radio 2.15 (latest) with SkyRaider 2.5.2 and Clockwork recovery and S-OFF.
How do i go about getting stock radio and stock ROM? Also, can the stock rom be rooted or no when flashing OTA?
Thanks!
Click to expand...
Click to collapse
Read http://forum.xda-developers.com/showthread.php?t=757927 to revert back to the stock radio and stock ROM. As you have S-OFF once you have intalled the OTA then just flash the custom recovery that Unrevoked has supplied http://unrevoked.com/rootwiki/doku.php/public/forever and apply SU and then you are rooted again.
lamusician said:
If you want root, you install unrevoked forever.
If you are worried about being able to revert to stock image for warranty reasons or otherwise, check Berzerker7's post in the development thread to downgrade. According to him you will have stock and VZW techs dont have a way for checking for s-off
Sent from my rooted Dinc using XDA App.
Click to expand...
Click to collapse
Well if HBOOT still runs, they can just power it up and look for it to say S-OFF at the top.
Yup
sryan2k1 said:
Well if HBOOT still runs, they can just power it up and look for it to say S-OFF at the top.
Click to expand...
Click to collapse
This is the dilemma ... I honestly do not know what I intend to do.
Can anyone help me. I made a nandroid backup of stock when I only had Unrevoked 3, then I did another backup of my Skyraider with all custom images and the works.
I would like to return to stock, but keep S-OFF so I can go through with the OTA. Can someone explain how I could do that why keeping S-OFF.
And how I can get Root access again after flashing the OTA
http://forum.xda-developers.com/showthread.php?t=766361
you just need to get stock recovery and then u can run the RUU to upgrade.
And then when I get to the lastest I can install clockwork again?
I have another off topic question about Skyraider, when he updates it with the official Froyo release, will I have to wipe everything to upgrade? or will it beable to just update over mine similiar to how HTC is rolling the update.
mikeymop said:
Can anyone help me. I made a nandroid backup of stock when I only had Unrevoked 3, then I did another backup of my Skyraider with all custom images and the works.
I would like to return to stock, but keep S-OFF so I can go through with the OTA. Can someone explain how I could do that why keeping S-OFF.
And how I can get Root access again after flashing the OTA
Click to expand...
Click to collapse
I would suggest using the official ota leak rom. It is exactly the same, with root already done. plus it is deodexed so you can theme!
But if I restore with my nandroid backup that I made after I rooted with unrEVOked 3, will I lose my S-OFF?
Not positive, but I believe you will keep S-Off but just lose root.
The ONLY way to turn s-off to s-on is by unrevoked s-on new release. that's the beauty of it, no ROM without root with take your rooting abilities away like the OTA, if you didn't have s-off.
Hmm. If and when it comes, could someone tell me what will happen for the s-off diNK? I've read weird stories in the past about excepting ota's while running a rom. Maybe we no get but if it does come in the notifications what should I do? Thanks in advance
Sent from my Incredible using Tapatalk
If you're running any of the latest ROMs, most developers removed the notification for the OTA. Don't accept it, as it won't install. In order to get it, you'd need to be S-ON and running the official VZW 2.2 stock ROM. They are releasing the OTA in small batches at first, then more and more over the next week here. You will lose root, and currently there is no gaining root back if you accept the OTA. You'd need to wait for Unrevoked or AlphaRev to gain the root exploit for it.
You're best bet: wait for a developer to put together a flashable zip of the official OTA when it comes out, and they get their hands on it. You keep root, and have the official release all in one nice zip.
RMarkwald said:
If you're running any of the latest ROMs, most developers removed the notification for the OTA. Don't accept it, as it won't install. In order to get it, you'd need to be S-ON and running the official VZW 2.2 stock ROM. They are releasing the OTA in small batches at first, then more and more over the next week here. You will lose root, and currently there is no gaining root back if you accept the OTA. You'd need to wait for Unrevoked or AlphaRev to gain the root exploit for it.
You're best bet: wait for a developer to put together a flashable zip of the official OTA when it comes out, and they get their hands on it. You keep root, and have the official release all in one nice zip.
Click to expand...
Click to collapse
This might be mis-information as I have read several posts about NOT putting S-ON back. Basically leave it as S-OFF, do the OTA, then reload custom recovery and superuser.
At this point being that I've read both, I'm just going to wait until I see what other's are experiencing with their rooted phones. I don't want to lose root, and there are already a ton of Gingerbread ROM's out there if I want one.
badogg said:
This might be mis-information as I have read several posts about NOT putting S-ON back. Basically leave it as S-OFF, do the OTA, then reload custom recovery and superuser.
At this point being that I've read both, I'm just going to wait until I see what other's are experiencing with their rooted phones. I don't want to lose root, and there are already a ton of Gingerbread ROM's out there if I want one.
Click to expand...
Click to collapse
I'm not seeing how that would work because the kernel lacks root. You could install SU, but it won't do anything.
badogg said:
This might be mis-information as I have read several posts about NOT putting S-ON back. Basically leave it as S-OFF, do the OTA, then reload custom recovery and superuser.
At this point being that I've read both, I'm just going to wait until I see what other's are experiencing with their rooted phones. I don't want to lose root, and there are already a ton of Gingerbread ROM's out there if I want one.
Click to expand...
Click to collapse
I've seen the same thing too. But going back to stock 2.2 you need to first S-ON then either RUU or PB31IMG.zip, you can't just run the RUU or PB31IMG.zip file with S-OFF. I would think that the OTA would check that security flag to make sure it's S-ON before flashing, and error out/not update if you're S-OFF.
Maybe I am wrong, but waiting never hurts! Someone will get a flashable zip of the OTA, so there's no need to risk losing root over it. Chances are the flashable OTA zip will be available the same day the OTA drops, whenever that'll happen.
RMarkwald said:
I've seen the same thing too. But going back to stock 2.2 you need to first S-ON then either RUU or PB31IMG.zip, you can't just run the RUU or PB31IMG.zip file with S-OFF. I would think that the OTA would check that security flag to make sure it's S-ON before flashing, and error out/not update if you're S-OFF.
Maybe I am wrong, but waiting never hurts! Someone will get a flashable zip of the OTA, so there's no need to risk losing root over it. Chances are the flashable OTA zip will be available the same day the OTA drops, whenever that'll happen.
Click to expand...
Click to collapse
Yep! Exactly why I'm waiting to see what happens with other people who are willing to try it.
Waiting for dev build seems like best/safest/easiest route. Patience wins again. Thanks for replies.
Sent from my Incredible using Tapatalk
to be honest i wouldnt even worry about the update if your rooted i would just let the devs do their thing and run a better version of 2.3.4 every dev will most likly use it as the base anyways.. also youll have to wait for root if you update and there probably wont be a way to downgrade android after you instal the OTA
reggie cheeks said:
Waiting for dev build seems like best/safest/easiest route. Patience wins again. Thanks for replies.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
oops missed this post lol
Ive been trying to research how to update my bootloader version but i've been failing miserably. I currently have 3.16 and ive been trying to flash a few roms that wont let me since its too old. I'm rooted but i have s-on. Help?
Ever try just doing the OTA updates?
From where? I'm on ReNovate 4.5 and i dont see any options under settings.
alex5857 said:
From where? I'm on ReNovate 4.5 and i dont see any options under settings.
Click to expand...
Click to collapse
For official OTAs, you need to return to stock ROM and stock recovery. Then you should be able to update by OTA, which will also update hboot.
redpoint73 said:
For official OTAs, you need to return to stock ROM and stock recovery. Then you should be able to update by OTA, which will also update hboot.
Click to expand...
Click to collapse
So then i just need to download a stock rom from here and run the OTA? Would that come with the stock recovery? Is there a way to do it without having to do that?
Thanks for the help!
alex5857 said:
So then i just need to download a stock rom from here and run the OTA? Would that come with the stock recovery?
Click to expand...
Click to collapse
No, you need to flash the stock recovery seperately. Get your stock ROM and recovery for your CID at the following thread (includes detailed instructions):
http://forum.xda-developers.com/showthread.php?t=2701376
alex5857 said:
Is there a way to do it without having to do that?
Click to expand...
Click to collapse
Another way to run the OTAs? For the most part NO. The exception being some US variants, where you can relock the bootloader and update by RUU. Otherwise, for non-US versions:
You need the stock ROM, otherwise the OTA will fail when it sees the /system (ROM) files have been modified from "stock".
You need the stock recovery, since this is required to actually install the OTA. Without the stock recovery, the OTA will attempt to install, fail, and you will be stuck in a bootloop as the phone keeps trying to reboot into stock recovery.
Unless you mean, is there another way to update hboot. The only other way would be to s-off the device by sunshine.
I would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.
theloneranger08 said:
I would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.
Click to expand...
Click to collapse
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom
an0ther said:
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom
Click to expand...
Click to collapse
Thanks for all of the info. I wish simply rooting your phone wasn't such a pain. I guess I'll just flash TWRP, make a backup of my phone, and then root it and then if I need to do an OTA I can just restore the backup and flash the stock recovery. I found this download site for the recovery. I'm assuming I'd pick developer and then recovery. Do I use the signed one? What happens if I flash the wrong recovery? https://www.androidfilehost.com/?w=files&flid=28830
Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?
theloneranger08 said:
Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?
Click to expand...
Click to collapse
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.
an0ther said:
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.
Click to expand...
Click to collapse
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.
an0ther said:
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.
Click to expand...
Click to collapse
Ok great and I can flash firmware regardless of what rom I'm running?
theloneranger08 said:
Ok great and I can flash firmware regardless of what rom I'm running?
Click to expand...
Click to collapse
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.
an0ther said:
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.
Click to expand...
Click to collapse
Awesome, thanks I really appreciate it. I'll definitely let you know if I have any questions.
theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Check it out this http://www.bestandroidrootedapps.com/how-to-root-htc-one-m9-and-also-have-custom-recovery-installed-on-it/