Related
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
jazacoop said:
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1764794
wbbigdave said:
http://forum.xda-developers.com/showthread.php?t=1764794
Click to expand...
Click to collapse
I saw that, but it was posted back in July, and seemed smaller than the original OTA.
Nevermind... I didn't see the October update to the post further down.
Cheers!
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.
jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.
Click to expand...
Click to collapse
Same here ... any luck with re-rooting?
Danged Amazon and their OTA
jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file.
Click to expand...
Click to collapse
Same here. I suppose I'll patiently wait for the next iteration of rooting this one. And hopefully a good way to stop the OTA updates from Amazon. If anyone reads this and knows of anything I can do in the way of offering files from my now unrooted device (ADB still connects at user level), I'll be glad to help the cause.
On the bright side, most stuff I've done works fine without root. I didn't bother with Google Play because that hadn't been perfected and the 1 Mobile Market seems to work fine, as well as side loading.
If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Sent from my Amazon Kindle Fire HD using Tapatalk
Sorry about that
chalid said:
Same here ... any luck with re-rooting?
Click to expand...
Click to collapse
I didn't have spare time yet. I'm gonna try whenever, I get some gadget time.
Downgrading? It would be worthwhile if I knew the push server's IP; and it's clearly not any of those that have roamed the net. There is a stray IP that hasn't been identified yet. downgrading and keeping the system offline or under a low battery level is too anoying to be worthwhile IMHO.
But those who want may try to proxy their wifi connection through their computer, downgrade their device, leave it alone and check in their proxy logs to pinpoint which IP is uploading the update to their device. Re-downgrade, root, re-wall their device.I'll try this but I won't be able to do it within the next few days.
In the meantime, gotta go.
Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"
jonathanlyng said:
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"
Click to expand...
Click to collapse
Yeah I've done something like that (on the 2012 model), but instead I used Android Firewall to block it from using Wi-Fi, no OTA updates now, been good for months
Seems the best way to prevent updates.
stunts513 said:
If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Click to expand...
Click to collapse
I presume the files you speak of are:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
But NOT the boot0block.zip img because that's specific to the individual's device. I thought about doing this, but admittedly, was a little uncertain. I don't want to brick it. Basically, if I fastboot, I can push those images over safely? I presume I'd want to have my wireless turned off in advance of this operation, lest I end up exactly where I began with the thing wanting to update right away again.
Thanks much for the feedback!
kfsowi 11.3.2.1
hello people,
this is my first post here love the site, anyways anything yet that can be done about kfsowi on 11.3.2.1 yet can it be rooted or downgraded so i could get my root back.
thanks
SOLUTION!
http://forum.xda-developers.com/showthread.php?t=2544736&page=30#post_message_50878798
Courtesy of GranPC
Fastboot cable
where is the best and fastest way to get a fastboot cable online or in a store.
thank you
louiep said:
where is the best and fastest way to get a fastboot cable online or in a store.
thank you
Click to expand...
Click to collapse
From Amazon.COM though they are quite easy to make
Sent from my KFSOWI using xda app-developers app
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!
Is there any way to downgrade to 4.5.3 without going through Amazon?
what is the command line to disable auto update ?
and does it auto update ?
alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?
alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak
Yeah it was an OTA update. Literally just as is was getting my laptop out to block them
otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.
Came out on July 14, 2016 10:30 PM. There is no bin file at this time.
Note: Don't try to downgrade from this. Might brick your FireOS. Need a report on it actually works or not first.
Cannot be rooted. Tested with NewKingrootV4.95_C149_B285_en_release_2016_07_15_105203.apk
Comment moved to different post. Sorry new to forum
Tip: If you log in on the Amazon it gonna try to update the system automatic. Don't log in then it gonna ask first after the download.
It wouldn't let me past the splash screen without logging in
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.
fmc000 said:
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.
Click to expand...
Click to collapse
I will - I just wish I would have waited longer with the update, but it was brand new and said: update me now
Thx for any help/ Info
I used the 5.1.2 bin file and installed adb drivers on my windows computer. I used a program called minimal adb and fastboot. I opened minimal adb and fastboot, powered on fire by holding volume down and power until bootloader. Selected apply update from adb. Typed ' adb sideload' and dragged the bin file into the window of minimal adb and fastboot. Hit enter and watched it climb to100%. This was from 5.1.4 and 5.1.3. I do not know if it will work going down from 5.3.1.0. the fire is a piece of crap with the stock amazon installed imo
Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
What is the date of your 5.3.1.0 FireOS ?
This thread is your friend :
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
You would try to sideload the 5.1.2 (the last version that's rootable at the moment). There is a chance the downgrade would brick (due to the possible higher version of the newer bootloaders ), so be prepared to send Fire back to Amazon if this fails.
One option is to write the entire new system, but that would take forever since those tools are slow ...
WARNING: Do not downgrade from 5.3.1.0. Brick the device if you do.
so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....
The ROM image for FireOS 5.3.1.0 has now been published on the Fire (5th Generation) Software Updates page. The filename is update-kindle-global-37.5.5.2_user_552153420.bin
http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Determine your software version
Determine the current software version on your Fire tablet before downloading and installing a software update.
Swipe down from the top of the screen and then tap Settings.
Tap Device Options, and then tap System Updates.
If you have the latest software update, it should look like this: Your device is running Fire OS 5.3.1.
Download Fire (5th Generation) software updates
Click the link below to download the software update to your computer:
Download Software Update 5.3.1
Click to expand...
Click to collapse
fusion01k said:
so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....
Click to expand...
Click to collapse
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
Thanks for the advice. I will check it out when it arrives soon.
beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?
jmorlin said:
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?
Click to expand...
Click to collapse
Well there doesn't seem to be another choice. A "work around" may come tomorrow or never. Seen both scenarios play out.
bibikalka said:
One option is to write the entire new system, but that would take forever since those tools are slow ...
Click to expand...
Click to collapse
@bibikalka what tools are you referencing here? And how to write entire new system?
beautiful3cellar said:
@bibikalka what tools are you referencing here? And how to write entire new system?
Click to expand...
Click to collapse
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available
bibikalka said:
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available
Click to expand...
Click to collapse
AFTV2 Tools works below OS 5.3.1 though?
beautiful3cellar said:
AFTV2 Tools works below OS 5.3.1 though?
Click to expand...
Click to collapse
I think the last version was 5.1.1. The tools don't work in 5.1.2 . Amazon replaces the preloader with each update, so they can fix it quite easily.