IT WONT LEAVE ME ALONE!
Does anyone know if this is worth it at all? I dont have the voice search bug (i have MANY others).
Is there a way to stop this thing from asking me. I keep saying later but there is no "leave me the hell alone" button.
either do it or root it. I for one would never let a carrier push any update to *my* phone.
thats the weird thing, i am rooted since day 1
...........
okay dont mean to keep bumping this but at least maybe someone else has taken the update already.
Im on stock rooted 2.3.4
My phone is trying to go 2.3.6
I currently have no interest in this and as of 10pm tonight i am leaving on vaca for 4 days. directly after work (3pm) i am going to dmv where i will prob rot for about 3 hours.
My main question is at least this. If i just take the update to stop the constant nagging its doing to me (like i am doing to this forum right now) will i lose my root? I CANT lose root right now because without tethering I will be FORCED to actually talk with my girlfreind while away instead of tethering her phone and letting her play on the web. This to me is like having my nuts squeezed in a vice!
If I take the update and my phone screws up I will have NO time to redo it until I get back. If it wasnt of this kind of importance I would have already tried the update and just restored if it didnt work. I have an image of my phone in CMR BUUUUUUUUUUUUT I have had CMR break down on me before trying to restore and cant risk it. Dont want to have to press later for 4 days lol.
Thanks
3rdcoast said:
either do it or root it. I for one would never let a carrier push any update to *my* phone.
Click to expand...
Click to collapse
Its Google pushing it not the carrier.
Sent from my Nexus S 4G using xda premium
tevil said:
okay dont mean to keep bumping this but at least maybe someone else has taken the update already.
Im on stock rooted 2.3.4
My phone is trying to go 2.3.6
I currently have no interest in this and as of 10pm tonight i am leaving on vaca for 4 days. directly after work (3pm) i am going to dmv where i will prob rot for about 3 hours.
My main question is at least this. If i just take the update to stop the constant nagging its doing to me (like i am doing to this forum right now) will i lose my root? I CANT lose root right now because without tethering I will be FORCED to actually talk with my girlfreind while away instead of tethering her phone and letting her play on the web. This to me is like having my nuts squeezed in a vice!
If I take the update and my phone screws up I will have NO time to redo it until I get back. If it wasnt of this kind of importance I would have already tried the update and just restored if it didnt work. I have an image of my phone in CMR BUUUUUUUUUUUUT I have had CMR break down on me before trying to restore and cant risk it. Dont want to have to press later for 4 days lol.
Thanks
Click to expand...
Click to collapse
If you are on stock rooted do yourself a favor and flash stock rooted of 2.3.6 and be done with it. Don't update via ota.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you are on stock rooted do yourself a favor and flash stock rooted of 2.3.6 and be done with it. Don't update via ota.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Is there a 2.3.6 rooted update file or do i have to start from scratch? Im hesitant to try and CMR a new version and have issues right before i go away. I guess Im stuck with the nagger for 4 days.......
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.
Im on stock rooted 2.3.4
My phone is trying to go 2.3.6
I currently have no interest in this and as of 10pm tonight i am leaving on vaca for 4 days. directly after work (3pm) i am going to dmv where i will prob rot for about 3 hours.
My main question is at least this. If i just take the update to stop the constant nagging its doing to me (like i am doing to this forum right now) will i lose my root? I CANT lose root right now because without tethering I will be FORCED to actually talk with my girlfreind while away instead of tethering her phone and letting her play on the web. This to me is like having my nuts squeezed in a vice!
If I take the update and my phone screws up I will have NO time to redo it until I get back. If it wasnt of this kind of importance I would have already tried the update and just restored if it didnt work. I have an image of my phone in CMR BUUUUUUUUUUUUT I have had CMR break down on me before trying to restore and cant risk it. Dont want to have to press later for 4 days lol.
Thanks
If you want to be on 2.3.6 save yourself the trouble and flash a rooted version.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you want to be on 2.3.6 save yourself the trouble and flash a rooted version.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
i just want to stop the nagger
tevil said:
i just want to stop the nagger
Click to expand...
Click to collapse
Its simple. Either take the update and then flash superuser from cwm to gain root again or just flash the update in cwm.
Ether way your bootloader will not be changed neither will your recovery.
Sent from my Nexus S 4G
if i flash it in CWR will it remove the root or does it stay there. also i have been looking for the update somewhere and havent had luck.
I see one 2.3.6 rom that was pulled for the 9020a and one update for i think the 9023
if you have a 9020a update link i can install from CWM i would appreciate it. Tried using search funtion.
thanks
i let the ota through and didn't loose root. did you check here for what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1056062
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
2.3.3 was all the rage about a month or so ago.
Sent from my LG-P999 using xda premium
Well, sure, but all news says that T-mobile stopped doing OTAs some time ago (started late July, stopped August 10). So why on earth is my phone just getting it now? I even do a manual check every so often and never got it. I didn't do anything special today that I can recall.
you should update it. you dont have nothing to lose. ifd your still rooted it will unroot but then you can flash nvflash recovery and go back to any rooted roms you want
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
No idea why you're just getting it now, but its the same one thats been out for a while now.
hmichaelkim said:
No idea why you're just getting it now, but its the same one thats been out for a while now.
Click to expand...
Click to collapse
T-Mobile removed the 2.3.3 update from their servers long ago. If you are getting something else it is new most likely. You can do an OTA if you are rooted as long as you have not modified any system files other than adding su and superuser.apk to get root..
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
So what was the update?
Sent from my HTC Desire using XDA App
What happens?
Sent from my LG-P999 using XDA Premium App
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
I'm on froyo to and rooted but no clockwork mod recovery. I tried to check for an update and it said some kind of error i dont remember.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Check in the /cache directory for the zip file for tthe update. If you can, before you install it can you save a copy of the zip to a separate area on your sdcard and thn upload it to a file sharing site so others can download it? Once you install it, it gets deleted from the /cache directory but if you save it elsewhere those copies will be saved.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Yes, you need to be on stock recovery and your phone's system partition must be stock. LG stores some OTAs very differently than other vendors.
Do a backup of your phone first to preserve the OTA image. It might be in the cache but it might be elsewhere. If you wouldn't mind giving me a link to the system and cache images I can try to find the OTA and see what it is for.
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Lenin809 said:
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Click to expand...
Click to collapse
Did you flash roms and then restore an old backup? That backup could have had the OTA on it and you did not notice it before. T-Mobile pulled the OTA months ago (was available less than two weeks). Doesn't seem likely it was pushed to you recently.
Okay...
So I accidentally dropped my phone, and it was a TOTAL loss. It would not even power back on. I received the replacement phone today and followed through with the GB update via Kies Mini. Now when I attempt to root the phone, Superoneclick stops responding. Any suggestions?
Check out the threads in the dev forum for info on how to root. You will need to flash a rooted kernel.
I've attempted to root by several different methods, and no matter how many times, or which method I use, it will not root. I made sure that the phone was checked for USD debugging and for unknown resources. Anyone have any suggestions?
Edit: My apologies, as I thought that I posted the thread in the Q&A section where it is supposed to be.
OnProzac said:
Okay...
So I accidentally dropped my phone, and it was a TOTAL loss. It would not even power back on. I received the replacement phone today and followed through with the GB update via Kies Mini. Now when I attempt to root the phone, Superoneclick stops responding. Any suggestions?
Click to expand...
Click to collapse
Did your screen crack? how did you not get charged?
Sent from my SAMSUNG-SGH-I997 using XDA App
OnProzac said:
Okay...
So I accidentally dropped my phone, and it was a TOTAL loss. It would not even power back on. I received the replacement phone today and followed through with the GB update via Kies Mini. Now when I attempt to root the phone, Superoneclick stops responding. Any suggestions?
Click to expand...
Click to collapse
If you want root back, you're gonna need to flash a rooted kernel through Odin. Currently Superoneclick doesn't work on GB. Hope this helps.
sent from my CommandCenter using xda premium
There is no root method for stock 2.3.6 yet... period..
Sent from my SAMSUNG-SGH-I997 using xda premium
you can root it but gasp, you wont be able to flash the "official" kernel back to it since we cant dump the kernel without root... but you can flash the kl2 leaked kernel to it (same thing) but with sdcard workarounds and voodoo lagfix you need to consider a few things and its alot to say, but why bother, just use the rogers root kernel with cwm to flash a yummy rom from the dev section...
as far as rooting it without a kernel replacement well good luck with that. i will likely make a rooted heimdall package in a few days but it will have the kernel from the leaked rom (same thing) if that scares anyone with their irrational rationalizations...
why heimdall? well the mac users need some love since samsung and att wont give it to them.. its more reliable that that crappy samsung software be it kies or odin. and with the package system introduced in version 1.3 it is idiot proof..
if you must have an odin version make it your self.
Idietssss
...... what's whit these people .....let it go for some time then try ....... I'm sick of these people asking for there problems to ... be solved ASAP
Sent from my SGH-I997 using xda premium
weve know this would be a problem for like a year when the rogers infuse came out.
the rogers method works but it's just so many considerations and annoyances to tell people how to do it problem free. you have to assume they can creaet a file to disable the lagfix before hand and that they can extract and compress another file and depending on the kernel they use to root it they may need to edit one charachter of text. it all easy stuff but it becomes a lengthy post explaining it and then the next guy doesnt read what you already answered. ill wait for source code and fully compatible kernels with cwm so we dont have to worry about the extra process of reverting to a stock kernel, till then im burnt out on saying the same thing over and over and over.
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!