[Android Q&A, Help & Troubleshooting] Ap0ca1ypse:
Hello everyone,

This is my first post on xda and I've read some of the posts etc and I thought it's time to begin to start questions related to my problem. This will be kinda long post and I'll try to give as much as information from my device specs to what I did to my device up to this point so you guys can understand my problem maybe help me or simply you can say its bricked and I can done with it. And last, I'm kind of newbie with android environment.

As you can see from the title my device is 'Reeder a8i Quad tablet' which is currently in Turkey. Device specs are following:

Uses Intel atom bay trail, Android 4.4.4, TF card (similar to sd)

bootloader title says 'droidboot' and for the recovery there is no install from sdcard or something like that.

There is almost little knowledge with the device and official site is not helping ( I guess they don't care at all )

Some Turkish forums actually got some idea about rooting and flashing stock rom. ( Later in 2015-2016 they released 5.1 for the device and that's all ). Forums actually use old how-to's from reeder support with images how the process done for upgrading android system.

First I try to find some ways to root the device but unfortunately my lack of knowledge and almost no guide for root get me stuck in the first time. I had 4.4.4 android and I was looking at ways to root it. My friend used King Root to root an old samsung phone but later he deleted it and suggested me to use it since I couldn't find any other way. I give it a try and use king root and followed instructions and voila! I had root access on my tablet and quickly installed greenify, root browser, uninstall ( for stock applications and especially google apps ) and later I installed superSU with terminal. Now for the fun part. I did give all these apps root access and deleted stock apps including google apps and 1-2 apps that king root installed while rooting. After deleting google apps I screwed up and keep getting crash reports for some of the services. I didn't know what I did to that point for google so I simply wipe data and wishing reverting all the things. After boot, there is king root app, google services again crushing and tablet looked unstable. I installed root checker which gives me that no 'root access' so I opened king root app and it couldn't root with error messages. I installed gapps for 4.4.4 and google services returned normal. Connected my tablet to pc and use king root again to root. Again device is rooted. Installed same apps, deleted king root apps and entire google apps, services, etc from tablet. Now I got no problems with google, successful root and happy face.

After closing my tablet and opened some day I saw that I don't have root access and king root app again no help at all. Again connected pc, app seems unstable with says my device is rooted and sometimes says not rooted. There was something wrong for sure and again wipe data etc. But now I found reeder tablet stock rom from the internet ( website is closed just today! ) including tons of tools and drivers and roms for other devices including mine. It's not actually site just index so you just go in a folder click and download etc. Installed my drivers, I already had android studio so adb fastboot etc but I did download some quick tools for just for this. I remember my device couldn't open so I just did some things from adb and fastboot and after 1 day work it's opened with 4.4.4. But google kept crashing so I understand that I didn't flash a stock rom entirely. Again root with all the apps and I simply use the device for some apps.

Up to this point I want to call part 1 because after this may be 3-4 months passed and about 2 days ago I started to play with tablet again. Now I installed some network tools to play with. Trying to use some MITM or cookie stealing etc. I used tons of apps including kali linux's nethunter tools which I get from their zip file. Obviously some of them not work and some other are. Still my root is unstable one time it says rooted one time says not. So It kept bothered me but now I don't want to use king root tried to search other ways to replace it with supersu. There is a guide here to use a shell script but it didn't worked so I found an app to replace it. It says done but king root app kept crashing and this point is where I called point of no return ( at least for me ) I downloaded king root app to my pc and tried to root it. It says rooted and now reboot etc. After that nothing changed and still the same. Btw, before tried root I used fastboot to try to open bootloader with boot.img from stock rom but I don't know what it actually does so. Again app is crashing there is no root access so I wanted to install stock rom. There is a guideline for 4.4.4-5.1 for my tablet and there is a tool named 'Manufacturing flash tool v6+' from intel. But I need an OTG for that since I don't have one. Flashing tool uses an xml file. Since I have that from stock rom's folder. I thought give it a try but nothing happened and tool supposed to detect my device but it didn't. At that time I could use fastboot and adb without a problem so I assumed tool got some sort of bug and installed again but result were same. I tried to wipe data and reboot but I got recovery screen with '3E' error. I tried to get into recovery screen to use adb and do something. I desperately used fastboot flash boot boot.img, fastboot flash recovery recovery.img and system system.img from 4.4.4 but not only it failed with the error 'end of footer from /tmp/update.zip not 0xFFFF file exists' but somehow corrupt the device rom and now I was stuck with reeder logo with infinite loop. After that I wanted to give that manufacturing flash tool a try again and same result. I did buy an otg cable for tablet and for my phone which screen destroyed couldn't unlock since touch screen almost not working and usb debug is closed to open that phone as well. There are files from reeder help desk to upgrade it to 5.1. I copied those files to tf card and used otg cable on my keyboard. Guide says press ESC key until bot manager is coming up. There is a screen with bot manager including bios settings. Guideline and tools says it's for upgrading bios so I did those steps and now again recovery mode. Opened manufacturing flash tool with my 5.1 xml but no result so I found something under menu to 'Print flash file cmds' used it and it simply bunch of fastboot commands. I opened fastboot and executed all those commands one by one for myself. Eventually some of them are failed with 'fastboot oem unlock' etc. Since it's changed into flashing unlock which both commands give error from tablet 'unknown command' I followed steps. ( At the end of the post I will give the xml commands from manufacturing flash tool ) After that at I used 'fastboot flash esp_update' provided with esp.zip file successfully. After that 'fastboot flash fastboot droid.img' failed. Following with 'fastboot flash boot boot.img' 'fastboot flash recovery recovery.img' 'fastboot -S 200M flash system system.img' all those commands failed and couldn't install the 5.1 manually.

At this point if I wanted to open my device it simply tries to update bios with the same file ( if tf card inserted ) other than that still at recovery with 3E and adb sideload not working with the error I got above 'end of footer from /tmp/update.zip not 0xFFFF file exists'

I know that my post is long and tried to give as much as information as I can. I just hope device is not completely bricked and there is a way to solve this. Any questions about information about device etc you can shoot I try my best to answer. Thank you for people who are reading this to spare their time.

Manufacturing flash tool xml file commands and success or fail after I executed them in DNX mode ( volume up + down + power at the same time )

fastboot flash osloader "I861B1C_1601001_64_20160115\efilinux-userdebug.efi" - success

fastboot boot "I861B1C_1601001_64_20160115\droidboot.img" - success

sleep - failed

fastboot oem enable_oem_unlock - failed

fastboot oem unlock - failed

fastboot oem wipe ESP - success

fastboot oem wipe reserved - success

fastboot oem start_partitioning - can't remember

fastboot flash gpt "I861B1C_1601001_64_20160115\partition.tbl" - success

fastboot oem enable_oem_unlock - failed

fastboot erase system - success

fastboot format cache - success

fastboot format config - success

fastboot format logs - success

fastboot format factory - can't remember

fastboot oem stop_partitioning - failed

fastboot flash ESP "I861B1C_1601001_64_20160115\esp.img" - success ( After this point I assume device is rebooted and opened a screen which is kinda new with big green 'NORMAL BOOT' text )

fastboot erase keystore - success

fastboot oem verified - success

fastboot format data - success

fastboot flash esp_update "I861B1C_1601001_64_20160115\esp.zip" - success

fastboot flash fastboot "I861B1C_1601001_64_20160115\droidboot.img" - failed

fastboot flash boot "I861B1C_1601001_64_20160115\boot.img" - failed

fastboot flash recovery "I861B1C_1601001_64_20160115\recovery.img" - failed

fastboot -S 200M flash system "861B1C_1601001_64_20160115\system.img" - failed

fastboot continue - failed ( it says success but reboot never happened )