Related
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
chicago4545 said:
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
Click to expand...
Click to collapse
i also have the same problem now and have been searching for about a week now and experimenting it seems there are no tools which are compatible with our tab.. which version of sp flash tool are you using? and could you send me a link to that a58p rom
chicago4545 said:
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
Click to expand...
Click to collapse
Hi, I know to recovery you Lenovo A8-50F. It's yet actually?
Thanks.
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip"
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
This is For people That currently have Safestrap-4.0.1 and a custom rom either the HDX Nexus ROM Thor-v4.0.5 or cm-11-Safestrap version On Kindle Fire HDX Thor 7 inch To Restore to the Stock Rom 4.55 If you choose to do so realize you will be on an unrootable version of kindle Fire OS and will have to repeat the entire downgrade upgrade root etc process to reinstall any custom roms, so don't do it unless you are sure.
Download safe strap version stock 4.52 here http://forum.xda-developers.com/kin.../hdx-stock-images-pre-rooted-updates-t2911954 ty ggow
Download su 2.46 zip http://forum.xda-developers.com/showthread.php?t=1538053 ty Chainfire
Download safestrap Safestrap-Thor-4.0.1 http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840 ty ggow
Attach the kindle to your Pc and copy ss_update-kindle-13.4.5.2_user_452004120 , and Su 2.46 zip to internal storage
Reboot to recovery
In safestrap factory reset
Install the 4.52 zip
Install the su zip
clear Dalvik Cache and reboot
when u get back on Your kindle firmware choose setup later I put mine in airplane mode so the update wouldn't download and pester me for the next part
on pc I adb installed es file explorer and safestrap 4.0.1
Next on Kindle Fire HDX Thor
open es file explorer on left side go to tools and click on root explorer grant it permission from super user then navigate to /system/etc/security/otacert.zip.orig
and rename otacert.zip.orig to otacert.zip ty to johim for noticing the small typo
next open safe strap and grant it super user permission , use it to uninstall the recovery
next open super user and go to settings and then to full un root and use it
Set up your wifi under settings turn off airplane mode
Now go to kindle settings device options, system updates click check now if you dont already see an update, click update to reboot and install newest firmware from amazon
Now back on 4.55 I realize the info is here all over the forums but for anyone that had the small issue where the update would download but not install on the safestrap 4.52 install might find it useful.
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Edit: see following post by @zippy411. Appears a rollback to FireOS 5.3.1 (rootable) is viable.
Davey126 said:
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Click to expand...
Click to collapse
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
great news that we can downgrade without issue.
P.S: Maybe my HD 10 5.3.1.0 will never see the light of getting root as Fire 7" as Amazon is pushing another update already
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Orbiting234 said:
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Click to expand...
Click to collapse
Quite likely you can retain 5.0.1 bootloader while 'upgrading' to FireOS 5.4.x (when released) using the time proven procedure in this thread yielding the best of both worlds. Backup your existing CM install in TWRP so you can revert back after grabbing the Alexa components. You could do the same with the FireOS build and toggle between the two (awkwardly) via TWRP backup/restore. Can do the same thing with recent FlashFire builds although I would always retain a true nandroid (ie: twrp backup) of CM as a fallback.
zippy411 said:
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
Click to expand...
Click to collapse
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
ManWithCamera said:
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
Click to expand...
Click to collapse
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Apart of the NEW Alexa, does anyone here has noticed something NEW or any improvements with the latest FireOS 5.3.2 update?
Can we root it after the update with dirty cow?
just4u32 said:
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Click to expand...
Click to collapse
Hi - this forum is for 5th gen Fire (released fall 2015); you'll want to ask you question here. While 5th and 6th gen devices often run similar builds of FireOS there are some differences attributable to hardware variations and software release cycles. What works on one type of device may or may not on others. Rollbacks can be especially dangerous as bootloaders/kernels generally differ across device types. A failed rollback attempt typically yields a bricked device with no recovery options. In short, I would not generalize across device types.
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
To my knowledge there is no indication Dirty Cow has any meaningful relevance on this device. Although the underlying vulnerability may exist there is no evidence it has been successfully exploited on FireOS.
OK I thanks
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
5.3.2 > 5.3.1 downgrade IS possible
Good Afternoon,
I recent purchased a Kindle Fire 7 (11/11/16) and it was upgraded to 5.3.2. I was able to downgrade the OS to 5.3.1 using the ADB sideload method and then root using Kingroot (11/18/16). Be sure to block OTA updates once completed. Have not seen any issues yet and will report if i do.
Good Luck everyone.
ManWithCamera said:
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
Click to expand...
Click to collapse
Thanks
Tried to disable lockscreen ads using adb (com.amazon.kindle.kso), but when I touch the special offers icon on lockscreen, I get a window that says Selected Offers. Is there another package that I should be disabling? I'm on Fire OS 5.3.2.
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Onlye root, not recovery modded or other rom.
Thanks
p.s.: not use slang with me, thanks
Palux said:
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Click to expand...
Click to collapse
Yes - 5.3.1 can be reloaded again if pure stock is desired. However, this is not generally required for warranty exchanges (the only type of hardware assistance Amazon provides) as they do not perform a detailed inspection of returned devices.
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
br
Arret said:
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
Click to expand...
Click to collapse
Something went wrong; the Amazon Logo should display for <30 sec. You will need to reload FireOS 5.3.1 from the stock recovery menu and start over. Guidance here, here. Once recovered post back for further assistance loading CM 12.1.
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.
Ahhh... so it somehow got locked back and need to redo the procedure?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????
I have already unlocked my 8hd (karnak) 2018 and flashed TWRP. It is now running Lineage OS 14.1.
I have 2 queries:
1. How can I re-install FireOS but keeping the device unlocked with TWRP recovery mode?
2. Where to download an older version FireOS which is rootable by mtk-su? (I want to remove some Amazon stuff as a Root user)
drdtyc said:
I have already unlocked my 8hd (karnak) 2018 and flashed TWRP. It is now running Lineage OS 14.1.
I have 2 queries:
1. How can I re-install FireOS but keeping the device unlocked with TWRP recovery mode?
2. Where to download an older version FireOS which is rootable by mtk-su? (I want to remove some Amazon stuff as a Root user)
Click to expand...
Click to collapse
As long as you have the latest version of TWRP for Karnak (3.3.1-0) you should just be able to flash the standard Amazon software 'update' (change '.bin' extension to '.zip'). You may have to wipe system and data first if changing OS. Don't wipe 'internal storage' if you want to keep your files (pictures, downloads etc.). One time I flashed a standard Amazon software package my recovery was overwritten, but if you have an mtk-su vulnerable version it is easy to redo the unlock with no opening of the tablet required.
The last build of OS 6.3.0.1 (mtk-su vulnerable) can be downloaded by clicking on this link: https://fireos-tablet-src.s3.amazonaws.com/qGCnGoVclGgaVdoLm9521w9byK/update-kindle-NS6301_user_1638_0001309042308.bin.
MontysEvilTwin said:
As long as you have the latest version of TWRP for Karnak (3.3.1-0) you should just be able to flash the standard Amazon software 'update' (change '.bin' extension to '.zip'). You may have to wipe system and data first if changing OS. Don't wipe 'internal storage' if you want to keep your files (pictures, downloads etc.). One time I flashed a standard Amazon software package my recovery was overwritten, but if you have an mtk-su vulnerable version it is easy to redo the unlock with no opening of the tablet required.
The last build of OS 6.3.0.1 (mtk-su vulnerable) can be downloaded by clicking on this link: https://fireos-tablet-src.s3.amazonaws.com/qGCnGoVclGgaVdoLm9521w9byK/update-kindle-NS6301_user_1638_0001309042308.bin.
Click to expand...
Click to collapse
Thank you very much.
May I also ask where to download an older version of FireOS (with mtk-su vulnerability) for Fire 7 (Austin) 2017 which is also unlocked with TWRP recovery mode?
drdtyc said:
Thank you very much.
May I also ask where to download an older version of FireOS (with mtk-su vulnerability) for Fire 7 (Austin) 2017 which is also unlocked with TWRP recovery mode?
Click to expand...
Click to collapse
The Fire 7 (7th generation, Austin) is not vulnerable to mtk-su. The shorting method is the only way to unlock this model.
MontysEvilTwin said:
The Fire 7 (7th generation, Austin) is not vulnerable to mtk-su. The shorting method is the only way to unlock this model.
Click to expand...
Click to collapse
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.
drdtyc said:
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.
Click to expand...
Click to collapse
MTK-SU is a temp root and doesnt allow for system changes. You would be better off flashing magisk for root usage. You can download the latest from amazon flash it, and flash magisk.
drdtyc said:
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.
Click to expand...
Click to collapse
Best of luck finding a version of Fire OS for Austin that is vulnerable to mtk-su.
If you don't want root access permanently on this tablet you could install SuperSU or Magisk, remove whatever Amazon bloat you want and then unroot. Your only other option is to manually rename or delete any unwanted system apps using the TWRP file manager while in recovery mode.