Related
Hello, my Kindle2 recently updated itself as soon as I connected to wifi the day I got it to 10.2.3 which doesn't appear to be rootable (?) currently.
I want to block access to further updates via my router since it only has wifi and will have to go through my router to get to the updates to prevent it from potentially updating to any other versions until someone figures out how to root this version of the software, or until I can find the information and get it to work.
Does anyone know exactly what addresses or whatnot I need to block on the router to prevent updates? Help greatly appreciated.
That is ridiculous. Next time you get root... just rename otacerts.zip and be done with it.
DssTrainer said:
That is ridiculous. Next time you get root... just rename otacerts.zip and be done with it.
Click to expand...
Click to collapse
I never -had- root.
It came, updated itself, and by the time I got around to looking up info on how to root it had updated itself.
Watch out if you are planning to root! Currently we do not know if this prevents new root!
New firmware 19084 was released yesterday. It predictably does not mention anything about fixing new root exploit, but anybody who would like to attempt root in future should prevent his Chromecast from updating.
https://productforums.google.com/forum/#!topic/chromecast/FOIWpJydK9Y
Thanks for the update! From google source site, it looks like they have yet to patch the new exploit, but until I have a copy in-house to test with, I can not confirm this.
They might purposefully neglect to mention any patch of the exploit in hopes of catching people by surprise....
Munch better safe than sorry for those who are still waiting for a teensy to root
HEADS UP: Seems that google HAS PATCHED the HubCap exploit, but did not post the source for it (to keep us guessing?). Please avoid this OTA if you want root!
How can we see which firmware is currently installed on the chromecast? I connected it back to my tv with router off so it can't update, but I see no info concerning firmware.
TRoN_1 said:
How can we see which firmware is currently installed on the chromecast? I connected it back to my tv with router off so it can't update, but I see no info concerning firmware.
Click to expand...
Click to collapse
Use the CCast setup app....
But I suggest you disconnect the Internet from the router before you check...
Asphyx said:
Use the CCast setup app....
But I suggest you disconnect the Internet from the router before you check...
Click to expand...
Click to collapse
I more than suggest. I don't know when it started, but the current Chromecast app will try to force an update before it completes setup.
I still have version 17977
I am not rooted I am hopping this new update allows native screen mirroring.
shamelin73 said:
I still have version 17977
I am not rooted I am hopping this new update allows native screen mirroring.
Click to expand...
Click to collapse
Screen mirroring is already available...A new update isn't going to change anything about that if you can't mirror already the issue is your phone or tablet not the CCast.
SO if you want to root I suggest not taking the Update until you do, You are not going to gain anything just lose the ability to root.
Asphyx said:
Screen mirroring is already available...A new update isn't going to change anything about that if you can't mirror already the issue is your phone or tablet not the CCast.
SO if you want to root I suggest not taking the Update until you do, You are not going to gain anything just lose the ability to root.
Click to expand...
Click to collapse
I am guessing I don't know how to get it to work then. I thought the Moto X was not supported yet till the update but I am guessing it is an update to the phone that I need.
Sent from my XT1053 using Tapatalk
shamelin73 said:
I am guessing I don't know how to get it to work then. I thought the Moto X was not supported yet till the update but I am guessing it is an update to the phone that I need.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Yes it is most likely the phone side that is the issue...
The Mirroring works for the devices that support mirroring and it is unlikely to change much in an update.
All the CCast does is receive a stream....the Phone/Tab does the majority of the work by creating the stream and not all units have the ability to do that yet.
Besides...Even if you root the CCast it won't take long for Team Eureka to update the rom to get any goodness the newest update has in it....
So even after you root if there DOES happen to be something that allows your phone to mirror you will get it in Team Eureka Rom soon enough.
If you have a Chromecast "tucked away" waiting to be rooted you might want to turn off WiFi and factory reset it so it has no ability to update when you power it up for rooting later.
Anyone know when the update mentioned in the io will be pushed?
Deeco7 said:
Anyone know when the update mentioned in the io will be pushed?
Click to expand...
Click to collapse
Been pushed already! SO if you haven't rooted yet and your unit has gotten the update your SOL...
It should also be noted, that once you get this update, a factory reset COULD essentially brick the device, or at least give you problems.
Sources:
https://plus.google.com/110558071969009568835/posts/QUjWK6fkHNR
...and
https://plus.google.com/110558071969009568835/posts/cEhdykfYstF
mdamaged said:
It should also be noted, that once you get this update, a factory reset COULD essentially brick the device, or at least give you problems.
Sources:
https://plus.google.com/110558071969009568835/posts/QUjWK6fkHNR
...and
https://plus.google.com/110558071969009568835/posts/cEhdykfYstF
Click to expand...
Click to collapse
Looks like they tried to push out an update to fix the new root exploit too quickly.
where is my backdrop? ;_;
It does not say what the heck it is, and I'm cautious about updating. Anyone know what this update does?
katrazi said:
It does not say what the heck it is, and I'm cautious about updating. Anyone know what this update does?
Click to expand...
Click to collapse
Probably a fix for the Stagefright vulnerability. http://forum.xda-developers.com/note-3-att/general/stock-receiving-update-t3177271
Im rooted on oc1 and want to know if this small update will break my root, so ill wait.
It is the stagefright patch. It will most likely break root if you update. All it fixes is stagefright and that's it. Nothing else.
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
I am trying this will update.
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
Any updates?
Also wondering if there is any updates? Would love to root this phone. Would help if I knew how to do it all.
I don't mean to be pessimistic, and I suppose it'll still be useful for those who don't want Marshmallow, but the rumor is it releases on the 18th. That's according to AT&T support, I might add. Again, keep up the great work, it isn't for nothing certainly, but I'm dying to update to Marshmallow, so this will be obsolete for me by the time you're finished.
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
Got the binary compiled with thanks to @zxz0O0. It didn't work on my device but it could work on yours.
1. Download file
2. Extract
3. "adb push iovyroot /data/local/tmp
4. "adb shell"
5." cd /data/local/tmp"
6."chmod 777 iovyroot"
7."./iovyroot"
How's this going?
I've been too busy to look at this lately. Maybe I'll try it next week or the week after.
Has anyone gotten it to work?
Ok I got the files in place how do you test?
G900aucu4bof3
Instructions say i need to roll back to OI5, im on OF3.
Ppl say all around that i can't roll back or anything, because that will brick it.
If this is not true, how can i do it, in order to test this root process?
I am on OF3 Rooted. If there is a way to do it from there then I will try it. Would this help achieve root on 6.0? If not then there is no reason for this.
I have a question, can I rollback to OI5 after I flashed the 4 PA2 files (BL, AP, CP, and CSC) on my phone?
dave1977nj said:
I am on OF3 Rooted. If there is a way to do it from there then I will try it. Would this help achieve root on 6.0? If not then there is no reason for this.
Click to expand...
Click to collapse
How is that possible? Did you have 4.4? Im on 5.0 And OF3, "everyone" say i can't do anything just yet.
If I am following the discussion here, folks are trying to root 5.0 OF3.
I am rooted G900AUCU4BOF3.
Three Steps:
Downgrade Samsung Galaxy S5 from 5.0 to 4.4 KitKat ([STRIKE]http://forums.androidcentra...amsung-galaxy-s5-5-0-4-4-kitkat.html[/STRIKE])I am mistaken. This is for the Verizon version NOT AT&T
Root 4.4.4 (http://forum.xda-developers.com/showpost.php?p=62467916&postcount=5)
Upgrade 4.4.4 to 5.0 Rooted (http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900)
NOTE: If you want to add WiFi Hotspot / Tether use G900A_OF3_TetherAddOn.zip instead of G900A_OC4_TetherAddOn.zip. The G900A_OF3_TetherAddOn.zip file is found at https://www.androidfilehost.com/?w=files&flid=27720 along with many other useful files such as other ROOTED Stock ROMs for the G900A.
I am rooted and on G900AUCU4BOF3. However, I started from 4.4.4
There is no 6.0 Root Method yet. Maybe you folks here working on iovyroot will advance the cause
bardell3600 said:
If I am following the discussion here, folks are trying to root 5.0 OF3.
I am rooted G900AUCU4BOF3.
Three Steps:
Downgrade Samsung Galaxy S5 from 5.0 to 4.4 KitKat (http://forums.androidcentral.com/sa...wngrade-samsung-galaxy-s5-5-0-4-4-kitkat.html)
Root 4.4.4 (http://forum.xda-developers.com/showpost.php?p=62467916&postcount=5)
Upgrade 4.4.4 to 5.0 Rooted (http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900)
NOTE: If you want to add WiFi Hotspot / Tether use G900A_OF3_TetherAddOn.zip instead of G900A_OC4_TetherAddOn.zip. The G900A_OF3_TetherAddOn.zip file is found at https://www.androidfilehost.com/?w=files&flid=27720 along with many other useful files such as other ROOTED Stock ROMs for the G900A.
There is no 6.0 Root Method yet. Maybe you folks here working on iovyroot will advance the cause
Click to expand...
Click to collapse
Nope. Nope nope nope
Downgrading from OF3 to NCE will brick your device.
Just upgrade from OF3 to OI5 and attempt to root.
UPDATE: Tried this on my phone a couple times. Keeps hanging at "Installing func ptr". If anyone around here knows how to fix it I can send any files required from the phone to make it work (@NavSad)
AptLogic said:
Nope. Nope nope nope
Downgrading from OF3 to NCE will brick your device.
Just upgrade from OF3 to OI5 and attempt to root.
UPDATE: Tried this on my phone a couple times. Keeps hanging at "Installing func ptr". If anyone around here knows how to fix it I can send any files required from the phone to make it work (@NavSad)
Click to expand...
Click to collapse
Which file are you having trouble on?
NavSad said:
Which file are you having trouble on?
Click to expand...
Click to collapse
I pushed the file to my /data/local/tmp, chmodded 777, and ran the file, but when I ran it, the process would go so far as something like "Starting Read Service" or something like that, display "Done", and then hang. Of course, seeing iovyroot in action, I know for a fact that it didn't finish, because there would be more output and I would get a root shell.
AptLogic said:
I pushed the file to my /data/local/tmp, chmodded 777, and ran the file, but when I ran it, the process would go so far as something like "Starting Read Service" or something like that, display "Done", and then hang. Of course, seeing iovyroot in action, I know for a fact that it didn't finish, because there would be more output and I would get a root shell.
Click to expand...
Click to collapse
Someone's had this problem here:https://github.com/dosomder/iovyroot/issues/37
The easiest way to get offsets for OI5 is to ask someone who is already rooted to do this:
su
cat /proc/kallsyms
Then ask them to copy and paste that output.
NavSad said:
Someone's had this problem here:https://github.com/dosomder/iovyroot/issues/37
The easiest way to get offsets for OI5 is to ask someone who is already rooted to do this:
su
cat /proc/kallsyms
Then ask them to copy and paste that output.
Click to expand...
Click to collapse
Well, unfortunately I don't know anyone with a rooted G900A. Most people I know made the smart decision to jump ship from AT&T and go to T-Mobile instead, and only one friend of mine has an S5 (G900T)
Shame... I got really hyped for nothing (oh well :/)
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
jonmike13 said:
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
Click to expand...
Click to collapse
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
sb1893 said:
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
Click to expand...
Click to collapse
I greatly appreciate you bringing me up to speed. It has been so long since I have done anything like this. It seems like I'm away for a year or so until I get a new phone, and then I'm back at it again. :laugh:
I used the first method on this link to carry out the deed: https://www.theandroidsoul.com/enab...ing-pixel-and-pixel-xl-verizon-sprint-others/
Really, the only reason I want to unroot is to update to 8.0. I would be totally fine with keeping root (would actually prefer it), but I want to get on 8.0, and I can't find any guides for updating and retaining root and my tethering. It appears as though that won't be an option for now based on your post unless I want to modify the build.prop. I wouldn't mind doing that, but I would need a guide for updating and then another guide for the build.prop, and I'm just not as brave as I used to be with this stuff. Back in the day, I would take some info a run with it, and adapt as necessary. It's almost like I have gotten "old" and haven't kept up with the times and constantly worry I'm going to turn the phone into a paper weight. :laugh:
EDIT: Would I be able to just use the OTA update and it basically undo everything I have done and then re-root myself and then do the build.prop mod, or would I need to get back to a factory state before being able to run the OTA update?
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
sb1893 said:
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
Click to expand...
Click to collapse
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
jonmike13 said:
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
Click to expand...
Click to collapse
Nice work! Welcome back to the fun! Good luck!