I got a notice today saying that my nook needs to be updated. Apparently they are forcing TLS 1.2 and a firmware update is needed to do so. Being the update file is 278mb this is the whole ROM not just the TLS update (v1.4.4 now).
Anyone installed this and will the old rooting tools still work? I am 98% certain they won't as B&N has always tried to block such access. Is anyone still around willing to update the tools? Or even have devices to do so?
I personally still like my NT, and it does all I need from a tablet at the moment (once I rooted it and installed a different launcher that is). I *think* I disabled OTA back when I rooted, but I am not 100% certain on that. Is there a easy way to check?
I have thought about doing other ROM's but never got around to it since this still meets my needs (reading, and a couple of simple games, and email/newsfeeds).
Updated, rooted using old tools for 1.4.3, flashed nougat, works fine.
Oh COOL. I guess they didn't bother changing anything more than the TLS. Glad to see. Now I just need to dig up my old microSD and get this done lol.
Probably will do a nandroid backup beforehand just to be safe. I have a lot of customizations I don't want to lose lol.
Related
Okay, so I haven't as of yet seen a thread that appears to spell out this process. Most of you are talking about applying developer-modified patches to get to DI01, using Clockwork recovery, and things like that. For various reasons, some of us prefer to remain a bit closer to stock, and not worry about bricking with custom recovery software and whatnot. I'm one of those people, and I've seen questions here and there on how to go back to stock, and if root can be maintained or redone afterward, etc., so I decided to document here what I did to apply the official update to my rooted and lag-fixed Fascinate. Without further ado, here's the process I followed:
Ran the unlagfixme.bat script from http://forum.xda-developers.com/showthread.php?t=779597, which automatically reboots the phone
Used Root Explorer to remove the ".old" extension I had added to all system .apk files I considered bloatware (I chose to disable them, not delete them)
Rebooted the phone again for good measure
Downloaded the update, and let it install normally, after which root access was gone as expected (Superuser.apk and other apps that required root access were still present, but they wouldn't function)
Rooted my Fascinate again per the instructions in http://forum.xda-developers.com/showthread.php?t=779238, just like I did the first time (only had to do it once, not twice like some here have said); note that I followed all instructions except for the final one, which is installing Superuser.apk, as that application was still installed, and still worked fine after applying the proper permissions to su and busybox
Opened Root Explorer, and once again added .old to all .apk files that I wanted to disable and remove from sight
Rebooted again
Ran the lagfixme.bat from http://forum.xda-developers.com/showthread.php?t=779597 to re-apply the lag fix
Rebooted one final time to make sure everything was in still good working order
So there it is. I'm still running stock ROM, stock recovery, etc. I should be able to easily repeat this process any time there's a new OTA update, with minimal risk of bricking.
Helpful thanks, but I think I screwed up.
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
propylene22 said:
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
Click to expand...
Click to collapse
Just re-root, either through adb or there was a one-click out there.
Yeah, just re-root using the original procedure you used (except no need to reinstall superuser.apk), and you should be good to go.
Sent from my SCH-I500 using XDA App
Thanks for taking the time to write that up Ivorycruncher!
How would this process differ when the Froyo update is released, also having ClockworkMod Recovery installed instead of stock recovery?
I, like you, would like to have legitimate updates installed while keeping root.
I've never installed Clockwork, so I can't comment on that. When Froyo comes out, I imagine the process will be much the same, though at this point there's no way to know if the original rooting method will still work or not after the upgrade. Also, depending on what they do with Froyo, the lag fix may not be necessary anymore, and might not work without some tweaking even if it is still needed.
Sent from my SCH-I500 using XDA App
Hey guys, sorry to bother everyone with another question about the update but there are a few things I could really use clarification on if it's not too much trouble.'
I'm currently on 1.57, gingerbreak rooted, gladi ROM and sbf flashed the hsupa radio. I can't really find anything about what's done in the update so i can't even tell if it'd be worth it for me to update. Will anything happen if I don't update? I didn't have any problems with my iphone when I skipped over 3 or 4 updates...just want to make sure nothing bad will happen.
Next, if I do want to update (which I don't think I will because I'm reading that a lot of people have been having problems with some things) if there a program I can use to save all of my rooted features and re-apply them after I've updated? I read about beforeupdate and afterupdate but I can't find any information about what they do and if they'll do what I'm looking for.
I'm thinking that with this update being buggy, moto will have to roll out another update pretty soon and maybe I should just wait for that one.
Here you go: Release Notes from Motorola
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
WiredPirate said:
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
Click to expand...
Click to collapse
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
spitefulcheerio said:
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
Click to expand...
Click to collapse
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
EDIT: You cannot use this method btw since you have modded. You have to sbf first.
Dirtburgler said:
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
Click to expand...
Click to collapse
Yeah i know I once I'm updated, I can root again but I've downloaded tons of apps and changed so many settings to get this phone to run exactly how I want. I've spent a good amount of time changing little things here and there and I don't want to lose all of it!
Is there away to retain all of this information through some kind of backup or something? I have all my apps and user data backed up with TiBackup. If I go back to 1.26 and then update to 1.83, can i restore using TiBackup?
im not too keen on titanium backup other than how to use it for the most part lol. The static phone settings will be defaulted to shipping state if you go back to 1.26. there may be a way to do what you are trying but that's out of my league. These is a setting in Titanium to transfer phone settings across Rom's but i've never tried nor have i seen it on the Atrix Forum. (I never really looked for it, didnt need it, so there may be a thread on it.)
The fact that you have Gladiatrix Rom throws a wrench into the whole easy update thing. Check This if you havent already----- http://forum.xda-developers.com/showthread.php?t=1063618
same here i have no problem
WiredPirate said:
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
Click to expand...
Click to collapse
Exactly what I did and everything is working fine. Ran afterupdate after the 1.83 OTA and things are working great~! everything retained
Hey guys,
Alright, so I was on my stock rooted ROM and saw an OTA come in. I download and apply the update, but it freezes and stops the update. So I unrooted, and tried again. Still failed. So then I remember I didn't disable SafeStrap, and I go and re-root, disable SafeStrap, unroot again, and THEN try the update. Still failed.
I did delete some of the games that came with the phone (while unrooted; I didn't remove system files to my knowledge). What do you guys think the problem could be? I'd really like improved signal connectivity and eventually ICS. And Fastbooting didn't work for me the last time I used it for some reason (although I wasn't on stock ROM at the time - could that have done it?)
Thanks!
Edit: Tried factory reset, did NOT work. Looks like SBF/Fastboot is my only option. What happens if it doesn't work? I'm on stock and unrooted and everything. Maybe I just need to install the missing files? I think I only deleted thinks like NFL 12 and the similar games that were ALLOWED to be deleted. SO blown right now...ugh.
It probably was the bloatware you removed. Before the update came down, I fastbooted back to make sure there weren't any issues with the update. Several people have said that with bloatware removed, the update will fail.
How did you unroot? The only way I've done it is to fastboot it (just to be on the safe side).
I used some app called Ginger Unroot from the market. Surprisingly, it actually worked - SU operations (including SafeStrap apk tasks, SetCPU, etc) ceased function due to a lack of root. I almost feel like VZW could just reset the phone because it is TECHNICALLY not rooted and is still not accepting the OTA. Also, I have a Mac, so it's a hassle to have to borrow a friend's PC every week and try again. But I'll see. There's absolutely NO WAY to fastboot via a Mac, right?
(Also - would a factory reset put the missing apps back and allow, then, for an OTA?)
Thanks!
Things like Safestrap can prevent OTA update.
Safestrap changes the boot structure.
I removed SafeStrap though. Like, it is NO LONGER on my phone, either in bootup OR in apk form. So it shouldn't be affecting the process anymore, right?
Sorry for double post - I found a FastBoot utility for Mac that MIGHT work. Not 100% on it though, but everyone who's used it has indicated it has worked for them.
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
See, that's my problem...I got rid of apps like the blockbuster app and Madden 12...you're telling me, essentially, that I'm screwed because VZW was stupid enough to make "vital" apps deletable? Also, I deleted those apps while non-rooted. How's that for ironic...
ViaCapita13 said:
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
Click to expand...
Click to collapse
How did you reload the pre install files? Where did you get the files?
I'm having same issue on xt926.
Thank you very much for the help!
Intro: I'm on the official Jelly Bean update, and by updating lost the root I had on ICS. I was one of the unfortunate users that backed up with an older version of Voodoo OTA RootKeeper, before the program updated to account for the JB changes, so my root got wiped even though it was backed up. Well I'm tired of sitting around waiting for exploits, and I treat my tablet with care anyways, so I figure it's finally time to take the plunge and unlock so I can root the thing, right?
Plan: According to this thread, I should run the unlock tool and then flash TWRP, after that I'll be free to flash custom updates and/or replace the whole OS/ROM.
Question: Do I really need to change ROMs in order to root? I've read vague mentions of flashing a zip with the su executable and such, if that works for an unlocked TF201 with the stock JB ROM, that'd save me a lot of trouble of backing up my apps and all that jazz. Does anybody have any info on this?
EDIT: Okay, it seems I can't do it right now. I'm currently getting network access via bluetooth tethering (pdanet app), but the unlock tool seems to explicitly demand wifi, as it tells me there's no network connection available even when I can browse just fine in the browsers and such... so this will have to wait until I can access some wifi.
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD