This does not work on Android 2.2 builds in its current state
Calling this xauBeta so we can distinguish between versions. Tested with Bestbuy Huawei Ideos S7-104 White (external microSD and internal 8GB).
Tested on BestBuy S7-104 running the newer Singapore ROM S7V100R001C61B011, for Android 2.1.
This was not tested on a stock BestBuy ROM. I do not know if this will work properly on that firmware. Please report your findings.
Use fastboot to flash (install fastboot and fastboot drivers, enter fastboot via vol+/- and power button combo, issue the command 'fastboot flash recovery recovery.img')
Download
v0.11
Internal NAND + External SD Version for S7-104 BestBuy, Radioshack:
I do not expect this version to work properly for single SD variants
Multiupload download
de54cb057b6b9ebbd5912588e4aad628 recovery.img
External Single SD Version for S7-105 Telstra:
Multiupload download
aa0c883aac0edb8f5d9929148cf56136 recovery.img
Changelog
v0.11
-forgot nandroid-md5.sh
v0.1
-initial version
Notes
This recovery image is functional enough for use.
If you have the dual-nand variant of the S7, you can still use the recovery image for the single-sd version. If you do so, installable update zip files will need to be placed on the external microSD instead of the internal nand. You also lose the ability to mount the internal nand to the computer via recovery.
What works: Nandroid works. USB mounts work (choose between internal and external mount hacked in for the dual-sd version). Flashing installable update zip files work. Fix permissions works.
This is still an ugly hack of a recovery image. Instead of waiting for developers, I threw this together so I can use it.
This recovery does not read the misc partition flags and boots into user mode every time. Hopefully this does not break too many things. It only displays only 50% of the screen, but it is still readable. It works for me, so I'm not going to touch the kernel framebuffer or whatever was causing the quad-screen craziness.
Buttons in this recovery image:
Up - vol +, dpad up
Down - vol -, dpad down, menu (cycles when menu reaches bottom)
Select - home, dpad select, power, send call
Back - end call, back
The weird color and the half-screen issues are known. No fixes are planned.
What hasn't been tested
Need someone to help figure out which would be the ideal way to deploy this. I typically fastboot. Will look into an easier method of deployment possibly in the future.
Not tested:
formatting external SD for apps2sd feature (under advanced)
format sdcard (not sure what this option does)
nandroid with apps2ext
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
boot
nandroid
Credit to koush and everyone who has worked on Clockwork recovery
Also http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
razor950 for the device files
perivarlura for some binaries from his ramdisk
Easier Windows Install
Requires full root on your tablet, and USB debugging enabled. Plug your S7 in via USB while booted into Android. This is a Windows install script. Just run install_now.cmd and follow the prompts.
Internal NAND + External SD Version for S7-104 BestBuy, Radioshack:
Download from Multiupload
External Single SD Version for S7-105 Telstra:
Download from Multiupload
This is a script that will try to automatically install this recovery image to your device. You will still need to install the Windows drivers on your computer.
Have the drivers ready from Huawei -> Direct Link
http://bit.ly/gjH9f9
Credit to install script for malez recovery: http://code.google.com/p/acer-liquid-malez-recovery/
Hi . Great to c that ideos s7 has clockwork mod now .
I would like to ask if there is any way to unlock the huawei u8150 android handset and sim unlock it ?
Sent from my GT-I9000 using XDA App
Link;
"External Single SD Version for S7-105 Telstra:
Download from Multiupload"
Seems to be brocken
take the <br%20> off the end of the url when you click on it
You should be able to fix the graphical issues by building a kernel with the framebuffer forced to rgb565 (this is what worked for u8800).
EDIT: Nevermind.. just saw that there's a newer version from a different developer that fixes it, though using a different solution.
Related
Alright, this thread is going to be dedicated to "Nooky" the supertool. What this script will do, is multiple things. Reset to factory firmware (exploit the /factory partition / bootcount.), Root, fix broken recoveries, and with root comes all of the mods for stock that I came up with. This is so then we can have everything in one tool without worrying about certain things. (also, after root, it could also install CWM recovery.)
Instructions:
I suggest that you have some kind of root shell. Either by using the adb hijack app I made found here or by being in recovery.
Extract the zip, and click "Nooky.bat" Ignore all other files, just click "Nooky" not nook and zergy. Nooky. Just needed to clarify. Anyway, then you just go through the menus and choose what you want. Enjoy.
*Note, you need to have an adb shell running as root on some of these options. So you may want to be booted into recovery off sd or something.
Features:
Root (includes nook and zergy script)
Md5sum check for recovery images.
Recovery flashers (root only.)
Reboot menu (Android and Recovery)
Reset nook to factory state (including /system and boot.) {8 failed boots method}
Auto device checker
More to come (maybe)
Download, screenshots, and changelog will be in 2nd post.
Download link:
download the awesomeness here.
Changelog:
Code:
1.0: Initial Release
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Very cool!
psh, seems more like a discussion thread >.> lol, J/k Will post video when made.
when you say install recovery, is this stock or CWM? If it is CWM, might I suggest a restore to stock flash as another option? or the reverse?
Other suggestions- stock image flasher? Stock image checker? check mounting of SD card? is it possible to use this tool to force people to boot from SD card by choosing an option here?
Just thoughts.
seems a good tool!
leegoon84 said:
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Click to expand...
Click to collapse
We should have full use of the storage on the Nook Tablet after the next release of the CM7 ROM that Celtic, Gonce and Indirect are working on, without changing partitions at all.
Repartitioning is kinda dangerous with these things, it's not like repartitioning an SD card or a PC. This tool is for prepping/rooting/factory-resetting a nook tab, among other things. I think it's going to be pretty important as a recovery/prep tool when everyone's flashing ROMs to their NTs.
Mike is right. Also, fixed a small bug.
Sorry i don't understand only one think (i hope), To use this supertool, i have to install adb and usbdriver?
Sorry for the stupid question? but i not sure
i want to buy NT, but first, i want know how to root it?
Thanks
Hi Folks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you may or may not be aware, I have been working on get CWM Recovery working on the Gen9's and basically make the layout of the Filesystems etc reflect some sort of Android Standard, In SDE mode at least. This is coming along nicely and I should be ready to kick out a Early Beta in the Next Couple of Weeks.
I would like to gather some input on any additional options people who like to see in CWM, Basically CWM Recovery Comes with a standard set of features but they maybe options that you have found useful on Device's you have had in the past etc.
I already plan to make it possible to boot into all modes on the device, that Archos Recovery, Archos Android, SDE Android and SDE CWM Recovery.
So Yeah, Give me Ideas and I'll seen If I can accomadate them
NOTE: Obviously We are just getting started on this and alternative recoveries will come in time, TWRP for example but one thing at a time eh :good:
Okay, Here's a currently "wishlist" of feature I think would be quite useful
Archos Specific Features
Include Stock Repair and Recovery Options
Include Stock Developer Edition Options
Reboot to Stock Recovery Option as a Fail Safe.
Reboot Stock Android
Flash Archos aos update
Upgrade Existing SDE Images to new structure
An the list goes on.....
Print system Properties
Print dmesg
Resize Partitions
Manage FS Image Location ( mainly nice to have on HDD Version I suppose )
Backup to Sparse Image ( I'm sure CWM5 Nandroid did this with ext4 partitions, god knows why they changed to a default choice between tar archives or dup differential blobs, What If I just a single portable file for my data partition backup!! )
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Power Off ( Suprisingly not include by default )
Full Touch Support with on screen keyboard and command line
I think those features will do nicely but If anyone has anymore then get involved!
The nandroid backup interests me a lot... its always nice to be able to "return" to when it was working if anything breaks.
Im watching this thread with interest good luck!!
TrOjAn
Maybe an ability to mount the whole system through usb? So one could DD clone the whole memory chip to PC. That could recover some bricks.
trevd said:
Resize Partitions
Click to expand...
Click to collapse
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
trevd said:
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Click to expand...
Click to collapse
But fastboot works on the bootloader level
gen_scheisskopf said:
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
But fastboot works on the bootloader level
Click to expand...
Click to collapse
Hi There,
I think, You've got your wires crossed None of this is related to letama CWM Recovery./ If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
I well aware of how fastboot works but to supporting the fastboot protovol allows the same workflow when it come to work with the AOSP source as any over device. which is
Build Rom
Flash the Partitions with fastboot
Reboot Into Rom.
???
Profit
When you control both ends of the conversation, We are free to do as we please.
Any news ... are there any files to do some testing?
shalkam said:
Any news ... are there any files to do some testing?
Click to expand...
Click to collapse
Would you mind reading... ???
trevd said:
If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
Click to expand...
Click to collapse
Follow the link and you are there.
Regards,
scholbert
Flash splash screen?
Swiped from my Galaxy Nexus using Tapatalk 2
Basically, there are 3 types of flash method for K900
SDFUSE
OTA Recovery
MFT (Manufacturing Flash Tool)
There is a lot of question, asking about why same version of VIBEROM_V1.0_1411_ST_K900 have so many method of flashing.
There are too many information from the general thread. so I create new thread here for beginner to understand more about flashing.
From my understanding, there are only one version ROM (eg. VIBEROM_V1.0_1411_ST_K900).
But there are a few format for different flashing method.
1) SDFUSE
This format usually flash by create sdfuse folder in internal SD. Normally for update ROM
Copy files system.img.gz, boot.bin, dnx_firmware.bin, etc. (or .inb file which is the one and only one file) into sdfuse folder.
Shutdown and boot up by pressing power + volume up for couple of seconds
select SDUpdate and press power to start.
After done select power off, then power on again. (direct reboot may cause boot loop)
2) OTA Recovery
The format of rom is in ZIP. The zip is signed and there will be checksum (SHA1 and MD5) during flash. so the zip is unable to modified before flashing.
this method normally for update ROM too.
Copy update.zip file into sd card (recommended is at root of SDCard) and shutdown.
Boot up by pressing power + volume up for couple of seconds, then select recovery.
wipe data / Factory reset and wipe cache partition ( optional, which will wipe all data in sdcard)
apply update from internal storage and select update.zip
system will reboot after done.
This does not works for me to upgrade to 4.3 where I am on Qubex Vibe ROM v4.
But there are a lot of K900 user able to flash original Vibe ROM v7 and follow the above method and upgrade successfully.
Refer this http://forum.xda-developers.com/showpost.php?p=51069544&postcount=3142 or
http://forum.xda-developers.com/showpost.php?p=51128922&postcount=3199
if you are using official Vibe Rom v7. There are a easier way to flash.
copy the downloaded OTA zip file into SD Card.
Go to System upgrade, swipe left get menu, and select tools.
Touch Install specified update package and browse for OTA Zip file in sd card.
Touch install Now.
3) MFT
This method require computer with driver and software installed and USB cable for sure.
Refer this http://forum.xda-developers.com/showpost.php?p=51162040&postcount=3245
I got this method successfully when I am on non-official Vibe rom.
Please correct me if I am wrong.
Thanks to Onesjy at lenovo forum.
http://bbs.lenovo.com/forum.php?mod=viewthread&tid=154595&extra=page=1
Edited:
From my experience, the MFT method is always succeed.
Url for latest 1418_DEV MFT : http://forum.xda-developers.com/showpost.php?p=52500023&postcount=3745
MFT
i know how to use it but where can i find Manufacturing Flash Tool 6.0.2??
As far reported to me by QuBeX the ADB mode is not working on that device... I guess for the issue we have with MFT, it is the only solution we can look for also because I haven't forum (and have to open it) a thread where to speak about the recovery of a stock ROM.
About the Method N.3, most of the compatibility issues are related to the OS you are working on.
For the Settings you have to apply what you see below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
... about the libraries, instead, download that packages and replaces (if so) the files already present in the 32 / 64bit Windows' system folders: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
You can find the Applications as well the Drivers you need directly starting from that shared folder: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
imei changed to null
i tried to flash viberom using sdfuse method but after flashing imei changed to null how to retore it
help
TWRP Alpha build for MT2-L05(LianTong) TeamWin Recovery Project
Not working:
Could not handle Internal Storage properly, i.e., Wipe data will wipe internal storage as well.
Most of the text and even the config/build itself is copied from Modding.MyMind work on US version MT2L03. Thanks, Modding.MyMind
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****
Please note, due the structure of this phone storage, the Internal Storage (/storage/emulated/0 size 12GB) is actually shared with /data partition, and the mount point is /data/share, this is not same as google recommended value /data/media, and current TWRP code could not handle this properly. Also Modding.MyMind has PM'ed me that he probably will spend less and less time on XDA/development work, and I really lack of expertise/time on this one, so This build didn't resolve this issue. That's why I labeled this as ALPHA version.
Internal Storage /data/share /storage/emulated/0 size 12GB
External SDcard: /mnt/media_rw/sdcard1/ An SDCard is required to use this TWRP build and recommended 32GB or bigger.
For more information about this issue, please check TWRP article http://teamw.in/DataMedia, and please noted that it mentioned "A stock AOSP recovery would format data including the "sdcard" but TWRP will use its regular factory reset setup that leaves the internal storage intact" is not working in this TWRP alpha build., i.e., This TWRP will wipe your internal storage when you wipe data.
So, using this TWRP recovery, fact is:
. The backup target must select External Storage.
. Backup /data will include the internal storage, and this partition size will be ~12GB if uncompressed.
. Restore /data will override internal storage area.
. Wipe data (Factory Reset) will wipe internal storage as well.
Please read above carefully, and understand the risk of using this alpha build.
Recommended approach:
In your daily usage of the phone, try to save everything to external SDCard, or manually backup internal storage to external SDCard frequently.
When using TWRP, back/restore following partition is safe:
/boot
/recovery
/system
And always take caution when backup-restore /data, also, it is recommended check the compress option when do the /data backup.
Again, Many application may save files into Internal Storage including the pictures you taken, and files/songs you downloaded. So be aware of the risk of using this TWRP that may wipe the internal storage. If you are not clear/comfortable of this risk, please do not install this TWRP.
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****END****
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
Steps for Backing up Stock Recovery:
within a terminal using dd (aka Data Destroyer);
Code:
su
dd if=/dev/block/mmcblk0p18 of=/mnt/media_rw/sdcard1/stockrecovery.img
TWRP for MT2-L05
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Installation (PC):
- You MUST have an unlocked Bootloader!
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
Download:
- TWRP 2.8.0.0
File name: TWRP_MT2L05_Alpha.img
File size: 11,040,768
md5sum: b8832fc6dfd5d6e47e63ba7f7e047518
CONTRIBUTORS
@Modding.MyMind
@xordos
And thanks @4L0M for the testing that is dangerous due to the nature of twrp
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel
- Stock Kernel
- TWRP source from Omnirom
- MT2-L05 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: ALPHA
- Created 2014-10-03
- Last Updated 2014-10-29
//reserved
Great work. If anyone could help finish this project off, I am more than happy to keep testing. If we can get this recovery fully working, then I think we would be far closer to understanding how to port kitkat to the MT2-L03 devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, I do have an idea/workaround for this issue, and hopefully open this discussion thread can get more idea/evaluation going on.
The /data/share folder is treated as internal storage, but twrp is hard coded /data/media in many many places. So maybe we can rename 'share' to 'media' when boot into twrp, then rename back before reboot. But the 2nd part may not easy to guarantee. If it get into normal OS booting, it may cause confusion even damage.
So I am not like this workaround even myself.
disregard...
I think B606 breaks recovery. After I update to B606 and reinstall TWRP, it just hangs on splash screen every time I try to enter recovery.
Hi, i flashed the recovery using fastboot and then i tried to reboot into recovery but the phone just reboot after 1 try. here is my bootloader screen. Plz tell me how to root this phone. Its unlocked but i'm unable to root it.
3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat
Ok, So you got your new Super Cheapo MTK8127 quad core Tablet from BestBuy or some other overpriced electronics emporium and want to install root and a custom recovery So it won't suck nearly as bad
Feeling hungry but don't wanna feed yourself??? Open wide......Here comes the airplane requesting permission to land
The Following procedure may "BRICK" your tablet and wipe your porn....You do so at your own risk, Neither Kneee or his lawyer claim to know ANYTHING about android....or anything else for that matter
THIS GUIDE WILL WIPE YOUR PORN!!!
If you've ever seen THIS:http://forum.xda-developers.com/chef-central/android/root-dl701q-install-twrp-touch-recovery-t2980339thread, You know that "iRoot/vRoot no longer works since updating to kitkat. I've BUNGLED my way into a solution, Hope it helps you too.....
THIS GUIDE ASSUMES YOU KNOW HOW TO USE ADB AND FASTBOOT (ENABLE USB DEBUGGING)OR AT LEAST KNOW WHAT THEY ARE AND DON'T SUFFER FROM GOOGLEPHOBIA
#1 Making a backup of this crap software when ADB , FASTBOOT and SP flash tool are working correctly is pointless (IMHO) (inm
Here's Everything you should need:
Stock ROM COURTESY...THIS DUMBASS https://drive.google.com/file/d/0B9DmzLnUt5tuaUtJS1FHcjNyX1U/view?usp=sharing
ADB_&_FASTBOOT_executables, no need to install, just extract the .zip to the directory of your choice and execute openCMD.bat with a right click + run as administrator. it will open a terminal window, you can run all your ADVB & FASTBOOT commands from there:https://drive.google.com/file/d/0B9DmzLnUt5tuM29vOTNHNEZya2s/view?usp=sharing
Driver installer & MTK_SP_FLASH_TOOL for MT8127 use this to install the drivers and flash the stock rom + custom recovery.img https://drive.google.com/file/d/0B9DmzLnUt5tudVlrSEtzSE1tWHc/view?usp=sharing
UBIFS_Modified_CWM FOR FLASHING UPDATE-SuperSU-v2.46.zip COURTESY Vampirefo: https://drive.google.com/file/d/0B9DmzLnUt5tueC04RDFVX3plTVk/view?usp=sharing
UPDATE-SuperSu-v2.46.zipflash this with vampirefo's modified CWM recovery image UBIFSRecovery4SuperSu.img" https://drive.google.com/file/d/0B9DmzLnUt5tuZjlmVm1Wc2tFUTA/view?usp=sharing
TWRP Setup.exe...Used to install TWRP recovery after flashing Stock ROM + Custom recoveryCOURTESY TWRP team & Protocol 9https://drive.google.com/file/d/0B9DmzLnUt5tuTVVJS2d2RERpbVk/view?usp=sharing
STEP 1: INSTALL THE DRIVERS INSIDE THE MT8127 SP_FLASH_TOOL.zip" file you downloaded It will install the mtk usb vCOM driver we need for the mtk8127. if u have questions PM vampirefo. after that, turn your tablet upside down, FIND THE reset hole and jam the nearest tiny object in there until the screen does something different (like go black) release the reset button, hold VOLUME DOWN and plug in the USB cord and the tablet should be reconized as a preloader USB VCOM Port device under "Ports" in Device Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, the necessary driver to save this POS is at hand. after it's done installing the tablet will probably reboot and the remaining drivers will install. (EVEN WITHOUT THE OTHER DRIVER YOU CAN ROOT AND FLASH NOW)
Fire up the MT8127 SP flash tool (run as administrator) you downloaded and you should see this:
Click "Scatter-Loading" and select the scatter file located in the stock rom folder you downloaded and unzipped (you DID unzip it right?) and click the "RECOVERY" FIELD LOCATED HERE:
and select the recovery image you downloaded called "UBIFSRecovery4SuperSu.img......yay, you should be all set up and ready to go!
Make sure youve already unplugged the USB cable AND hit the reset button. HIT THE DOWNLOAD BUTTON (the program is now waiting for your device...no rush) HOLD VOLUME DOWN AND PLUG IN THE USB CABLE, the computer will detect the device, the program will proceed to shove a bunch of ones and zeros down the the tablets throat and it will reboot (hopefully to a mediatek logo).
If so, youre not as stupid as everyone says when u leave the room
Toss "UPDATE-SuperSU-2.46.zip" on a microSD, Power off the device, shove the SD in his home and hold POWER + VOLUME UP until you get prompted to select either RECOVERY OR FASTBOOT, we want recovery so make sure it's selected and press VOLUME DOWN to boot into recovery & install your SuperSU.zip and reboot
once the OS is fully running, run TWRP.exe as ADMINISTRATOR in AUTO mode, TWRP recovery should be installed and u should still have root, if not, you'll need to go into advanced, then mount system before re-installing from zip.
NOW learn ADB and fastboot so I can save my breath next time:
PS, all your GAPPS are gone....quit *****ing, I've got em here: htpa_gapps-modular-micro-4.4.2-20140608-signed.zip(pa_gapps-modular-micro-4.4.2-20140608-signed.zip 85.3MB) & HERE: https://drive.google.com/file/d/0B9DmzLnUt5tuSl9lME9VZnFJTU0/view?usp=sharing(pa_gapps-stock-4.4.2-20140608-signed.zip 267MB))
I have requested this thread be removed, you are using my stuff without permission, and even crediting yourself with the firmware, I took the time to download, you yourself have done nothing but take others work including mine without permission.