Related
My NT just updated to the latest firmware so I hve lost all ability to sideload apps.Up untill last night I was downloading and installing apks from the Amazon App store and loving it.My NT was NOT rooted just sideloaded and running Launcher Pro and Button Savior.My question is will rooting my NT after the OTA update restore my ability to install non Nook Store aps?I have found a great thread on rooting the NT using a Mac and wanna give it a try but if this won't give me that ability I'll just leave it be and not void my warranty. My wife gave it to me for Christmas and got the extended warranty so I really don' t want to root it unless it will fully unlock the device.
Thnax everyone.
To root the update, look for the thread about rooting 1.4.1 here in general. Otherwise you'll need to revert to 1.4.0, which I believe requires you to start from scratch.
Sent from my SCH-I500
ckevinwelch said:
To root the update, look for the thread about rooting 1.4.1 here in general. Otherwise you'll need to revert to 1.4.0, which I believe requires you to start from scratch.
Click to expand...
Click to collapse
As I understand it, the 1.4.1 with root involves reverting to 1.4.0, and then rooting, and then upgrading in a special way to 1.4.1, which will avoid losing root.
cfoesch said:
As I understand it, the 1.4.1 with root involves reverting to 1.4.0, and then rooting, and then upgrading in a special way to 1.4.1, which will avoid losing root.
Click to expand...
Click to collapse
Doh ... you're right. I forgot about that part.
I received my new nook tablet for xmas and it is still on 1.4.0. as I haven't connected it to the internet yet. So do I just follow Indirect's post on full root step by step? And will that block OTA's as well? Sorry for noob posts I just want to get this right as I am still on 1.4.0. Thanks.
jumpman23j said:
I received my new nook tablet for xmas and it is still on 1.4.0. as I haven't connected it to the internet yet. So do I just follow Indirect's post on full root step by step? And will that block OTA's as well? Sorry for noob posts I just want to get this right as I am still on 1.4.0. Thanks.
Click to expand...
Click to collapse
Using the method found here: http://forum.xda-developers.com/showthread.php?t=1354487 you will block any OTAs, and will give you options along the away on how much google you want, and how little B&N and you. It is the closest we have to a 1-click root.
Go Here. Follow the steps exactly, particularly the ones about installing the drivers.
Indirect has added OTA Blocking to his root script so once the script is done, you will be OTA proof!
Thanks guys! I really appreciate it.
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
I have a Transformer Prime with an Unknown Serial Number. My tablet can NOT be pushed OTA Updates by ASUS. Do NOT suggest going to ASUS's website and downloading their update file, you can NOT keep Root using those files. OTA RootKeeper ONLY Works on OTA Updates PUSHED by ASUS to your tablet.
Do NOT suggest going to ASUS's website and downloading their update file. Do NOT suggest any blob file that has been linked to on these forums, UNLESS it is from someone who has actually COPIED the OTA Update from ASUS AS IT WAS BEING PUSHED to their tablet. These blob files are NOT OTA Updates.
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21. I want root.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can manually update it using wolf849 method, which is really used to downgrade but im more then certain it would work to manually upgrade.
Ill go step by step.
1. If you want root, and are on 9.4.2.15 now, root it now! then backup root with OTA ROOTKEEPER
2.Download latest .21 FW here http://support.asus.com/Download.aspx?SLanguage=en&p=20&s=16&m=Eee+Pad+Transformer+Prime+TF201&os=32 you likely want US build, not WW (check in settings under about this tablet)
3. Download my modded ViperMOD tool from here http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 this allows for one click downgrade.
4. Extract the .21 fw you download and find the file named "blob" and put blob on the root of you primes INTERNAL MEMORY
5. Make sure all prime drivers are installed (should install by themselves , mine did) then open my modded viperMOD (thanks viperboy) and connect transformer prime. Select option 1 in modded viperMOD tool to downgrade tablet (in your case upgrade, it just manually apply's the blob file (firmware) )
6. Should reboot to .21 then restore root with OTA Rootkeeper if wanted
Hope it works
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
slayvus said:
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
Click to expand...
Click to collapse
I was on .21 downgraded to .15, then rooted, then installed OTA rootkeeper to backup root, updated to .21 OTA then restored root with OTA rootkeeper, and im now on .21 rooted with out a unlocked prime. This has also been stated by many others.
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
slayvus, im with you, im gonna get my prime replaced or rma'd on thursday if i cant find exactly what your looking for!.
slayvus said:
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
Click to expand...
Click to collapse
doing the manual update is like doing the OTA updates
you keep all your information on your prime hence you can just use the root keeper to restore root
of course we're just trying to help you but if you refuse to listen to us and want us to spend time to prove to you that something works when you can always try your self, then never mind just stay on your firmware that you're on @[email protected];
This is getting tiresome of repeating this. So I let you hear it from someone who MADE Primetime, -viperboy-.
http://forum.xda-developers.com/showpost.php?p=25495366&postcount=1634
-viperboy- said:
Assdikes said:
How come I can't root or how come vipermod is not getting the job done anymore? Also I don't really know how to make real use of the OTA root keeper, because everytime I updated I made a SU backup, and then I think this is where I mess up, Then I would install the update manually from my sd card and everything is out of whack the root is messed up in a half root state sometimes, and my apps are gone, and blah blah blah...... someone help!?!?!?!?!?!?!?!?
Click to expand...
Click to collapse
Dear God, can you read?! DIRECTLY from the OP:
THIS WILL NOT ROOT .21 AT THIS TIME!!
Click to expand...
Click to collapse
There is no root method for .21, only a downgrade procedure. The reason why OTA Root Keeper didn't work is because...
maatsby said:
...it's called "OTA rootkeeper", not "manual update rootkeeper".
Click to expand...
Click to collapse
...when you update it from the sdcard, it's the full install, not the OTA that only makes certain changes. You are wiping out the OS and your su-backup.
Click to expand...
Click to collapse
Again, lets go over this ONE more time since people can not seem to read and think EVERYONE on the internet is wrong.
THE BLOB FILES ARE NOT OTA UPDATES! THEY ARE MANUAL UPDATES AND YOU CAN NOT KEEP ROOT IF YOU USE THEM!
If someone can show a know developer saying different, THAN I will believe you. Until than, I will go with the assumption that, again, BLOB files are manual updates. I do NOT want to waste time to have to do everything over again on my Prime and risk bricking it AGAIN. I already risked it once by downgrading.
bimbobo said:
It worked finally, but I wasted my time.
I installed WW15, rooted it, save the root with OTA RK, reinstalled 21WW but OTA RK did not restore the saved root. Either I cannot OTA RK correctly, or you cannot root 21 at all. I do not get that somebody reported they could restore 21 root, maybe they are unlocked.
I need to decide to stay with 15 or rest in peace with 21 not rooted.
Click to expand...
Click to collapse
bimbobo said:
I installed using the guide in the dev forum, sd card and blob.
Then I do not know.
I just clicked on "backup root", I have no idea where it's installed.
But you can eventually explain how to use it correctly.
Click to expand...
Click to collapse
b.huss2 said:
No, I'm asking how you went from 15 to 21. Did you let it update over the air or did you manually update via an SDcard update? Just wondering because Root Keeper only works for OTA updates from what I understand. For example, I was on version 15, rooted with this tool, installed Root Keeper, backed up root, and when the update came it installed automatically, and I just had to go back into Root Keeper and restore root.
EDIT: just noticed this
I think this is your problem. It's an OTA Root Keeper. You did not update OTA
Click to expand...
Click to collapse
Now PLEASE, stop suggesting that I install .21 using a BLOB file off my SDCard. It's making me feel bad having to prove you wrong. All I want to know is if it is possible to intercept ASUS' OTA Updates so that people like ME can make use of them.
Could be a way
slayvus,
This guy managed to intercept this us one, now it would be nice if they could do it for my ww version.
http://forum.xda-developers.com/showthread.php?t=1437274
im downloading this old firmware to comare it to the manual blob to see if its just a case of putting the blob in the cache folder :S
we would just need someone with a non .21 prime to download the ota for us
It looks promising, but it doesn't seem like anyone has contributed to that method in over a month.
without trying to get your hopes up im returning mine tomorrow if i dont find a solution tonight i did find this http://forum.xda-developers.com/showthread.php?p=22928122
a direct link to asus ota update for 8.6.5.21 -> 9.2.1.11 US
im going to check out whats in this zip, and see if i can find an ota link for ww, if i find one for .21 its worth you trying, you can allways downgrade again.
i went from .21 to .11 to .21 to 8.8.3.33 now im back at .15, lol
You can download FOTAKILL.apk and install it in /system/data and it will no longer OTA.
Did it for the Xoom on 4.0.3 Team EOS 1.0. Works perfect. Will work on the Lemon TF201 as well.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can go to Asus.com and download the .21 updated zip file. If you unzip it you will find the blob file there. You will have to manually update but you will lose root. OTA root keeper wont work for this method.
If you want to intercept, accept the OTA download but dont install it. Go to your cache folder (I forget the sub folder maybe someone can chime in) and there you will find the dlpkxxxxx file. I assume if you copy that file into another Prime in the same directory that the tab will assume you have just downloaded an update and will install it as if it were OTA. Then you may be able to use OTA rootkeeper to restore root afterwards. I haven't tried this myself so just a theory.
Sent from my Transformer Prime TF201 using Tapatalk 2
slayvus
im going to get mine rma'd or replaced this afternoon,
when i get a working one back ill get a copy of the OTA from my cache folder, i feel this may be a way for unknown serial number units to get .21 with root!
i may be getting mine fixed but i will still strive to get a fix for this situation.
Believe me ive upgraded and downgraded to and from .21 about 10 times sofar so its still worth trying.
Again, the updates from ASUS on their website, which are the blob files people are passing around for things like downgrades and such ARE NOT THE SAME THING AS AN OTA UPDATE.
An OTA Update is smaller than the blob files by a LOT. The OTAs are like less than 100 MB for the incremental updates. The updates on ASUS's website are over 300MB.
calm down, im sorry if i didnt say it right, im only human, i am going to get the ota update that downloads to the cache folder which as you say is smaller than the asus blob, i fully understand this, i spent all last night looking for the asus OTA 9.4.2.21 update, the best i could find is one to update to 9.4.2.11.
I repeat, I do not mean the one from asus.com, i am refering to the ones the units automaticly notifys you that they are availble and you then download direct to device, allowing you to use ota root keeper.
i upgraded to .21 using wolfs method last night and confirm that root is not kept if you do it that way.
when i get a working unit i will help intercept where the update downloads to and get a copy from my device, even if it means downgrading multiple times till we get it right!
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
aznmode said:
You can go to Asus.com and download the .21 updated zip file.
Click to expand...
Click to collapse
slayvus said:
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
Click to expand...
Click to collapse
Did you see my 2nd paragraph? Did that not answer your question? I try to help and you have a problem with it. Get that stick out of your ass dude.
Sent from my PG86100 using Tapatalk 2
Did you even read my OP before I updated it? I have no problem with reading.
I can NOT receive OTA Updates. My Prime has an Unknown Serial Number. ASUS refuses to push OTA Updates to Primes that have the Unknown Serial Number.
I understand you cant receive OTA and thats a known problem ever since the first ICS build came around and Asus is well aware of it and I've been in this ATP forums since this tablet was release so I am well aware of that issue as well. My 1st prime was in Dec of last year. Anyway I was generalizing when I said "you" and I didnt mean YOU cause obviously you cant get the OTA. My main point was how it can be done. I have intercepted an OTA before and I have some saved and I've done it with my Acer a100 as well. We're all here to help each other out so you should be thankful instead of being an ass about it. People will less likely to help you in the future. Not gonna waste anymore time..but good luck and hope you get your problem sorted out.
Sent from my Transformer Prime TF201 using Tapatalk 2
Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Update
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Zman8881 said:
Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Click to expand...
Click to collapse
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
Zman8881 said:
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Click to expand...
Click to collapse
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Davey126 said:
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Click to expand...
Click to collapse
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Zman8881 said:
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Click to expand...
Click to collapse
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
One Last Question...
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Zman8881 said:
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Click to expand...
Click to collapse
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Davey126 said:
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Click to expand...
Click to collapse
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Zman8881 said:
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Click to expand...
Click to collapse
Sorry it didn't work. There is a way around that message but you need root to make the change. Catch 22.
The wait may not be that long. Fingers crossed
Couple more questions
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
lekofraggle said:
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Click to expand...
Click to collapse
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Rvby1 said:
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Click to expand...
Click to collapse
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Davey126 said:
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Click to expand...
Click to collapse
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Rvby1 said:
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Click to expand...
Click to collapse
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Davey126 said:
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Click to expand...
Click to collapse
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Rvby1 said:
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Click to expand...
Click to collapse
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Davey126 said:
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Click to expand...
Click to collapse
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Rvby1 said:
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Click to expand...
Click to collapse
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Davey126 said:
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Click to expand...
Click to collapse
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Also, in trying to find the solution, I found another post by you:
Davey126 said:
You'll need to follow the guide linked by ggow (here) which is rather technical and requires a Windows host to complete (there are variants for Linux and OS X) plus a fair bit of technical knowledge. There are no canned tools, videos or step-by-step tutorials. Unlocking is not risky (failed attempts won't harm your device) but it can be a frustrating experience.
If unlocking feels uncomfortable you can do a controlled upgrade to FireOS 4.5.2 and then install Safestrap v4 followed by Nexus v4 or CM11. However, you will permanently loose the ability to unlock your bootloader which is the key to running roms like Nexus and CM in 'native' mode. Unlocking also offers greater recovery capability should something go wrong.
There is also the 'do nothing' option which leaves you with a perfectly serviceable device running a very nice Nexus rom (Jelly Bean 4.2 based).
Click to expand...
Click to collapse
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Rvby1 said:
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
Click to expand...
Click to collapse
Surprised about that but glad it worked! Perhaps the version built into HDX Toolkit contains the bits & pieces that normally require online access.
Rvby1 said:
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Click to expand...
Click to collapse
Kingroot works great on 4.5.2 and is far easer than the alternative methods. Some question the origins of Kingroot (China) but the tool is widely used across a variety of platforms. Personally I could care less where it comes from as long as the reputation is solid. Sharing this in case you have a different perspective.
Rvby1 said:
Also, in trying to find the solution, I found another post by you:
[removed - see previous post for content]
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Click to expand...
Click to collapse
As your start point was FireOS v4 your device was never eligible for bootloader unlocking. More specifically, Amazon fixed the vulnerability that allowed bootloader signature forging in 3.2.4. Clever folks figured out how to roll back to 3.2.3 up through 3.2.6. Starting with 3.2.7 Amazon became aggressive about blocking rollbacks. Any attempt to do so will blow an efuse which is equivalent to a brick. It's always possible another vulnerability will be discovered in higher firmware levels that permits bootloader unlocking. Don't hold your breath.