Related
The factory reset doesnt put it back to 5.4.0.0 anymore, it keeps it at 5.4.0.1. The device was 5.4.0.0 when I purchased it.
WeiKaiTsai said:
The factory reset doesnt put it back to 5.4.0.0 anymore, it keeps it at 5.4.0.1. The device was 5.4.0.0 when I purchased it.
Click to expand...
Click to collapse
If you are on 5.4.0.1, you cannot uninstall/disable system apps anymore. You can try to downgrade back to 54.0.0 using the firmware here. A few new users reported a hard brick when they tried. I don't know whether that holds any truth or not. No regular users, that I have seen (may have missed them), have tried.
Hi DragonFire, thank you for the response. Do you know how to install that version of the OS, I tried to use the system update tool in device settings but it wont allow me due to "older version."
WeiKaiTsai said:
Hi DragonFire, thank you for the response. Do you know how to install that version of the OS, I tried to use the system update tool in device settings but it wont allow me due to "older version."
Click to expand...
Click to collapse
Put the file into the internal storage of your tablet. Power off. Reboot to recovery by pressing and holding volume down first, then power button until Amazon logo appears. When recovery screen comes up, select update from ADB. Open an ADB window and type:
adb sideload your.file.name
Warning: A few users say this will hard brick your device. Though no regular users have tried that I know of. So the decision is yours. I am not responsible for a broken tablet.
---------- Post added at 03:09 AM ---------- Previous post was at 03:07 AM ----------
WeiKaiTsai said:
Hi DragonFire, thank you for the response. Do you know how to install that version of the OS, I tried to use the system update tool in device settings but it wont allow me due to "older version."
Click to expand...
Click to collapse
Also see this thread. Apparently you CAN downgrade. If you try, and are successful, please let us know.
Hello DragonFire,
For the Fire HD 8 7th Generation on 5.4.0.1, the attempt to downgrade to 5.4.0.0 using "adb sideload <filename>" in recovery failed, but the device was not bricked, everything was fine. The recovery simply showed that signature verification of the package failed.
Both good news and bad news I guess. I did a factory reset before installing the 5.4.0.0 file.
WeiKaiTsai said:
Hello DragonFire,
For the Fire HD 8 7th Generation on 5.4.0.1, the attempt to downgrade to 5.4.0.0 using "adb sideload <filename>" in recovery failed, but the device was not bricked, everything was fine. The recovery simply showed that signature verification of the package failed.
Both good news and bad news I guess. I did a factory reset before installing the 5.4.0.0 file.
Click to expand...
Click to collapse
I forget...is there an option to update from SD card? If so you can try that.
EDIT: That having been said, I don't know the other methods (if there are any) to downgrade, as I have never done it.
Hello DragonFire,
Don't see the option for SD card.
The link you gave me on this thread is for Fire (7th Generation). I saw there is another link on amazon for Fire HD 8 (7th Generation). I used the one for Fire HD 8 (7th Generation) and the downgrade failed, bricking the device. Can not power it on or do anything.
No way to downgrade Fire HD 8 7th Generation for now unless you want to hard brick it.
This doesn't void the warranty does it? I didnt really break or hack anything, just try to restore it back to the good old 5.4.0.0
WeiKaiTsai said:
Hello DragonFire,
Don't see the option for SD card.
The link you gave me on this thread is for Fire (7th Generation). I saw there is another link on amazon for Fire HD 8 (7th Generation). I used the one for Fire HD 8 (7th Generation) and the downgrade failed, bricking the device. Can not power it on or do anything.
No way to downgrade Fire HD 8 7th Generation for now unless you want to hard brick it.
This doesn't void the warranty does it? I didnt really break or hack anything, just try to restore it back to the good old 5.4.0.0
Click to expand...
Click to collapse
No. If you want to return it to Amazon for a courtesy replacement, you have 30 days from the day of purchase.
The warranty is 90 days though, I asked the support and they told me to mail the device to them and they will either fix it or send me a replacement
WeiKaiTsai said:
The warranty is 90 days though, I asked the support and they told me to mail the device to them and they will either fix it or send me a replacement
Click to expand...
Click to collapse
90 days is new unless you purchased a better warranty. If not, 90 is great news!
Amazon has a best customer support in a whole world (especially for the Prime members. BTW, do you know, any of your friends with the Amazon Prime can add you (i.e. your Amazon account) to his Prime account without any trouble? Actually, no proof of the family membership required), telling you like a very long-long time Amazon customer (practically since launch in the year 1997 or 98?).
P.S. Last couple of years Amazon's customer support has become a little worse (because of the massive outsourcing) but IMHO still the best on the world.
I really dont have any friends So no friends can help me test it out, sorry.
[OFFTOPIC_MODE] @WeiKaiTsai, try to make some... It's really hard to live without friends If you in US, there are lot of possibilities to make a new friends here.[/OFFTOPIC_MODE]
5.4.0.1 downgrade
Recently bought Fire HD 8 (7th gen). It came with 5.4.0.1. Tried booting into stock recovery and side loading update-kindle-50.5.7.9_user_579225620.bin in order to downgrade back to 5.4.0.0.
It went though following steps:
Finding update package
Opening update package
Verifying update package
Installing update
Patching system image unconditionally
script succeeded: result was []
Install from ADB complete
I rebooted, and baam dead tablet. Nothing on screen at all. Even tried vol down plus power.
Lesson is.. if youre on 5.4.0.1 - dont try this at home kids!
DrummerDanTX said:
Recently bought Fire HD 8 (7th gen). It came with 5.4.0.1. Tried booting into stock recovery and side loading update-kindle-50.5.7.9_user_579225620.bin in order to downgrade back to 5.4.0.0.
It went though following steps:
Finding update package
Opening update package
Verifying update package
Installing update
Patching system image unconditionally
script succeeded: result was []
Install from ADB complete
I rebooted, and baam dead tablet. Nothing on screen at all. Even tried vol down plus power.
Lesson is.. if youre on 5.4.0.1 - dont try this at home kids!
Click to expand...
Click to collapse
If you have an HD 8, regardless of the generation, you CANNOT downgrade back to 5.4.0.0. However, if you have a 7th generation Fire 7, you CAN downgrade. Weird eh?
DragonFire1024 said:
If you have an HD 8, regardless of the generation, you CANNOT downgrade back to 5.4.0.0. However, if you have a 7th generation Fire 7, you CAN downgrade. Weird eh?
Click to expand...
Click to collapse
Totally weird. But this is the game we play with any hardware vendor to achieve freedom on our devices. It's fun
Here's some more info:
I still have no activity on the tablet screen, but when I connect USB cable to PC and hit power button, PC will ding the new hardware connected sound. About a second later the disconnected hardware ding sounds.
I was able to verify the new hardware found is labeled by Windows as "MediaTek PreLoader USB VCOM (Android)" It disappears in sync with the disconnect sound.
I don't think it's completely bricked - I'll keep posting results of what I can get it to do from here.
Update: Couldn't get it to do anything else - Asking AMZ for a do over (replacement)
Fire HD 8 v5.4.0.1 is NOT DOWNGRADABLE - confirmed!
Hey there,
just tried to downgrade my Fire HD 8 (7th gen) v5.4.0.1 to the version 5.4.0.0 using the file "update-kindle-50.5.7.9_user_579225620.bin" and, as unfortunately expected, hard bricked the poor thing. Fire doesn't react on power button or any other buttons - just black screen. Using the same method I downgraded today my Fire 7 (7th gen) and everything went really good.
So guys, yet another (sad) confirmation here that the Fire HD 8 (7th gen) is not downgradable.
FreewareLovers said:
Hey there,
just tried to downgrade my Fire HD 8 (7th gen) v5.4.0.1 to the version 5.4.0.0 using the file "update-kindle-50.5.7.9_user_579225620.bin" and, as unfortunately expected, hard bricked the poor thing. Fire doesn't react on power button or any other buttons - just black screen. Using the same method I downgraded today my Fire 7 (7th gen) and everything went really good.
So guys, yet another (sad) confirmation here that the Fire HD 8 (7th gen) is not downgradable.
Click to expand...
Click to collapse
So far as I know, none of the HD 8s can be downgraded, regardless of the generation.
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Click to expand...
Click to collapse
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
[2019-01-29 17:33:56.846249] Waiting for bootrom
[2019-01-29 17:34:07.704879] Found port = /dev/ttyACM0
[2019-01-29 17:34:07.744128] Handshake
[2019-01-29 17:34:07.766738] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 128, in <module>
main()
File "main.py", line 57, in main
handshake(dev)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 152, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 89, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
...
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
Click to expand...
Click to collapse
See this post for the proper output:
https://forum.xda-developers.com/showpost.php?p=78792151&postcount=14
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
@powerpoint45
bibikalka said:
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
Click to expand...
Click to collapse
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
spenceboy98 said:
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
Click to expand...
Click to collapse
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
bibikalka said:
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
Click to expand...
Click to collapse
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
spenceboy98 said:
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
Click to expand...
Click to collapse
Yep - it's a tough cookie. No labels on the board, and button pushes don't work either to get the device into the BootRom mode. I could only get the pre-loader mode as well.
We will have to wait for somebody to figure out the electrical connections here. Unfortunately, I don't have time to dig around like that.
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
r3pwn said:
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
Click to expand...
Click to collapse
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
...
Click to expand...
Click to collapse
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
bibikalka said:
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
Click to expand...
Click to collapse
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
I see. Usually, recovery is verified each time you boot, and the OS will overwrite it if the checksum does not match. But, in your case, TWRP disabled that feature, so you are out in the cold.
I have 2 tablets that are looping on the white Amazon logo. I tried to restore them via aftv2-tools, but nothing worked. It's interesting you got the same glitch.
Look at the bright side - keep poking around now on your motherboard, you have nothing to lose!
I attempted to overwrite the beginning of EMMC - and got an absolutely dead tablet, see here:
https://forum.xda-developers.com/showpost.php?p=78871662&postcount=784
No bootrom mode as far as I can see ... One of these days I'll open the case, and try to disconnect the battery.
bibikalka said:
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
Click to expand...
Click to collapse
2017 Fire HD7, so 7th gen, aka austin
r3pwn said:
2017 Fire HD7, so 7th gen, aka austin
Click to expand...
Click to collapse
You are in the wrong forum.
The 2017 Fire 7 AKA austin doesn't use the suffix HD. It's just Fire or Fire 7.
This is what you are looking for: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
Did put any more time into this? Was it some damaged contact?
bibikalka said:
Did put any more time into this? Was it some damaged contact?
Click to expand...
Click to collapse
No I haven't. Not sure what the issue is. As far as I know it's still not booting up to anything. I just started school recently and I left my Fire HD6 at home, so I haven't had the chance to mess around with it more.
Just for test. Is there any possiblility that pressing the power button with any volume button makes the tablet enter in BootROM. My Fire and my BQ enter in BootROM when I press volume -. Just try all the bootloaders for see if one support it like 5.0.1.
Regards!
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
Click to expand...
Click to collapse
I would love to get my HD 6 working again.
I recently ran the amonet script on my HD 10 and in a few minutes had an unlocked bootloader and TWRP. I read the HD 8 thread where the author posted his exploit and it really is an epic achievement. I'm also hoping the bootloader unlock comes to the 4K firestick as well. It's a lot of work from I read, but the firestick is popular enough to warrant that kind of attention. I have a Fire HD 6 which only boots to a recovery that allows me to reset or reboot but has no option to apply update from adb, so I've been stuck on stock Fire OS. It would be nice to finally get TWRP after so long on the HD 6.
***
My girlfriend bought a Fire 10 and now that she has opened it she is thinking her son would rather it be an Android. (He is autistic and does not deal with change well and his phone is Android but he has a dying iPad.) I found [ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019] and I see this might be just what the doctor ordered but it is asking me to do a bunch of pre install items - Unlocked Bootloader - TWRP Installed. I have installed TWRP on a phone many eons ago and never had to unlock a bootloader (super early smartphone days when I used TWRP). Is there anything that gives a dummy, step by step method, on doing this Frankenstein change all from a Windows 10 PC? I have done the fastboot and ADB stuff in the past (got rid of specials and offers) so I am not squeamish with that portion of things. I do have some concerns on the link at the top to [UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez) since this is pointing to *nux which I have not used in the past. Help me obi-wan you are my only hope.
This will be easy unfortunately. There is no permanent root or TWRP for the new HD 10 yet, which, BTW, is known as Maverick. The ROM you found is for an older model, Suez, which does have root and TWRP. Sorry man. You can always try to the Fire Toolbox located in the development section to change the default launcher to Nova which is much more Android looking, but that's not permanent either and is prone to switching back to Amazon's default. It's early days right now.
StumpedTechy said:
My girlfriend bought a Fire 10 and now that she has opened it she is thinking her son would rather it be an Android. (He is autistic and does not deal with change well and his phone is Android but he has a dying iPad.) I found [ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019] and I see this might be just what the doctor ordered but it is asking me to do a bunch of pre install items - Unlocked Bootloader - TWRP Installed. I have installed TWRP on a phone many eons ago and never had to unlock a bootloader (super early smartphone days when I used TWRP). Is there anything that gives a dummy, step by step method, on doing this Frankenstein change all from a Windows 10 PC? I have done the fastboot and ADB stuff in the past (got rid of specials and offers) so I am not squeamish with that portion of things. I do have some concerns on the link at the top to [UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez) since this is pointing to *nux which I have not used in the past. Help me obi-wan you are my only hope.
Click to expand...
Click to collapse
No root/unlock methods here for this device. You can only customize it using Fire toolbox.
Hi, can anyone point me in a direction of how to upgrade my Fire HD OS (5.3.7.0 7th gen) to the latest Fire HD release (7.0 anything, 9th gen)? I work on Windows 10.
I am happy to follow previous threads/instructionals on root, bootload, finding right downloads etc - just would love an expert to point me in right direction than going in the wrong direction myself.
Are you looking for stock or custom. There is no Amazon update, it was a hoax. There is an option b to have Android 7.1.2 lineage 14.1 but you must unlock first. Likely you will need to open your device, unless you have to access..
Start here for unlocking,
https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
I am assuming you have a 10 inch. A Linux live disk will be needed, but instructions are easy, it's like cmd prompts. I can try to assist if you can't figure it out.
Hello! I want to install LineageOS on my Kindle Fire HD8 5th Generation running fire os 5.6.8.0, build date december 31st, 2020 at 1:27 pm (not sure if that means anything). It's wiped right now, it's not even my main kindle, meaning nothing will be lost if i have to wipe it again.
I dont want to have to open it up and solder wires, because I dont have the equipment for that.
Where do i begin?
Edit: I am using windows, so I don't have a linux install.
Just checking- how long does it usually take for responses? I've waited about 1 1/4 days and nothing.
Did you look in this post? Check this out first. There is not a lot of Kindle development taking place, but there should be enough information to keep you busy. Don't just rely on asking a question on XDA, either. Search for an answer, first. If you can't find it after diligently searching, then post.
Check this post out. It sounds like it has the answer to your qustion.
[Root] Amazon Fire HD 8 & 10 (5th Gen 2015)
08 Feb 2016 It seems Kingroot (NewKingrootV4.80_C135_B242_office_release_2016_02_ 03_105203.apk) is working, but you may need to run it a few times before it will root XDA Thread: KINGROOT: The One-Click Root Tool for Almost All Devices Direct...
forum.xda-developers.com