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.
Related
https://www.youtube.com/watch?v=TBYbWZNtCjA
mj0528 said:
https://www.youtube.com/watch?v=TBYbWZNtCjA
Click to expand...
Click to collapse
I saw this posted earlier. I think the big question is does he release it and thus burn an exploit or does he wait for 4.3 in hopes that it is still there and thus provides a root option for 4.3 as well. I'm not sure which is my preference. The only thing I personally miss by not being rooted is the tethering, which I only use in emergency situations anyway, so its not crucial for me. However, it is nice to have freedom from the carrier release cycle if we get a way to flash roms without an unlocked bootloader.
bugsy said:
I saw this posted earlier. I think the big question is does he release it and thus burn an exploit or does he wait for 4.3 in hopes that it is still there and thus provides a root option for 4.3 as well. I'm not sure which is my preference. The only thing I personally miss by not being rooted is the tethering, which I only use in emergency situations anyway, so its not crucial for me. However, it is nice to have freedom from the carrier release cycle if we get a way to flash roms without an unlocked bootloader.
Click to expand...
Click to collapse
you got any idea what was going on with the order in which he clicked on things in the about phone menu? was that part of the exploit or what? I couldn't tell if it was doing something or he was just showing you it was the OTA.
jayboyyyy said:
you got any idea what was going on with the order in which he clicked on things in the about phone menu? was that part of the exploit or what? I couldn't tell if it was doing something or he was just showing you it was the OTA.
Click to expand...
Click to collapse
Just proving the version.
I would rather that he wait and see if the exploit is still available in 4.3. There's a way to go back to the first build from this update, so if you really need root that badly, you can always just do that. Once SafeStrap is ready, we'll probably see a zip of the update that can be flashed, so I find little reason for him to burn this flaw right now.
freak4dell said:
I would rather that he wait and see if the exploit is still available in 4.3. There's a way to go back to the first build from this update, so if you really need root that badly, you can always just do that. Once SafeStrap is ready, we'll probably see a zip of the update that can be flashed, so I find little reason for him to burn this flaw right now.
Click to expand...
Click to collapse
how would one go back to the first build after the update is applied?
mj0528 said:
how would one go back to the first build after the update is applied?
Click to expand...
Click to collapse
You can't. Jcase stated in another thread that the exploit he used wasn't practical for most users so he probably won't release it. Was more a proof of concept
Sent from my XT1058 using Tapatalk 4
mj0528 said:
how would one go back to the first build after the update is applied?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=46007395
Not sure if anybody ever tried that on a locked device, but I think it should work.
Amazon has published the source code for the Fire TV at http://www.amazon.com/gp/help/customer/display.html?nodeId=201452680
Please code responsibly.
35395596831
elmerohueso said:
Amazon has published the source code for the Fire TV at ...
Please code responsibly.
Click to expand...
Click to collapse
PSA: I've tracked the kernel part of the code drop back to the closest msm-3.4 tag, so we have a partial git history. Please use that as a starting point rather than importing the kernel src into a new git tree without history:
git://github.com/freedreno/kernel-msm firetv
robclark said:
PSA: I've tracked the kernel part of the code drop back to the closest msm-3.4 tag, so we have a partial git history. Please use that as a starting point rather than importing the kernel src into a new git tree without history:
git://github.com/freedreno/kernel-msm firetv
Click to expand...
Click to collapse
This does not appear to match the binary... wth Amazon
*EDIT*
Your source was for the first release they did, the initial OTA came with a new kernel, and numerous fixes, including fixing the get_user/put_user vuln (CVE-2013-6282) which was what caused the confusion. Binary not vuln, but your source was.
My bad for not pulling their latest source.
jcase said:
This does not appear to match the binary... wth Amazon
Click to expand...
Click to collapse
hmm, well no guarantees amazon actually posted the correct kernel dump.. that could be an extra headache. I'm a bit new to the android side of things so don't really know what Amazon's track record is like.
fwiw, the src drop I grabbed kernel from was firetv_src_51.1.0.1_user_510055620.tar.bz2 (md5sum: 0cba752bd8e6154667120718efe619b2)
---------- Post added at 12:15 AM ---------- Previous post was at 12:05 AM ----------
jcase said:
This does not appear to match the binary... wth Amazon
*EDIT*
Your source was for the first release they did, the initial OTA came with a new kernel, and numerous fixes, including fixing the get_user/put_user vuln (CVE-2013-6282) which was what caused the confusion. Binary not vuln, but your source was.
My bad for not pulling their latest source.
Click to expand...
Click to collapse
oh, whoops, should have read your later reply first
when I get my fire-tv tomorrow, should I take steps to avoid OTA update?
robclark said:
hmm, well no guarantees amazon actually posted the correct kernel dump.. that could be an extra headache. I'm a bit new to the android side of things so don't really know what Amazon's track record is like.
fwiw, the src drop I grabbed kernel from was firetv_src_51.1.0.1_user_510055620.tar.bz2 (md5sum: 0cba752bd8e6154667120718efe619b2)
---------- Post added at 12:15 AM ---------- Previous post was at 12:05 AM ----------
oh, whoops, should have read your later reply first
when I get my fire-tv tomorrow, should I take steps to avoid OTA update?
Click to expand...
Click to collapse
hmm you sure? firetv_src_51.1.0.1_user_510055620.tar.bz2 is not vulnerable, but the source you linked to is
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Blocking the server providing the OTA alone won't allow it to boot, intercepting it and telling the unit that no ota is available probably would.
so is the OTA gonna patch the vuln that allows root ?
jcase said:
hmm you sure? firetv_src_51.1.0.1_user_510055620.tar.bz2 is not vulnerable, but the source you linked to is
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Blocking the server providing the OTA alone won't allow it to boot, intercepting it and telling the unit that no ota is available probably would.
Click to expand...
Click to collapse
hmm, can you check md5sum on the file you got and see if it matches what I have. There were two files available to download when I grabbed the src drop..
fwiw, it is no problem to update the kernel to a newer src drop.. the only thing that will take any time is actually downloading the src drop
robclark said:
hmm, can you check md5sum on the file you got and see if it matches what I have. There were two files available to download when I grabbed the src drop..
fwiw, it is no problem to update the kernel to a newer src drop.. the only thing that will take any time is actually downloading the src drop
Click to expand...
Click to collapse
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
jcase said:
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
Click to expand...
Click to collapse
damn.. well, I'll go ahead and download the other tarball (will take a while, on slow network connection at the moment) and import it on another branch and see what the difference is..
btw, if anyone else has downloaded firetv_src_51.1.0.1_user_510055620.tar.bz2 more recently, could you check md5sum to see if file has changed since the day of the announcement?
bkdg100 said:
so is the OTA gonna patch the vuln that allows root ?
Click to expand...
Click to collapse
OTA patched at least two that would have allowed root. Doesn't patch the one I am working with right now.
robclark said:
damn.. well, I'll go ahead and download the other tarball (will take a while, on slow network connection at the moment) and import it on another branch and see what the difference is..
Click to expand...
Click to collapse
I can redownload it if it is a bother, no big deal.
jcase said:
I can redownload it if it is a bother, no big deal.
Click to expand...
Click to collapse
well, if you have a good network connection, you can probably get it faster than I can..
I'm keeping all the files I download (not out of disk space yet).. tomorrow when I have a good connection I'll grab firetv_src_51.1.0.1_user_510055620.tar.bz2 again to check (if no one has confirmed before then)
just got mine tonight , figured i would hold off on the updates until a secure root exploit id posted,. anyone script a network mitm to spoof the update for now?
bkdg100 said:
just got mine tonight , figured i would hold off on the updates until a secure root exploit id posted,. anyone script a network mitm to spoof the update for now?
Click to expand...
Click to collapse
I believe it force updates OTAs, so no holding off
jcase said:
Possible to mitm the update process. I do believe it is http. This is why i was asking for a pcap of it, but by the time I got mine I had already confirmed I could do what I needed and didn't bother actually get a pcap.
Click to expand...
Click to collapse
btw if anyone else did get a packet trace of it contacting the ota server, I'd be interested to see it. (Well, if no one replies before tomorrow when my box, then don't bother, I can get the trace myself. I'm just impatiently waiting now )
is your root exploit secure enough to outlive the updates ? any chance a virgin box can be spoofed later to limit the OTA from patching everything ?
robclark said:
btw if anyone else did get a packet trace of it contacting the ota server, I'd be interested to see it. (Well, if no one replies before tomorrow when my box, then don't bother, I can get the trace myself. I'm just impatiently waiting now )
Click to expand...
Click to collapse
Not to my knowledge, possibly if you can feed it a low version number then you can boot without taking the OTA, and then use public roots
bkdg100 said:
is your root exploit secure enough to outlive the updates ? any chance a virgin box can be spoofed later to limit the OTA from patching everything ?
Click to expand...
Click to collapse
Amazon updates reflash everything, they don't do delta updates. No ota survival
jcase said:
OTA patched at least two that would have allowed root. Doesn't patch the one I am working with right now.
Click to expand...
Click to collapse
just ran the bluebox app for the heck of it - it claims my firetv is safely patched for 8219321, 9695860, and 10148349 (those are the only 3 it tests for) - yes, I do have the ota update.
are there other recent ones android-using peoples of the world should be aware about? 9950697?
tarvoke said:
just ran the bluebox app for the heck of it - it claims my firetv is safely patched for 8219321, 9695860, and 10148349 (those are the only 3 it tests for) - yes, I do have the ota update.
are there other recent ones android-using peoples of the world should be aware about? 9950697?
Click to expand...
Click to collapse
I checked all of the zip parser bugs first, obvious choice considering it runs 4.2.2.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
jcase said:
Sorry can't, i deleted it after extraction. Running out of space on the disk I keep android data on, so I'm bit tight about it
Click to expand...
Click to collapse
I've pushed firetv-0 branch which is from firetv_src_51.1.0_user_510047320.tar.bz2 ... definitely looks like some additional error checking, etc, between the two. Maybe what I thought was the original src drop was the update and visa versa. Not what I'd expect given the file names, but it would explain...
FXZ SU4.21 Thanks to @stras1234 for the initial FXZ! Thanks to @Skrilax_CZ for posting them to the SBF site!
Use my RSD Flasher to flash it.
I guess it still needs to be spelled out in this day and age, but, yes, you WILL lose root if you use this. It's an FXZ that overwrites all partitions with stock. So uh, yea, there's that.
I love you.
In a not creepy way.
Sent from my XT1080DE
LOL you're welcome.
Thanks, I hope somebody finds a way to root it.
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
SamuriHL said:
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
Click to expand...
Click to collapse
v4.4.4 would not install and this fixed it ... all without losing any data ... big thanks!
NP enjoy! Stras1234 is the man for giving me the FXZ and allowing me to post it.
SamuriHL said:
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
Click to expand...
Click to collapse
Well, not easy! so far Im not needing root access, there are no roms and wifi tether works for me without doing anything, Im using the phone outside US of course. I would like to remove some bloatware.
I love modding and all that things but Im happy with stock kitkat. I think we could get android L sometime in the future.
SamuriHL said:
FXZ SU4.21 Thanks to @stras1234!
Use my RSD Flasher to flash it.
Click to expand...
Click to collapse
Great work samurihl! This isn't even out of soak and we already have the fxz!
I have no doubt these phones will get L. They'll only be a year old at that point so I'd not worry about it.
Does anyone know if you have to edit the xml file and remove the getvar line like in 4.4? Or just RSD Lite and go?
Is it supposed to take forever to flash the system.img?
I've let it go for between 5 and 10 minutes, and it's still on system.
ad fu said:
Does anyone know if you have to edit the xml file and remove the getvar line like in 4.4? Or just RSD Lite and go?
Click to expand...
Click to collapse
That's why I gave a link to my tool. It does all that for you plus allowing you to keep your data.
LunaticSerenade said:
Is it supposed to take forever to flash the system.img?
I've let it go for between 5 and 10 minutes, and it's still on system.
Click to expand...
Click to collapse
Yes, it's over a gig in size. It takes a while.
SamuriHL said:
That's why I gave a link to my tool. It does all that for you plus allowing you to keep your data.
Yes, it's over a gig in size. It takes a while.
Click to expand...
Click to collapse
Ah. Makes sense. Thanks!
Samuri thanks a lot I love you to but in a creepy way . This has to be a record for an fxz being available.
Sent from my XT1080 using XDA Premium 4 mobile app
Yea, stras1234 rocks on that FXZ front. He got the HD/M FXZ's early for us last time, too. You checked out my new tool yet, btw? I made it as easy to flash FXZ's as possible now.
Not yet I saw you were working on it. I will check it out when I get home and use it. I always like to run a fxz after an update.
Sent from my XT1080 using XDA Premium 4 mobile app
It's pretty simple to use.
I would like to know if this is the final version or when the final ota update is released there will be another?
I take it you don't know what a soak test is? Unless something goes wrong, which is unlikely, this will be pushed OTA in the next few days.
Hi All,
Please forgive me if this sounds like a noob question...
Here is the situation:
Rooted verizon galaxy s5 with towel root.
Cannot install the new OTA update they just released, the update downloads and fails on the attempt to install. Shows the little green android with red ! in his belly:cyclops:
Please help! You guys are awesome! I really want this update
nickd1976 said:
Hi All,
Please forgive me if this sounds like a noob question...
Here is the situation:
Rooted verizon galaxy s5 with towel root.
Cannot install the new OTA update they just released, the update downloads and fails on the attempt to install. Shows the little green android with red ! in his belly:cyclops:
Please help! You guys are awesome! I really want this update
Click to expand...
Click to collapse
First, plug phone into computer, and install updater software from the phone that is on the device in 'Installer Mode'. Take the download on the PC, then follow directions below, and you can still have root after.
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For more information, read through this thread as well.
http://forum.xda-developers.com/verizon-galaxy-s5/general/verizon-ota-rolling-t2834027
Thank you so much!!!
Sent from my SM-G900V using XDA Free mobile app
Some reason the upgrade button is greyed out
kprice8 said:
First, plug phone into computer, and install updater software from the phone that is on the device in 'Installer Mode'. Take the download on the PC, then follow directions below, and you can still have root after.
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For more information, read through this thread as well.
http://forum.xda-developers.com/verizon-galaxy-s5/general/verizon-ota-rolling-t2834027
Click to expand...
Click to collapse
Hi again,
I installed the upgrade assistant in installer mode but for some reason it is not picking up the new NE9 update on my computer. See attached print screen. Very strange.. It sees the update on my phone to download though.:cyclops: Do you know why this is and how I can get it to see the update on the upgrade assistant as you mentioned?
Kind Regards
Can you explain why you want the update so bad? You do realize that rooting and accepting official otas is completely contradictory, correct? OTAs are generally what fix things like what towelroot exploits. If you accept official OTA, you will likely lose root.
But can't I just re root after the ota? I guess the reason I want the Ota because I heard of camera enhancements and stability fixes
Sent from my SM-G900V using XDA Free mobile app
nickd1976 said:
But can't I just re root after the ota? I guess the reason I want the Ota because I heard of camera enhancements and stability fixes
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
edit: in this case I believe folks have figured out a work around for keeping root with the update. In general though, if you value root and what it provides you do not accept official releases.
ks3rv3rg said:
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
Click to expand...
Click to collapse
@ks3rv3rg I believe the links mentioned above provide a workaround for the Root to be kept after updating.
As for the problem nick, I can't help you there. I haven't personally take it as I see taking OTA's is silly with a rooted phone you can modify to be much more. Perhaps someone else who has done it will chime in...
Thank you both for your perspectives.. Plus, I can always just wait for a ROM that currently has the update installed.
ks3rv3rg said:
No. OTA have patches for known security flaws as well. The flaw that towelroot relies on is closed after the new OTA. Meaning, no more root.
edit: in this case I believe folks have figured out a work around for keeping root with the update. In general though, if you value root and what it provides you do not accept official releases.
Click to expand...
Click to collapse
kprice8 said:
@ks3rv3rg I believe the links mentioned above provide a workaround for the Root to be kept after updating.
As for the problem nick, I can't help you there. I haven't personally take it as I see taking OTA's is silly with a rooted phone you can modify to be much more. Perhaps someone else who has done it will chime in...
Click to expand...
Click to collapse
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
nickd1976 said:
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
Click to expand...
Click to collapse
I just saw that JasmineROM came out and it's updated to NE9 and all you do is flash the stuff. Check it out.
http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-jasminerom-v1-0-bases-t2836387
nickd1976 said:
Thank you both for educating me on this. Ill try the work around to try to keep the root and update. I just wish I could get the Verizon update assistant to download the NE9. Either way Ill just wait for a ROM with the new OTA.
Click to expand...
Click to collapse
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
ks3rv3rg said:
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
Click to expand...
Click to collapse
Me? Directly above you? XD lol
ks3rv3rg said:
Good choice. I know I saw someone mention that they were building a safestrap flashable ota rom.
Click to expand...
Click to collapse
I think you are referring to my safestrap flashable OTA zip file. I'm going to keep that one in my back pocket for the next OTA since the kernel swap worked.
I'm happy to say I installed this rom and the firmware and it rocks!! Thank you .plus I got my download booster and my overclock settings!!
Sent from my SM-G900V using XDA Free mobile app
I have a similar question but reversed. How do I stop it from updating and it from asking me to update? I have the free version of titanium backup and can't freeze it. Is their another way? I can't turn off SDM that runs the ota upgrade i can only force stop it.
jpcloudsurf said:
I have a similar question but reversed. How do I stop it from updating and it from asking me to update? I have the free version of titanium backup and can't freeze it. Is their another way? I can't turn off SDM that runs the ota upgrade i can only force stop it.
Click to expand...
Click to collapse
Remove it. Won't hurt anything.
TiBu
Buying the pro version of TiBu was the best money I ever spent!!!!
What is tibu?
Sent from my SM-G900V using XDA Free mobile app
nickd1976 said:
What is tibu?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Titanium Backup
HDX - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.6_user_326001820.bin
HDX 8.9 - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.6_user_326001820.bin
Root possibility - yes, Towelroot.
ONYXis said:
HDX - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.6_user_326001820.bin
HDX 8.9 - https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.6_user_326001820.bin
Root possibility - unknown.You can try and tell us)
But boot.img is totally similar to x.3.2.5 and changed files are apps, frameworks and trapz_scripts only. So towelroot must work.
Click to expand...
Click to collapse
2.5 won't let us downgrade currently. I wonder if 3.2.6 will. I really doubt it.
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
r3pwn said:
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
Click to expand...
Click to collapse
Towelroot still works on latest update but can't rollback.
Sent from my GT-N5110 using XDA Free mobile app
ptrsnshane said:
Towelroot still works on latest update but can't rollback.
Sent from my GT-N5110 using XDA Free mobile app
Click to expand...
Click to collapse
I am actually getting closer. I think there is something different in the permissions or something of build.prop. I finally have mine showing the older version. About to try a rollback and see if it works. This is from 3.2.5.
r3pwn said:
I am 95% positive towelroot will not work, unless Amazon got REALLY stupid (and I don't even have the HDX).
Click to expand...
Click to collapse
I compared both fw's:
ONYXis said:
But boot.img is totally similar to x.3.2.5 and changed files are apps, frameworks and trapz_scripts only. So towelroot must work.
Click to expand...
Click to collapse
And I think that this is not enough to prevent root possibility.
ONYXis said:
I compared both fw's:
And I think that this is not enough to prevent root possibility.
Click to expand...
Click to collapse
I don't know what you mean by "totally similar", but one small change in the boot image is all that is required to patch towelroot. Take every update with a grain of salt...
Ok. I'm new to bin files. How would one go about flashing a bin file?
Sent from my KFAPWI using Tapatalk
No Change to Kernel or Recovery
r3pwn said:
I don't know what you mean by "totally similar", but one small change in the boot image is all that is required to patch towelroot. Take every update with a grain of salt...
Click to expand...
Click to collapse
No change to kernel or recovery between 3.2.5 and 3.2.6--binary-compared those files within the BIN archive, and they're bit-for-bit identical.
There were noticeable changes to both kernel and recovery between 3.2.4 and 3.2.5 which probably accounts for 3.2.5---and 3.2.6--unable to roll back.
I can confirm that towelroot works.
So how would I flash a bin file?
I guess no one knows then?
Sent from my KFAPWI using Tapatalk
If you are speaking about the update bin file you simply copy it to your sdcard and go to settings/device/system update and check now.
Sent from my VK810 4G using XDA Free mobile app
The Kindle doesn't have an sdcard. Do you mean the emulate/0 folder?
exactly
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
btw kindle has partition named sdcard
Can we use safetrap for this version?
I didn't try
but pretty sure that safestrap would work
iattilagy said:
I can confirm that towelroot works.
Click to expand...
Click to collapse
Just another confirmation that towelroot does support/works to root the latest update ie., 13.3.2.6 :good:
I have not installed SU yet or attempted to block any future updates. I have read that renaming the proper odex file can stop future updates--any info on this method or other ways to accomplish would be appreciated. I would like to prevent losing root when another update comes along.
Thanks all.
kico42 said:
Just another confirmation that towelroot does support/works to root the latest update ie., 13.3.2.6 :good:
I have not installed SU yet or attempted to block any future updates. I have read that renaming the proper odex file can stop future updates--any info on this method or other ways to accomplish would be appreciated. I would like to prevent losing root when another update comes along.
Thanks all.
Click to expand...
Click to collapse
Download the HDX toolkit and use the option to block updates.
ONYXis said:
exactly
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
btw kindle has partition named sdcard
Click to expand...
Click to collapse
Yeah. Meant no physical external Sd card. Which btw, I have an OTG cable but can't get that to work.
Sent from my KFAPWI using Tapatalk