Related
Hi. I am relatively new to unlocking, rooting etc. with devices like these. I was recentlt attempting to root my Nook Tablet on 1.4.3, and came acroas a thread on this site with step-by-step instructions on how to do so. Well, to get to the point, I had already formatted the card and everything, but when I went to download the actual file for the root to the card, it said the file was not found. Does anybody know anywhere else I could find the file? Im really tired of this tablet sucking ****.
If you're looking for ALbert's root image someone may have it mirrored. Check out the last page of the topic
http://forum.xda-developers.com/showthread.php?t=1439630&page=19
There are other root images available as well and tehre is also the option to install CM10. No root required prior to the install.
aerialstoner said:
Hi. I am relatively new to unlocking, rooting etc. with devices like these. I was recentlt attempting to root my Nook Tablet on 1.4.3, and came acroas a thread on this site with step-by-step instructions on how to do so. Well, to get to the point, I had already formatted the card and everything, but when I went to download the actual file for the root to the card, it said the file was not found. Does anybody know anywhere else I could find the file? Im really tired of this tablet sucking ****.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
Thanks a ton.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for some pointers/tips on risk mitigation in rooting and flashing custom ROM.
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
I am using a RCT6573W23, I have rooted it using Kingo and editing the ADK file... Everything went well, and I had installed SU and Busybox, Developement was on, but I don't think it remains on... I did some build.prop tweaks, and when messing with the LCD I messed up my system, disabling it from booting up.
I boot into Recovery just fine, and I DID BACKUP AND HAVE my original build.prop file, however, good ol' RCA doesn't provide any "files" for support at all, and connecting ADB is "SIDELOAD" only... I've read several places but everyone suggests going INTO recovery, which, I can do, or using ADB, but fail to realize it's sideload issue... I've pushed several files, but every single file is a bad footer, and wrong signature... I'm at a loss... Does ANYBODY have a recovery.zip from their Apollo 8" who could make a backup for me, so that I could sideload an official zip file. I would MUCH appreciate it... Thank you.
I have the same model... you're the only one I've heard of that has successfully rooted this one... is there a way I could get my official stock ROM copied without root?
Rooting it was simple, I believe you can go to settings backup and restore to get a .zip of your stock.. If you could shoot me a copy that'd be great. I can share how it was rooted, although it was super easy to look up.
There's not an option to backup entire system just app files.
What recovery did you use? and did you use the kingo universal rooting tool? And what edits did you have to do to the ADK?
I've successfully rooted but have no way, as of yet, to zip up my ROM. Any thoughts?
Anybody know if xposed framework or clockworkmod will work on this device?
-- Rooting your RCT6573W23 --
Install your USB drivers... If you don't have them, or you can't make your system acknowledge them, use the SDK-Method to fool your computer into reading the correct USB for your device... That method can be found at: addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Once you've got your drivers, before even plugging in your phone, make sure you have all of these options checked... From the developer's menues: "USB Debugging" "Allow Mock Locations", and in your security & screen lock settings: "Device Administrators", and "Unknown Sources" need to be checked...
Install Kingo from kingoapp.com
NOW, simply plug it in and click root on the pc... It'll install SuperUser and enable you to use just about any feature a rooted device can use, but without flashing roms... Still nice for cheatengine and stuff.
----------- Finished, Now... -------------------
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
I've acheived root and have SU, but Here's no way to make a nandrid without some sort of recovery...
Edgia said:
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
Click to expand...
Click to collapse
I believe these tablets have the RK3188T chipset, and I found These CWM Recovery images: http://androtab.info/clockworkmod/rockchip/
I don't have time to mess with it right now but I thought I'd share. I'm going to do some more reading on the subject before trying anything real crazy. Let me know if this works out for you...
Any luck on this? I was hoping to install a mod on this tablet myself
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).
Hello ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.