Hi all,
I received my Thunderbolt today from Wirefly and one of the things it's offering me is an OTA update dated today.
Has anyone experienced any rooting issues with this update? So far, my phone is stock, and it would be easy for me to apply the update. But, if it's going to be an issue with rooting it then I'd rather hold off.
Thoughts?
Robert
Its probably the MR1 update the phone got a little bit ago. When they send phones out, they come with the factory firmware (meaning not updated). If you root your phone, then return to stock, your phone won't be on the latest firmware anymore.
What I'm trying to say is it's probably not a new update.
The info on the update is:
Mecha_VERIZON_WWE_1.13.605.7-1.12.605.6
Does that help figuring out which one it is? If it is the MR1 is it OK to update without causing issues for rooting?
Robertjm said:
The info on the update is:
Mecha_VERIZON_WWE_1.13.605.7-1.12.605.6
Does that help figuring out which one it is? If it is the MR1 is it OK to update without causing issues for rooting?
Click to expand...
Click to collapse
Go to the root tutorial sticky in the development section and compare them. If it is the Mr1 then rooting will not be a problem.
Sent from my HTC Thunderbolt
Im pretty sure its fine... we have that update already anyways so if you just have them ship you the phone when you root it you'll end up with the update. Rooting on this phone requires a downgrade first so I would just have them ship you the phone then you can update when you root.
Sent from Gingertits, I mean itis...
So I went and checked that does appear to be the OTA update number. I already have the phone. Sounds like it really doesn't matter whether I update now and then root, or vice versa.
I wouldn't update it if your planning root, its the update that has been causing reboots, so I would just not update, root your phone and do whatever mine was never updated and it works great.
Sent from my ADR6400L using Tapatalk
I just got my Thunderbolt today, I got the same message about an update, I went ahead with it, thought it was GB Anywho, just finished jcase's PermRoot all is good, so you should have no problems.
So I chose "reject" the last time I was offered the OTA. Does that mean it's going to embargo that update going forward?
Robert
oxidant11 said:
I wouldn't update it if your planning root, its the update that has been causing reboots, so I would just not update, root your phone and do whatever mine was never updated and it works great.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Robertjm said:
So I chose "reject" the last time I was offered the OTA. Does that mean it's going to embargo that update going forward?
Robert
Click to expand...
Click to collapse
If you decide you changed your mind, you can always go to Settings ->Software Update -> Check new, and it will prompt you again.
Like somebody else said, though, if you are planning on rooting, there is no need to do the OTA beforehand. You will end up with a rooted version of the OTA update at the end of the rooting process, anyway (assuming you follow jcase's instructions...which you should).
If you accept the update is there a way to remove it?
captinmahem said:
If you accept the update is there a way to remove it?
Click to expand...
Click to collapse
Only by rooting and flashing a new ROM.
Thanks, Robertus
Related
Samsung just released the first firmware update today... i installed it but cant find any info online anywhere about what all it changed/fixed? anyone have more info on this?
There's a post in general about it coming soon. I haven't gotten it yet, anyway to extract it and host it? just in case they release it in phases. According to the other post, you can install it via OTA, Store, or home computer, so it should be available to the masses soon.
Always the same first question... Does it kill root?
Sent from my SPH-D700 using Tapatalk
Same usual first question: Does it kill root?
Roger
Sent from my SPH-D700 using Tapatalk
Sorry about the double post. Got an fc and then didn't show.
I got the update a bit ago. Phone rebooted to install...there was an error but I didn't get to see what it was. Phone rebooted again and is going fine now. Titanium backup still shows root. I went to about phone and it shows 2.1_update 1. I read media hub was supposed to be enabled but mine still says check later...I'm wondering if my phone didn't actually update. I will see what others say about their updates.
Oh and my specs...one click rooted with andromeda kernel and adw launcher...pretty much stock other than that
Sent from my Epic 4G using Tapatalk Pro
i have had 2.1 update one since i first got my phone... :-( i was soo excited about an update ... I want the puzzle unlock
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.
done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App
JojoSteez said:
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.
Click to expand...
Click to collapse
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App
rufflez2010 said:
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's what I figured...I could flash back to stock I guess, but might be moot if the phone can't find the update again. It was pushed to me to begin with and now it's like it never happened...
rufflez2010 said:
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I still have dg27 so it seems my update just failed. It's gotta be the custom kernel then. hmm...what to do, ha
Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.
JojoSteez said:
Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.
Click to expand...
Click to collapse
Let us know if battery life is any better.
Sent from my SPH-D700 using Tapatalk
Samsung's build number is always easy to read.
A, B, C, D, ... : month.
January, February, March, etc. G means July, therefore.
27 means July 27th: the date of kernel/firmware build.
So DI07 means September 07, which is fairly new.
http://community.sprint.com/baw/message/213524
Here is a Sprint Admin talking about it. It is an official release as of today. He has all the fixes listed too.
it is a 2.1 exploit through adb actually so this shouldnt be of any worries to us
Just got a pop up on my phone about the update. Accepted it and told it to apply. Phone rebooted, then showed an error when trying to apply the update. Hit the Home button and phone rebooted. No further notifications now about the update. Went in and manually checked and it tells me none are available. So,..I guess you only get one shot at the update and then you're skipped??
anyone that is rooted with stock kernel able to update and keep root?
wait what update? i checked for an update but there wasnt one.
Logged into an At&T wifi yesterday and the phone offered an HTC system "update".
Having owned several HTC products and never seeing any sort of update from them for a device I owned, Ill admit i was a bit shocked. lol
Downloaded for a few mins, although I didnt see a file size.
Reboots, resets twice then boots. Both my Inspires updated to
Software Version
1.84.502.11
took about 5 mins total
Sorry If this was somewhere else, I searched and didn't see anything.
What'd they do to my phones?
This is the update from ATT that added hsupa
Sent from my Desire HD using Tapatalk
This tells you all .. update was pushed out back in April 29th.
http://www.htc.com/us/support/inspire-att/downloads/
The install doesn't work for me. Just shows an exclamation point and the android guy. I'm suspecting it's because I'm rooted and running TPC. Any ideas?
lockheedload said:
The install doesn't work for me. Just shows an exclamation point and the android guy. I'm suspecting it's because I'm rooted and running TPC. Any ideas?
Click to expand...
Click to collapse
You got it.
Sent from my Inspire 4G using XDA App
-Kevlar- said:
You got it.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
How do I get rid of the update notification?
Same thing with me shows exclamation point and the android guy for me to im also rooted i wonder if we can get the update being rooted. im tired of the notification also
Anyone get it to install with root? I just don't want it to screw up my root where i'd have to do it again.
The OTA update is mostly a collection of patches. These are very specific as to the files they are to patch. If you don't have the official AT&T ROM (or a very close approximation) then the update won't do anything.
there is the full ATT rom with the included patches and fixes and stuff in the development section. just dl the rom and flash it since you are already rooted
simple and stuff.
but also a lot of the newer roms are importing the fixes
Gene Poole said:
The OTA update is mostly a collection of patches. These are very specific as to the files they are to patch. If you don't have the official AT&T ROM (or a very close approximation) then the update won't do anything.
Click to expand...
Click to collapse
Even with stock Rom? So my question is, if on rooted with stock Rom, and I try the update, will it screw anything up with the root?
c4k30rd34th said:
Even with stock Rom? So my question is, if on rooted with stock Rom, and I try the update, will it screw anything up with the root?
Click to expand...
Click to collapse
It will not run, it will fail the process.
How long does it take to install after downloading?
I'm going on about 10 minutes of the green arrows on the black screen with the phone image under it. Don't think it should take this long should it?
K, thanks. Simple answer. Is there a way to disable that notification then?
Nevermind. Hung on the install but pulling the battery worked
Install this stock rooted Rom. It has the ota update in it. http://forum.xda-developers.com/showthread.php?t=1058042
hi guys simple question bc my software is still 1.73.502.1, all i've done is root my device so i can grab some apps and get titanium backup to uninstall some bloatware.
my question is there's lots of talk about 1.85 and i'm wondering why i haven't gotten the auto-update yet. can you confirm its bc at&t hasn't sent the 1.85 OTA update yet, and not bc i rooted my device thus negating any auto software updates? sorry if this is a dumb question.
There are no OTA updates as of yet. Those on 1.85 are on it because they ran the leaked RUU.
Unless you know what you're doing don't bother updating to .85 because you can lose all root/bootloader/CID to let you do as you please because theres no current exploit. Its also been reported by people [and me] that you get lower CPU benchmark scores via Quadrant for example, although a faster / snappier phone. A couple people have also said its more sluggish now for them but I believe thats based on what they have running [I use one home screen + no widgets].
thank you very much. will an unlocked boot and s-off phone still receive updates as well from AT&T both software and android updates?
chillsen said:
thank you very much. will an unlocked boot and s-off phone still receive updates as well from AT&T both software and android updates?
Click to expand...
Click to collapse
We won't know for sure what will happen until AT&T releases it.
Best practice is to not OTA update until the devs have had a crack at it and we know what's what.
iElvis said:
We won't know for sure what will happen until AT&T releases it.
Best practice is to not OTA update until the devs have had a crack at it and we know what's what.
Click to expand...
Click to collapse
thank you for that key info. will not be ota'ing until xda squad cracks it alllll!
Basically ... NO!
chillsen said:
hi guys simple question bc my software is still 1.73.502.1, all i've done is root my device so i can grab some apps and get titanium backup to uninstall some bloatware.
my question is there's lots of talk about 1.85 and i'm wondering why i haven't gotten the auto-update yet. can you confirm its bc at&t hasn't sent the 1.85 OTA update yet, and not bc i rooted my device thus negating any auto software updates? sorry if this is a dumb question.
Click to expand...
Click to collapse
Basically, once you root your phone, or change the CID, you will never again be able to get OTA up-dates. Sorry.
Peter
P.S. Then again, I could be wrong ... but that's what I've been led to believe.
Is it safe to assume, that if people who flashed leaked ruu's don't get ota's then some of the devs will release ruu's of the newest ota's ?
Sent from my HTC One X using XDA
PeterHTC said:
Basically, once you root your phone, or change the CID, you will never again be able to get OTA up-dates. Sorry.
Peter
P.S. Then again, I could be wrong ... but that's what I've been led to believe.
Click to expand...
Click to collapse
That would make the existence of this app a bit hard to explain, then.
All this info going around is very confusing for me...Basically i started on 1.73 (rooted)....ran 1.82 (rooted)....ran 1.85 (stuck).....anything i can do?.....i never unlocked any bootloader....i just liike the idea of root to get rid of bloat......
I know the feeling
patstock11 said:
All this info going around is very confusing for me...Basically i started on 1.73 (rooted)....ran 1.82 (rooted)....ran 1.85 (stuck).....anything i can do?.....i never unlocked any bootloader....i just liike the idea of root to get rid of bloat......
Click to expand...
Click to collapse
Same with me - waiting for root for 1.85 - nothing much we can do at this point! Sounds like there are quite a few of us stuck in Limbo.
Just keep watching the forums and waiting for Root!
Mike
Not really ...
iElvis said:
That would make the existence of this app a bit hard to explain, then.
Click to expand...
Click to collapse
Not really. That app is not compatible with the ONE X.
Peter
PeterHTC said:
Not really. That app is not compatible with the ONE X.
Peter
Click to expand...
Click to collapse
So you're suggesting that the root = no OTA is One X (or HTC) specific? Where did you hear that?
FWIW, I've got that app installed and it successfully saved a su copy.
PeterHTC said:
Not really. That app is not compatible with the ONE X.
Peter
Click to expand...
Click to collapse
Sorry, but you are wrong. If you are rooted and nothing else, you CAN and will receive OTA updates, for most devices. I've heard many accounts of people being rooted and then updating OTA and losing root, and getting it back after a while after a new exploit was found. Now, if you use custom ROMs or anything, that changes things, but just rooting doesn't do anything. Think about it, you aren't changing the ROM or the way it connects to AT&T's servers. You are just exploiting a vulnerability and gaining root access. Now, AT&T may have found a way to detect root, but as far as I know they don't and with only a root, OTA updates can be installed. Although any post-root modification might screw that up.
The ICS OTA update keeps failing on my A2. I rooted it quite some time ago, and I don't really remember what method I used. As I recall, I initially used super one click, but it became un-rooted some months ago when they the OTA update was released that added emergency updates and a few other tweaks. I then used the first exploit available to root the phone.
I imagine that root access is the most likely culprit, so I did a factory reset; and put in blank microSD card just for good measure, but somehow, it was STILL rooted. I tried unrooting with super one click, and during the process it says
Shell rooted...false
su rooted...True
and continues to say that no matter how many times I try to unroot it. I seem to be stuck. The only other possibility is that it won't update because I'm visiting my wife's family in Canada; but it ALERTED me to the update, and it DOWNLOADS it just fine, so I would imagine that is should install it regardless. Someone help me out?
yes im a noob...please help me not to be
I tried updating and ended up haveing to wipe to the original 2.3.5 install...then update all the way back...unfortunently I think that will kill your root.....
I was having your issue now I am not and am on 4.5.1 but un-rooted till I can find a way to root it again...
hope that helps
theundecided said:
I tried updating and ended up haveing to wipe to the original 2.3.5 install...then update all the way back...unfortunently I think that will kill your root.....
I was having your issue now I am not and am on 4.5.1 but un-rooted till I can find a way to root it again...
hope that helps
Click to expand...
Click to collapse
I was able to un-root it, from what I can tell. I found the exploit I used and there was an un-root option. Root check says it's lokced down, so does super one click, but it still won't update; so I suppose it's probably just more of AT&T's crap. I guess I'll know when I get back to the states next week; I'm just impatient.
Then again, I waited this long for the official OTA, fighting back the urge to just install the leak, so I guess I'm not TOO impatient.
I just want my freaking update!
Having root will not affect being able to OTA update.
What else have you done to your phone?
Sent from my MB865 using xda app-developers app
dk-v1 said:
Having root will not affect being able to OTA update.
What else have you done to your phone?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Nothing. I've even un-rooted it. My next step is to try to locate a stock ROM and flashing instructions, roll it back and see if that helps. Can anyone point me in the direction for that.
Aaaaand now I've screwed myself up even further. Tried to flash back to 2.3.5 and it's failing at step 6/20. Guess I'll have to go dig up the 2.3.6 stock, which will put me all the way back at square 1.
Sounds like you are trying to use the unmodifed 2.3.5 FXZ. Read this. It has everything you will need to recover.
Good luck!
Yup. That was the problem with that step. I'm not sure WHAT was going on when I was on 2.3.6, but that thing did NOT want to take the update. Going down to 2.3.5, then OTA to 2.3.6 FINALLY allowed me to OTA to ICS. Thanks everyone!
Hello all, I know that att's 4.2 update came out January 29, and it's been longer than 1 month, yet my phone still has not gotten the OTA update. nothing comes up for both system updates or software updates in my settings, and my phone is not rooted. any other possible solutions since i dislike updating through PC?
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2628920
But if you ever want to unlock your bootloader and root your phone you need to do it before taking the update.
Sent from my Evita
timmaaa said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2628920
But if you ever want to unlock your bootloader and root your phone you need to do it before taking the update.
Sent from my Evita
Click to expand...
Click to collapse
one more thing. will i lose all my data from that method?
p.s.
mark my words, if it were my phone, i would know how to update this phone easily. but it's my brothers haha.
It shouldn't wipe any data but make backups just in case. If it's your brother's phone then he should be doing the work, I don't assist when the person who owns the phone isn't willing to do the learning and the work.
Sent from my Evita