Related
Ok, so last night my phone downloaded the update (guessing Gingerbread). I'm still running 2.2.1 on my Thunderbolt, as I was out of the country for the past few months. I caught the phone before it completed the installation and thought that if I removed the PG05IMG.zip file from the sd card, that would prevent it from being able to install the update. I turned the phone back on and it began to attempt to install the update again. I would like to flash a new ROM to the phone (as I was simply rooted without a custom ROM before) so that I am running 2.3+ but I don't want to have to re-root the phone. I would like to be able to back everything up before I flash a new ROM. How do I prevent the phone from installing the OTA update that was inadvertently downloaded last night , which will unroot my phone??
Please help! Thank you
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Someone fee free to correct me, but if you flash the CWM recovery it will prevent the update from happening?
Essentially, I just use the phone for wireless tether, so that's mainly why I root. Doubt that changes much of anything...
hallstevenson said:
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Click to expand...
Click to collapse
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
tomgillotti said:
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Click to expand...
Click to collapse
That's a common problem as I recall from a few weeks back. I saw threads about it but never read them as I wasn't affected. I don't know if it's a dead-end or easily fixed or complicated to fix...
Sent from my ADR6400L using XDA App
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
tomgillotti said:
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
Click to expand...
Click to collapse
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Thread moved to Q & A
tomgillotti said:
Any thoughts on how to prevent VZW from pushing this update from now on?
Click to expand...
Click to collapse
Install a non-stock ROM. Don't worry, you can get Sense-based ones that won't be anything "new".
It appears that VZW will eventually force the update so there's no way that I'm aware of to stop it while running stock (even rooted stock).
tomgillotti said:
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Click to expand...
Click to collapse
Flash a ROM that has the update. There are a few around here that are 2.11.605.5 that you flash in Recovery so that it'll stop bugging you to update. Just pick one that is already rooted. You can do a backup of your currrent rom, flash the 2.11.605.5 then restore your data and your all set....
jv
There are a couple threads on preventing ota updates. A quick search will tell you what file to rename and how to.
Sent from my infected thunderbolt.
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Gabewalters said:
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Click to expand...
Click to collapse
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
shreddintyres said:
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
Click to expand...
Click to collapse
I have only edited one /system/app file and it was to paste the Svoice app to see if it would work. I am pretty sure I deleted it though. Would this be why? And what do you mean by hitting the factory reset?
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
tkdsl said:
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
Click to expand...
Click to collapse
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
I checked the Sticky on the Dev Section and they don't cover this type of damage.
This means I have to send my prime to ASUS. dang it.
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Gabewalters said:
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
Click to expand...
Click to collapse
I tried restarting with the recovery kernel and I get an android logo laying down with red exclamation mark. not sure what that means how to fix that yet.
---------- Post added at 11:52 AM ---------- Previous post was at 11:44 AM ----------
MRCANNADY said:
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Click to expand...
Click to collapse
the only thing is, I did not change system files on my prime, I kept it stock. and I have received updates and updated them before. I just found out that the repair center for ASUS in Los Angeles does not service Primes.
The update may have bricked your prime. Although updates succeed with some devices they can fail with others. There is a long history of such issues across platforms.
Sent from my Transformer Prime TF201 using Tapatalk 2
try a hard reset.... insert a paperclip into the hole by the SD card to reset.
If not ping Gary Key or the other Rep, I forget the name and see if they can have an Asus tech offer some other solution. If not RMA it is..
just dont say its rooted
good luck!
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
sledgie said:
I just wanted to have a little post for those of you like me that may have tried updating after downloading the .28 OTA update, then the Prime freezing on the Asus Splash Screen and not rebooting...I found the solution after finally downloading the update this morning from Asus' TW site.
I only have the Prime as my computer and I have an Android phone. No PC for me - was going to try to use a friends last night to get into ADB but it just wasn't happening.
So for me - this is what I had to do.
If after your prime reboots you are still stuck on your asus splash screen, and nothing will get it to boot up - do this:
You must know your Prime's version of the update.
Goto ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF201/ or check cky2000's thread right here
forum.xda-developers.com/showthread.php?t=1429873
Download the **COMPATIBLE** update of .28 (I tried .21 plenty of times - .21 would not update my Prime)
If on an Android phone (like I was) goto ES File Explorer and open the **UpdateLauncher.zip file
It should say something like **_epad-user.9.4.2.28.zip
Extract the file to the root directory of your microSD card
Now, goto your microSD card
rename the **_epad-user.9.4.2.28.zip to
EP201_SDUPDATE
**don't rewrite the extension so that it's EP201_SDUPDATE.zip.zip, ES File explorer will only allow you to rename the name, not file extension**
You should now have EP201_SDUPDATE.zip on your microsd
**make sure you charged your prime at least 30 min if it turned off previously**
Put microsd in your Prime
Hold the Volume Down button and the Power Button until it resets and something is written at the top asking if you want to boot into a certain mode press volume up.
Immediately press Volume Up. Make sure Microsd with EP201_UPDATE.zip is in Prime.
It will start to switch to the Android Operating Mode screen with the Android lying sideways with some nuclear fission animation going on.
Blue status bar should start within 3 minutes.
Reboot and rewrite should take approximately 5-10 minutes. When done, your About should show .28 update. Hope this helps anyone who was in the same boat as me. I believe my Prime was bricked a certain way - not sure how.
Click to expand...
Click to collapse
Sent from my VS910 4G using Tapatalk 2
I had the same problem. My Prime is on its way to Asus. Does anyone know what their procedure in these cases? Do they reinstall the system and ship the tablet back or is there more to it? I take it this is all under warranty since the tablets were not unlocked?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I don't need it, but it's nice to know with stock recovery. I thought recovery was just missing.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I had same issue, just fixed it using this guide! Many thanks to author too!
It's Alive and thank you again for the post and the link, I was really worried about the
If anyone else runs across this thread, you guys don't give up so early. If your prime shows a sign of power, it's fixable without the prime leaving your house.
Congratulations to the guys who are now back up and running. That's amazing. I know how scary that can be to brick an expensive device.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Dont you need to have to be unlocked to be able to install .zips from recovery?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Gabewalters said:
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Click to expand...
Click to collapse
He likely means make sure you download the proper sku version. For example, if you have a u.s. prime, can be seen in settings and about tablet info, then you need to download the version for u.s. primes. If you ww. Then you need to download version for ww. If you De. Version, then you need to download De version for your prime.
So I downloaded the right version but when you unzip it, you get a folder, not another zip file. Any help?
EDIT: Figured it out. Apparently unzipping and then moving to the sd card isnt the same as moving to the sd card and unzipping.
Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
K-OtiK said:
Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
Click to expand...
Click to collapse
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
ellisz said:
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
Click to expand...
Click to collapse
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
K-OtiK said:
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
Click to expand...
Click to collapse
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
I have the same issue, however I have not tried to wipe yet. I tried the No-Wipe factory restore, however odin fails during the write every time...
Maybe it would work for you:
http://forum.xda-developers.com/showthread.php?t=2301259
K-OtiK said:
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
Click to expand...
Click to collapse
Full wipe, custom splash gone
Using this link as a guide http://forum.xda-developers.com/showthread.php?t=2301259
and this specific recovery image for the VRUEMJ7 http://forum.xda-developers.com/showthread.php?t=2507253
I was able to completely wipe (and unroot) my dad's verizon galaxy S4. It no longer has the custom splash screen (which was created by Vroot)
The user lordazoroth originally posted this method here in the T-Mobile SGSIII forum. However, I have confirmed that it works with the Note 3 (at least with the Verizon variant) with one small difference. Feel free to give us both a "THANKS" if this helped you out.
You can disable the OTA Update notification by following the steps below. Just be aware that there is a small change in STEP #3.
Solution:
Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear. (My phone rebooted and tried to install the update - this is the point where my Note 3 gave the update failed notification. I just rebooted the phone and went to STEP #2.)
Step 2. Disable otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
(NOTE: The difference in STEP #3 for the Galaxy Note 3 is that the [FotaClient.apk] is named [LocalFotaClient.apk] instead of just [FotaClient.apk]. All of the other steps are the same.
Continue running JB 4.3 and enjoy your Note 3 without that nagging update notification!
But the kitkat update is awesome... so you might want to reconsider doing this
Sent from my Note 3 using Tapatalk Pro
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
lmike6453 said:
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
Click to expand...
Click to collapse
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Grompy said:
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
TMFGO45 said:
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I personally use ROM Toolbox to do it
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
As of this morning...Verizon seems to be trying to "ram the update" onto your note 3
I was rooted and safestrapped on MJE and when I unplugged my phone from the charger this morning...I had a notice that the update failed to install.
I had previously downloaded, but removed the download.
Sent from my Note 3 via Tapatalk
boamuro said:
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
Click to expand...
Click to collapse
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
LeftyGR said:
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
Click to expand...
Click to collapse
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
boamuro said:
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
Click to expand...
Click to collapse
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
LeftyGR said:
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
Click to expand...
Click to collapse
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
boamuro said:
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
Click to expand...
Click to collapse
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Hulk0069 said:
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
boamuro said:
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
Click to expand...
Click to collapse
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Hulk0069 said:
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
boamuro said:
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
Click to expand...
Click to collapse
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
mwshows said:
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
Click to expand...
Click to collapse
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
boamuro said:
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
Click to expand...
Click to collapse
Unfortunately no. Once you have nc4 loaded you cannot go backwards.
<Note3>
bummer
Just checked updates and there it was.
gaww said:
Just checked updates and there it was.
Click to expand...
Click to collapse
Installing now, I wonder what the exact changelog, wish they have more info with these updates
champ784 said:
Installing now, I wonder what the exact changelog, wish they have more info with these updates
Click to expand...
Click to collapse
Please post how things went - especially if you are rooted (?), as its easy to end up unrooted at times.
OTA is failing for me after unrooting. I also restored the latest restore.img from the relevant thread before I attempted to update.
Anyone with root able to get OTA installed?
NotATreoFan said:
OTA is failing for me after unrooting. I also restored the latest restore.img from the relevant thread before I attempted to update.
Anyone with root able to get OTA installed?
Click to expand...
Click to collapse
I have not updated, but it will continue after rebooting - is there any way to stop it ?
gaww said:
I have not updated, but it will continue after rebooting - is there any way to stop it ?
Click to expand...
Click to collapse
The update was already downloaded to my phone, but did not attempt to install until I started it manually.
NotATreoFan said:
The update was already downloaded to my phone, but did not attempt to install until I started it manually.
Click to expand...
Click to collapse
I am not so worried about rerooting if it is necessary, but am very worried about getting wiped. How did yours come out ?
gaww said:
I am not so worried about rerooting if it is necessary, but am very worried about getting wiped. How did yours come out ?
Click to expand...
Click to collapse
I'm all set. No wipe, and rooted again on 10.0.31.
NotATreoFan said:
I'm all set. No wipe, and rooted again on 10.0.31.
Click to expand...
Click to collapse
Did you have to unroot before updating ?
Never-mind had to unroot it would not work otherwise. But still wont finish - maybe because i may still have a different then stock kernel even though I unrooted.
gaww said:
Did you have to unroot before updating ?
Never-mind had to unroot it would not work otherwise. But still wont finish - maybe because i may still have a different then stock kernel even though I unrooted.
Click to expand...
Click to collapse
You need to unroot, and also make sure you have the reserve.img partition restored. If you unlocked the bootloader after the .27 OTA, reserve.img is deleted during unlock.
NotATreoFan said:
You need to unroot, and also make sure you have the reserve.img partition restored. If you unlocked the bootloader after the .27 OTA, reserve.img is deleted during unlock.
Click to expand...
Click to collapse
I had read something about that file earlier, but forgot about. I spent hours trying to get it updated to no avail. i will search, but wondered if you could show me the way to do that,
gaww said:
I had read something about that file earlier, but forgot about. I spent hours trying to get it updated to no avail. i will search, but wondered if you could show me the way to do that,
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/7t...d1925-10-0-19-fastboot-rom-ota-fixer-t4040629
Download the newest package in the first post, and then download the updated userdata.img from this post: https://forum.xda-developers.com/showpost.php?p=82141557&postcount=117
NotATreoFan said:
Go here: https://forum.xda-developers.com/7t...d1925-10-0-19-fastboot-rom-ota-fixer-t4040629
Download the newest package in the first post, and then download the updated userdata.img from this post: https://forum.xda-developers.com/showpost.php?p=82141557&postcount=117
Click to expand...
Click to collapse
Will this cause a wipe ? If so, will wait for a bigger update.
I'm not currently rooted, so my results won't matter too much atm
gaww said:
Will this cause a wipe ? If so, will wait for a bigger update.
Click to expand...
Click to collapse
No. All data will be intact. You are not formatting or overwriting userdata.
NotATreoFan said:
No. All data will be intact. You are not formatting or overwriting userdata.
Click to expand...
Click to collapse
All I have to do is to not screw up, and after having been on Samsungs since S3, where most things were straight forward and relatively easy, there is a good chance I will.
Will be doing more reading - wish there was a guide like the unlocking and rooting of the US TMo guide thread.
gaww said:
All I have to do is to not screw up, and after having been on Samsungs since S3, where most things were straight forward and relatively easy, there is a good chance I will.
Will be doing more reading - wish there was a guide like the unlocking and rooting of the US TMo guide thread.
Click to expand...
Click to collapse
It's very simple, and the script does most of the work. All you have to do is hit Enter a few times, and let it run.
Back up your data to be safe, and worse case scenario, there is an MSM tool available that will restore the phone to stock.
NotATreoFan said:
It's very simple, and the script does most of the work. All you have to do is hit Enter a few times, and let it run.
Back up your data to be safe, and worse case scenario, there is an MSM tool available that will restore the phone to stock.
Click to expand...
Click to collapse
Is there a better backup than Google Drive for data - was so easy with TWRP ?
gaww said:
Is there a better backup than Google Drive for data - was so easy with TWRP ?
Click to expand...
Click to collapse
Use Google Drive backup, but you should first temporarily turn off your password/fingerprint authentication. That's the only way to ensure a complete backup is run. That's been an issue with Google device backup as a whole since 9.0 began enforcing encryption on backups.
You can turn it back on as soon as the backup completes.
One thing I've noticed already on this update is idle battery drain with 5G enabled (connected or not) has improved dramatically.
I would suggest that anyone who re-roots after makes sure to use a freshly patched kernel pulled after the update.