Related
Hi everyone!
I am getting messages on my Nexus One to install a 2 part update. The first prepares the Nexus One and the second installs the update.
I already installed a custom rom from here - and the build number is ERE36B with MCR2.0
I do not want to install the updates.
My question is - how do I stop the notifications to update?
I am searching both the Nexus, and the net!
Any advice appreciated.
Ofiaich
^Same here. I'm running stock 2.2 rom (but rooted) and the notification wont go away, really annoying. I tried the update just to see if it would get rid of the notification, but even though it fails (b/c of root) the notification still comes up. Any help would be appreciated. I'm just going to switch over to a custom ROM if it doesnt go away in a week (looking at a mostly stock rom but w/ black bar )
twolves14 said:
^Same here. I'm running stock 2.2 rom (but rooted) and the notification wont go away, really annoying. I tried the update just to see if it would get rid of the notification, but even though it fails (b/c of root) the notification still comes up. Any help would be appreciated. I'm just going to switch over to a custom ROM if it doesnt go away in a week (looking at a mostly stock rom but w/ black bar )
Click to expand...
Click to collapse
This exact thread exists on the MoDaCo site where I already told the OP that suppressing the update notification isn't an option here. Your have two options. One: You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method. Two: Flash a custom ROM, or a pre-rooted stock ROM. Paul has a stock ROM with root available on his site on this page. The ROM you mentioned should be fine too if you decide to flash that. Whatever you decide to do, good luck!
Cheers!
crawler9
Sent from my Nexus.
Reboot using Quickboot. It'll get rid of the notification for 4-5 days. Rinse & repeat when it starts popping up again.
Sent from my Nexus One
Thanks for the information, crawler9.
sitinon327 said:
Reboot using Quickboot. It'll get rid of the notification for 4-5 days. Rinse & repeat when it starts popping up again.
Sent from my Nexus One
Click to expand...
Click to collapse
I heard about this method, but I just tried it and it didn't work
Notification came like 5 minutes after boot.
twolves14 said:
I heard about this in other places, but didn't work
Notification came like 5 minutes after boot.
Click to expand...
Click to collapse
Worked for me fine unless I powered off the N1...then I just would Quickboot/reboot again to get rid of it
crawler9 said:
You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method.
Click to expand...
Click to collapse
If you restore the N1 to stock is there a way to only accept 2.2 ota instead 2.2.1?
Just attempt to install it. It will fail (due to incompatible recovery) and IT WILL stop displaying. Worked for me and I haven't seen the message yet. Just don't go back to "update software" or whatever in the settings.
stuff said:
Just attempt to install it. It will fail (due to incompatible recovery) and IT WILL stop displaying. Worked for me and I haven't seen the message yet. Just don't go back to "update software" or whatever in the settings.
Click to expand...
Click to collapse
Already tried that multiple times. Comes back within a few hours. Thanks though. But i'm just going to install a custom rom on the weekend.
crawler9 said:
This exact thread exists on the MoDaCo site where I already told the OP that suppressing the update notification isn't an option here. Your have two options. One: You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method. Two: Flash a custom ROM, or a pre-rooted stock ROM. Paul has a stock ROM with root available on his site on this page. The ROM you mentioned should be fine too if you decide to flash that. Whatever you decide to do, good luck!
Cheers!
crawler9
Sent from my Nexus.
Click to expand...
Click to collapse
Thanks crawler9,
Yes, it is my thread there too! I am trying the Quickboot method and will report back.
Ah! That didn't work for me!! Got the message on reboot!
At the weekend, I will read up about latest roms and install it! Only done this once before, and that was quite a few months ago... so always a bit nervy!
Ofiaich
Ofiaich
You're using an ERE36B based ROM? That's bloody ancient!
At least upgrade to a Froyo based ROM.
Hi Rusty!
I will!
I need to read up and be sure of the steps!
I also need to read about Baking roms, where to find latest etc..
But I got a more or less free weekend to do it!
Any specific advice welcomed!
Ofiaich
The Quickboot method actually did work for me, even though it comes back on reboot, if you do "install later" it stopped harassing me for the last few days!
Thank you sitinon327 and galaxys!
ofiaich said:
Hi Rusty!
I will!
I need to read up and be sure of the steps!
I also need to read about Baking roms, where to find latest etc..
But I got a more or less free weekend to do it!
Any specific advice welcomed!
Ofiaich
Click to expand...
Click to collapse
Quick & easy solution would be Enom or Cyanogen, both well specced and upto date.
In addition, both would get you rid of the update notification.
Just to give some info: there is no way to get rid of the notification without modifying the ROM. build.prop needs to be modified with the new signature to avoid this notification when running FRF91.
Just do the install and it will fail and stop asking you... until next time you reboot your phone
Sent from my Nexus One using XDA App
Hi everyone!
I ahve now installed a Modaco Rom and my setting -> About Phone show Android 2.2 and the Build Number shows the info for the Modaco Custom Rom -
FRF91
Now setting up screens as I like them!
Thank you to all for replying and giving advice.
Ofiaich
deleted by user
I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Nick James said:
I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Click to expand...
Click to collapse
I believe you are stuck like me! I was using a jailbroken iphone which would block any update from apple and I got used to that. I forgot to freeze the updater and it automatically updated my brand new s4 that I had just rooted and tweaked to my liking just a few days ago :crying::crying::crying:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You guys are on hold right now.
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
scream_clarity said:
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
Click to expand...
Click to collapse
some are seeing, even if they are rooted, it will say official and do the update, lose root after, but it has been seen.
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
Avoid all updates by flashing custom roms. You can always go back to factory stock, unrooted and untouched. But this way, you can see what updates do what, and then decide.
The Ax says, just a helpful tip.
I tried to avoid the update but lost the battle when I plugged my phone in to charge and walked away! I should have froze those services listed in another thread. I had no idea. Its only time... Hopefully
Sent from my SAMSUNG-SGH-I337 using xda premium
I don't mean to make matters worse for you, but stories like these are really depressing. I sincerely hope that some of our advanced Devs will find a solution for MF3 root soon.
And now for the potentially helpful part: AT&T typically has a 14 "buyers remorse" policy. They'll take back the handset (so long as it is in perfect condition) for ANY reason and exchange it for another (or same one, as far as I know). Two caveats:
You will likely be forced to pay a $35 re-stocking fee. Might be worth it for root/ROMs though!
You can only do this once per purchase.
Otherwise, you'll need to wait until a solid root is found for MF3. Even still, keep in mind that your "aboot" has been patched, and now Loki will not work for you (it means no custom roms/kernels, and no custom recovery). This might be permanent, as the bootloaders are locked-down TIGHT. The Loki exploit was just a workaround, but even it is gone in MF3.
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
jeffreii said:
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
Click to expand...
Click to collapse
I did that exactly. I just ignored it. I have no idea what triggered my phone to do the update. I checked just now and even when I plug my phone in, Kies doesn't even open. I'm not sure what I did... Its really annoying though.
I'll keep my fingers crossed.
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
xamadeix said:
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm not sure but if I had to guess I would think not.
Just curious, when I first got got the phone and rooted twice, I became unable to perform profile/prl update along with software update checking as well. I also couldn't do a ##786 or ##72786. I really want to root again with MF9 to do the hotspot mod. Anyone els ecome across this issue and can offer any advice I would really appreciate it.
titans1187 said:
Just curious, when I first got got the phone and rooted twice, I became unable to perform profile/prl update along with software update checking as well. I also couldn't do a ##786 or ##72786. I really want to root again with MF9 to do the hotspot mod. Anyone els ecome across this issue and can offer any advice I would really appreciate it.
Click to expand...
Click to collapse
I use aosp 95% of the time I've had my GS4 and I never update prl/pro and I have lte when other people who are completely stock tw don't and have to update to get it. Not sure what your issue was, all tw have the option to update pro/prl maybe something was up with Sprint..? I've had no issues using Aosp and we have some killer roms (official) for this device! Maybe someone else will have a solution to this.. I used Chainfires auto root twice and always was able to update em.
flashback7 said:
I use aosp 95% of the time I've had my GS4 and I never update prl/pro and I have lte when other people who are completely stock tw don't and have to update to get it. Not sure what your issue was, all tw have the option to update pro/prl maybe something was up with Sprint..? I've had no issues using Aosp and we have some killer roms (official) for this device! Maybe someone else will have a solution to this.. I used Chainfires auto root twice and always was able to update em.
Click to expand...
Click to collapse
The error I get which I forgot to mention is "session in progress, please try again later". it only does this while rooted. I can immediately unroot and flash back to stock and everything works perfectly.
I've seen that a few times but I immediately hit update again and everything works fine.
Oh and I'm always rooted.
Esoteric68 said:
I've seen that a few times but I immediately hit update again and everything works fine.
Oh and I'm always rooted.
Click to expand...
Click to collapse
Same for me
Sent from my SPH-L720 using Tapatalk 2
I took the chance and this time everything worked perfectly! I only wanted to root for the hotspot mod so I'm glad all went well.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
A week ago, I got a prompt to update to the most recent Android version. I have a Galaxy S5 SM-G900F. Had rooted it with Towelroot in July and everything was smooth, haven't done any major changes other than SuperSU and titanium. After I ok'ed the software update, it got to like 30% or something until it crashed and rebooted. Everything seems fine, just the update didn't get installed, I'm still 4.4.2. When trying to update it, it says that my operating system has been modified in an unauthorized way (towelroot) and that I should try to download updates using Kies.
So I looked a bit for solutions, I checked the SuperSU survival mode AFTER failing the update, and now my question is, what is the best way to update whilst retaining root and all my settings, in the fastest way? Or just what is the best solution to update? Don't really want to download Kies just for this. Sorry for noobness. Thanks for any help, appreciate it.
tempest22 said:
just what is the best solution to update?
Click to expand...
Click to collapse
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
fffft said:
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Click to expand...
Click to collapse
Thanks for the answer. I'm not technically well versed, I just know that this forum is the best for people like me who need advice from the pros lol. I would rather just have the most recent update because I don't want any vulnerabilities or whatever. I haven't ever used Odin, just Towelroot and done. I don't use any roms, just factory plus root through towelroot and supersu, that's it for now. So again, how would a noob like me go about safely getting an update and having the reassurance that Towelroot will either still be there, or if an unroot is necessary, that towelroot will be able to root again? Kies? Also, is an actual OTA update still possible (I'm getting that error message) or is a computer update the only thing left?
Prof Peach said:
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
Click to expand...
Click to collapse
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
can anybody help please?
Why not find a stock rooted rom for your model and flash it?
tempest22 said:
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
Click to expand...
Click to collapse
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
metalfan78 said:
Why not find a stock rooted rom for your model and flash it?
Click to expand...
Click to collapse
I'm sorry but I really don't know what that means in this context for an update. I used Towelroot 2 months ago to root and still haven't gotten myself anx root aps or mods (but was planning on it right when the update failed). Is there not a simple way to make this update work while either 1)unrooting, then updating then rerooting with Towelroot, or 2) updating whilst retaining Towelroot?
and ecniqu
gee2012 said:
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
Click to expand...
Click to collapse
I don't think you understand what I'm asking for, or I'm just way too much of a noob, probably that. but I'd just like to update to the most recent Android version. I'm 4.4.2, got an update prompt 1 week ago, have an SM-G900F, and have Towelrooted 2 months ago. All I want is to update. How can I do this, since I'm getting the failure message that it can't be updated due to my device being modified. If I unroot with supersu, then update, then (if the update works) try to Towelroot again, will Towelroot work? Or does the new update **** with it? Or an I update with Samsung Kies, while retaining Towelroot? Ahhhh I'm so sorry for this stupid question but I really don't know
no halp?
I'm really sorry for bumping this again, but I just honestly have no clue what to do to get it updated and either retain Towelroot or be able to install it again after updating. somebody help a noob out please.
my samsung galaxy s5 , it is rooted but I would like to upgrade, I can't do the OTA upgrade so I should proceed with Kies , I would like to know whether I have to unroot my phone (how do I do that? via kies? it does not matter if it'll lose the root, I just want to be sure I would still be able to use my samsung without creating any damage)or just directly proceed with the upgrade,furthermore, my phone was a sumsung galaxy s5 tmobile but I managed to unlock it in order to use it with other carriers, if I install the original firmware and then upgrade to the newest version, can I still use it with other carriers or will return locked? thank you in advance for your help
Heya. I have a rooted verizon note 3. I see i can get the 4.4.4 ota update. So i uninstalled root via SuperSU. I get an error trying to do the ota update. Is there a way to install this update without having to use odin and flashing stock? I dont want to lose all my appz settings etc. Any help appreciated. Thanks.
Sent from my SM-N900V using XDA Free mobile app
Probably not a good idea to take the update. I'd wait until our trusty devs get ahold of the OTA and do their magic.
Yah, but i get pretty poor 4g for some reason and this update might (is suppose to) fix it. I read a lot of people have unrooted with superSU and installed the OTA update fine but for me it isnt working. Even though i dont have root.
Sent from my SM-N900V using XDA Free mobile app
lackdog said:
Yah, but i get pretty poor 4g for some reason and this update might (is suppose to) fix it. I read a lot of people have unrooted with superSU and installed the OTA update fine but for me it isnt working. Even though i dont have root.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Just install the nk1 modem. That is all you need if you are trying to get better reception.
https://www.androidfilehost.com/?fid=95897840722641747
Flash with Odin 3.09.
lackdog said:
Heya. I have a rooted verizon note 3. I see i can get the 4.4.4 ota update. So i uninstalled root via SuperSU. I get an error trying to do the ota update. Is there a way to install this update without having to use odin and flashing stock? I dont want to lose all my appz settings etc. Any help appreciated. Thanks.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
That might just of been the best error ever, especially if you use root a lot. No way to go back and no known, released root at the moment for that version. Like above me has said, try flashing the NK1 modem using Odin and see if that improves your signal any.
Well, i just have been using the stock rom, rooted with safestrap. Id like to update to 4.4.4 just to have the latest OTA with whatever various fixes it might have. Before i did the update i uninstalled anything from wanam exposed framework wise. Then i did the "remove root" from superSU. I still have the unlocked lock on the note 3 splash screen after reboot and the OTA fails....says error at install screen. I have read other people have done what i have done and the update worked. What im asking is am i overlooking something? Is it really even possible without using odin and reverting to stock even though i have read people have had sucess????
Sent from my SM-N900V using XDA Free mobile app
lackdog said:
Well, i just have been using the stock rom, rooted with safestrap. Id like to update to 4.4.4 just to have the latest OTA with whatever various fixes it might have. Before i did the update i uninstalled anything from wanam exposed framework wise. Then i did the "remove root" from superSU. I still have the unlocked lock on the note 3 splash screen after reboot and the OTA fails....says error at install screen. I have read other people have done what i have done and the update worked. What im asking is am i overlooking something? Is it really even possible without using odin and reverting to stock even though i have read people have had sucess????
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
If you want the benefits "fixes" of the latest, would be be smart to Odin stock so you are clean when you take the OTA.
lackdog said:
Well, i just have been using the stock rom, rooted with safestrap. Id like to update to 4.4.4 just to have the latest OTA with whatever various fixes it might have. Before i did the update i uninstalled anything from wanam exposed framework wise. Then i did the "remove root" from superSU. I still have the unlocked lock on the note 3 splash screen after reboot and the OTA fails....says error at install screen. I have read other people have done what i have done and the update worked. What im asking is am i overlooking something? Is it really even possible without using odin and reverting to stock even though i have read people have had sucess????
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
You do realize...that if you take the OTA...you WILL lose root. At this point in time...there is no known way to root 4.4.4 and the latest OTA.
Sent from my Note 3 via Tapatalk
how to track 4.4.4 rooting progress?
donc113 said:
You do realize...that if you take the OTA...you WILL lose root. At this point in time...there is no known way to root 4.4.4 and the latest OTA.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
I too have read ambiguous posts of people who have used the 4.4.4 OTA on a towelroot'ed Verizon Note 3s. I've been skeptical that this would work and keep root so thanks for clarifying.
I have a question though. Where should I look to keep track of the latest news about a root technique for a Verizon Note 3? Also, is there a place to contribute to a bounty for someone who can figure this out?
I ask because If you google "samsung note 3 Verizon 4.4.4 towelroot" there are tons of hits, but most of them are from eons ago and while I root my phone, I am not a developer, and so don't know the lay of the land. In the past I've just searched for "root verizon samsung note 3" and crawled through the resulting mound of irrelevant material until eventually I found the answer. Or is the answer simply that every few days I search again to see if anything new pops up?
I realize this is a totally newbie question, but I'm a long-time newbie: I've been rooting my phones for years but I don't have a lot of phones and updates only come out every so often so I never really move up the learning curve of how to do this quickly and easily. I suspect others have the same problem. Any advice would be greatly appreciated!
lackdog said:
Yah, but i get pretty poor 4g for some reason and this update might (is suppose to) fix it. I read a lot of people have unrooted with superSU and installed the OTA update fine but for me it isnt working. Even though i dont have root.
My phone messed up earlier this week and I had to use repair assistant and when I did it updated me to NK1 KitKat 4.4.4 and I lost root and can not get it back plus the reception issue is still terrible.
Click to expand...
Click to collapse
Marlon1691 said:
I too have read ambiguous posts of people who have used the 4.4.4 OTA on a towelroot'ed Verizon Note 3s. I've been skeptical that this would work and keep root so thanks for clarifying.
I have a question though. Where should I look to keep track of the latest news about a root technique for a Verizon Note 3? Also, is there a place to contribute to a bounty for someone who can figure this out?
I ask because If you google "samsung note 3 Verizon 4.4.4 towelroot" there are tons of hits, but most of them are from eons ago and while I root my phone, I am not a developer, and so don't know the lay of the land. In the past I've just searched for "root verizon samsung note 3" and crawled through the resulting mound of irrelevant material until eventually I found the answer. Or is the answer simply that every few days I search again to see if anything new pops up?
I realize this is a totally newbie question, but I'm a long-time newbie: I've been rooting my phones for years but I don't have a lot of phones and updates only come out every so often so I never really move up the learning curve of how to do this quickly and easily. I suspect others have the same problem. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It likely is possible to update and keep root. But if after updating you screw up a mod, etc. and need to get back to stock you will lose root permanently.
flashing modem
leroybrute said:
Just install the nk1 modem. That is all you need if you are trying to get better reception.
https://www.androidfilehost.com/?fid=95897840722641747
Flash with Odin 3.09.
Click to expand...
Click to collapse
Hello I see flashing with odin 3.09, I think I have 3.29- does it matter and I am on biggins rom as well. You dont have to unroot or anything?
Thanls,
TJ
tjmethod said:
Hello I see flashing with odin 3.09, I think I have 3.29- does it matter and I am on biggins rom as well. You dont have to unroot or anything?
Thanls,
TJ
Click to expand...
Click to collapse
There is no Odin 3.29 out. Just Google Odin 3.09 and download to your desktop if you don't
already have it. Then flash the modem to your phone. Don't unroot.
Odin 3.09
leroybrute said:
There is no Odin 3.29 out. Just Google Odin 3.09 and download to your desktop if you don't
already have it. Then flash the modem to your phone. Don't unroot.
Click to expand...
Click to collapse
Hi I did have the 3.09, plugged in as media & media 3.0 but it didnt work- any ideas?... I think I have plenty of space. Attached is is the screen I get on Odin.
Thanks,
TJ
tjmethod said:
Hi I did have the 3.09, plugged in as media & media 3.0 but it didnt work- any ideas?... I think I have plenty of space. Attached is is the screen I get on Odin.
Thanks,
TJ
Click to expand...
Click to collapse
You need to put your phone in download mode before plugging into pc. Make sure debugging is checked in developer settings.
Thanks…
I forgot the download mode and to check the debug- always in a rush…
Ill check it when I get in- thanks again
tjmethod said:
I forgot the download mode and to check the debug- always in a rush…
Ill check it when I get in- thanks again
Click to expand...
Click to collapse
No, I thank you... Ha
GoNavyMike said:
lackdog said:
Yah, but i get pretty poor 4g for some reason and this update might (is suppose to) fix it. I read a lot of people have unrooted with superSU and installed the OTA update fine but for me it isnt working. Even though i dont have root.
My phone messed up earlier this week and I had to use repair assistant and when I did it updated me to NK1 KitKat 4.4.4 and I lost root and can not get it back plus the reception issue is still terrible.
Click to expand...
Click to collapse
Verizon forced me to upgrade before they would troubleshoot my phone.
I was not able to do it OTA, but using the Verizon upgrade tool works.
Now I lost root, & I gained a whole bunch of bloatware. Very frustrating
Click to expand...
Click to collapse
Brainfire2 said:
GoNavyMike said:
Verizon forced me to upgrade before they would troubleshoot my phone.
I was not able to do it OTA, but using the Verizon upgrade tool works.
Now I lost root, & I gained a whole bunch of bloatware. Very frustrating
Click to expand...
Click to collapse
That is why you should always tell them you are on the latest firmware
Click to expand...
Click to collapse
I read about 4.4.4 and didn't like what they took away from 4.4.2. I won't go to it. If I were you I'd 'towelroot'- (get the simple steps on xda), and 'beanstown 106' has all the firmwares for these phones, put the nc4 on w/ 4.4.2, then install biggins rom v7, then upgrade via dirty flash with 8.0 then immediately w/ 8.3- fast touch response and after about 3-4 days, you'lI be getting twice the battery life… I jumped up to the new v9 but they dont have the theme for it yet. I miss the Kromex blue on black…