So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc.
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Joshy8 said:
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc. [emoji14]
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Click to expand...
Click to collapse
There's newer firmware out. Look in neo's 5.1 deodex thread. That os is also 5.1 (rom).
Sent from my HTC6535LVW using Tapatalk
LOL! So it is! I saw it last night and somehow I screwed up and linked to your thread. Hooray for tired long days.
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Thanks for the response bschram. It is appreciated.
I actually wiped my phone and installed 3.0.0 without updating the firmware. Phone still works fine, but I will be updating the firmware as soon as I am confident I know what I'm doing with firmware upgrades. I'm a bit more nervous about updating firmware as I don't want to break the phone.
I'm glad to hear that I don't have to do a full wipe, and I'll definitely be doing that going forward. I will say that 3.0.0 is way more reliable than 1.9.1 was.
Just to make sure I am doing things correctly.... I am not totally new to this. Coming from stock 5.0.2... with S-off/Bootloader Unlocked. Flash firmware from NEO's deodexed rom in fastboot, advanced wipe in TWRP, then flash any 5.1 rom that is compatible IC, Viper, ect.... Then we should be good to go?
Then when offical OTA arrives, wait until firmware is pulled then flash the same way? Just making sure I will doing things right..... Thanks in advance
bschram said:
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Click to expand...
Click to collapse
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
teckels said:
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
Click to expand...
Click to collapse
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
andybones said:
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
Click to expand...
Click to collapse
Is it a common thing or has it only happened to one or two people.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
I
Thiss I am not too sure of, but I don't think too many.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
Me and one or two others. I have my suspicions as to what caused it and the casual crack rom flasher likely won't fall victim to it.
Sent from my HTC6535LVW using Tapatalk
Related
Engadget states that Verizon is going to push the official 2.2 Froyo update tomorrow for all HTC incredible users.
IF this is true I have a few questions. I'm currently rooted and running Sky Raider 3.0 RC2. I did a nand backup of my old original 2.1 Stock sense rom. If i revert back to that, can I just check for updates and apply the new stock 2.2 Froyo rom that is pushed from verizon?
Thanks,
ej_424
It is true. Unlike previous rumors, VZW employees were told today (this afternoon) and it shows on their bulletin screens now.
That and sometime between 1pm and 2:30pm they updated the support page.
So who's gonna jump in and who's gonna wait?
Please answer my question on how to go about updating. I'll jump in but want to knwo what process i have to take. Is there a chance that I wont be able to re-root if i go with the OTA update?
why go through the trouble of unrooting and going back to stock just to receive an update "officially" thats already been rooted and simplified here in 2 threads?
mb02 said:
why go through the trouble of unrooting and going back to stock just to receive an update "officially" thats already been rooted and simplified here in 2 threads?
Click to expand...
Click to collapse
Honestly.. It's pre-rooted, and is almost positively the exact same as the official OTA.. why bother?
ej_424 said:
Please answer my question on how to go about updating. I'll jump in but want to knwo what process i have to take. Is there a chance that I wont be able to re-root if i go with the OTA update?
Click to expand...
Click to collapse
Honestly there is so much information out there. Do what I did when I first got my Incredible. Do a search, and read, read, read. Mind you when you're done your head is going to be spinning. But that is the best way to get all the information you need.
To answer your question.
it was said along time ago that accepting the 2.2 OTA may cause you to not be able to re-root.
now, unrevoked forever takes S-OFF and with this you can accept the 2.2 OTA and still keep root, it was permanent, but with the new release of S-ON there is absolutely no reason not to use S-OFF, then un-root, if you want the "official" 2.2.
I thought that SkyRaider 2.5.2 and 3.0 were built off of the previous leak of FroYo 2.2...am I wrong? I love SkyRaider Vanilla, so I don't get giving that up for an "official" OTA? Maybe it is for some, but I don't see what else you'd really get that you don't have yet that was built into the 2.2 ROM's...
Mods will probably move this to Q and A,
But, you have to provide more info as what radio you are on, hboot.., etc. There are several threads started providing info as to how to prepare yourself...
I mean, the leak OTA has been ripped apart and placed all of this forum. The only thing you can get from verizon will be the satisfaction of a cool Blockbuster app and more vzw crapware, but hey if its what you want
RMarkwald said:
I thought that SkyRaider 2.5.2 and 3.0 were built off of the previous leak of FroYo 2.2...am I wrong? I love SkyRaider Vanilla, so I don't get giving that up for an "official" OTA? Maybe it is for some, but I don't see what else you'd really get that you don't have yet that was built into the 2.2 ROM's...
Click to expand...
Click to collapse
Skyraider pre2.0 was based off an evo port, yes. 2.0 and onward is based off the leak, hence the necessity of the radio upgrade.
Gotcha. That's what I thought, as when I installed SkyRaider 2.2, I remember getting an email saying "thanks for registering your Nexus One" or something like that... Thank you for confirming, much appreciated!
Your recovery image must be stock as well. There are several threads that provide the needed file to return the DInc back to 100% stock/pre-root (just make sure S-OFF is applied first).
Mandatory OTA?
I read the pdf files from Verizon's website on the expected 2.2 OTA, and it says it is MANDATORY. That the only options it gives you are install and DELAY install. That it will keep bugging you every 30 minutes til you do !
I have used Unrevoked3, and Unrevoked Forever and love the phone as it is now (particularly the wifi tether). I want to avoid the OTA but do I HAVE to accept it? If I do, I hope I can reload the version I got with Unrevoked3.
(I assume that Verizon will, in their new version make you PAY to wifi tether)
Any info on this?
Thanks
charlier26 said:
I read the pdf files from Verizon's website on the expected 2.2 OTA, and it says it is MANDATORY. That the only options it gives you are install and DELAY install. That it will keep bugging you every 30 minutes til you do !
Click to expand...
Click to collapse
I'll be pissed if thats the case. gotta do everything all over again. But if we're already @ 2.2 shouldn't it recognize that and not force the OTA to even appear on our phones?
I'm still pretty new to this so sorry if I sound like a complete outsider lol
For those of us who've rooted, forever'd, upgraded radio, and installed some leaked version of Froyo already -- if/when we get prompted to update the phone should we accept or deny it?
With the OTA update will be a radio update as well. And if they attempt to install over the same version won't that be the same as manually attempting to update it twice which equals brick?
Or will the update detect an upgraded radio already and skip that step?
Hackenstein said:
For those of us who've rooted, forever'd, upgraded radio, and installed some leaked version of Froyo already -- if/when we get prompted to update the phone should we accept or deny it?
With the OTA update will be a radio update as well. And if they attempt to install over the same version won't that be the same as manually attempting to update it twice which equals brick?
Or will the update detect an upgraded radio already and skip that step?
Click to expand...
Click to collapse
IIRC, you will only be prompted if you have sock recovery installed. As for the OTA, it includes updates to the radio and HBOOT. The update doesn't check to see if you already have an upgraded radio because, in theory, no consumer should have it yet.
najaboy said:
The update doesn't check to see if you already have an upgraded radio because, in theory, no consumer should have it yet.
Click to expand...
Click to collapse
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
PIYIRIO said:
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
Click to expand...
Click to collapse
Not a 100% sure but I think its only if you flash a radio.diff twice you get brick.
Never the less just don't have the updated radio with old builds and stock recovery and all should be fine.
Sent from my ADR6300 using XDA App
Nope
PIYIRIO said:
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
Click to expand...
Click to collapse
That applied because the prior unrEVOked hack was simply a diff ... it patched. So if you apply the patch to the patch, THEN you brick. Flashing a wholesale radio (while higher on the danger scale) is not the same.
Fairly new to the flashing scene, but seriously loving the freedom and features available to my flashed handsets. Currently using Wicked v1 on my SGS3 and now he's got a new one out that I want to install asap. At nearly the same time an OTA has apparently dropped and there's a new (and improved?) radio/modem flash out there.
My main concern is making sure my handset is as rock solid as possible while having the best available functionality (btw, Wicked rom is an amazing daily driver). Would it be in my best interest to unroot and go back to stock so I can get the OTA and then reroot, flash a rom, flash a radio etc?
OR
Can I just flash Ev1l's new Wicked rom, flash the new radio and not worry about the OTA at all?
I guess you could sum this up as a 'What would you (the experienced pro flasher) do?'
Thanks all.
Krazeee said:
Fairly new to the flashing scene, but seriously loving the freedom and features available to my flashed handsets. Currently using Wicked v1 on my SGS3 and now he's got a new one out that I want to install asap. At nearly the same time an OTA has apparently dropped and there's a new (and improved?) radio/modem flash out there.
My main concern is making sure my handset is as rock solid as possible while having the best available functionality (btw, Wicked rom is an amazing daily driver). Would it be in my best interest to unroot and go back to stock so I can get the OTA and then reroot, flash a rom, flash a radio etc?
OR
Can I just flash Ev1l's new Wicked rom, flash the new radio and not worry about the OTA at all?
I guess you could sum this up as a 'What would you (the experienced pro flasher) do?'
Thanks all.
Click to expand...
Click to collapse
I never worry about the OTA's...go for it. The Devs fix all that anyway.
I flashed the new radio over the latest euroskank nightly
Sent from my SGH-T999 using xda premium
Thanks!
TheAxman said:
I never worry about the OTA's...go for it. The Devs fix all that anyway.
Click to expand...
Click to collapse
Awesome. I figured as much, but it's good to know the likelyhood of my opening a wormhole in my livingroom is slightly smaller now.
While you probably won't experience any problems by not worrying about the OTAs, especially since you are not on stock, there are often other elements to an update than just radios. There can also be updates to other partitions on the phone. Sometimes bootloaders, parameters, etc. can be updated also. You won't get these (if you care about them) if you skip the update and just flash the radio. If it were me, I would go back to complete stock with the update and start over. Probably not necessary, but you may want to consider it.
I posted a thread a while back but I apparently posted the wrong type of thread. This one should be the right of the right type and in the right place.
On the Samsung devices I've had in the past, the boot loader was always a big deal when flashing new versions of android. I've had this tablet for a while now and haven't updated it since I bought it...and Odin flashed/rooted/installed TWRP on it.
From reading the megathreads, from threads, flashing threads, etc...it's not very clear if this is like the other Samsung devices I've had, or if this is like the EEEpad Transformer and Nexus 7 I had...and could move freely between android versions, stock roms...and nonstock ROMs, etc.
I'm running 5.0.2 and I play hearthstone competitively. I bought this for the display mainly, and now that I've loaded it with some crap, I'd like to flash a custom from/update. It seems my crap+samsungs crap saturates the ram quite well. Can I pretty much flash what I'd like? Or do I have to ODIN from stock to the latest build and then worry about number versions.
Also...I used to run an all that kept my TWRP version up to date. Goomanager I believe...but there are dozens of apps that claim to do this now...can I get a trusted suggestion?
Rooted on stock.
Android Version: 5.0.2
Kernel: 3.4.106 IronKernel V2.0 (mainly for s tweaks to boost audio)
Build LRX22G.T800XXU1BOC3
Forget about using an app to flash twrp.
Do it manually and be safe. Plus the official updates are lacking in features compared to the unofficial builds. Just check out the dev section and you'll see what I mean.
Thanks for the advice. And as far as flashing roms...can I pretty much flash what I'd like? Ex: go back and forth between Cm and stock builds...and between version builds while ignoring the boot loader? I'm basically trying to see if I've missed something critical since I rooted and flashed so long ago.
Jamesyboy said:
Thanks for the advice. And as far as flashing roms...can I pretty much flash what I'd like? Ex: go back and forth between Cm and stock builds...and between version builds while ignoring the boot loader? I'm basically trying to see if I've missed something critical since I rooted and flashed so long ago.
Click to expand...
Click to collapse
As long as you don't flash a firmware build that is incompatible with your current bootloader you can flash what you want back and forth.
ashyx said:
As long as you don't flash a firmware build that is incompatible with your current bootloader you can flash what you want back and forth.
Click to expand...
Click to collapse
Thats what I figured. I'm running the stock rom rooted. I don't know what boot loader I'm on, or how to get to the latest one. I have all the access in the world-- recovery, root. But there isn't a place here...or anywhere that clearly says what am going on. I have a charging issue and would like to foahh a new Kernel, and I might as well update in the process,...by there is no "Upgrade from Xxx while on the stock rooted ROM" guide. Plus my laptop has a crappy USB port, so If I need to Odin something on here, itd be quite the process.
Ive asked around for months, literally. I've never been in this position before. Have always kept up to date. But once you fall behind, in forums like these (especially given the fact hat there are multiple devices in this section), you need something explicit to get back where you need to be.
Last time I looked, there weren't any instructions. Ill look against today to see if I can just download the latest..zip of a 10.5 stock ROM from somewhere in the dev section and then wipe, and flash that. If you know if its alright to just wipe and flash a new ROM, lemme know. Or if I have to Odin to a new one in order to get a new boot loader before I flash the latest Kernel, which I think then one I'm trying to use his BOJ. IRONKernel. I use it for S Tweaks, the sound, and a few performance tweaks.
You have to flash the bootloader with Odin they are posted in the bootloader thread.
You can flash the stock firmware with flashfire.
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
mikeprius said:
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
Click to expand...
Click to collapse
More signs point to hardware failure rather than the update. I think it was just coincidence that 7.0 came out when phones were getting close to 1 year old. I've been running my replacement from last month on 7.1 beta and it's just fine.
Sent from my Nexus 5X using Tapatalk
Ezekial said:
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
Click to expand...
Click to collapse
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
mikeprius said:
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
Click to expand...
Click to collapse
Gotcha. I have only had my 5x for just over a month so not the most knowledgeable. My take is largely the same as the other guy, failures are from hardware or just bloat from long term use.
I start with the latest 6 and considered staying on it for root, xPosed, etc. I have always ran this way for years. But it is super annoying not having Android pay and a few other things. I sucked it up and decided to try not rooting or even unlocking BL. There are things I miss but I am staying locked down for now. The primary issue I have is for tethering, which I cannot do. The rest I have surprisingly been able to do without.
Flash away
Hey mate, you will not have issues flashing what ever you like, issues are caused by hardware failures ( unavoidable ) or just not following instructions correctly. I flash factory images, beta etc, and custom ROMs. Never have issues. Flash like crazy. It's just a phone and almost all of them can be fixed, if something goes wrong.
P.s. You gotta try the 7.1.1 beta. Its has potential.
Hello all,
Long story short I currently have an Unlocked 10, rooted, s off, and bootloader unlocked. I have flashed over the Verizon rom and radios last year and left it this way for a while. I'm getting to the point where I'm about ready for a factory reset but figured I might as well update if I'm going to do that. Better yet I'd like to get on LeeDroid but preferably on Android N.
So I need to update to an Android N ROM first, then over to LeeDroid. I can do it, but frankly I do this stuff so little that every time I get a little nervous. My 10 is my daily driver but I currently have a raggedy s6 here I can pop a sim in for a minute if needed.
So I'm wondering would it make sense to just do a backup, flash the latest Unlocked N version then flash LeeDroid? Wouldn't my Verizon radios stay where they're at, or will flashing those roms over write them? And, none of this flashing should overwrite my recovery, should it?
Also, I apologize if this is not appropriate but my other option at this point is to ask, are there any fairly well regarded XDA friends here with some spare time that would be open to taking 20 bucks or so to get me fixed up remotely over teamviewer or something?
Thanks for all your help. I don't post here often but when I do I always find the direction I need as someone who is not a frequent modder anymore lol.
Launchpadmcqu4ck said:
Hello all,
Long story short I currently have an Unlocked 10, rooted, s off, and bootloader unlocked. I have flashed over the Verizon rom and radios last year and left it this way for a while. I'm getting to the point where I'm about ready for a factory reset but figured I might as well update if I'm going to do that. Better yet I'd like to get on LeeDroid but preferably on Android N.
So I need to update to an Android N ROM first, then over to LeeDroid. I can do it, but frankly I do this stuff so little that every time I get a little nervous. My 10 is my daily driver but I currently have a raggedy s6 here I can pop a sim in for a minute if needed.
So I'm wondering would it make sense to just do a backup, flash the latest Unlocked N version then flash LeeDroid? Wouldn't my Verizon radios stay where they're at, or will flashing those roms over write them? And, none of this flashing should overwrite my recovery, should it?
Also, I apologize if this is not appropriate but my other option at this point is to ask, are there any fairly well regarded XDA friends here with some spare time that would be open to taking 20 bucks or so to get me fixed up remotely over teamviewer or something?
Thanks for all your help. I don't post here often but when I do I always find the direction I need as someone who is not a frequent modder anymore lol.
Click to expand...
Click to collapse
To minimize potential problems I would start fresh going from M to N.
Flash the full N RUU.exe. Flash the latest TWRP, then flash LeeDroid. New firmware, TWRP, and custom rom.
comstockload said:
To minimize potential problems I would start fresh going from M to N.
Flash the full N RUU.exe. Flash the latest TWRP, then flash LeeDroid. New firmware, TWRP, and custom rom.
Click to expand...
Click to collapse
Would you suggest Verizon N rom since I'm already on Verizon M or would Unlocked N be better?
Launchpadmcqu4ck said:
Would you suggest Verizon N rom since I'm already on Verizon M or would Unlocked N be better?
Click to expand...
Click to collapse
Get a copy of your current M rom for the firmware you currently have and download that. Remember, we're talking full roms not updates. Now get the latest N rom for your device (full ruu.exe). Now you have options. I would flash the N rom, then the latest TWRP, then LeeDroid. Any problems, and you can go right back to M. I always use TWRP 3.0.2-6 with M. So if I go back to M I flash that version of TWRP (from within TWRP itself) first. Take your time. You can do this. You can get the latest N rom from HTC's website. To get your M rom you'll have to search for it using your firmware numbers. Someone should have a copy.
BTW, you can watch ROOT JUNKY's videos on youtube as a refresher on the basics of flashing TWRP and so on. Don't use his files though. They're old.
comstockload said:
Get a copy of your current M rom for the firmware you currently have and download that. Remember, we're talking full roms not updates. Now get the latest N rom for your device (full ruu.exe). Now you have options. I would flash the N rom, then the latest TWRP, then LeeDroid. Any problems, and you can go right back to M. I always use TWRP 3.0.2-6 with M. So if I go back to M I flash that version of TWRP (from within TWRP itself) first. Take your time. You can do this. You can get the latest N rom from HTC's website. To get your M rom you'll have to search for it using your firmware numbers. Someone should have a copy.
Click to expand...
Click to collapse
Yeah I think you're right. I made it this far lol. But the N rom from HTC would just be the unlocked N wouldn't it, not Verizon? I know the Verizon ruu is over in the Verizon HTC 10 forum here so I could get that. Also I think I need to go brush up on firmware vs rom I tend to think they're the same thing but they're not, right?
Launchpadmcqu4ck said:
Yeah I think you're right. I made it this far lol. But the N rom from HTC would just be the unlocked N wouldn't it, not Verizon? I know the Verizon ruu is over in the Verizon HTC 10 forum here so I could get that. Also I think I need to go brush up on firmware vs rom I tend to think they're the same thing but they're not, right?
Click to expand...
Click to collapse
I see. By "unlocked" you mean the US unlocked GSM HTC 10. I wouldn't mess with trying to alter your radios right now. Yes, stick with Verizon on everything. LeeDroid should run fine with that. Installing a new HTC rom changes your firmware. It will be updated as you go to N. If you decide to back to M, it will be downgraded. Installing a custom rom won't change your firmware. A full rom is composed of several components. The firmware is one component.
comstockload said:
I see. By "unlocked" you mean the US unlocked GSM HTC 10. I wouldn't mess with trying to alter your radios right now. Yes, stick with Verizon on everything. LeeDroid should run fine with that. Installing a new HTC rom changes your firmware. It will be updated as you go to N. If you decide to back to M, it will be downgraded. Installing a custom rom won't change your firmware. A full rom is composed of several components. The firmware is one component.
Click to expand...
Click to collapse
Ohhh okay I follow. Yeah sorry I did mean the GSM Unlocked model, I bought direct from HTC. But I couldn't get it to work on unlocked firmware with Verizon so I ended up flashing the Verizon ROM and radio last year.
So I'll grab the Verizon RUU and flash that, then LeeDroid. And update my TWRP. Its long over due anyways lol
Can't thank you enough for your help. I'm going to give it a shot this weekend I think. I really want to run LeeDroid!