Hi,
I have an Asus memo pad HD 7 ME175KG1/K00S model (dual sim).
Android : 4.3
kernel : 3.4.0-g1ce4f69
build number : JSS15J.WW_epad4G2C-10.12.13.4-20140307
Specification : memopadhd7gweb[.]io/asus-memo-pad-hd7-dual-sim[.]html
(This model is different from the Asus Memo Pad ME172V)
I managed to root this tablet with a generic rooting software called vroot : vroot_1.7.8.7753
Unfortutnly I was unable to detect/know the methode used by this software to root my device (I have tryed many known kernel vulnerabilities, but it looks like they are all patched) If any one could help here I will be grateful (I hate magical tools doing unkowning things to my devices, I love to understand how it is done)
After rooting my device I am working on porting CWM to this baby(work in progress ): I know I can use dd tool to directly write my CWM to the recovery partition, but I want to use fastboot mode to do this : fastboot run
The problem is that I can not access the fastboot : I have tried every singe possible combinision of keys connected/disconnected to pc but without succes. adb reboot bootloader did not help (adb reboot recovery works fine)
So I decided to dump the bootloader and check for fastboot support. I did this :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img (attached)
strings aboot.img > aboot_strings.txt (attached)
The good new is that fastboot is there
Code:
asus_fastboot_permission(): asus_security_flag = 0x%x, device.is_authorized =%d , device.is_unlocked = %d
[BL] aboot_init - Detect Volume Up Key (fastboot)
ERROR: Could not do normal boot. Reverting to fastboot mode.
Fastboot Mode !!!
fastboot: processing commands
Could not allocate memory for fastboot buffer
app/aboot/fastboot.c
fastboot: oops!
fastboot: %s
...
But it is some how locked/inaccesible.
I need your help to guide me on how to unlock this bootloader in order to access fastboot mode and install CWM.
(I have good linux skills and good experience in reverse engineering x86 asm language with IDA Pro, and I will burn this tablet to unlock its bootloader if needed )
Thank you
It looks like I am on my own on this one
I will keep updating this post with my progress(if any)
need help
Hi,
I need your help my friend!!
I have "asus fonepad 7 k00s" and somebody flash this device with this ROM.
now, many of apps that installed on this device, are crashing and I can't send massage, have a call etc.
I must change this ROM bot I can't. because the fastboot not start with power button+volume up
If you can help me please contact me!!
Email: [email protected]
Related
(Q) Root Dell venue 3840,
I've tried the Guide with the boot image for 4.4.4, with 4.4.4 and I tried the tether method. doesn't work....(stuck on CWM fastboot waiting.....) tried T3, T2, T1.... please help me!!!!
how can i root? and provide clear instructions?
thanks, sorry for being an ass...
Windows or Linux?
Edit: OK windows:
social-design-concepts said:
Thread still under construction
Intel Android Devices Root / Temp CWM Session
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME AN UNLOCKED DEVICE
Tethered Temporary CWM Recovery Session :
Note : This is a Temporary CWM Recovery Session for some Intel Devices with locked bootloaders, This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM Recovery. . .
WARNING : This Temporary CWM Recovery Session is for some Intel Devices with locked boot loaders , it is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
IntelAndroid-FBRL-01-17-2015.7z
Changes :
Fixed recovery.fstab generation should work for almost every device i can't guarantee for all devices if device uses some funky mounting point or a block device other than /dev/block/mmcblk1xx but after reviewing more than 50 different recovery.fstab from various fastboot.img i think i covered all the common intel devices.
If needed you can always include your own custom recovery.fstab in the recovery.zip
fstab generation automatically marks reserved / hidden partitions fs_types as emmc to prevent recursive mount loops this has the added benefit for devices that use traditional mount points for boot / recovery they are now able to be backed up too.
fixed adb on devices that don't have adbd as a service in fastboot.img init.rc
Note : WORKING
backing up to external storage / internal storage
unsigned .zip installation
adb root shell
you tell me
Note : KNOWN BUGS
installing using adb side-loading of zips doesn't work and breaks adb
you tell me
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-01-17-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME AN UNLOCKED DEVICE
Click to expand...
Click to collapse
T3 don't be in a rush! It says failed but then will load anyways. Wait for it! Use the very first link here. To root ¿ well when in recovery, flash superuser zip. Wait for it! Reboot from the cwm menu. In windows you can leave the device on normal and when you execute the launcher bat it'll put the tab in its proper mode. Just choose T3 and flash super user zip and then reboot.
it's android. i am using a windows 7 machine...
it boots into droidboot and just sits at cmd waiting.... i waited about 10 minutes. i am missing a step. can someone create a youtube video to follow by? i am willing to donate 10 bucks. thanks
mrazndead said:
it boots into droidboot and just sits at cmd waiting.... i waited about 10 minutes. i am missing a step. can someone create a youtube video to follow by? i am willing to donate 10 bucks. thanks
Click to expand...
Click to collapse
Sorry I didn't get back sooner , the issue is the fastboot driver installed as an adb driver seems to happen to most Intel devices.
Anyways with the device booted into droidboot open windows device manager select the adb device and right click and update driver software. Select browse my computer. select let me pick. then select the bootloader driver .
No donation required gotta get back to playing with my little girl i'll add pics later.
ok thanks man, pics will help me, i'm not too bright.
i will try that. as the device is waiting on droidboot, i will open device manager, and load the driver (where can i download this driver?)
Thanks for trying to help me guys. I give up. Too hard.
Yes! I did it! the social concepts step was what i was missing... thanks man i am rooted
Perfect!!
justlovejoy said:
Windows or Linux?
Edit: OK windows:
T3 don't be in a rush! It says failed but then will load anyways. Wait for it! Use the very first link here. To root ¿ well when in recovery, flash superuser zip. Wait for it! Reboot from the cwm menu. In windows you can leave the device on normal and when you execute the launcher bat it'll put the tab in its proper mode. Just choose T3 and flash super user zip and then reboot.
Click to expand...
Click to collapse
I follow all the steps and I sucessfull root my device (Dell Venue 8 HSPA+ 3830-A30P)
Tks!!!
Here is full rooting method which i share with you from Dell Venue 8 3840 Manual. I hope this is easiest and result-oriented method:
Download and install the Intel Phone Flash Tool Lite on your PC. Also download the venue_3840_droidboots.zip.
Run Intel Phone Flash Tool as administrator and connect Dell Venue 8 to PC using OEM USB cable.
Browse and choose venue_3840_droidboots.zip file.
Select ‘1-502_droidboot_and_firmware.xml‘ from the drop down menu and click on start.
Reboot Dell Venue 3840.
DESCRIPTION:
Today i found the New Root & Installing Custom Recovery(CWM) in KITKAT surely...
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
PREREQUISITES:
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
PROCEDURE:
FOR UNLOCKING BOOTLOADER, FOLLOW THIS
Download the Attached PC Software Named "Huawei Product ID Generator" then Extract this zip file...
Now open it, fill all Info in it and select the device Y300-0000... After this, it will Generate a Product ID for your Phone....
Now go to this site Unlocking Code website
Login to this site using your Huawei id which you made in themes store or in huawei cloud!!
Use the Serial Number Written on BACK OF YOUR PHONE..!!
Fill like, samrtphone>Product Model should be "HUAWEI Y300-0000"
then fill all fields and captcha also.. Click Submit and get the UNLOCKING CODE....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
Now go in your 4C's Settings>About Phone.
Then tap on Build number 10 times,,, you will get the Developers options in Last of Settings app. Open Developers option and Turn On the USB DEBUGGING.
Now connect your device to PC in MTP mode and then install the ADB drivers for it....
To install adb drivers correctly, use the Software Adb Driver Installer from here
LINK FOR ADB DRIVER INSTALLER
Full ADB folder is also attached Below.... put this folder in drive C.
Now Direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
BOOTLOADER UNLOCKED NOW!!
Now You are Ready to install CWM recovery first.... Download the Root and CWM recovery File from here...
This File Also contain Stock Recovery of Kitkat Rom
4C Root+CWM by [email protected]
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in adb to install the Custom Recovery(CWM) in your phone.
fastboot flash recovery cwm.img
Then
fastboot reboot
This will reboot your phone and cwm installed.
Now move the Root.zip file to sd card and using CWM recovery, install it.. and Whoa!
Its done and phone Rooted for sure... wid no bootloop chance..
Now Customize Your Phone Install Viper4Android And Roms Xposed ^_^
If You Want To Stock Recovery After Root Simply Use The Command In Fastboot Mode
fastboot flash recovery stock.img
Then
fastboot reboot
This way, you will have Stock Recovery back.
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01
Version Information:
Status: Stable
Stable Release Date: 2015-09-28
Created on: 2015-05-29
Last Updated on: 2016-02-19
Reserved
I'll try it when i arrive home.
Enviado do meu CHC-U01 através de Tapatalk
I flashed the cwm zip .. But now unable to boot in to recovery .. After doing Vol up + power .. Honor title come n nothing happens .. Normal booting is fine , just recoverys bricked I think :crying:
Nops... keep pressing vol up for 3 sec then keep power button pressed also untill cwm appears... Dont release keys when logo appear... Release when cwm appears... @Srijit
Press thanks if i helped you
Followed all the steps but still not able to boot into cwm .. I have lollipop beta installed .. Is that the problem ? :crying:
Its for kitkat nd has kitkat kernel.....
inshaalmirza said:
Today i found the New Root & Installing Custom Recovery(CWM) for sure,,,
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
Just mail at [email protected] wid subject that unlock bootloader huawei honor 4c and in mail type all info..like imei, serial no. Product number nd model number...they will send you unlocking code....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
download the installer utility ADB and Fastboot and set (if you have them yet);
direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
Now You are Ready to install CWM recovery first.... Download the Root and CWM recovery File from here...
https://drive.google.com/file/d/0B0iMDu5QRxNicU1EalpZeHNUR3M/view?usp=sharing
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in adb to install the Custom Recovery(CWM) in your phone.
fastboot flash recovery recovery_cm.img
Then
fastboot reboot
This will reboot your phone and cwm installed.
Now move the Root.zip file to sd card and using CWM recovery, install it.. and Whoa!
Its done and phone Rooted for sure... wid no bootloop chance..
Now Customize Your Phone Install Viper4Android And Roms Xposed ^_^
If You Want To Stock Recovery After Root Simply Use The Command In Fastboot Mode
fastboot flash recovery recovery_official.img
Then
fastboot reboot
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Credits: Gizdev site...
Click to expand...
Click to collapse
where is for lollipop,,
No lollipop cwm yet...
tested recovery and cannot made a advanced restore. Tried only system but after selection cannor made it to apply.
Anyone knows how?
I backup full... Nd its done
I still dont have the bootloader unlock code
Sent from my ALCATEL ONE TOUCH 7047D using XDA Forums
Lol.... Follow procedure carefully... Nd dont write anything other
Honor 4x I need custom rom and cwm r lollipop update
Sent from my Che1-L04 using Tapatalk
inshaalmirza said:
I backup full... Nd its done
Click to expand...
Click to collapse
Me to.
I tried to restore only system but don't know how.
Everything else seems to work OK.
Enviado do meu CHC-U01 através de Tapatalk
OP! how do you able to get CWM,
does it came from own recovery of 4C? if yes, can you show how
Custom recoveries use the kernel properties of device.... Not the stock recovery converted to cwm.....
Hey. Kingo root android application make tempory root your device. After restart mobile. Back to normal
Sent from my CHM-U01 using XDA Forums
Unlock bootloader... Then it wont come back to normal...
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
Hello, my name is Alberto, i've a big problem with my tablet.
I've tried to root the device but probably i have choosen the wrong rooted system maybe from another region, so now the tablet stay always on the asus logo and i can't enter in recovery modo to upgrade the firmware.
If i try to enter in recovery mode i see a screen with the usb cable in the centre and starting from left on top the following commands :
Droidbot provision os
IFWI version 51.33
serial num . 1111111111111111
Droidboot version : local build or english version
After, all the command with volume up and down for :
Reboot droidboot
reboot
factory reset
sd download
power off
Down in can see :
E: unable to open debricking
Fastboot init...
Fastboot CMD WAITING...
Everytime i try to install a new firmware the asnswer is :
unable to rename file cache/update.zip
unable to write file/cache.zip
That's all.
I don't know what to do to unbrick the tablet, before was android 4.3 but now i don't know what i have done.
Please help me if you can with instructions and programs to use.
The device is not seen by my pc with seven and if i try to flash the original asus upgrade it fails.
Hope you can help me.
Sorry for the disturb guys.
Thank you.
Alberto
Gabbathe said:
Hello, my name is Alberto, i've a big problem with my tablet.
I've tried to root the device but probably i have choosen the wrong rooted system maybe from another region, so now the tablet stay always on the asus logo and i can't enter in recovery modo to upgrade the firmware.
If i try to enter in recovery mode i see a screen with the usb cable in the centre and starting from left on top the following commands :
Droidbot provision os
IFWI version 51.33
serial num . 1111111111111111
Droidboot version : local build or english version
After, all the command with volume up and down for :
Reboot droidboot
reboot
factory reset
sd download
power off
Down in can see :
E: unable to open debricking
Fastboot init...
Fastboot CMD WAITING...
Everytime i try to install a new firmware the asnswer is :
unable to rename file cache/update.zip
unable to write file/cache.zip
That's all.
I don't know what to do to unbrick the tablet, before was android 4.3 but now i don't know what i have done.
Please help me if you can with instructions and programs to use.
The device is not seen by my pc with seven and if i try to flash the original asus upgrade it fails.
Hope you can help me.
Sorry for the disturb guys.
Thank you.
Alberto
Click to expand...
Click to collapse
Anyone can help me please? :crying:
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 )