Related
seeing a bunch of tweets regarding another update. anyone have a link?
my apologies if this belongs in q&a
Never heard. Any changelogs?
Sent from my Nexus One using XDA App
found link here:
http://forum.xda-developers.com/showpost.php?p=7030780&postcount=3
It just popped up on my phone as I clicked this thread.
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
It states security fixes
El Daddy said:
It just popped up on my phone as I clicked this thread.
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
It states security fixes
Click to expand...
Click to collapse
Same here. I verified the URL with my alogcat, it's the same. Rebooting now....
Took a while to boot, but it booted and I'm on FRF91 now. Nice.
Will these updates to FRF85 be integrated into aosp??
clickwir said:
Took a while to boot, but it booted and I'm on FRF91 now. Nice.
Click to expand...
Click to collapse
It did take a long time to boot. I hooked it up to ddms to make sure it wasn't looping.
bewA said:
Will these updates to FRF85 be integrated into aosp??
Click to expand...
Click to collapse
These updates are pulled FROM aosp.
edit: This update appears to target Gmail.apk.
El Daddy said:
It states security fixes
Click to expand...
Click to collapse
With my old Android phone Samsung used the term "security fixes" as synonym for "fix glitches that allowed root access"… I hope Google is doing some real security fixes
nvm...................
It would be nice if we had a full update of it instead of incremental. That would be easier to make a rooted update from for those of us that are lazy.
lauslein said:
With my old Android phone Samsung used the term "security fixes" as synonym for "fix glitches that allowed root access"… I hope Google is doing some real security fixes
Click to expand...
Click to collapse
Nexus One is a dev phone, they will never fix root access.
513 said:
Nexus One is a dev phone, they will never fix root access.
Click to expand...
Click to collapse
But they may fix the new "root access without unlocking the bootloader" exploit that popped from FRF72 onward.
You're right, didn't think about this one.
hmm... I don't use gmail all that much. I think I'll stick to CM 6 as the alpha 3 or test 1 will be here soon with FRF91 I'm sure
another Froyo OTA Update [FRF91]
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
From FRF85B to FRF91
I can´t believe it... Froyo will never be completly done i think
Aggghhh I'm getting annoyed with all these updates :\
I just want the final one jesus!
izmar said:
aggghhh i'm getting annoyed with all these updates :\
i just want the final one jesus!
Click to expand...
Click to collapse
+9999999999
izmar said:
Aggghhh I'm getting annoyed with all these updates :\
I just want the final one jesus!
Click to expand...
Click to collapse
LoL! They'll never have a "Final" one...
Amazon has updated their Fire TV Source Code page with a new software package: version 51.1.3.0_user_513011520
I haven't heard of anyone receiving this version in an OTA update yet, but I figured I'd let everyone know to keep an eye out and get the discussion going for the inevitable rollout.
Anyone already stuck without root would probably get that update since they are stuck.
They have no choice anyway unless they still use one of blocking methods.
We might need at least one person to stay on the first unrootable version in case rbox or anyone else could find a new exploit or something.
I wonder,what has changed in this new update anyway?
Edit:Amazon,listen to the users of Fire TV and add support for USB Media Storage.
It probably had a negative effect on sales,especially since the blocked root access which was the only way they could access USB media storage using stickmount.
retroben said:
Anyone already stuck without root would probably get that update since they are stuck.
They have no choice anyway unless they still use one of blocking methods.
We might need at least one person to stay on the first unrootable version in case rbox or anyone else could find a new exploit or something.
I wonder,what has changed in this new update anyway?
Edit:Amazon,listen to the users of Fire TV and add support for USB Media Storage.
It probably had a negative effect on sales,especially since the blocked root access which was the only way they could access USB media storage using stickmount.
Click to expand...
Click to collapse
so native enabled usb storage with the update? we need to get that aspect without updating for us rooted users. im kinda tired of the stick mount method. it would be nice to not need it
So this tarball is smaller than the previous, but I can see no difference in it. Quite strange...
retroben said:
Edit:Amazon,listen to the users of Fire TV and add support for USB Media Storage.
It probably had a negative effect on sales,especially since the blocked root access which was the only way they could access USB media storage using stickmount.
Click to expand...
Click to collapse
I don't think there was any doubt they would eventually add it. Ouya did the same thing. Originally yhey said it was over security concerns they needed to work out.
lost my root...Help Geohot!!!
Damn it!!! I just lost my root. I totally forgot to disable auto update on my Fire TV cuz was enjoying it all customized to my liking. Totally forgot to hack auto update feature. This sucks!!! :crying: It just happend about 10 min ago. Came back to tv and saw that amazon home screen was on screensaver. Knew that I had left Fire TV on xbmc. Went right to settings to see if box had been updated, and sure enough it was 51.1.3.0_user_513011520. So bummned out ritht now. I have another box that is disabled for auto updates, but this one is back to stock features. XBMC still works, just all root access apps are no longer working. Have to wait for root access to arrive again...Help Geohot!!! We need you!!! Yeah...this sucks.
oscargo29 said:
Damn it!!! I just lost my root. I totally forgot to disable auto update on my Fire TV cuz was enjoying it all customized to my liking. Totally forgot to hack auto update feature. This sucks!!! :crying: It just happend about 10 min ago. Came back to tv and saw that amazon home screen was on screensaver. Knew that I had left Fire TV on xbmc. Went right to settings to see if box had been updated, and sure enough it was 51.1.3.0_user_513011520. So bummned out ritht now. I have another box that is disabled for auto updates, but this one is back to stock features. XBMC still works, just all root access apps are no longer working. Have to wait for root access to arrive again...Help Geohot!!! We need you!!! Yeah...this sucks.
Click to expand...
Click to collapse
And I'm assuming you actually tried all the root methods and didn't just assume it wasn't going to work? I know the reports were that 51.1.2.0 didn't allow root, but unless they are lying about their source dump, I see no evidence that they patched the kernel vulnerability.
rbox said:
And I'm assuming you actually tried all the root methods and didn't just assume it wasn't going to work? I know the reports were that 51.1.2.0 didn't allow root, but unless they are lying about their source dump, I see no evidence that they patched the kernel vulnerability.
Click to expand...
Click to collapse
What other root method might you be talking about. All I know of is towelroot by geohot. Am i wrong about this being the only root method. I sure hope I'm wrong.
oscargo29 said:
What other root method might you be talking about. All I know of is towelroot by geohot. Am i wrong about this being the only root method. I sure hope I'm wrong.
Click to expand...
Click to collapse
I remember people talking about different versions of it.
rbox said:
I remember people talking about different versions of it.
Click to expand...
Click to collapse
I've read that v2 of towelroot does not work on the Fire TV. I personally have not tried v2. I've used both v1 and v3 of towelroot successfully root on 51.1.1.0_user_511070220 and older.
One of my Fire TV's just got the update notification. Unfortunately it's my primary device, so I blocked the update. I'll be trying to get the update on a Fire TV that I don't mind losing root on. WIll report back shortly.
The download URL for the version 51.1.3.0_user_513011520 update is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.3.0_user_513011520-signed.bin
Just a bit of clarification as the first mention of USB wasn't clear to me the later posts assumed USB is enabled in this version. Can anyone actually confirm that they have a USB drive working on this latest firmware version?
I just checked for updates and my FireTV is still on 51.1.1.0_user_511070220 with no new updates found. It never updated to the 51.1.2.0 version, was never rooted, updates are not blocked, at least not intentionally.
AFTVnews.com said:
I've read that v2 of towelroot does not work on the Fire TV. I personally have not tried v2. I've used both v1 and v3 of towelroot successfully root on 51.1.1.0_user_511070220 and older.
Click to expand...
Click to collapse
When you say older, do you mean older as in update 51.1.2.0_user_512073320. Cuz update 51.1.3.0_user_513011520 is not able to root with towelroot v3. Wishful thinking on my part thinking it will work.
I have rooted 3 Fire TV's. All 3 came with software 51.1.0_user_510047320 and I updated all to 51.1.2.0_user_512073320. I rooted all with towelroot v3. Towelroot v3 no longer worked after update 51.1.3.0_user_513011520. That's the first thing I tested after auto update happened. Towelroot v3 state's "This phone isn't currently supported". So no "rain" for me I'll try to find v1 or v2 of towelroot and see what happens.
---------- Post added at 01:38 AM ---------- Previous post was at 01:03 AM ----------
Well that was quick...and painful. Towelroot v1, v2, and v3 are now confirmed by me, to not be able to root Amazon Fire TV.
O'well, I tried.
v1 just halts but was able to press back button and get out. v2 and v3 both say "This phone isn't currently supported". Good thing I have a spare Fire TV
In all honesty, as long as XBMC still runs on Amazon Fire TV, this shouldn't be such a total loss.
But when you get your settings and your customization just right, and then its all gone, it really hurts...a lot. :laugh:
Just got to wait now till further updates on root for this last Fire TV update.
Just a FYI. My first 2 Fire Tv's came from Amazon. 3rd one was from Best Buy. All came with Amazon's 1st firmware put out for this box 51.1.0_user_510047320.
I was expecting latest update when ordered from Amazon for sure. That was weird.
Heads up Everyone. Don't forget to disable OTA update for Amazon Fire TV so you can keep Root Access.
Silly me forgot to follow this big rule.:silly:
I was able to manually install v51.1.3.0_user_513011520 onto a rooted Fire TV that had not received this update.
I can confirm that towelroot v1, v2, and v3 all CAN NOT root the Fire TV running v51.1.3.0_user_513011520. Towelroot v3 reports that the 'phone' is not compatible, while v1 and v2 just sit there frozen when you press "make it rain".
I'm currently going through to determine what has changed with this new update. Please list anything you'd like me to check.
Thanks for checking into this update.
AFTV news:
Please check if the USB port is active and allows access to external storage from XBMC. I don't care if I can root as long as it supports external USB storage... 4TB hopefully
alexb101 said:
Please check if the USB port is active and allows access to external storage from XBMC. I don't care if I can root as long as it supports external USB storage... 4TB hopefully
Click to expand...
Click to collapse
I don't know why everyone thinks out of no where Amazon would add USB support...
---------- Post added at 07:11 PM ---------- Previous post was at 06:56 PM ----------
Preliminary examination shows that the main bootloader hasn't changed, but the sbl1/2/3 and the rpm images have changed. The image was built on September 5th. It looks like they added german to the recovery. Not sure how it decides german vs english, probably means there is a difference between the english and german versions.
alexb101 said:
AFTV news:
Please check if the USB port is active and allows access to external storage from XBMC. I don't care if I can root as long as it supports external USB storage... 4TB hopefully
Click to expand...
Click to collapse
That's a big NO. XBMC does not detect any external storage. I don't think Amazon will give end users this feature.
Only root access will allow this. Hoped might just work, but only way this would work is with root access.
Wishful thinking Amazon will add this feature.
A "no go" for external storage on latest update 51.1.3.0_user_513011520.
Hate being the one know this first hand.
rbox said:
I don't know why everyone thinks out of no where Amazon would add USB support...
---------- Post added at 07:11 PM ---------- Previous post was at 06:56 PM ----------
Preliminary examination shows that the main bootloader hasn't changed, but the sbl1/2/3 and the rpm images have changed. The image was built on September 5th. It looks like they added german to the recovery. Not sure how it decides german vs english, probably means there is a difference between the english and german versions.
Click to expand...
Click to collapse
Damn, it looks like the german Fire TV will be shipped with the unrootable firmware
Hope we can find a way to get it rooted soon.
Is sideloading still working with this firmware? Without XBMC, this box would be useless for most people.
Xedos9er said:
Damn, it looks like the german Fire TV will be shipped with the unrootable firmware
Hope we can find a way to get it rooted soon.
Is sideloading still working with this firmware? Without XBMC, this box would be useless for most people.
Click to expand...
Click to collapse
you dont need root to install xbmc. just sideload the app
I was wondering if there is any specific person or group we could reach out to to help root the Nexus Player. The bootloader is easily unlocked so all we need is root to enabled quite a few features that the NP needs (access to usb drives/keys from all apps, etc).
Chainfire is, of course, the obvious first contact, but is there anyone else that has shown Lollipop kernel experience to date on any other Nexus platforms?
You need to wait for the insecure-boot.img to be uploaded by someone.
Insecure boot.img
Insecure boot.img for Nexus Player tested and works, compiled from aosp_fugu-eng.
adb shell returns a #.
I imagine it is only a matter of time until we'll see TWRP for the NP. TWRP for the Nexus 9 was just released today.
guylamar2006 said:
Insecure boot.img for Nexus Player tested and works, compiled from aosp_fugu-eng.
adb shell returns a #.
Click to expand...
Click to collapse
can someone try this with supersu? Chainfire released 2.23 version for the 5.0 devices. I'd try it myself but my NP didn't manage to leave the warehouse yet.
I asked ChainFire on the official cf-autroot thread about autoroot for the NP earlier this week. He said he will getting a NP soon and would look at providing an autoroot package for it.
I like the TRWP approach a little more and may move to that for my Nexus 9.
IskiE
isketerol said:
I asked ChainFire on the official cf-autroot thread about autoroot for the NP earlier this week. He said he will getting a NP soon and would look at providing an autoroot package for it.
I like the TRWP approach a little more and may move to that for my Nexus 9.
IskiE
Click to expand...
Click to collapse
just released root myself :good:
bunchies said:
just released root myself :good:
Click to expand...
Click to collapse
Thanks !
But where ? I looked at your recent posts and didn't see anything downloadable.
mikereidis said:
Thanks !
But where ? I looked at your recent posts and didn't see anything downloadable.
Click to expand...
Click to collapse
Check the development section
About to release the latest OTA version any minute now
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.
** Update**
Seems after the LS997ZV4 update was pulled off, they changed it to LS997ZV5 instead and just got it 12/26/16
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I've been waiting for the OTA update on my phone, I have been manually checking for updates too but nothing happens!
The release date says 12/5/16 and I usually can get updates by manually checking with other android devices, not this time though..
https://support.sprint.com/support/...20:FindAndUpdateTheSoftwareVersionOnYourLgV20
Nope
Nope and don't take it if u planning on rooting in the near future
pbedard said:
Nope and don't take it if u planning on rooting in the near future
Click to expand...
Click to collapse
Thanks for your response!
rooting isn't important for me as it was before lollipop, there's not much bloatware on the V20 and ads are being taken care of with adguard.
It's just bug fixes and security patches anyways
pbedard said:
It's just bug fixes and security patches anyways
Click to expand...
Click to collapse
Yes I know! Security and bug fixes are important..
ls9997zv4 update no longer shown on sprint website
I saw that update listed on Sprint's site last week and was also frustrated not to get it. It must have had an error because it has been pulled. We are lucky not to received flawed firmware.
They probably pulled it to fix the exploit they have found for rooting the phone.
fury161 said:
they probably pulled it to fix the exploit they have found for rooting the phone.
Click to expand...
Click to collapse
wooo i caused something!
Is there a way to stop the update from appearing or stop the phone from checking? I would like to accept updates only once people here assure us that it won't break the root method, given I may root at some point.
Sent from my LG-LS997 using Tapatalk
I just got updated to LS997ZV5 Dec 1 Security patches, fixed an issue with loud speaker and stuff I don't remember.
I got it on 12/24. I had to click "check for update" quite a few times for it to show up.
Same here. I hoped it would have fixed the speaker distortion problem. But it did nothing for me.
Zor Omega said:
Same here. I hoped it would have fixed the speaker distortion problem. But it did nothing for me.
Click to expand...
Click to collapse
to be Honest, never had the issue..
I was hoping for maybe camera software fine tuning
I also did a full restore, I like to start fresh with updates
So is it confirmed that the root method on the ZV5 no longer works? I just got my V20 off swappa and it already had the ZV5 installed. :crying:
longunmin said:
So is it confirmed that the root method on the ZV5 no longer works? I just got my V20 off swappa and it already had the ZV5 installed. :crying:
Click to expand...
Click to collapse
Ditto, just got my V20 and it has ZV5 installed......ugh...........praying theres a way to roll back
Edit.....nevermind......my zv5 did manage to get root using DirtySanta....Profit!
jauger said:
Ditto, just got my V20 and it has ZV5 installed......ugh...........praying theres a way to roll back
Edit.....nevermind......my zv5 did manage to get root using DirtySanta....Profit!
Click to expand...
Click to collapse
Awesome! So you just followed the Dirty Santa guide from the other thread and you were golden? Is everything functional and working properly?
longunmin said:
Awesome! So you just followed the Dirty Santa guide from the other thread and you were golden? Is everything functional and working properly?
Click to expand...
Click to collapse
I read everything I could find about rooting this thing and read all the comments that the bootloader exploit was fix with the December patch.but nothing convinced me not to...Im a old Samsung guy, Note 2, 3 & 4 so rooting without having Odin to back me up was a tad daunting as well as having to remember how to use ADB....I took a chance and it worked......I got the sd corrupt error ( no biggie, I had backups) and battery drain is kinda high ( no sprint custom kernels yet) ....of course it not being a stock sprint rom things like wifi calling, sprint zone and voicemail are missing ( but Team Dev now hows a stock rooted sprint rom out, Ill try that in the am) everything is running just fine...installed all my apps, made a titanium backup and a twrp backup.....
jauger said:
I read everything I could find about rooting this thing and read all the comments that the bootloader exploit was fix with the December patch.but nothing convinced me not to...Im a old Samsung guy, Note 2, 3 & 4 so rooting without having Odin to back me up was a tad daunting as well as having to remember how to use ADB....I took a chance and it worked......I got the sd corrupt error ( no biggie, I had backups) and battery drain is kinda high ( no sprint custom kernels yet) ....of course it not being a stock sprint rom things like wifi calling, sprint zone and voicemail are missing ( but Team Dev now hows a stock rooted sprint rom out, Ill try that in the am) everything is running just fine...installed all my apps, made a titanium backup and a twrp backup.....
Click to expand...
Click to collapse
Thank you! I may wait to see how the stock sprint ROM works and then I'll jump in. Definitely won't update with any security patches in the meantime