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.
I rooted my phone and s-off, and I tried to return it to stock. When I used the factory Rom, it seems Alittle laggy and it keeps on saying I dont have mobile data when I have 1 out of 5 bars. My phone is also still s-off and any help would be appreciated. Thanks.
Sent from my Desire HD using XDA App
Did you use the RUU to return to stock? Worked fine for me.
http://forum.xda-developers.com/showthread.php?t=952224
Yes i did but now i'm trying to get my s-on, maybe that has something to do with it.
onthezone said:
Yes i did but now i'm trying to get my s-on, maybe that has something to do with it.
Click to expand...
Click to collapse
I'm running stock with s-off and no problems.
Well I did the temproot then turned s-on, then installed stock software. Also reset the phone when it came back up and now everything is running 100% better and gets awesome upload and download speeds for some reason. 3mb download and .79 upload. Thanks for trying guys but maybe this forum can help someone else in the future.
Sent from my Desire HD using XDA App
What steps are used to turn it back on.
Sent from my Inspire 4G or Desire HD or whatever this thing is called via XDA app.
Start here if your unrooted!!!
http://forum.xda-developers.com/showthread.php?t=952352
So i went through the hole root process with the GOLDCARD to get it at least temp rooted. Once you get to the temp root shell in step (step)3.7(dot) that states
"Launch Terminal Emulator again in the phone, it Force Closes. Launch a another time, and you'll have a temp root shell."
Start here if your already rooted or temp root!!
Go to this link and put the steps in your command promt, also from you ace-hack-kit-v002 folder navigate to "tools/win" or "tools/mac" to get to the adb file:
http://forum.xda-developers.com/showpost.php?p=11486587&postcount=27
I used the 3rd one and when you do the process su will respond with su su not found, but keep going it's fine. Once you complete that your s-on and should say on top of the boot loader.
After that i used the stock ruu from
http://forum.xda-developers.com/showthread.php?t=952224
then when it came back up, i just returned it to factory settings through SD & phone storage.
I'm not sure if there are great instructions lol but if you have trouble, just let me know and i'll help you out or try to make more sence of it.
and it's really ****ed up my phone. i have one of the white nexus s models from nigri electronics when they first came out in april. i rooted it to flash the kb3 radio to enable hsupa. "unrooted" it to be able to get ota updates which worked fine until this ****ty 2.3.6 update was released.
downloaded the 2.3.6 update, no cellular connectivity. rooted the ota, flashed to a new radio (i really don't remember which one it was, this was about a week ago). that didn't help, so i went back to 2.3.4 and i believe i flashed the rom for the wrong model on my device. now it gets stuck at the animation logo, it's not recognized when i have it connected to my computer (i don't have any windows machines anymore GRUMBLEGRUMBLEGRUMBLE) but i can still get into fastboot.
is there anything i can do at this point to flash the correct 2.3.4 back on it, and which is the correct 2.3.4 anyway? underneath the battery it says i have a gt 19020a, but i seem to remember having to follow the instructions for a 9023, even though it has a super amoled screen. if anyone could help me out, i would appreciate it immensely. i still love my nexus one, but i want to get back on my nexus s until the prime is released.
incidentally... i got the notification the same day for my nexus one to download 2.3.6 and it's purring right along LOLOL.
eric b
also, when i go to recovery, i get the exclamation point in the triangle with the android below it.
eric b
other info:
hw version - rev 16
bootloader version - i9020xxka3
baseband version - i9020ucke1
lock state is, of course, unlocked.
eric b
Stay on 2.3.6 do not downgrade.. root your phone
Download Root Explorer in 4shared.com... v 2.16
Go into efs files and move "nv.log"
"nv_data.bin" and "nv_data.bin.md5" to Root Of SD Card
Restart phone.and u should be good
I think u should flash UCKD1 Radio First ... then Flash KB3
Make sure to back up your efs file just in.case =]
Sent from my Nexus S using xda premium
i sent you a pm a little while ago, lol. how can i flash 2.3.6 on it if i can't get the computer to recognize the the phone is hooked up in the first place?
eric b
additionally: when i plug in the usb to the phone while in recovery, a line of text appears at the bottom that says
STANDARD_SET_CONFIGURATION
so it seems at least the phone knows it's hooked up, but my computer isn't letting me access it.
eric b
You said you don't have a windowsachind right? Flashing on a mac is much easier anyways?
Sent from my Nexus S MV from the XDA Premium app.
well, got her running thanks to yourmaindude! where i'm at now:
i'm at 2.3.4 (rooted)
radio ucke1
where do i find 2.3.6 at to be up to date, and 2.3.7 is around the corner if i read everything correct, correct?
eric b
loaded kb3 radio, finally got my data speeds back to par
eric b
Lol thought u were on 2.3.6 already xD told u not to downgrade
Sent from my Nexus S using xda premium
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.
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!