Develop Bugs

Sprint Updates, do I want them? (rooted phone)

Hi all. I am a proud EVO user and generally love the phone. It's rooted for use w/ wifi tether. Not really using root much beyond that. Question, do I want or need the Sprint system update(s)? I had read that unrooting my phone could keep it from being rootable later on. Will the phone perform any better w/ the updates? Are there alternatives? My last phone was WM and it had a custom ROM. What do you all think?
Thanks!

lawyeradam said:
Hi all. I am a proud EVO user and generally love the phone. It's rooted for use w/ wifi tether. Not really using root much beyond that. Question, do I want or need the Sprint system update(s)? I had read that unrooting my phone could keep it from being rootable later on. Will the phone perform any better w/ the updates? Are there alternatives? My last phone was WM and it had a custom ROM. What do you all think?
Thanks!
Click to expand...
Click to collapse
Anything Sprint releases ends up on here rooted and ready for flashing (usually within hours). I would not do any ota updates knowing that.
Sent on the go from my HTC EVO

Thanks, that being said, should I flash to a custom ROM? I'm sure all this has been asked and answered, so appologies to that. Also, if i do that, should I back up my current apps (what should I use) and when i restore can i restore to a newly flashed phone or is part of the back up process the system files?

People do create rooted versions of the stock ROMs that Sprint releases. So, you can try custom ROMs, but you don't HAVE to. You can get the latest one here:
http://forum.xda-developers.com/showthread.php?t=874251
Here's a thread where you can grab all of the latest Radio, WiMax, PRL, etc updates:
http://forum.xda-developers.com/showthread.php?t=715485

No, installing and official OTA can cause you to lose root. Download the rooted version ^ or stall the latest update for your rom.

New convert from launch day Evo 4g...which modem, update, etc?

So...I was going to save my upgrade subsidy for when the Galaxy Nexus or SGS3 hit sprint later in the year but the charger in my Evo died today and it wasn't the known USB port issue (mine had gotten chipped on the little bit of plastic inside where the contact pins are) so they couldn't do a repair or swap for free. Anyway, I had kinda wanted this phone anyway and with discount and selling back my Evo it only cost me like $110 plus tax.
I had hacked and rooted my Evo every which way but I'm now back to being a noob. I got a prompt to update my software on first boot but I don't want to update anything that will make it harder to root or mod later on once I get familiarized with the new handset.
My software version is EG30 right now. Do I want to avoid any ota updates like on most devices? What should my course of action be? I see all of the different builds mentioned on the forums but I'm not sure which ones to go for and which ones to avoid. Do people recommend rooting and flashing a specific build for now? I tend to go stock for a week or so when I get a new phone and then flash a new rom once I know what's available. With the update prompts I might want to jump ahead on that process now.
By the way, my sprint store people were awesome. When they wanted to test my Evo I kinda worried about it being rooted and running cyanogen. I couldn't flash back to stock since it would not charge and I didn't have a spare battery. They just said "well htc supports unlocked bootloaders now so as long as its not a software issue we can try to fix it. If its a software issue we would just need you to flash back to stock". Turned out to be a hardware issue but I must say that was a refreshingly fair attitude. Some places won't even look at a rooted/unlocked phone even if there is no software issue.

I also came from the EVO. I love this phone!!!! Everyone here is very helpful. As far as ROMS go, I would start with Calkins with the Rogue Kernel if you plan on using TW. That is what I am running with the optional ICS theme. Love the way that it looks. I can't say enough about how great this phone is. Great performance and batterylife. I tried the EVO3D for all of 3 days and returned it for this phone. Night and Day difference. Welcome to the E4GT family

I would go take a look at qbkings videos on how to everything. and also sfhubs auto root thread.but it doesn't lock you out of being able to do anything by upgrading like htc does. by the way calkulin has the el29 rooted stock. then after getting that I would odin the el29 modem. el29 is the current update for this phone. welcome to the community tho! happy flashing!

patrao_n said:
I would go take a look at qbkings videos on how to everything. and also sfhubs auto root thread.but it doesn't lock you out of being able to do anything by upgrading like htc does. by the way calkulin has the el29 rooted stock. then after getting that I would odin the el29 modem. el29 is the current update for this phone. welcome to the community tho! happy flashing!
Click to expand...
Click to collapse
So if I let the OTA update go through I won't be screwing myself over for later in the week when I want to start trying out new roms? Just wanna make sure
On Evo it seemed to mostly consist of getting root, installing custom recovery, then you could try out any new kernel, radio, or rom you wanted. Is it relatively similar on the sgs2? Is there anything I want to avoid now to save on headaches later?
Thanks for the tips and the welcome! Between my girlfriend's brand new iPhone getting stolen on Friday and my charger breaking this weekend it's been a bad phone week for us.

nope. I however wouldn't even deal with the update. I would just odin a kernel then from the recovery you could flash any rom you want to try out. I definitely recommend calkulins 2.8.1 or blu kuban v1.1.2 odexed. they come with kernels already installed. then I would either odin or flash a modem. I used recovery to flash all my stuff. if you want a purely stock rom, then in the dev section calkulin has a stock rooted el29 rom. which is just the rom plus root. remember almmost all roms are flashed through cwm. so definitely odin a kernel first. there is a wiki sticky thread in dev section that has all the stuff. btw with odin make sure to ONLY flash kernels through pda. if you put kernels or roms in phone it Will brick it. also never disconnect your phone while odin is flashing.
---------- Post added at 02:53 AM ---------- Previous post was at 02:49 AM ----------
also to answer your other question once you get a kernel on your phone you can flash whatever you want. I a tually prefer it to using odin. radio kernel rom. btw unlike htc new recoveries have to be bundled in with kernels. so if you wanted a different recovery like rogue u have to grab a rogue kernel. I love the newest rogue kernel. it has a touch clockwork mod recovery in it. its called rogue "hitman"

updating to kit kat flashing?

hey guys been a while but back it it..im on jelly still and rooted and i cant get the OTA update.. can i just flash the kit kat? not sure what one to download.. i just want a stock base rooted version..im on att but have tmo note 3 and going back to tmo later this month..
do i have to factory restore clean via kies first?
thanks guys

markysd said:
hey guys been a while but back it it..im on jelly still and rooted and i cant get the OTA update.. can i just flash the kit kat? not sure what one to download.. i just want a stock base rooted version..im on att but have tmo note 3 and going back to tmo later this month..
do i have to factory restore clean via kies first?
thanks guys
Click to expand...
Click to collapse
Yea, if you wanted the ota, in short you would have to grab the stock non rooted firmware kies , I prefer Odin and just get back to stock stock. You may be able to hide root, and grab the ota but I've never got into that. I prefer to back up whatever needs it via titanium saved to ext card, wipe completely and just start fresh with the kk update. That way you getbthe modem, you get the boot loader, the new partitions etc etc and IMO a more solid user experience. Some may beg to differ, but, updates are updates for a reason and ne6 is far more stable and reliable than nb4 was. Kernel source is cleaner, ROM bits were cleaned up, volte was added and its just better. If you've never checked tweaked ROM out before man, you are missing out. Its the way touch wiz was meant to be, dwitherall is a friggin smali destroyer, and his work is the work others strive to do. Thats just my two cents and what I would do, but if you wanted to just flash a kk ROM right now, ya probably could, but you aren't getting the benefits of why is was the upgrade in the first place. Users may disagree with my statement but, the real devs, would agree ne6 is a far more solid base to be on, and once tweaked is done is game over. Thanks for the time man

[Q] Most efficient way to update my GS3

http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.

If you don't want to do the research or take the time to go through the trouble of reading through these forums, then the most efficient way will be to remain stock unrooted and update via the approved methods from your carrier and/or Samsung (OTA and/or Kies usually). All software versions from ICS on up (non international S3s are now officially on KitKat) have been covered extensively by now so I doubt anyone is going to entertain your direct request for information. There are many things you need to be aware of, such as but not limited to how the new bootloaders and KNOX, as well as how custom roms and kernels, are working together in the big picture of things.
NOTE: Regardless of which route you take, no one in this forum, including myself, is responsible should anything happen to your phone. Anything you do to your phone is at your own risk, including official updates from your carrier and Samsung.

xshadowinxbc said:
http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.
Click to expand...
Click to collapse
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.

BWolf56 said:
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.
Click to expand...
Click to collapse
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.

xshadowinxbc said:
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.
Click to expand...
Click to collapse
Kernel will be overwritten in the flashing process. All you gotta do is make sure you recovery is up to date if you go the custom ROM way.
We don't make suggestions as for what ROM/kernel to use to avoid flaming and it also comes down to user preference. Although, I do suggest starting to look at some custom ROMs (most of them come with their own kernel but can also flash another one). It will most likely come down to AOSP vs TW (stock) base.
The closest to a suggestion I can make is to look at the top threads in the Dev section, those are the most "popular" ROMs/kernels.

Alright, looking around at the various threads in the development section I see that most of them look pretty simple to install. Just download the zip, reboot into clockwork and install after doing some resets.
I notice that some of these require a new bootloader/modem, though... I haven't seen those terms when I last did this. What are the general installation instructions for those; the same as custom roms? Can they brick your device (assuming that I even pick the one for my device)? I'll probably just install something that doesn't need me to update the bootloader/modem to make things simple.

For the most part, if you've updated to 4.3 you will be able to flash any available roms. The catch is once on 4.3, you cannot downgrade your firmware.
Firmware is updated either by ota or flashing with Odin.

I went ahead and got the Slimkat because the instructions for it were pretty easy. There are some unpleasant changes about it that I would like some assistance on, but I suppose that would go in the dev thread to ask about those. Thanks for the info, it helped give me some confidence about just trying it out. Like I said a little iffy about some of the things but overall I like. At least it hasn't randomly crashed on me yet, and getting all of my apps back was as easy as having TitaniumBackup extract them from my Nandroid backup.

[Q] Confused...

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