Database Users

FRG83D OTA Update Files

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

51.1.2.0_user_512073320 Source Code Uploaded

Amazon has already made the current "root blocking" software update's source code available. This is a bit strange since for the previous version, 51.1.1.0_user_511070220, they didn't upload the source until the update was "official" (i.e., their documentation page listed it as the latest version).
I've created a page at AFTVnews.com/software to keep track of all the Fire TV software versions. Feel free to comment on the page or in this thread if I'm missing any information, or I have something listed incorrectly.

AFTVnews.com said:
Amazon has already made the current "root blocking" software update's source code available. This is a bit strange since for the previous version, 51.1.1.0_user_511070220, they didn't upload the source until the update was "official" (i.e., their documentation page listed it as the latest version).
I've created a page at AFTVnews.com/software to keep track of all the Fire TV software versions. Feel free to comment on the page or in this thread if I'm missing any information, or I have something listed incorrectly.
Click to expand...
Click to collapse
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.

rbox said:
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.
Click to expand...
Click to collapse
perhaps puts to the kernel build tree is frozen. it may be a simple file change which breaks it. They released the code to show you where it wasn't so you could undo. I'm sure there is a smart developer who knows leaving it open to towelroot means more device sales. he just has to appease his boss who was given the call "shut it down"

rbox said:
So I think I am going to call shenanigans on Amazon. The kernel source is the same between 51.1.1.0 and 51.1.2.0, yet towelroot, which exploits a kernel bug stopped working. If they fixed the kernel to patch the exploit, it should show up in the diff.
Click to expand...
Click to collapse
That's very interesting. So you're saying it looks like they explicitly blocked towelroot without patching the exploit that towelroot uses?

AFTVnews.com said:
That's very interesting. So you're saying it looks like they explicitly blocked towelroot without patching the exploit that towelroot uses?
Click to expand...
Click to collapse
No. I think they patched the kernel but didn't include that change in the source drop.

Is it possible that towelroot may still work on the latest update with some tweaks to the modstrings?

rbox said:
No. I think they patched the kernel but didn't include that change in the source drop.
Click to expand...
Click to collapse
Ah, ok. That does make more sense.

{ParanoiA} said:
Is it possible that towelroot may still work on the latest update with some tweaks to the modstrings?
Click to expand...
Click to collapse
If I put trust in Amazon that they didn't slip a change in the kernel without putting it in the source drop, then that's a possibility. I don't really know much about towelroot, but I did notice about the modstrings when I was reading about it.

I guess the only way to tell would be to diff the firmware update instead of the source?

New update

I am not sure why no one is talking about it. but the update that was being tested is now being released to everyone. I think I have better wifi and blue tooth then before then update.

smooth781 said:
I am not sure why no one is talking about it. but the update that was being tested is now being released to everyone. I think I have better wifi and blue tooth then before then update.
Click to expand...
Click to collapse
Interesting. Must be the stagefright patch update. Can you give me the build number, or post a screenshot of your device info?

Sure here is a screen shot

smooth781 said:
Sure here is a screen shot
Click to expand...
Click to collapse
Awesome, thanks. Once someone captures the OTA, or once Verizon releases the full firmware, I'll create new versions of my custom system.imgs based on it. Can you confirm that the stagefright vulnerabilities have been patched using this app: https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector?

keeps failing to update. 3rd try.

This was not stagefright. I am not patched per this app.

smooth781 said:
This was not stagefright. I am not patched per this app.
Click to expand...
Click to collapse
Even more interesting. I wonder what this update is all about then.

https://drive.google.com/file/d/0B29Dy2cIxJSXdk13MG1BMW4talU/view?usp=sharing
try this

I have never got wifi speeds like this before on my phone. I like it.

wrecklesswun said:
https://drive.google.com/file/d/0B29Dy2cIxJSXdk13MG1BMW4talU/view?usp=sharing
try this
Click to expand...
Click to collapse
That's 23.11.39. It came out in July.

if theres anything i can do to help i have the update downloaded atm and waiting on my turbo, West coast (Washington) 23.21.44
Dubbed:
"This software update includes Android security update for your Motorola Droid Turbo"

So should we upgrade? I'm not rooted, but I would like to. Also I'm on 5.1

nils39 said:
So should we upgrade? I'm not rooted, but I would like to. Also I'm on 5.1
Click to expand...
Click to collapse
If you really want to root, I'd wait. Potentially there is a bootloader unlock coming which may provide it for 5.1. If you upgrade, who knows what happens.
No one knows when though. UItimately, if root is important to you, not updating is always the best decision.

My WiFi speed is the same it has always been and it's still vulnerable to stagefright.

Ok it doesn't seem like a very important update so I'll just hold off. Are you referring to the rootnija's work on unlocking it?

When you put your phone on a wireless charger, a full-screen dialog no longer pops up to tell you that it's wireless charging (at least, while playing a video in the YouTube app).

It is stagefright patch at 30 mb but it still left 1 vulnerability. I hate vzw. I use zimperium detector

TheSt33v said:
That's 23.11.39. It came out in July.
Click to expand...
Click to collapse
This is what was in my cache folder, as well, in the status of the phone it reads version system version 23.11.39.
This is kinda confusing.

wrecklesswun said:
This is what was in my cache folder, as well, in the status of the phone it reads version system version 23.11.39.
This is kinda confusing.
Click to expand...
Click to collapse
It could be that for some reason you never got the OTA that came out immediately after the initial lollipop release. But yeah, 23.11.39 is old news. 23.21.44 appears to be the number for the most recent update.

it shows as it's applied?
https://dl.pushbulletusercontent.co...yQTu2b3BWP/Screenshot_2015-10-07-15-59-13.png
i also deleted and it is only recently that this file shows as an update - prior, i would check for updates and daily it would show that i am up to date.
---------- Post added at 08:08 PM ---------- Previous post was at 08:00 PM ----------
the update says .44 but the cache file is 39, and is also 30 mb approx... am i missing something? also if applied, can't i mofo it?

Firestick 1st gen update

Will 1st gen firestick get the 5.0.5 update? Stuck on 5.0.3 atm

I'd like to know that as well.
Sent from my iPhone using Tapatalk

fach1708 said:
Will 1st gen firestick get the 5.0.5 update? Stuck on 5.0.3 atm
Click to expand...
Click to collapse
patt2k said:
I'd like to know that as well.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
yes I have gotten it on ver 1 of stick and tv and have rooted both already

timezone12 said:
yes I have gotten it on ver 1 of stick and tv and have rooted both already
Click to expand...
Click to collapse
but how did you get it on beta firmware 5.0.3?

everyone who seems to have received the update was not on 5.0.3. I have yet to see anyone on 5.0.3 confirm they were able to update to 5.0.5.
I'm on 5.0.3 myself.
apparently we can root with kingroot on 5.0.3... so depending on how soon things get figured out related to custom recovery... rooting on 5.0.3 then using a custom recovery and pre-rooted 5.0.5 rom may be quicker than waiting on Amazon.

autoprime said:
everyone who seems to have received the update was not on 5.0.3. I have yet to see anyone on 5.0.3 confirm they were able to update to 5.0.5.
I'm on 5.0.3 myself.
apparently we can root with kingroot on 5.0.3... so depending on how soon things get figured out related to custom recovery... rooting on 5.0.3 then using a custom recovery and pre-rooted 5.0.5 rom may be quicker than waiting on Amazon.
Click to expand...
Click to collapse
I'm still waiting on the update URL for the stick. I need either the url from os3 to os5, or the url for beta to 5.0.5.

rbox said:
I'm still waiting on the update URL for the stick. I need either the url from os3 to os5, or the url for beta to 5.0.5.
Click to expand...
Click to collapse
I've been actively logging in hopes to grab the FTV Stick 5.0.3 -> 5.0.5 URL but at by the looks of it someone going from 3.x -> 5.0.5 should be able to grab it first. We shall see... :fingers-crossed:

autoprime said:
I've been actively logging in hopes to grab the FTV Stick 5.0.3 -> 5.0.5 URL but at by the looks of it someone going from 3.x -> 5.0.5 should be able to grab it first. We shall see... :fingers-crossed:
Click to expand...
Click to collapse
5 to 5 updates are all incremental, and I have them already. I need the 3.x -> 5.0.x update to get the full system image.

I have another stick on it's way from Amazon.co.uk, if it comes with 3.x how do I get what you need?

D-an-W said:
I have another stick on it's way from Amazon.co.uk, if it comes with 3.x how do I get what you need?
Click to expand...
Click to collapse
I just received the URLs from @AFTVnews.com

rbox said:
I just received the URLs from @AFTVnews.com
Click to expand...
Click to collapse
Is there any chance these will be urls will be posted, or is it worth posting, or some risk if they are posted? Couldn't we use the url to copy the image and force the update? I guess now that you have the URLs the best things will come, but I definitely want to get my stick to a rootable place =)

ImCoKeMaN said:
Is there any chance these will be urls will be posted, or is it worth posting, or some risk if they are posted? Couldn't we use the url to copy the image and force the update? I guess now that you have the URLs the best things will come, but I definitely want to get my stick to a rootable place =)
Click to expand...
Click to collapse
AFTVNews used to have a list of software updates and their URLs. Dunno if it still does. Unfortunately you can't force the update, as you need to be able to write to /cache to do it.

rbox said:
AFTVNews used to have a list of software updates and their URLs. Dunno if it still does. Unfortunately you can't force the update, as you need to be able to write to /cache to do it.
Click to expand...
Click to collapse
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times

ImCoKeMaN said:
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times
Click to expand...
Click to collapse
The software talks to the update server over ssl and sends it encrypted data. Can't be faked.

Just got the update on the firetv stick today. I guess I can kingroot it now, but is there any chance that there will be another root method for these?
Update: used kingroot 4.1 and it said it failed, but after a reboot it was in fact rooted. Next used adb with su command to pm disable dcp and ota

ImCoKeMaN said:
ok I saw it wasn't updated on @AFTVnews.com site ( http://www.aftvnews.com/software/ ) but I guess without r/w /cache it isn't as important wonder if we could replay the sw update check and use a pc proxy to push it. I'm sure I'm not thinking of something more advanced than what you already have though so I can stop and await the update patiently like everyone else, and see if you have the custom recovery already. I guess I'm just excited that after all this time the stick is finally software rootable. That hardware method was a little too tight soldering for me on the stick... at least without some other donor device to practice a few times
Click to expand...
Click to collapse
I've been meaning to update that page for some time now. It needs to be completely redone since there are now newer devices and forks due to the dev preview and the voice vs non-voice Fire TV Stick split.
The URLs are no secret. I hope to get around to updating my software page next week. For the time being, here is everything missing from that page for those interested.
Fire TV Update URLS
2nd-gen: 5.0 to 5.0.2.1
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-521044920-to-531006320.bin
2nd-gen: 5.0.2.1 to 5.0.2.2
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006320-to-531006420.bin
2nd-gen: 5.0 to 5.0.2.2
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-521044920-to-531006420.bin
2nd-gen: 5.0.2.2 to 5.0.3
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006420-to-532011220.bin
2nd-gen: 5.0.2.1 to 5.0.3
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-531006320-to-532011220.bin
2nd-gen: 5.0.3 to 5.0.3.1
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-532011220-to-534011720.bin
1st-gen Dev Preview - v5.0.3 (previous one is 5.0.0)
http://amzdigitaldownloads.edgesuit...te-kindle-bueller-51.5.3.2_user_532008220.bin
2nd-gen: 5.0.3.1 (534011720) to 5.0.4 (536116920)
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-534011720-to-536116920.bin
2nd-gen: 5.0.4 (536116920) to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...sloane_full_sloane-536116920-to-537174420.bin
1st-gen: 51.1.6.3 to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-kindle-bueller-51.5.3.7_user_537174420.bin
—————————————————————————
Fire TV Stick Update URLs
Production (non-voice) 54.1.2.3 (123067020)
http://amzdigitaldownloads.edgesuit...6fbe3/montoya-ota-54.1.2.3_user_123067020.bin
Dev Preview 5.0 (530042950)
http://amzdigitaldownloads.edgesuit...evpreview_montoya-54.5.3.0_user_530042950.bin
Dev Preview from 5.0 (530042950) to 5.0.3 (532008220)[54.5.3.2]
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.2_user_532008220.bin
Production (voice bundle) 5.0.3.2 (535062120) to 5.0.3.2/3 (535062420)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-535062120-to-535062420.bin
Production (voice bundle) 5.0.3.2/3 (535062420) to 5.0.4 (536116920)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-535062420-to-536116920.bin
Production (voice bundle) 5.0.4 (536116920) to 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-montoya_montoya-536116920-to-537174420.bin
Production (non-voice) 5.0.5 (537174420)
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin

Rooted, surprised not on here:

Hope some XDAers are able to get it rooted before it gets patched.
http://www.androidheadlines.com/201...te-available-for-android-root-access-bug.html

This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.

But, can we just load an older build using an auto-loader ?

Artemis-kun said:
This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.
Click to expand...
Click to collapse
I haven't.

santimaster2000 said:
But, can we just load an older build using an auto-loader ?
Click to expand...
Click to collapse
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader

Tipika said:
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader
Click to expand...
Click to collapse
This is not BB10, this is Android, and yes, I can downgrade, I've tested it.

can root using this exploit?

A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.

Seeing all those one click root apps i was thinking it was going to be easier to root the priv once an exploit was found
Sent from my Nexus 5X using XDA-Developers mobile app

FrankenDroid said:
A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.
Click to expand...
Click to collapse
Could you link me to that post please ?

Boom, right here: https://github.com/dosomder/iovyroot

So does this mean one can downgrade and then root using iovyroot?

Shani Ace said:
So does this mean one can downgrade and then root using iovyroot?
Click to expand...
Click to collapse
Theoretically, yes, you would need to add the absolute kernel addresses of the Priv to the source code, then compile it, but still, you would only get temp root, that's only good for using Titanium Backup and the like.

Ah okay, I understand.

So this root is only temp then? Still hoping something comes out but the community seems very small.