Rooted: Not Bricked after OTA? - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Ok folks, Noob question I’m sure but here it goes. This is the first android device I have rooted. While I was out of town my wife noticed an OTA update available. Not realizing there should be any concern she allowed the OTA to go through. I assumed the worst when she told me at about it. However the update went through completely fine, SU stayed and seems to work beautifully. The only thing was I had to reapply the Hulu tweak. So here is my question, I was under the impression that root+OTA = brick. Obviously that is not %100 of the time, did we simply get very lucky? Was I wrong to be afraid of the OTA’s while having root? I haven’t rebooted the device since the update, is there a reason I should expect any issues when one is required? Thanks in advance for your thoughts.

BUMP No thoughts? Have I posted this in the wrong forum?

Related

[OTA UPDATE] 45.2.5.en.US

It looks like Motorola has officially updated the device. I found it about 2 hours ago when I was on the road. To my surprise, there is still no thread on this that I noticed.
Hopefully, we can get some info on this update as it pertains to those who either root or unlock. I don't have the information but hopefully, someone will brave it and attempt to get it. Such questions that I would like to see answered include:
- Do you lose root after the update?
- If you lose root, does the dock root method still work? Does the dockless method still work?
- If you installed bootstrapped or unlocked recovery, does this update cause any problems? Are backups made before the OTA still good to use after?
Well, for those of us who are dock rooted, or at least for me, I can say that the update goes seemingly through the entire process and then it comes back and says that the update failed. I check for updates and it is there again asking me to try. Not sure what's up.
This is new and exciting.
Sent from my MB855 using xda premium
Root is lost with update
My phone updated yesterday and I lost my root. I will try the photon root method again to see if I regain root. I will keep you all posted.
if im not mistaken this is the ota.. on which i can confirm that afterwards you can root again. its just like any other phone tho updating will kill root
Well it will not update for me. "Update failed" every time. I am dock rooted and installed boot strap recovery (CWM). Any suggestions?
enigmatl said:
It looks like Motorola has officially updated the device. I found it about 2 hours ago when I was on the road. To my surprise, there is still no thread on this that I noticed.
Hopefully, we can get some info on this update as it pertains to those who either root or unlock. I don't have the information but hopefully, someone will brave it and attempt to get it. Such questions that I would like to see answered include:
- Do you lose root after the update?
- If you lose root, does the dock root method still work? Does the dockless method still work?
- If you installed bootstrapped or unlocked recovery, does this update cause any problems? Are backups made before the OTA still good to use after?
Click to expand...
Click to collapse
EDIt: Nvm this is old news bud. Posts everywhere
-DJ
Sent from my MB855 using xda premium
Lost my root torpedo version
Sent from my MB855 using XDA App
Re-root after update confirmed
I just re-rooted my phone using the dockless photon.tar method and regained root without any problems.
enigmatl said:
It looks like Motorola has officially updated the device. I found it about 2 hours ago when I was on the road. To my surprise, there is still no thread on this that I noticed.
Hopefully, we can get some info on this update as it pertains to those who either root or unlock. I don't have the information but hopefully, someone will brave it and attempt to get it. Such questions that I would like to see answered include:
- Do you lose root after the update?
- If you lose root, does the dock root method still work? Does the dockless method still work?
- If you installed bootstrapped or unlocked recovery, does this update cause any problems? Are backups made before the OTA still good to use after?
Click to expand...
Click to collapse
Welcome to last week!!! j/k. I am glad that you finally found out about the official update. FYI there were tons of threads about ppl receiving the official update. It may not have been on the XDA sites but some of the other fan sites like androidforums, sprint users all posted that the official release was out since last tues, 8/23.
Yes you do lose root but you can just re-root it to get it back. Just do the dockless root. It is wayyyy easier since you don't have to go to a website and dl the tar file.
enigmatl said:
It looks like Motorola has officially updated the device. I found it about 2 hours ago when I was on the road. To my surprise, there is still no thread on this that I noticed.
Click to expand...
Click to collapse
When you're looking for old news, you need to look at more than the last few threads.
I heard that Sprint is coming out with their first 4g device soon.... the Evo 4g.
Sent from my Motorola Photon 4g
Okay. Some people are in serious need of a freakin CHILL PILL.
I got my notice of an update a few hours ago. I came here thinking XDA was the place, the hub for this kind of stuff. I checked like the first 20 threads and there was nothing. Neither I nor most other people are going to go through dozens of pages to look for info on this especially when as I typed the subject, XDA's search returned NOTHING.
And a note to the mods, there have been a lot of unfriendly BS answers to very good questions as of late. If a blind eye is turned to it over and over, it is gonna cost XDA it's title in the minds of many that this is THE place for information on the devices that it covers.
So enough of the unfriendly sarcastic BS answers. There's no need for crappy answers like welcome to last week especially when such a post doesn't come with a link.
That said, I will try this one more time. When I try to install the update, it always says update fails. I rooted with the dock method and installed the bootstrap recovery. Does anybody know what could be causing this to happen?
If you are having problems then flash this.. http://forum.xda-developers.com/showthread.php?t=1202666
Final build courtesy of the fine folks at MOTOROLA 8/11/11 The sarcasm was in fun. But on your end just think of how annoying it is when this happens on a daily basis. Take a couple of minutes to look through development and see all the crap people have posted. You'll see how cluttered it can get. We do appreciate that you meant well.
Sent from my Motorola Photon 4g
enigmatl said:
Okay. Some people are in serious need of a freakin CHILL PILL.
I got my notice of an update a few hours ago. I came here thinking XDA was the place, the hub for this kind of stuff. I checked like the first 20 threads and there was nothing. Neither I nor most other people are going to go through dozens of pages to look for info on this especially when as I typed the subject, XDA's search returned NOTHING.
And a note to the mods, there have been a lot of unfriendly BS answers to very good questions as of late. If a blind eye is turned to it over and over, it is gonna cost XDA it's title in the minds of many that this is THE place for information on the devices that it covers.
So enough of the unfriendly sarcastic BS answers. There's no need for crappy answers like welcome to last week especially when such a post doesn't come with a link.
That said, I will try this one more time. When I try to install the update, it always says update fails. I rooted with the dock method and installed the bootstrap recovery. Does anybody know what could be causing this to happen?
Click to expand...
Click to collapse
Maybe the difference is the bootstrap recovery installation. I rooted with the docking method but didnt install a bootstrap recovery. The OTA update went perfect today. Maybe it succeeded because i didnt have the bootstrap recovery installed? A possibility?
If you have updated webtop (dockless connection), your OTA update may fail. Replace the files with your original webtop files and the OTA update should work.
OTA update speeded up my photon
My photon is opening apps, emails, and web pages 50% to 100% faster after running the OTA update.
Holy smoking photons! My phone is BLAZING fast, google maps and navigation are nearly instantaneous, YELP populates in 1 second!!!
Isn't this just the leak from 8/11/11?
I don't understand the big deal, or why an OTA update of a leaked rom two weeks ago is being talked about in the development board?
enigmatl said:
Well it will not update for me. "Update failed" every time. I am dock rooted and installed boot strap recovery (CWM). Any suggestions?
Click to expand...
Click to collapse
Did you uninstall any system apps after rooting? If so, those will need to be restored.
When you try the update how far does it get? If the phone reboots and gets to the Android guy with the progress bar just press and hold both volume buttons at same time and it will show you the error message.
My Phone was Rooted using the Dock Method... installed the update without any issue and Re-Root it using the Dock method again. Everything still runs like a charm.

[Q] I'm I337UCUAMF3 . . . I'm screwed for rooting, aren't I?

So, I just popped online to see that, apparently, not only did I lose the chance to root my phone when my phone took the first update, apparently my phone took a SECOND update and the most recent workaround is for the previous version. So I've learned my lesson about letting my phone take any updates (I don't remember taking the 2nd one at all . . .).
What are the chances of rooting my phone at this point? Is it pretty unlikely there will be any future workarounds? I have a number of rooted apps from my last phone that I'd like to be able to use on this one. Am I screwed for being able to root my phone or is it still possible to get mine rooted?
It's really disappointing to see that they're locking the bootloader in an OTA update. That's pretty weak (and sneaky).
Edit: Sorry, missed a word in the title so it might be a bit confusing. My baseband version shows I337UCUAMF3.
jbrookley said:
So, I just popped online to see that, apparently, not only did I lose the chance to root my phone when my phone took the first update, apparently my phone took a SECOND update and the most recent workaround is for the previous version. So I've learned my lesson about letting my phone take any updates (I don't remember taking the 2nd one at all . . .).
What are the chances of rooting my phone at this point? Is it pretty unlikely there will be any future workarounds? I have a number of rooted apps from my last phone that I'd like to be able to use on this one. Am I screwed for being able to root my phone or is it still possible to get mine rooted?
It's really disappointing to see that they're locking the bootloader in an OTA update. That's pretty weak (and sneaky).
Edit: Sorry, missed a word in the title so it might be a bit confusing. My baseband version shows I337UCUAMF3.
Click to expand...
Click to collapse
Pretty sure the i337 and MF3 baseband are AT&T, not Verizon?
MF3 root thread for AT&T: http://forum.xda-developers.com/showthread.php?t=2387577
grussinko said:
Pretty sure the i337 and MF3 baseband are AT&T, not Verizon?
MF3 root thread for AT&T: http://forum.xda-developers.com/showthread.php?t=2387577
Click to expand...
Click to collapse
I'm sorry about that, I didn't notice that the phones were differentiated by carrier here. I'll post this in the AT&T section. Thanks a lot!

[Q] I -had- 4.2.2. How bad did I mess up?

Until about 30 minutes ago, I had the stock 4.2.2 that came with my S4 when I bought it.
Every day it would ask me to update and I kept on delaying it and telling it another time...
Until today, when it popped up while I was using my phone and fingers hit it into the (apparently) pre-downloaded update.
Not wanting to brick it mid-update I let it go and am now on 4.3.
While I haven't yet rooted my device, I did intend to, but haven't followed along with rooting an S4.
So my question is, how screwed am I?
skeven said:
Until about 30 minutes ago, I had the stock 4.2.2 that came with my S4 when I bought it.
Every day it would ask me to update and I kept on delaying it and telling it another time...
Until today, when it popped up while I was using my phone and fingers hit it into the (apparently) pre-downloaded update.
Not wanting to brick it mid-update I let it go and am now on 4.3.
While I haven't yet rooted my device, I did intend to, but haven't followed along with rooting an S4.
So my question is, how screwed am I?
Click to expand...
Click to collapse
Well hopefully you weren't on MDK 4.2 prior to this since that's the build you could had a true custom recovery on. Most likely though you were not since now your on 4.3.
You're not screwed you can still easily root it and install SafeStrap if you want to. I'd suggest root it and freeze SDM so you can stay on 4.3 where things are just easier. Wait for kit kat to be out a little longer and all the upgrade/root methods to be perfected
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well hopefully you weren't on MDK 4.2 prior to this since that's the build you could had a true custom recovery on. Most likely though you were not since now your on 4.3.
Click to expand...
Click to collapse
I had the root page for my build bookmarked; I545VRUDMI1
Nothing is more comforting to know that I could of done worse than I already had.
I gotta learn to do it right off the bat -- this phone is about 7 months old. No excuse to not have found time to do it
But thanks, I'll get right on it

[Q] System State "Modified"

Okay so I was browsing my phone and happened to run across the System state saying "Modified"
The issue I am having is I have never even downloaded a rooting app. The only thing close to root I have used is called Helium, which does not require root, but it can backup/restore apps+data.
I am slightly worried that if I have to send my phone in for some reason they will see this and say I have messed with the system, although I have not in the first place.
Has anyone else encountered this random issue? Other than that this phone is quite a good phone and I'm pleased with it greatly.
Did you......root your phone?
Sent from my VS985 4G
veteranmina said:
Okay so I was browsing my phone and happened to run across the System state saying "Modified"
The issue I am having is I have never even downloaded a rooting app. The only thing close to root I have used is called Helium, which does not require root, but it can backup/restore apps+data.
I am slightly worried that if I have to send my phone in for some reason they will see this and say I have messed with the system, although I have not in the first place.
Has anyone else encountered this random issue? Other than that this phone is quite a good phone and I'm pleased with it greatly.
Click to expand...
Click to collapse
Let me grab a non-rooted G3 here in a few and check. I don't know that they dont all say that. Get back to you shortly. Mine also says this; however, I did root and unlock mine.
rp201 said:
Did you......root your phone?
Sent from my VS985 4G
Click to expand...
Click to collapse
Did you fully read his post before replying? I suppose my question is as rhetorical as yours...
My interpretation was that he has not installed one rooting app. One was left to assume he had rooted the phone or did not have a rooted phone which was the basis of my question. And yes I did read his post to answer your question. I would not leave you to assume I did from my response.
Sent from my VS985 4G
no big deal that it says that. move along
If you go to the Verizon store and look at the G3's they have on display, they all say "modified" instead of "official" however when I received my phone it said "official" until I rooted it.
Sent from my VS985 4G using Tapatalk
Just flash it back to stock if you have any issues. May as well root now anyway. G3 tweak box is amazing!
Sorry for late reply, at work so hard to get on atm.
I have not touched a single rooting app to this phone since I bought it new the day they came out. I have thought about rooting it, but I am touchy when it comes to phones that are in warrenty.
Although I might just say heck with it and actually root it anyways since it's saying modified, my main concern was why it was already saying it was modified when I hadn't touched it yet. I have experience rooting/restoring phones/tablets ever since the mesmerize/desire/fascinate ages so it shouldn't be too hard
I doubt this has anything to do with it, but when it turns on from a restart/shutdown one of the verizon apps "vzrwsservice" or something like that says it has crashed and then goes away until i restart again.
Thanks for you replies though, if someone does come up with a phone that isn't rooted but says modified, I'd be interested to know so that we can figure what's causing this.
My unrooted Verizon g3 does not say modified. It says official.
veteranmina said:
Sorry for late reply, at work so hard to get on atm.
I have not touched a single rooting app to this phone since I bought it new the day they came out. I have thought about rooting it, but I am touchy when it comes to phones that are in warrenty.
Although I might just say heck with it and actually root it anyways since it's saying modified, my main concern was why it was already saying it was modified when I hadn't touched it yet. I have experience rooting/restoring phones/tablets ever since the mesmerize/desire/fascinate ages so it shouldn't be too hard
I doubt this has anything to do with it, but when it turns on from a restart/shutdown one of the verizon apps "vzrwsservice" or something like that says it has crashed and then goes away until i restart again.
Thanks for you replies though, if someone does come up with a phone that isn't rooted but says modified, I'd be interested to know so that we can figure what's causing this.
Click to expand...
Click to collapse
Hypothetical.... lets say someone bought it, played with it and rooted it or botched a root and returned it. try root checker in app store. just saying. makes more sense then someone snuck in your bedroom and took it and rooted while you were sleeping and returned it.
Another hypothetical...
Could it switch to "modified" if one were not rooted but had disabled some of the bloat? Just a thought.
Rodeojones said:
Another hypothetical...
Could it switch to "modified" if one were not rooted but had disabled some of the bloat? Just a thought.
Click to expand...
Click to collapse
As of now, I cannot tell what it was to change it to modified, I went ahead and tried a reset through the settings and it kept the modified status, did a flash restore and it finally got rid of the modified and is now stating Official.
(To note that when it was in download mode it also stated modified before I flashed it with the ToT file.)
I did also find the reason for the verizon server to crash, which I cannot find the location of the thread elsewhere, but it is due to Google+ and one of verizons apps not being compatible with each other and eventually causing verizons app to crash. The only way so far to fix it is either downgrade google+ to stock, or disable the VerizonAvsService to stop the crash at boot.
Rodeojones said:
Another hypothetical...
Could it switch to "modified" if one were not rooted but had disabled some of the bloat? Just a thought.
Click to expand...
Click to collapse
I have disabled a bunch of bloat without root and it has not changed to modified.
It's a Fact!!!
veteranmina said:
Sorry for late reply, at work so hard to get on atm.
I have not touched a single rooting app to this phone since I bought it new the day they came out. I have thought about rooting it, but I am touchy when it comes to phones that are in warrenty.
Although I might just say heck with it and actually root it anyways since it's saying modified, my main concern was why it was already saying it was modified when I hadn't touched it yet. I have experience rooting/restoring phones/tablets ever since the mesmerize/desire/fascinate ages so it shouldn't be too hard
I doubt this has anything to do with it, but when it turns on from a restart/shutdown one of the verizon apps "vzrwsservice" or something like that says it has crashed and then goes away until i restart again.
Thanks for you replies though, if someone does come up with a phone that isn't rooted but says modified, I'd be interested to know so that we can figure what's causing this.
Click to expand...
Click to collapse
I have verified for myself, that my Verizon LG G3 says "Modified" as well, yet it's a fact that I have never rooted or modified any of my system settings... I'm running Stock 6.0 Marshmallow... Go figure... Who knows with Verizon...

[Q] Fire HDX 7 - Is it safer to flash Roms and Root now?

First, I apologize if this ins't the right area but it seems like a General question.
I recently bought a Kindle Fire HDX 7" and have had it about a week now. With all the Amazon Bloat and lack of Google apps I need more out of it. I am not a beginner with flashing roms and such, my HTC One is Rooted, CyanogenModed, and has a boot loader, anyways...
I have spent the last couple days reading up on the ways to do it on the HDX 7 and heard many warnings and bricks of this device, but some of the posts are a little bit older. I can't really tell which method of Rooting/Flashing is the safest out of all the different ones. My current OS version is 13.3.2.1. Using the Safestrap looks pretty easy and from what I understand is that even if you do brick it you can recover the original?
My question is... Is it any safer to flash a Rom lately (due to the updating problems?), and how safe is just rooting it for the time being? Also, what method/tools would you suggest to use? I don't like the FireOS and would like to get it close the a standard Android and/or CyanogenMod.
Thanks for your time.
well
Eclipsys said:
First, I apologize if this ins't the right area but it seems like a General question.
I recently bought a Kindle Fire HDX 7" and have had it about a week now. With all the Amazon Bloat and lack of Google apps I need more out of it. I am not a beginner with flashing roms and such, my HTC One is Rooted, CyanogenModed, and has a boot loader, anyways...
I have spent the last couple days reading up on the ways to do it on the HDX 7 and heard many warnings and bricks of this device, but some of the posts are a little bit older. I can't really tell which method of Rooting/Flashing is the safest out of all the different ones. My current OS version is 13.3.2.1. Using the Safestrap looks pretty easy and from what I understand is that even if you do brick it you can recover the original?
My question is... Is it any safer to flash a Rom lately (due to the updating problems?), and how safe is just rooting it for the time being? Also, what method/tools would you suggest to use? I don't like the FireOS and would like to get it close the a standard Android and/or CyanogenMod.
Thanks for your time.
Click to expand...
Click to collapse
actually you came just in time and have the right firmware and place go to the development section and start reading we now have a brand new recovery that bypasses the security on our bootloader. I would advise reading reading these threads thoroughly. And your particular software is rootable with the existing utilities we have in the development section also. There has been a lot of development very recent keep in mind they are first version may be buggy but the utility .94 can get you rooted and safe from updates until you can do more research. And get your new recovery in place.
Thanks, by what you said I am guessing the internal workings haven't been figured out quite yet. I will head over to the development boards and see if I can find. Sadly I updated to FireOS 4.5 not knowing that there wasn't software to to roll back for versions above 1X but read that I can call Amazon and have it rolled back so no worries.
nope
Eclipsys said:
Thanks, by what you said I am guessing the internal workings haven't been figured out quite yet. I will head over to the development boards and see if I can find. Sadly I updated to FireOS 4.5 not knowing that there wasn't software to to roll back for versions above 1X but read that I can call Amazon and have it rolled back so no worries.
Click to expand...
Click to collapse
they have shut that opportunity down I believe it was probably getting abused. And I believe they were only able to roll back from 4. 1. 1 from now on
jimyv said:
they have shut that opportunity down I believe it was probably getting abused. And I believe they were only able to roll back from 4. 1. 1 from now on
Click to expand...
Click to collapse
I actually just got it rolled back, I read that people saying it doesn't happen anymore, but the very nice tech lady down graded me from 4.5.1 to 13.3.2.7. She stayed on the phone until it was completly reset. =) Now I should be able to root it easily with towelroot.
I was being pretty damn charming to her though, lol
I'm sure they don't want to and won't do it most of the time, but I is still 100% possible on their end, it's just wether they want to or not. I had a pretty decent story too, not just 'its slow and buggy'
Eclipsys said:
I actually just got it rolled back, I read that people saying it doesn't happen anymore, but the very nice tech lady down graded me from 4.5.1 to 13.3.2.7. She stayed on the phone until it was completly reset. =) Now I should be able to root it easily with towelroot.
I was being pretty damn charming to her though, lol
I'm sure they don't want to and won't do it most of the time, but I is still 100% possible on their end, it's just wether they want to or not. I had a pretty decent story too, not just 'its slow and buggy'
Click to expand...
Click to collapse
after rolling back a couple of them it helps if you say that it was on version 3 then you updated to the latest one then make up some plausable combination of symptoms for example the one i went with is that my device restarts alone every 20 minutes or so and almost no apps work and then proceed to say that you were happy with how it was before it was updated
EDIT:also to note that i have yet to have them refuse me a single time through chat
well
Davengerr said:
after rolling back a couple of them it helps if you say that it was on version 3 then you updated to the latest one then make up some plausable combination of symptoms for example the one i went with is that my device restarts alone every 20 minutes or so and almost no apps work and then proceed to say that you were happy with how it was before it was updated
EDIT:also to note that i have yet to have them refuse me a single time through chat
Click to expand...
Click to collapse
I have just been reading about several people that have been rejected and why. There is a rumor that they gave it to their developers only and their technicians will go through your device logs and decide whether or not it is appropriate. Again rumor. I do not need roll back at least so far I have stuck with the old software all year...I just hate having to mess with trying to keep the OTA blocked. I just want them to take me off the ota push servers.

Categories

Resources