Ok, I am curious. For those of you who have read my thread below, you'll note that I said my son's MT4G recieved a firmware update. What updat is this? When he first showed me the phone in update mode, I did some quick research and kind of thought it might be gingerbread. When it was done, I checked, and it wasn't. I asked him what it said when in started and he told me it said something about firmware.
Of course, then he pulled the battery to put his sim back in... and, well, the details are in my other post
madwolf27 said:
Ok, I am curious. For those of you who have read my thread below, you'll note that I said my son's MT4G recieved a firmware update. What updat is this? When he first showed me the phone in update mode, I did some quick research and kind of thought it might be gingerbread. When it was done, I checked, and it wasn't. I asked him what it said when in started and he told me it said something about firmware.
Of course, then he pulled the battery to put his sim back in... and, well, the details are in my other post
Click to expand...
Click to collapse
Why did you create a second post?
When T-Mobile released their phone, they had 2.2 on it. Later they updated it to 2.2.1. That was the update your son got on his phone.
I created a new post Because this was just really a side issue I was curious about. And thanks
Related
I updated it and it bricked my phone, what shoud I do...
Explain......Updated to a custom rom? Updated the official firmware? What exactly have you done?
t-mobile sent me a update, so i clicked start update, it said it will take 10 minutes after restart, i been waiting 20 min now...
It might be froyo because someone on Samsung's facebook an hour ago said " Samsung vibrant tmobile USA running froyo finally i love it thanks for the update finally."
source: http://www.facebook.com/SamsungGalaxyS/posts/155785287802201
poster: Jessie Montejano
sadface that it bricked you, whether it's froyo or not.
so what should i do
well, how did it brick it? is it stuck on the galaxy s screen or does it just not turn on?
its stuck on the vibrant screen
well to fix it, go to the dev section and look at the "rom bible". you will have to ODIN back to stock.
did you ever receive the J16 update? it could either be that, or froyo being released.
Jaytek said:
its stuck on the vibrant screen
Click to expand...
Click to collapse
So take out the battery and put it back in. Let us know what happens.
I tried the CHECKIN method a few days ago and it would just bring me to the homescreen. I did it today and it just gave me a blank dialer with no numbers after I hit the last *.
Could this mean there is an update on their server?
stuck on the same vibrant screen
take out the battery, press both volume keys, plug into computer while pressing keys, insert battery. you should be in download mode. ODIN back to stock. search for the noob-friendly guide.
Did you have the JI6 update before this one?
im getting the files to odin it
ok good. just remember to flash jfd before ji6 if you are going back to 2.1
where is this ota update? i want to see it!
is this trolling...?
I would have expected more news if 2.2 really came out for vibrant
Damonkashu said:
is this trolling...?
I would have expected more news if 2.2 really came out for vibrant
Click to expand...
Click to collapse
no hes probably asking for an older update, maybe he just got his phone?
Don't firmware updates begin to roll-out on a Monday and not a Friday?
axion68 said:
Don't firmware updates begin to roll-out on a Monday and not a Friday?
Click to expand...
Click to collapse
i dont THINK theres a set day for firmware updates, but yeah...... hope your right, this monday? ?
Isn't everyone else getting 2.2 via Kies and not an OTA?
Hi All,
[ This OP has been edited based on receiving clarification from forum members...]
I just received a System Update on my rooted Nexus. The System Update says that it is part 1 of 2. I quote from my phone:
Android Update (Part 1 of 2)
Downloaded and verified 380kb
-----------------------------------
This is the first of a two-part System Update
This first part is required to prepare your device
to receive new Android system software.
Your device will restart, and your settings and
data will be preserved.
Soon thereafter, you will receive a second
update containing the new Android system
software itself.
I isolated the following files from /cache and verified their checksums every step of attaching them here:
d6096cac5e9f.signed-hboot-0.35.0017.zip (380.60KB)
(MD5 b0669d79f3ace07fdd3e1c03d88d2c68)
downloadfile.apk (1.76MB)
(MD5 1dbbb71e77a70494549e8ea9be5b631e)
downloadfile-1.apk (1.76MB)
(MD5 566a4566d4f6321f8d7f37a957ef1698)
Bill Bedard
Fort Washington, MD
That would be FRG83D
And off to the races!
http://www.droid-life.com/2010/12/06/motorola-droid-frg83d-update-rolling-out-today/
false alarm
As millions of people spam *#*#CHECKIN#*#* and overload the OTA servers....
I am amazed at how small they were able to make it......just over 2mb.
I call False Alarm.
What the hell, 1.76mb??? That's no Gingerbread, more like Bread Crumbs. Left over crumbs called FRG83D.
chromiumcloud said:
http://www.droid-life.com/2010/12/06/motorola-droid-frg83d-update-rolling-out-today/
false alarm
Click to expand...
Click to collapse
Ummm, I thought I mentioned I was using a Nexus One. I doubt Motorola is pushing me an update. Good head's up, though!
BTW, my build is listed as FRF91 so am assuming that nothing in the FRF83 series would register as an update. Am I wrong here?
wbedard said:
BTW, my build is listed as FRF91 so am assuming that nothing in the FRF83 series would register as an update. Am I wrong here?
Click to expand...
Click to collapse
FRG is later than FRF, dude. G comes after F in the alphabet right?
wbedard said:
BTW, my build is listed as FRF91 so am assuming that nothing in the FRF83 series would register as an update. Am I wrong here?
Click to expand...
Click to collapse
Yes, you are wrong. FRG83* is newer than FRF91.
Nothing to see here, people. Move along.
musashiken said:
I call False Alarm.
What the hell, 1.76mb??? That's no Gingerbread, more like Bread Crumbs. Left over crumbs called FRG83D.
Click to expand...
Click to collapse
I also thought I showed that this was part 1 of a 2-part update (and the update msg was pretty clear about this). I'm not saying that I'm running GB on my phone nor am I planning on applying either Part 1 of this update or what might be a much larger Part 2 containing the actual GB update.
I'm just trying to help my posting these files but I really think many of you need to take a few more minutes to read before posting. I'm not trying to say I'm cool or anything...I'm just trying to help here!
Bill
laslow said:
Yes, you are wrong. FRG83* is newer than FRF91.
Nothing to see here, people. Move along.
Click to expand...
Click to collapse
Aha...I see. Thanks for the tip as I wasn't aware of that (focused more on the number than the prefix...my bad!). Moving along then...:>)
Bill
You might want to change the topic of this thread so as not to get a lot of hopes up... >.>
laslow said:
You might want to change the topic of this thread so as not to get a lot of hopes up... >.>
Click to expand...
Click to collapse
...already there! -Very- good call, though!~
Bill
Just got my OTA for the Verizon update. Given the success in the P-605 thread with achieving root post install, I'm taking the update and will report back.
Here's some more info - http://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Ran into an install error (the infamous error 402), so having to use Verizon's Software Updater to try to get it to install.
Can you root after install?
Sent from my SM-N910V using Tapatalk
tolymatev said:
Can you root after install?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Can't get installed. It is a 2 step update and I got a 402 error on the 2nd update. Thought from searching that I could use the built in Verizon Software Update utility but getting an incompatible Firmware error from it. The new versions aren't up on Kies yet and trying to Odin back to the previous is erroring out (though trying once more now).
So at this point I'm stuck until they release the latest through Kies or I find a chunk of time to get on the phone with Verizon tech support.
i get an error also. i even factory reset my device to see if itll go through and still a no. "Update failed, 402"
---------- Post added at 08:59 AM ---------- Previous post was at 08:42 AM ----------
Im talking to Verizon support right now. will update with the answers i get
---------- Post added at 09:22 AM ---------- Previous post was at 08:59 AM ----------
What a useless ***** on the chat. she's so stupid i don't understand how she got a job at support.
Unfortunately I suspect we are stuck until they either update the Verizon Update app to recognize the new firmware versions or Samsung releases it through Kids..... I don't remember what the normal delay is between OTA and Kies but suspect it will be a week or so.
rgerrans said:
Unfortunately I suspect we are stuck until they either update the Verizon Update app to recognize the new firmware versions or Samsung releases it through Kids..... I don't remember what the normal delay is between OTA and Kies but suspect it will be a week or so.
Click to expand...
Click to collapse
Ummm...Last time I checked, Samsung doesn't release updates through kids...
Shawn5162 said:
Ummm...Last time I checked, Samsung doesn't release updates through kids...
Click to expand...
Click to collapse
I don't know, my 14 great old can be pretty sharp I even caught that the first time spell check "corrected" it, guess it decided even after two times I still didn't want to spell it Kies....
So here is the latest. After chatting with a helpful Verizon rep, they said that due to the device having been previously rooted (even though I had uninstalled root prior to updating) that might be causing the issue and that I'd have to talk with Samsung. The Samsung rep said that yes, the reported baseband is 5.1.1 so that is likely causing the issue that it took the 1st OTA but not the second. Unfortunately they can't update it through Smart Switch (their Kies replacement) and said I'd have to take it into a Samsung service center in a Best Buy since they'd have the tools to get it on the right firmware. Heading there today or tomorrow so will report back.....
i went to bestbuy and the samsung guy tried to be very helpful but he couldn't, his programs dont show an update for our devices yet. He wouldnt believe me when i told him im suppose to get 5.1.1. Note pro 12 doesnt have 5.1 theres no way note 10.1 is getting it is what he told me.
Then i inserted my phones sim into the note 10.1 and we checked for an update, he saw the error and he saw that there was an update 5.1.1 available for download. We tryed to update it again but it also failed.
So i went home after spending 1 hour at bestbuy without success.
The tech I met with ran a diagnostic and identified that I had a "binary mismatch" which requires 2 hours to fully reflash the device. He unfortunately didn't know how to do it so I have to go back when the more experienced tech is working.
I think we are all in the same boat. I received and installed the first OTA update, then the second one failed with the 402 error. I tried Kies and it states that I have the latest firmware. The 402 error seems common with Verizon OTA updates. I may try a trip to Best Buy also, but I don't think that the update is in full effect yet. One positive for me, the tablet seems a bit better after the first OTA received yesterday.
I was told once they get the update on their computers they can push it to any device. Hopefully thats the case.
I wonder if we can odin back to the previous version we had. If it works it'll be all stock without any root history. Maybe it'll work that way.
Just thinking out loud
Sent from my SM-N910V using Tapatalk
tolymatev said:
I was told once they get the update on their computers they can push it to any device. Hopefully thats the case.
I wonder if we can odin back to the previous version we had. If it works it'll be all stock without any root history. Maybe it'll work that way.
Just thinking out loud
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Tried Odin with 4.4.2 but ran into the same binary mismatch. Assumed it was from a changed bootloader, but not technical enough to know.
Likewise think that might be a path forward once they publish the firmware, but no sign of it yet (I know it normally takes a week or so to see it show up on SamMobile)
How did you root? Has anyone had success with this? Is your tablet still usable?
Sent from my SM-P605V using Tapatalk
I got the update. It was available through Kies this morning. Installed without any problems.
cajun456 said:
I got the update. It was available through Kies this morning. Installed without any problems.
Click to expand...
Click to collapse
Thanks for the heads up. I'll see if it will install and save me a trip to Best Buy today
KwestJones said:
How did you root? Has anyone had success with this? Is your tablet still usable?
Sent from my SM-P605V using Tapatalk
Click to expand...
Click to collapse
Haven't yet. After the headaches of getting it installed may take a breather before rooting. Here's a good summary from the P605 thread (obviously skipping the first couple of flashes and starting with the permissive kernel flashing) - http://forum.xda-developers.com/gal...xy-note-10-t3215876/post63187053#post63187053
rgerrans said:
Haven't yet. After the headaches of getting it installed may take a breather before rooting. Here's a good summary from the P605 thread (obviously skipping the first couple of flashes and starting with the permissive kernel flashing) - http://forum.xda-developers.com/gal...xy-note-10-t3215876/post63187053#post63187053
Click to expand...
Click to collapse
My bad...my question was how did you root before the update? With towelroot? Does that make a difference or was it just a bad update from vzw?
Sent from my SM-P605V using Tapatalk
Mine was rooted with towelroot. The first update wiped out root. The OTA error for the second update can happened whether you are rooted or not.
Hey fellas,
My note 4 finally died on me so I decided to get the s7 edge and stay with the android fellers. I did have some questions though-
I got notified yesterday of a 164mb update. I'm trying to ignore it because I think whenever root is obtained it should be for older firmwares right? I'm on G935TUVU2APC8 and I don't want to upgrade and get shafted.
My second question is where are the update files stored and is it possible to delete them or disable the update so I can get rid of this annoying screen that pops up every now and again?
And I know I shouldn't ask but does anybody have a progress report for root on this phone? For previous phones I saw a donation page for root, this one I have yet to see it...
Hell-Razor said:
Hey fellas,
My note 4 finally died on me so I decided to get the s7 edge and stay with the android fellers. I did have some questions though-
I got notified yesterday of a 164mb update. I'm trying to ignore it because I think whenever root is obtained it should be for older firmwares right? I'm on G935TUVU2APC8 and I don't want to upgrade and get shafted.
My second question is where are the update files stored and is it possible to delete them or disable the update so I can get rid of this annoying screen that pops up every now and again?
And I know I shouldn't ask but does anybody have a progress report for root on this phone? For previous phones I saw a donation page for root, this one I have yet to see it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470/page54
The latest update is root able confirmed by a few people
guaneet said:
http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470/page54
The latest update is root able confirmed by a few people
Click to expand...
Click to collapse
well that thread I've read a couple of times. According to the OP, the 35T is still not rootable. I see more about the 30T, the U, but no 35T
Hell-Razor said:
well that thread I've read a couple of times. According to the OP, the 35T is still not rootable. I see more about the 30T, the U, but no 35T
Click to expand...
Click to collapse
LOL I don't think you read the first post. It confirms working on g935T...
I'm rooted on 935T....
guaneet said:
LOL I don't think you read the first post. It confirms working on g935T...
I'm rooted on 935T....
Click to expand...
Click to collapse
heh, I thought that was the tekguys post, his still says unable to root. When I get home tomorrow is root'n time
Does anybody know if there is anything special with the koodo / telus builds? Even though the June update has been out for a week and a half it is still MIA in Koodoland. I know I can download the OTA and sideload it, it's what I've done the past few times, but the last time I decided to not root the phone again because I didn't feel like going through the trouble again and wanted to start installing OTAs. If there is nothing special with the koodo / telus builds I might just go ahead and do that again... but then why is it taking so long?
You don't need to root to flash an ota. Flash it in stock recovery, get the ota file from essential website.
Or are you just saying that sideloading itself is a hassle? I don't find it takes very long and is pretty straightforward. You'll probably get more answers if you post this in Q&A as well since that's what that section is for.
crixley said:
You don't need to root to flash an ota. Flash it in stock recovery, get the ota file from essential website.
Or are you just saying that sideloading itself is a hassle? I don't find it takes very long and is pretty straightforward. You'll probably get more answers if you post this in Q&A as well since that's what that section is for.
Click to expand...
Click to collapse
Yeah, I meant more the hassle part. I wanted to try it like the normal folks do.
And thanks for the suggestion, I wonder if a mod could move it... or else I'll repost it there in a little bit.
toy187 said:
Yeah, I meant more the hassle part. I wanted to try it like the normal folks do.
And thanks for the suggestion, I wonder if a mod could move it... or else I'll repost it there in a little bit.
Click to expand...
Click to collapse
Np! For the record mine would fail even when I wasn't rooted and I ended up having to sideload anyway. Not sure why!
Got mine from Amazon.ca, unlocked. Bootloader says VARIANT: OPENAM
I'm on Koodo's network and the June update's still not here. Ended up sideloading instead. Don't know what's up with that.
toy187 said:
Does anybody know if there is anything special with the koodo / telus builds? Even though the June update has been out for a week and a half it is still MIA in Koodoland. I know I can download the OTA and sideload it, it's what I've done the past few times, but the last time I decided to not root the phone again because I didn't feel like going through the trouble again and wanted to start installing OTAs. If there is nothing special with the koodo / telus builds I might just go ahead and do that again... but then why is it taking so long?
Click to expand...
Click to collapse
i just got mine from a guy who was with fido and inserted my videotron sim and got the update right away...