Related
As I sit here at work my mind start to think. There is a host file on the Nook Color that is used just as the host file on a Windows machine is used. The Nook Color can auto update itself with out knowledge of the user. Why not monitor the ip address the Nook Color downloads the Side Loader update zip file from and block that address in the host file? That is better then renaming the OTACert file and if the site isn't found by the device the device will not try and update its self.
I thought of it now one of you go figure it out....here is what you have to do;
1. Make sure your on 1.0.0 firmware on the B&N Nook
2. Run Monitoring program on your router to see incoming data and what IP's are being utilized.
3. Run WIFI on Nook
4. Look for new data (side loader being downloaded from B&N)
5. Block that IP address in the hosts file
6. Reboot nook and see if it still tries to update its self.
Post back results.
2nd Idea:
I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access rights through adb or root explorer.
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
mtl171 said:
Nice though I heard it leads to authentication errors when you the store... which in turn leads to your nook reverting back to 1.0.0.
Click to expand...
Click to collapse
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
xboxexpert said:
I thought that was renaming the OTACert file. I also though of putting a empty Sideload_update.zip in the root of the device and giving it no access through adb.
Click to expand...
Click to collapse
Aparently you can not chmod anything in /media folder
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
wvcachi said:
I renamed the otacert file and have been on 1.0 for several weeks now without any update.
Click to expand...
Click to collapse
That works good but what if i wanted to stay on 1.0.1 with out updating...
How come some people get the auto update and some don't? I've been on 1.0 since before Christmas and haven't been forced into an update. I've even been sitting in B&N for hours at a time.
xboxexpert said:
That works good but what if i wanted to stay on 1.0.1 with out updating...
Click to expand...
Click to collapse
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
wvcachi said:
1.0.1 is the newest update, so there's nothing to update at this point. Unless they changed something, I'm guessing the otacerts method would probably work for future updates as well.
Click to expand...
Click to collapse
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
xboxexpert said:
If you rename OTA in 1.0.1 and try and use the BN Shop or what not it will knock you out and reformat your nook. I'm looking to just block the update site via host file.
Click to expand...
Click to collapse
It looks like that was based on one post that the poster later attributed to something else (read thread http://forum.xda-developers.com/showthread.php?p=10390633#post10390633).
So I see no reason not to disable otacerts on any firmware right now.
I have not seen it posted here but wolf849 has put together a guide to downgrade so you can downgrade, root then upgrade to .21 all without the need for root access or unlocking.
I linked below
http://forum.xda-developers.com/showthread.php?t=1622628
Thanks! I stupidly updated to .21 right away when I first got my prime and regretted it ever since. Finally I can get some use out of this!
Man this is GREAT news.
Even a noob like me has down graded from .21 down to .15
Used Vipor Mod to reroot - Thank you Vipor Boy
Intalled OTA Rootkeeper and backed up my root
reinstalled the .21 updated
restored root!!!!
Thank You Wolf
Can a TF201 owner confirm?
Thanks.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed !!!!!
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed, I just finished.
Wooooooooot!!!! This is awesome.
-lukin- said:
Can a TF201 owner confirm?
Thanks.
Click to expand...
Click to collapse
Confirmed also.
Useless post was useless. figured it out. plz delete this post.
It worked! Downgraded to .15 from .21 and have now managed to install SuperUser and SU binary. Waiting for OTA Rootkeeper to install before upgrading to .21 again.
Finally I can fix some of the bugs that I've had to put up with due to Asus' incompetence, such as the bad I/O performance and shocking web browser performance.
Awesome, I've been looking for a solution for a good while. I'm glad this is confirmed. Hopefully someone will update the reference guide to link it to wolf's guide!
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
put the blob in the root directory of your internal sd.
I extrated the blob from the US version .15.
don't us .21 that is what you have installed now and that one can not be rooted
pileot said:
im going to post here because the other thread is like 40 pages long and i dont want to get confused with other information there (dont wanna brick my tablet)
it says to put your blob file in a directory on your prime.... Which blob is relivent for us? do we use the blob for the version were using or what? I realize this guy's native language is not english, can someone whos done it write the instructions so its easier for a non geek to understand?
Click to expand...
Click to collapse
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Mekrel said:
Well, we want the following blob, as it has the exploit that allows us to gain root.
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or zip)
That's the "world wide" version, I'm not sure which firmware locale you should have as you're Canadian? Check you "About tablet" section with your tab settings and see which firmware you have installed.
There's threads around which tell you how to extract blobs from the firmwares on Asus' website, so if you need a different version to the world wide blob, you could extract your own.
Just follow his method 2, I did and it was very easy as long as you have adb set-up.
Click to expand...
Click to collapse
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Replying to see where this goes, not going to be a beta tester for it though.
kageebe said:
So with wolf guide we are downgrading to .15 then rooted in any manner we want?
Click to expand...
Click to collapse
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Mekrel said:
Yes, that's correct. However I would recommend ensuring you use the blob for your region. The one Wolf links to is the WW (world wide) version.
Click to expand...
Click to collapse
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
robertg9 said:
A little help for Android noob, please. I read that I need ADB enabled.
What is that? I looked on Google Play, and there is no app specifically named ADB.
Is that the checkmark "Allow USB Debugging" listed under Developer Options?
Do I also need to install something similar on my Win7 PC.
If I can figure out this ADB stuff, I think I'm good to go.
Thanks,
bob
Edit: Will we be able to use this same technique when they come out with their new update....or is it better to wait till that arrives?
Click to expand...
Click to collapse
ADB is a tool that comes with the Android SDK, so you need to install the SDK onto your laptop and install the SDK Tools and Platform Tools. Then edit your path variable so that your command line know's where to find the adb executable. You might also have to install Java development kit, I'm not sure if the Android SDK manager moans if you don't have it installed.
There's easier ways of using ADB, by just downloading the .dll and .exe and referencing them via command line but I always recommend having a full SDK tool install and learning about ADB as it's a god send.
kageebe said:
Is there any way to check which region my blob is from? Also, where would 1 find the blob for their region?
Click to expand...
Click to collapse
Like I said, go to "About Tablet" in your tablet settings and there's something called a "Build Number". Mine says IML74K.WW_epad-9.4.2.21-20120323 - the initials stipulate which region firmware you have, in my case "WW" aka World Wide.
If anyone can locate a US blob please let me know, I've been searching on the forums for a .15 US blob to no avail and no luck at all.
Hey all,
I posted this in wolf's thread as well as the thread here but not have not fixed yet so I thought I would post this problem in it's own thread.
I successfully downgraded my prime using the tool (batch file) to .15 with a US blob for my (what was) US .21 prime. I rooted with the tool and then voodoo OTA and protected root.
The prime sees the OTA to .21 and downloads it. Asks me to install it. When I say OK it boots into the android guy with the spinning wire mesh. The progress bar makes it up to around %25 and the android guy falls on his back and theres a triangle with a "!" in his open stomach. It sits there for 1 maybe 2 minutes and reboots back into .15 saying there was an error and I've been reverted back to .15.
In searching, I found a thread that detailed some steps that might prevent an update from installing. It started out by looking at the log located in /cache/ to find out what the problem is and fix it. However, my /cache/ folder is empty with no sub-folders.
I've been told it may be my build.prop. I don't think I have added or changed anything in it without changing it right back to the way it was. I change the model and manufacturer once to see if I could get a game from google play but changed them back to exactly what they were (including case).
Would anyone care to link me to a trustworthy .15 build.prop (trustworthy so I dont brick my device putting someone's practical joke in as build.prop). If thats the problem that might fix it.
I have a TB backup so if a complete wipe and factory reset is in order I'm up for that but not even sure how to go about that with the TFP. But I hope theres an easier way if anyone knows one. Would love to get back on the update path and also use the GPS dongle that came in yesterday.
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
buxtahuda said:
PM'ed you.
Sorry, I get so busy being lazy and working at the same times that I get a little jumbled
Click to expand...
Click to collapse
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Shinare said:
Thank you so much bux! First thing I learned is that just because a file explorer program says it can explore root doesn't mean it does a good job. Thanks for pointing me to root explorer app. There actually were folders in my cache folder with log files. Second thing I learned was editing ur build.prop even putting it back exactly the way it was messes with the update check. Thank u for all ur help. I'M NOW .21 ROOTED WOOWOO!!! The build.prop was in fact the culprit. If I could give thanks from this xda app I'd give u 20! (Actually 21!)
Edit-you can give thanks from this!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Lol, yes, in the reply menu. Good stuff, glad it's worked out! I may edit this last post with a public link to the unmodified build.prop in my DB account, we'll see
*EDIT:
Just for other's reference if they face similar issues. Also never hurts to have yet another unmodified build.prop somewhere on the web lol
buxtahuda said:
Shinare said:
buxtahuda said:
Kind of forgot about you I know, I'm terrible lol
Install root explorer and again try to look at your /cache/recovery directory. Pretty sure you must have root access to see it, and root explorer will attempt to get just that when you start it the first time.
Let me know if this gets it so you can look at the recovery logs, if not then I hope more people have a look at your thread.
Click to expand...
Click to collapse
There are logs in there! Can u take a look and let me know?
Thank You!
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Ok, yeah, build.prop is definitely your problem.
Code:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
assert failed: apply_patch_check("/system/build.prop", "6d6091deb35156e27166bfc8577483040d62c59f", "800e051d6445d0dfae5c04fcdb66dd1f0ce7a330")
I have a backup of my build.prop from .21, I'll get it to you and we'll see if that won't do the trick. If not, we'll have to take to the forums and hope some others will have a good build.prop or actual explanation for the issue.
http://db.tt/0tDq7Sih
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
Click to expand...
Click to collapse
no FOTA
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
Have you tried locating your DMClient in your apps and clearing its data/cache? Try that and see if maybe blob'ing between regions didn't just discombobulate it. The build.prop wouldn't help you there I don't think. I hate to say it, but try a factory reset?
hi
Have you tried locating your DMClient in your apps and clearing its data/cache?
Click to expand...
Click to collapse
yes. no efect
but try a factory reset?
Click to expand...
Click to collapse
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
MrCat226 said:
yes. no efect
the same
i iven tried to put the FOTA menuali
dlpkgfile in the terminal:dd if=/sdcard/dlpkgfile of=/dev/block/mmcblk0p4
it copy the file but dont see the update
Click to expand...
Click to collapse
Hmm. I haven't had a chance to collect all the different dlpkgfile files yet, I'm setting off on that adventure soon so hopefully I may run into your issue while I install all the different blobs.
I really don't know at this point. Have you also tried this route?
hi
now traing)
but 1 thing
Once downloaded, extract the zip. Inside, there's another file file.
Rename this one into EP201_SDUPDATE.zip and put it in the root of a microSD card.
Put the microSD card into the tf201.
Click to expand...
Click to collapse
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
MrCat226 said:
now traing)
but 1 thing
can i put the FOTA update file(dlpkgfile) in the zip file or some how use the file?
Click to expand...
Click to collapse
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
buxtahuda said:
I'm not sure. I don't think so, if I'm understanding you correctly. Do you mean you'd like to put the dlpkgfile that you have into the ASUS update zip?
Click to expand...
Click to collapse
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
MrCat226 said:
yes.
when the device detect that ther is an update, it download the update as a ZIP? or this is what it download(dlpkgfile)?
Click to expand...
Click to collapse
Yes, when your Prime detects an update it downloads dlpkgfile to your /cache/ directory, and upon reboot updates the Prime. So putting a .21 WW dlpkgfile in your cache directory should update you to .21 WW.
The last one I linked to involving the UPDATE.zip has you manually update your Prime from recovery, as a last resort kind of thing and should work.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
hi
i tried this. it dont see the update
after this trick in the cache folder i found 2 new files "last_log" "last_install"
No OTA after motherboard replacement
MrCat226 said:
first sorry for my bad english.
i am i the same setuation BUT some kind difrent)
my prime was at the ARM(replace the main bourd) it came back witch US 9.4.2.21(my original was WW 9.4.2.21) no idea why thy do that, i use the moded vipermod to downgrade to 15 witch WW blob, all seems ok
then root+backroot and traying to see if there an FOTA update, NO FOTA update
"there is no update available for your device currently" i tray all the blobs(US,WW,DE,CN,TW) still no FOTA
i dont tray et your build.prop
Click to expand...
Click to collapse
There is another post having a very similar complaint in:
http://forum.xda-developers.com/showpost.php?p=25890334&postcount=258
I have an extremely similar issue, that is:
Bought a TF201 on March 2012, updated OTA (several times) up to ICS .21
Sent to the local (Israel) lab complaining for WIFI and GPS issues.
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
I cannot say I feel any improvement with the WIFI or the GPS.
(BTW, the GPS dongle arrived a day after and that one makes miracles!
But only on .21! Furthermore, it is rather big [has the length of the TF201] so I guess I will not carry it with me daily)
Tried the wolf downgrade (US .15) - works fine.
Wiped as suggested on his page.
No OTA!
(rooted or unrooted)
Tried WW .15 and US .14 as well.
No OTA.
Waited over 24h (as suggested in some webpages).
Found the ratchet solution for S/N fixing - still no OTA (neither on WW nor US .15) - all wiped as well (long vol-down press while turning on + 2 x vol-up presses while wipe is flashing).
I've been through 3 factory resets in a row (As suggested in some sites) - both on .15 as well as .21
I'm just about to contact the seller and ask for a replacement (but I really don't feel like it).
I hope a solution is found in the next couple of days as I'm afraid I will have to deal with the seller by Sunday otherwise.
hi
Received back with the motherboard replaced.
Changes that were observed:
* MAC addresses (Bluetooth and WIFI) have changed - well... MB has been replaced...
* MAC of the BT does not appear under the about -> status menu
* S/N unknown under the same menu
* SKU is US (.21) instead of the original WW
Click to expand...
Click to collapse
Exactly the same problem!
BUT i put back the S/N(ratchet) witch no efect(
That sucks. Can't believe they're so sloppy they can't even make an annotation in the paperwork what firmware you were already on and give it back how they received it.
I'll keep looking around, but it's likely going to take someone more ingenious than I to come up with a solution since you're getting the SN Unknown issue. Does ASUS not even have properly working NVflash?
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
ferrouskid said:
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
Click to expand...
Click to collapse
I'm just curious as to if you never had root or lost root.
zXiC said:
I'm just curious as to if you never had root or lost root.
Click to expand...
Click to collapse
Yes I did have root, I used AOSP ROM, and made it almost pure android. I found a nice tool called "Android Commander" that has the ability to access the system files from the pc. I was attempting to flash the previous version of Mojito OS using the casebook utility but failed, and as far as I figured I might just be able to extract and maybe delete the file the check for automatic updates, and thus do a manual update on the kindle, which literally requires dropping in the .BIN file into internal storage and the lb upgrade it. Then use the old root method, so if you are interested you could help me locate that file
I have been doing a lot of indepth reading regarding the whole process of loading Lollipop on a Kindle Fire HDX 7.
I thought I had the process understood but have realised I might have a problem. It seems that there is a loop where you need to ROOT the Kindle in order to rollback the ROM, but all the rooting methods seem to rely on having a 13.3.2 or earlier ROM in order to ROOT it.
It seems that the vulnerabilities which allowed the zergRush root method have been fixed, as have the TowelRoot vulnerabilities. These are the only two methods I have found so far after extensive searching.
I am not certain which ROM my Kindle will have since I have ordered it as present for my wife off of Ebay. It maybe that its got an old ROM and all will be OK, but I would rather not waste my time and possibly brick the Kindle by trying outdated fixes.
I have loaded Android-SDK and Android-Tools onto my Opensuse system, but I understand that I can only "adb push" a rollback ROM if I have already ROOTed the Kindle.
Any guidance to avoid a horrible mistake would be much appreciated.
Stephen
What version of FireOS are you on?
EncryptedCurse said:
What version of FireOS are you on?
Click to expand...
Click to collapse
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Shoog03 said:
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Click to expand...
Click to collapse
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
EncryptedCurse said:
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
Click to expand...
Click to collapse
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Shoog03 said:
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Click to expand...
Click to collapse
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Thats good to know.
There are so many redundant instruction sets out there that it is very confusing.
Will post the OS when I get it and hopefully get a good pointer to the right strategy.
Stephen
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Davey126 said:
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Click to expand...
Click to collapse
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Stephen
Shoog03 said:
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Click to expand...
Click to collapse
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Davey126 said:
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Click to expand...
Click to collapse
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Stephen
Shoog03 said:
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Click to expand...
Click to collapse
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Davey126 said:
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Click to expand...
Click to collapse
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
In my specific case the full instructions will go:
adb kill-server
adb start-server
adb devices <confirm kindle present>
adb push /home/stephen/Desktop/Fire_HDX_7/ES-File-Explorer-4.0.4.1.apk /sdcard/Download/
adb install /sdcard/Download/ES-File_Explorer-4.0.4.1.apk
adb kill-server
Cheers
Stephen
Shoog03 said:
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
Click to expand...
Click to collapse
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Davey126 said:
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Click to expand...
Click to collapse
So it finally arrived (only took about 3 weeks thanks to Ebays ****ty GSP delivery fraud).
It looks brand new, so might be a reconditioned unit. Its a third generation Thor running OS 4.5.5.1 with a Build date of 13 November 2015 (which seems very late and may present an issue in itself).
The roll back thread seems to indicate that it is possible to roll-back the 4.5.5.1 using the mod-update-kindle-thor-13.3.2.8_user_713328020.bin image. I have plugged the Kindle into my Linux box and it appears as an android device, and I dragged and dropped the rollback image to the Download folder. However it will not allow me to check for updates since it requires a working Internet connection to proceed.
I have attempted to place the bin file straight into the sd card next to the Internal Storage folder, but this is root privileged and I have not yet rooted the device.
So its seems it back to the situation that the first step has to be rooting - which means switching on the WIFI to run Kingroot.
So wanting to be extremely cautious at this stage is there any advice as to how to proceed.
I also pushed out a copy of ES_File manager and tried to install using adb install but got this
[email protected]:~> adb devices
List of devices attached
D0FBA0A034530BHD unauthorized
[email protected]:~> adb install /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Internal storage/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: storage/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /Download/ES-File-Explorer-4.0.4.1.apk
Click to expand...
Click to collapse
Stephen
OK, I didn't follow the instructions for the rollback precisely. I placed the rollback file into the internal storage folder and it found it straight away and is currently installing and doing its first reboot.
Stephen
So i am now running the rollback 13.3.2.8
What next ?
Best root method and then install safestrap and Kitkat and call it a day ?
Stephen
Managed to sideload ES_File_explorer by copying the file into my adb folder and running adb install.
Now I am downloading the update ROM 4.5.2
Will then sideload cve20147911.apk
Stephen
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Shoog03 said:
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Click to expand...
Click to collapse
Took the long rollback/upgrade road - 4.5.5.1 can be directly rooted with Kingroot. Assuming you secured root there is no need to tweak permissions. Simply rename DeviceSoftwareOTA.apk (details).