Related
HI all,
Dexter wrote a super-cool folio 100 mod including Android Market, Flashplayer and much better performance. You find it here: http://dext3r.komodin.org/folio100/FolioModv13d.zip. I think this makes the folio 100 finally useful.
When I wanted to install it, however, I had to overcome several hurdles (which had nothing to do with Dexters work). Therefore, I thought that it would be useful to post a full description of what I had to do here.
1. Download the mod from the URL above. Put the update.zip file which you find in the archive into the root of an SD-Card with at least 150-200 MB of free space.
2. Shut down you folio 100
2. Put the SD Card into your folio 100
3. Start your folio 100, when you see boot image push "Power" and "Vol +" quickly (you only have 3 seconds to do this) ==> You should now see a message explaining that are in the recovery menu!
4. Press VOL + Factory reset or system update.
5. Press VOL - to continue to system update.
6. Press VOL + to confirm system update
==> WHEN ALL GOES FINE UPDATE SHOULD NOW START AND THE DEVICE WILL AUTOMATICALLY REBOOT (it is possible that you must shutdown and restart manually after update. This is the case when the android label is shown but the device does not start for a very long time).
BUT for some of you (including me) this will fail and you will see a text on the screen like booting recovery kernel image and the tablet freezes there.
In this case, it seems that your recovery image used to run updates is broken and you must first reload a working recovery image.
Now it gets a bit hairy:
We will use Android Development Environment and load a working recovery image via USB. Here are the steps:
1. Download the Android SDK here: http://developer.android.com/sdk/index.html. For Windows users I suggest to get the zip and NOT put it in Program Directory unless you want to run all commands with administrator privileges.
2. Now we must extend the drivers section to be able to load software onto our folio tablet. Goto %android_install_dir%/usb_driver/android_winusb.inf and enter the following lines in the sections [Google.NTamd64] and [Google.NTx86] (depending on your systems architecture you could place it only in one section but why not in both?).
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
3. Last but not least you should ensure that the comand fastboot.exe located under %android_install_dir%/tools knows where it finds the AdbWinApi.dll. Test this by running the tool without option from a command line. If you get and error message add the path to AdbWinApi.dll to your PATH variabe. The path is usually: %android_install_dir%/platform-tools . The PATH variable you can enter under Control Panel->Maintenance->System->Environment Variables.
4. Now you must run your table in fastboot mode. To do so you should start your folio tablet and on the Toshiba loading screen quickly press 3 times the startbutton and then the VOL + button.
5. The tables should print a message that it is now in fastboot mode. Connect it via USB to your PC.
6. Windows will try to load a driver but it will fail to recognise it. Choose the option to manually add a driver. Ensure to manually select a file NOT search in a directory and select the aforementioned file %android_install_dir%/usb_driver/android_winusb.inf .
7. Windows will ask you what driver you want to lead. Choose Bootloader and Windows will install it.
8. In Dexters update.zip for the foliomod (mentioned above and found inside the package here: http://dext3r.komodin.org/folio100/FolioModv13d.zip) is a working recovery.img. Extract this image (file recovery.img) and best place it under %android_install_dir%/tools.
9. Now we are ready to replace the faulty recovery image. Open a command line and go to %android_install_dir%/tools. Type:
fastboot erase recovery
this will erase the old recovery image.
10. Now lets laod the working recovery image. Type
fastboot flash recovery recovery.img
this will load the recovery.img of Dexter which we placed in the %android_install_dir%/tools folder before. Note: If you do want to place the img file in this folder you must indicate the full path to it inside the command.
11. Now we are nearly done. You can unplug your tablet and restart the update procedure for the foliomod as described at the beginning of this post. This time the update should work fine.
Well, I hope this helps someone. At least in my case the update worked and I thought it might be use to sum up all information.
Best regards
Patrick
hi,
in order to rewrite the recovery image, do i need to be root ?
no, because the update.zip is signed with the same key toshiba's deployed is latest release.
enricogatti said:
hi,
in order to rewrite the recovery image, do i need to be root ?
Click to expand...
Click to collapse
Do I need the OS update for my Folio 100
Hi there,
I am a bit confused. I have installed the Super Dexter Folio 100 mod and it is great. Do I then need the OS update??
I cannot download it from Toshiba web site. After the Dexter install. the data needed like Model no. Serial no. and Part no. is blank !!
Any ideas.?
Regards,
Per.
If you have installed Foliomod 1.4 there is no need to update.
Foliomod 1.4 has the update integrated.
blank part and serial no
sorry,
but i have to enter correct model, part and serial numbers in order to send it back to Toshiba, how can we do?
Regards
Why do you need these numbers? They are not needed for custom roms.
in order to revert to original toshiba's rom to send it again for repair.
This method worked perfect for me, while I was having trouble with the other one. Thanks alot!
Thank you very much. You saved my life.
I was searching for days to fix my folio!!!
It worked excellent for me. Now everything is fine.
Downgrade
If I installed the toshiba stock rom it will be perfctly good. I mean the model number an so on..
i was to hasty when i bought my folio and i update my firmware to the latest , is there any way to downgrade ? , i tried both this way and an ADB shell command to restore my recovery image , but my recovery still dont start , after i press power button followed by VOL + it just goes black for 5 sec and then boots android with no message at all, :/ , possible to fix it ?
tried using fastboot to install update.zip but failed.
=>
C:\Program Files\Android\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
<=
I don't know why the 'thanks' button isn't active for TS. But thanks for your comprehensive guide to put another ROM on the device. The Fastboot method of replacing recovery.img worked like a charm .
Hello,
Thanks for this very clear tutorial... but...
When I try to execute the fastboot command, the prompt hangs:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot erase recovery
< waiting for device >
Click to expand...
Click to collapse
What to do?
Kind regards,
Daniel
Failed (remote: (00030003))
always this !!! I can't flash anything !!!
Hi, I tryed to reinstall, but 9th step is problem, because Commander in Windows 7 don't know this tag...
I can't connect to my touchpad by this tag
fastboot erase recovery
In others forums I found some notes about fastboot.exe, but this application is not in folder tools.
Can you some help me?
Thanks
In newer SDK versions it's in platform-tools.
so ,everything works installing it this way , but after that how do i get into recovery?
if i use "power" and "volume up" i'm getting the old recovery.
GUIDE - Restore G Tablet after a Failed Recovery Mode "update.zip"
==================================================
Table of Contents
==================================================
GUIDE CHAPTERS
A ) CAUTION!!!!!
B ) GUIDE INFORMATION
C ) THANK YOUS!!!
D ) VALUABLE INFORMATION
E ) ALTERNATIVE SOLUTIONS
F ) BACKGROUND
G ) PROBLEM DESCRIPTION
H ) FAILED ATTEMPTS
I ) KEY TERMS & NOTES
J ) SYSTEM AND UTILITIES USED
K ) SOLUTION STEPS
L ) FINAL THOUGHTSAPPENDIX CHAPTERS
M ) APX MODE AND NVFLASH TIPS
N ) WINDOWS USER NOTES==================================================
A ) CAUTION!!!!!
==================================================
The steps presented in this guide are aggressive. You do not need a microSD card in the G Tablet, so it should be removed before beginning to prevent an unintended impact. Also, one of the steps involves partitioning the internal SDcard memory, all the data stored there will be wiped.
==================================================
B ) GUIDE INFORMATION
==================================================
This guide is divided into chapters which were outlined above in the Table of Contents. The chapters are broken down into one or more sections and/or steps. I believe reading through the entire guide at least once to develop understanding is the first step to potentially restoring your G Tablet. However, if you are already familiar with the various tools and methods used below you are welcome to jump right into the "K ) SOLUTION STEPS" chapter.
My objective in this guide was to provide all the steps I used to successfully restore the G Tablet. There are probably unnecessary steps in these instructions. You are more than welcome to skip any steps you deem unnecessary.
As you read through the guide you will notice that three main "tools" are used in various steps. The tools used are nvflash, ADB, and Recovery (both Stock and ClockWorkMod ). nvflash is the only tool you need to get started assuming you can put the G Tablet into APX mode (instructions on entering APX mode are in this guide).
Note that there are alternatives to accomplish the tasks where I used ADB. If you know or find another way to accomplish the "ADB" tasks, go ahead and substitute with the other method. Again, my objective was to detail the exact steps I used and ADB was one of my tools.
Although I cannot assume this guide will work for anyone else, if you happen to be in the same position as I was, then hopefully it will work for you too. Even if you are not successful, you might take away a piece that eventually leads to your solution. That is what happened for me by carefully following the recovery steps others so graciously posted. Of course there is a risk that matters could become worse.
If for some reason my links fail or are removed, you should be able to find the needed files and information with some forum and/or google searching.
==================================================
C ) THANK YOUS!!!
==================================================
Big Thank Yous to all the hard working developers who made the apks, scripts, and roms I used to restore my tablet. And just as important, the documentation they make readily available.
Special thanks and acknowledgement; roebeet, bekit, goodintentions, rr5658, Mp4, and Titanium Track's.
And thank you to the people who moderate and make sites like slatedroid.com and xda-developers.com possible. They are both invaluable sites to me.
==================================================
D ) VALUABLE INFORMATION
==================================================
Viewsonic GTablet for Dummies - Extremely helpful site. I learned the most from this site (belongs to member goodintentions) and roebeet's postings.
Viewsonic G-Tablet Disaster Recovery - Read up. Especially the topics posted by roebeet.
==================================================
E ) ALTERNATIVE SOLUTIONS
==================================================
The solution that worked for me is not the only working solution available. In fact, depending on your situation, one of the alternatives may be a better solution for you. Thank you to all who have posted solutions that worked! I read a lot of posts and all of the information contributed to what finally worked for me. The purpose of this post is just to add another series of steps and give decent detail, hoping that they help someone else. Here are a few other solutions you should review to see if they would be better for your situation:
Review the "Code" levels on this site. Viewsonic GTablet For Dummies
See post by K J Rad. A much more streamlined process and no ADB required. Tablet will not turn on - Post #114
See post by boogiebear575. A variation of K J Rad's process. modifcation of K J Rad's recover worked!
See post by burbley. Only requires use of nvflash. NO Birds NO recovery - Post #20
==================================================
F ) BACKGROUND
==================================================
A day after receiving the Viewsonic G Tablet from Woot, I was ready to get a custom ROM flashed on it. Even before placing the order I had a ROM chosen, CyanogenMod's 7.0.3-Harmony with Google Apps version 20110613.
I need to state something upfront. I like CyanogenMod's ROMs and greatly appreciate all they do in the android community. It was my favorite ROM on my Droid Incredible (no longer my primary device) and the ROM is working well on a friend's Viewsonic G Tablet (that tablet was ordered from a different retailer and a month or so before mine). I do NOT / will NOT blame any developer/themer/modder when something I chose to flash messes up the device. My choice, my risk, my consequence.
I followed CyanogenMod's “Viewsonic G Tablet: Full Update Guide” exactly:
installed ClockworkMod_Gtab_v08.zip (renamed to update.zip) with Stock Recovery
installed CyanogenMod and Google Apps zip files with ClockworkMod Recovery
I wasn't going to use ROM Manager for the install even though it was an option presented. I have done a lot of ROM flashing on my Droid Incredible and now Thunderbolt and have learned I get the best results when flashing from Recovery.
One step I did not do was backup. I should have used ClockworkMod and/or nvflash (didn't know about nvflash yet) to do a backup, but figured since I had made no changes out of the box, why bother? Had I done a backup, I might have saved hours upon hours of trouble shooting. Live, fail, and learn.
Note: This guide does not cover nvflash backup, but I included a couple of links in the "M ) APX MODE AND NVFLASH TIPS" chapter.
Once the installs finished on ClockworkMod, I wiped cache, factory reset/user data delete, and then selected system reboot. I soon realized I had a problem.
==================================================
G ) PROBLEM DESCRIPTION
==================================================
No matter what I did, I could not get the tablet to boot. No combination of pressing and holding keys would boot the tablet into any mode. All I could get was blank screen. (Note: Early on in this process I knew nothing about APX Mode.)
Unfortunately, I did not check the original stock bootloader version. I assume it was 1.1, but I really don't know. I read a few forum disaster postings that seemed to be from flashing Woot purchased G Tablets.
I think I had APX Mode available the whole time. I was well into the process of trying to restore the tablet before I started to understand APX Mode. At one point I did try a “shorting the circuit” solution, so it is possible that I had lost APX Mode too and got it back after the “shorting”. Although I am pretty confident I had APX Mode available the whole time.
==================================================
H ) FAILED ATTEMPTS
==================================================
I spent many hours trying different solutions posted on various forums. Although no one solution fixed my tablet, I believe working through them resulted in the steps that led to a working solution for me.
Brief descriptions of solutions tried (I even combined some in different patterns to find what would work):
nvflashing back and forth between 1.1 and 1.2 based ROMs (stock and custom)
nvflashing froyo, gingerbread, and honeycomb ROMs (some stock, mostly custom)
“shorting” the internal connections
fully draining the battery
As it turned out the more aggressive attempts by “shorting” internal connections and draining the battery were probably not really needed in my case. These appear to be techniques for getting APX Mode back. I don't think I ever lost APX Mode.
I spent at least 30 hours before finding the right combination of steps that restored the tablet. It all came together the morning of July 4, 2011 (Happy Birthday U.S.A.)
==================================================
I ) TERMS & DEFINITIONS
==================================================
APX Mode - Hold down “Volume minus” key and press “Power” key for a couple seconds.
APX Mode check - APX Mode and the USB connection with the computer can be checked by typing lsusb in a Linux terminal window. The “Bus Device” will include a line containing “ID 0955:7820 NVidia Corp.” if the tablet is in APX Mode.
Recovery Boot - Hold down “Volume plus” key and then press and hold “Power” key until Recovery is booted (does not matter whether Stock or ClockworkMod recovery is installed).
Volume Keys - I was messed up by the volume key plus and minus placement at first (I am new to tablets). When holding the tablet as portrait with the navigation buttons (Home, Menu, Back, and Search) at the bottom, the Volume minus key is closest to the top and the Volume plus key is farthest from the top.
SDCARD - I used the tablet's internal SDCARD for the entire process. No microSD card was in the tablet's slot.
Hash - I strongly recommend checking a downloaded file's hash when the checksum is provided. If not provided, then at least check to see if the downloaded file is the same size as the one posted.
Terminal Commands - Terminal commands (including adb shell commands) are bold-green for clarity. Example: ./nvflash_complete.sh
File Paths/Names - File paths and names are bold-blue for clarity when they are not part of a command. When file paths/names are part of a command they will be bold-green.
Linux User - It is assumed work is performed as a normal user with sudo privileges and from the user's /home/user/ file location.
Shell Scripts - Note the . (dot) and / (forward slash) in front of the script commands (the ones that have the extension .sh). The dots are sometimes hard to see.
USB Debugging - Whenever you are successful in reaching a full boot into the tablet's OS, one of your first tasks is to go into Settings-|Applications-|Development and make sure USB debugging is on.
nvflash - instructions below cover downloading and what to do with the program and shell scripts.
adb – Android Debug Bridge (adb) will be used below. It is assumed adb is already set up on your computer. For reference - I used the instructions at this link to setup the Android SDK without eclipse on my Linux Mint Debian computer - Linux Mint Forums • View topic - How To: Android SDK/ADB setup for lmde *Updated 1/29/11*
Methods - If you haven't already, read up and learn about APX Mode and Recovery Mode. They are different and the steps below use one or the other for flashing/installing.
READ - Read this entire post and read the referenced, linked information before you start executing the steps.
==================================================
J ) SYSTEM AND UTILITIES USED
==================================================
Computer -
OS – Linux Mint Debian (32 bit)
Desktop Environment - Gnome
Gedit – used for editing shell scripts
Archive Manager – used for extracting
Terminator – terminal program that allows multiple running sessions within the same window pane.
Nautilus 2.30.1 – file browser, used for moving files around, selecting scripts for editing, checking file permissions, and setting up directories
nvflash
adb
Viewsonic G Tablet -
Purchased from Woot on June 28, 2011
Model - UPC300-2.2
Note to windows users - The steps in this guide are not exclusive to any particular OS. The appendix at the very bottom lists the different downloads needed and other differences when using a windows computer.(continued in next post)
GUIDE - Restore G Tablet after a Failed Recovery Mode "update.zip"
(continued from previous post)
==================================================
K ) SOLUTION STEPS
==================================================
----------------------------------------------------------------------
01 ) FILES NEEDED & LINKS
----------------------------------------------------------------------
These are not direct download links, but rather links to the pages where the download links can be found. The information on these pages is worth understanding as well. List format meaning key - type of files - file description/reference - file name/link.
NVFLASH application & script - roebeet's link to bekit's dropbox files - [RECOVERY] nvflash FULL restore, using either 1.1 or 1.2 based images - [G-TABLET]
NVFLASH bootloader.bin - roebeet's link to bekit's dropbox files - bootloader.bin
NVFLASH image files - rr5678's xda developers post on Utility G Tablet - FORMAT.zip
NVFLASH imgage files - Viewsonic Gtablet For Dummies NVFlash to Stock with CWM pre-installed - gtab.nvflash.1.2.branch.20110508 with cwmv3028.zip
NVFLASH image files - roebeet's Slatedroid forum posted stock NVFlash branch 1.2 files - gtab.nvflash.1.2.branch.20110617.zip
RECOVERY update.zip & command files - roebeet's Slatedroid forum posted Mountain Laurel 1.1.0 files - gtab.Mountain.Laurel.1.1.0.rar
RECOVERY update.zip & command files - roebeet's Slatedroid forum posted Mountain Laurel 1.1.1 files - gtab.Mountain.Laurel.1.1.1.suppl.rar
APK file - Mp4's Slatedroid posted file - 4root.1.3.0.apk
APK file - Titanium Track's - TitaniumBackup_latest.apk
If you need the Android Debug Bridge (adb), then install Google's Android SDK. ADB is a tool within the Android SDK package.
Android SDK download page - Download the Android SDK
Android SDK Install information - Installing the SDK
Additional help with installing the SDK and adb can be found by googling something like "how to install android sdk" or "how to install adb".
----------------------------------------------------------------------
02 ) SET UP
----------------------------------------------------------------------
This is an important part of the process. Setting up the folder structure and placing the tools used within the structure made execution easier for me. Here are a couple of reasons why:
The nvflash shell script files expect the program and bin file to be in the same folder. The same would be true if using windows and the nvflash batch file.
Some of the files used in this process have the same or very similar names. Organizing before execution helped me keep track of where I was in the process and what needed to be done next.
a ) Folders
Create the following folders and sub-folders in your Linux working directory (assumed to be /home/user/):
/gtab/nvflash/format/
/gtab/nvflash/vgdum/
/gtab/nvflash/off12fw/
/gtab/adb/off12fw/
/gtab/adb/ml110/recovery/
/gtab/adb/ml111/recovery/
b ) nvflash - program, bin, and shell scripts
Extract nvflash_linux_2010110500.tar.gz
Create 2 new versions of the nvflash_gtablet.sh shell script.
Open nvflash_gtablet.sh for editing.
File Save As nvflash_complete.sh (do NOT close after save as)
Change the following line:
From
Code:
sudo ./nvflash --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
To
Code:
sudo ./nvflash --bl bootloader.bin --download 9 part9.img --go
Alternative I learned from burbley's post. To
Code:
sudo ./nvflash -–bl bootloader.bin --sync --go
Note - The dashes in the script lines above are two dashes with no space between. If you try to copy & paste, be sure to double check the syntax.
File Save As nvflash_boot.sh (ok to close now)
Place copies of nvflash, bootloader.bin,nvflash_boot.sh, and/or nvflash_complete.sh in the following file directories as indicated (made execution easier for me):
Folder = /gtab/nvflash/format/ - Files = nvflash, bootloader.bin, nvflash_boot.sh,nvflash_complete.sh
Folder = /gtab/nvflash/vgdum/ - Files = nvflash, bootloader.bin, nvflash_boot.sh, nvflash_complete.sh
Folder = /gtab/nvflash/off12fw/ - Files = nvflash, bootloader.bin, nvflash_boot.sh, nvflash_complete.sh
Folder = /gtab/adb/ml110/ - Files = nvflash, bootloader.bin, nvflash_boot.sh
Folder = /gtab/adb/ml111/ - Files = nvflash, bootloader.bin, nvflash_boot.sh
c ) File movement and extraction
gtab.nvflash.1.2.branch.20110508 with cwmv3028.zip
Move to /gtab/nvflash/vgdum/, extract contents.
Move contents of extracted folder /gtab.nvflash.1.2.branch.20110508 with cwm up to /gtab/nvflash/vgdum/.
Delete the /gtab.nvflash.1.2.branch.20110508 with cwm/, folder (it should be empty now).
FORMAT.zip
Move to /gtab/nvflash/format/, extract contents.
Move contents of extracted folder /FORMAT/ up to /gtab/nvflash/format/.
Delete the /FORMAT/ folder (empty).
gtab.nvflash.1.2.branch.20110617.zip
Move to /gtab/nvflash/off12fw/, extract contents.
Move contents of extracted folder /nvflash1.2/ up to /gtab/nvflash/off12fw/.
Delete the /nvflash1.2/ folder (empty).
gtab.Mountain.Laurel.1.1.0.rar
Move to /gtab/adb/ml110/, extract contents.
You should now have - /gtab/adb/ml110/update.zip and /gtab/adb/ml110/recovery/command.
gtab.Mountain.Laurel.1.1.1.suppl.rar
Move to /gtab/adb/ml111/, extract contents.
You should now have - /gtab/adb/ml111/update.zip and /gtab/adb/ml111/recovery/command
z4root.1.3.0.apk
Move to /gtab/adb/off12fw/.
TitaniumBackup_latest.apk
Move to /gtab/adb/ml111/.
----------------------------------------------------------------------
03 ) CHECKLIST
----------------------------------------------------------------------
Double check the folders and files established in “SETUP”.
Use the terminal for running nvflash and adb (I had two terminal windows open at the same time; one for nvflash commands and the other for adb commands).
Check the permissions on all nvflash (5 copies in 5 different folders), nvflash_boot.sh (5 copies in 5 different folders), and nvflash_complete.sh (3 copies in 3 different folders) files using your file browser:
right-click, select "Properties",
left-click "Permissions" tab,
make sure the check box for "Allow executing file as a program" is checked,
left-click "Close".
----------------------------------------------------------------------
04 ) EXECUTION
----------------------------------------------------------------------
a ) Terminal command line
All commands are run in a terminal session window. Open two terminal session windows, keep both visible if possible.
“nvflash terminal” - In one terminal Navigate to /gtab/nvflash/.
From here on I will refer to this as the “nvflash terminal”.
“adb terminal” - In the other terminal Navigate to /gtab/adb/.
From here on I will refer to this as the “adb terminal”.
b ) Flash FORMAT.zip utility
“nvflash terminal” - Navigate to /gtab/nvflash/format/, put tablet in APX mode.
“nvflash terminal” - Type ./nvflash_complete.sh; Press enter (do NOT hold any volume keys)
Once the script completes, the tablet should display the “Magic Value Mismatch” error, which is ok.
Press the power button to turn the tablet off.
c ) Flash gtab.nvflash.1.2.branch.20110508 with cwmv3028 rom
“nvflash terminal” - Navigate to /gtab/nvflash/vgdum/, put tablet in APX mode.
“nvflash terminal” - Type ./nvflash_complete.sh; Press enter (do NOT hold any volume keys)
Note - The tablet should boot all the way into the gtab.nvflash.1.2.branch.20110508 with cwmv3028 rom. If for some reason is does not, make sure the tablet is off and skip down to step "e )" below.
d ) Tasks in gtab.nvflash.1.2.branch.20110508 with cwmv3028 rom
Nothing really, just go to the home screen, press the power button, and select power off.
e ) Boot gtab.nvflash.1.2.branch.20110508 with cwmv3028 rom
“nvflash terminal” - Navigate to /gtab/nvflash/vgdum/, put tablet in APX mode.
“nvflash terminal” - Type ./nvflash_boot.sh, BEFORE pressing enter, hold down the Volume plus key on the tablet. Keep holding until the tablet has booted into Stock Recovery, press enter
If all went well you should now be in ClockworkMod recovery.
ClockworkMod tasks -
wipe cache partition,
wipe data/factory reset,
partition SDCARD 2048 and 0,
reboot system
Comment - You are now back where you started, a blank screen. No worries, not done yet.
f ) Flash FORMAT utility (yes we are going to do this again)
“nvflash terminal” - Navigate to /gtab/nvflash/format/, put tablet in APX mode.
“nvflash terminal” - Type ./nvflash_complete.sh, press enter (do NOT hold any Volume keys)
Once the script completes, the tablet will display the “Magic Value Mismatch” error again.
Press the power button to turn the tablet off.
g ) Flash gtab.nvflash.1.2.branch.20110617
“nvflash terminal” - Navigate to /gtab/nvflash/off12fw/, put tablet in APX mode
“nvflash terminal” - Type ./nvflash_complete.sh, press enter (do NOT hold any Volume keys)
The tablet should now boot all the way into the stock gtab.nvflash.1.2.branch.20110617 rom.
Before powering down, there are a few tasks to do in the gtab.nvflash.1.2.branch.20110617 rom:
tablet - Turn on “USB Debugging” in settings, applications
computer - Navigate to “adb terminal” to /gtab/adb/off12fw/; Type adb install z4root.1.3.0.apk, press enter
tablet - launch the z4root app and select Temporary. When done, return to home screen.
tablet - launch esFileExplorer and navigate to SDCARD/
computer - go to your “adb terminal”, you should still be in the /gtab/adb/off12fw/ directory. Type adb shell and press enter;
Note -To verify you are in the adb shell, Type ls. If the result is a tablet directory and file listing, then you are in.
computer -Type su and press enter.
Look at the tablet, “Superuser” should be prompting you for permission. Make sure the “always allow” box is checked and press "ok". The adb shell session should now display the # (pound sign) prompt instead of the $ (dollar sign) prompt.
computer -Within the adb shell as superuser complete the following:
cd sdcard and press enter
mkdir recovery and press enter
exit and press enter (backs out of superuser)
exit and press enter (exits adb shell).
computer -Now do the following in the “adb terminal”
Navigate to /gtab/adb/m110/
Type adb push update.zip /sdcard/update.zip and press enter (wait until it finishes, big file – takes time)
Type cd recovery and press enter
Type adb push command /sdcard/recovery/command and press enter
tablet - using esFileExplorer, confirm that the "pushed" files are in the right location; /sdcard/update.zip and /sdcard/recovery/command
computer - execute the following commands:
Type adb shell and press enter
Type su and press enter
Type reboot recovery, HOLD the Volume plus key on the tablet and press enter
You are now back to the blank screen. Still ok, more to do. If by chance you actually landed on the Stock Recovery screen, then skip down to step "h ) 3." below.
h ) Boot gtab.nvflash.1.2.branch.20110617 Stock Recovery
“nvflash terminal” - Navigate to /gtab/nvflash/off12fw/, put tablet in APX mode
“nvflash terminal” - Type ./nvflash_boot.sh (note - we are using the “boot” shell script this time), BEFORE pressing enter, hold down the Volume plus key on the tablet. Keep holding until the tablet has booted into Stock Recovery. Press enter
You should now be in Stock Recovery and it should have immediately started applying the update.zip file from gtab.Mountain.Laurel.1.1.0.rar you pushed earlier with adb. Once the update completes, you will still be in Stock Recovery.
Do the following in Stock Recovery:
wipe cache partition
wipe data/factory reset
select "reboot system" (do NOT hold any volume keys).
Comment - I think this boot was the first time I saw the three birds since messing the tablet up! However, I still had more to do before testing a power button boot.
The tablet should now boot into roebeet's Mountain Laurel 1.1.0 rom (good signs to note - “3 birds”, “Mountain Laurel” splash, “Honeycomb” animation. Be patient, booting a new rom can take some time.)
i ) Tasks to complete in booted Mountain Laurel 1.1.0 rom
tablet - make sure USB Debugging is on.
tablet - launch esFileExplorer and navigate to the internal SDCARD.
Complete the following:
delete the existing update.zip file;
Navigate into the /SDCARD/recovery folder;
delete the existing command file
computer - select your “adb terminal” and do the following:
Navigate to /gtab/adb/m111/;
Type adb push update.zip /sdcard/update.zip and press enter (wait until it finishes, big file – takes time);
Type cd recovery and press enter;
Type adb push command /sdcard/recovery/command and press enter
tablet - using esFileExplorer, confirm that the "pushed" files are in the right location; /sdcard/update.zip and /sdcard/recovery/command
computer - execute the following commands:
Type adb shell and press enter
Note - Since this rom already has root, you should be superuser upon entering the shell (should see the # prompt). If not ($ prompt instead), then type su and press enter. Confirm with tablet's superuser permissions request if prompted.
computer - Type reboot recovery, HOLD the Volume plus key on the tablet until the tablet boots into recovery, press enter.
Comment -If successful, you are now back to Stock Recovery and this is the first time you haven't been stuck in APX mode. However, we are still not done.
You should now be in Stock Recovery and it should have immediately started applying the update.zip file from gtab.Mountain.Laurel.1.1.1.suppl.rar you pushed earlier with adb. Once the update completes, you will still be in Stock Recovery.
Do the following in Stock Recovery:
wipe cache partition
wipe data/factory reset
select "reboot system" (do NOT hold any volume keys)
Tablet should now boot into the Mountain Laurel 1.1.1 rom. Again, no halt in APX mode. Still not done, we need to do some cleanup.
j ) Tasks to complete in booted Mountain Laurel 1.1.1 rom
tablet - make sure USB Debugging is on.
tablet - launch esFileExplorer and navigate to the internal SDCARD.
Complete the following:
delete the existing update.zip file;
Navigate into the /SDCARD/recovery folder;
delete the existing command file
Note - Some apps were not showing up in Google's Android Market, so I followed roebeet's "Market fix" instructions that are documented in the Mountain Laurel rom posting.
Since we already have adb up and running, let's use it to push the TitaniumBackup_latest.apk.
computer - “adb terminal” - Navigate to /gtab/adb/ml111/; Type adb push TitaniumBackup_latest.apk /sdcard/Download/TitaniumBackup_latest.apk and press enter
Note - I just "pushed" the apk to the tablet's /sdcard/Download/ folder instead of installing it like we did with the z4root.1.3.0.apk previously. I then used esFileExplorer on the tablet to navigate to the folder, then pressed the TitaniumBackup_latest.apk, and selected install.
Follow roebeet's Mountain Laurel instructions for the rest of the fix.
----------------------------------------------------------------------
05 ) TESTING
----------------------------------------------------------------------
Power off your tablet.
Wait a couple minutes to be sure it is off.
Press the power button to turn the tablet on (do NOT hold any Volume keys unless you intend on entering APX Mode or Recovery)
Tablet should boot into Mountain Laurel 1.1.1 rom
----------------------------------------------------------------------
06 ) DONE!
----------------------------------------------------------------------
======================================================================
L ) FINAL THOUGHTS
======================================================================
I have only applied this solution once to one tablet. I do not plan on recreating the APX Mode problem to run through this again. Why? Our household only has one G Tablet and it has since been given to my wife as a birthday present.
I do not know exactly why this sequence worked for me when nothing else I tried did. I leave it to the wonderful expert developers who created the tools and documentation I used to figure out the whys (if they so desire).
Why Mountain Laurel? Because it was coming from a respected and well published developer and it was based on 1.2 branch. It worked in my restore attempt, so it needed to be in my steps. You can try a different custom rom if you want, but I would recommend against anything Honeycomb (only until your tablet is restored). After restoration, I followed roebeet's Brilliant Corners rom instructions and successfully flashed Brilliant Corners over Mountain Laurel with no issues. I have also successfully followed roebeet's instructions in the Brilliant Corners rom post to switch back and forth between Stock and ClockWorkMod Recovery with no issues.
I truly hope these instructions help someone else restore their Viewsonic G Tablet. Good Luck!
djab67
(appendix in next post)
GUIDE - Restore G Tablet after a Failed Recovery Mode "update.zip"
(continued from previous post)
APPENDIX
==================================================
M ) APX MODE AND NVFLASH TIPS
==================================================
Understanding APX Mode and how to use NVFLASH when in APX Mode was the most confusing piece for me to learn. It seems that others also struggle with the relationship between the two and how they are used.
APX Mode is a low level “on” state for devices with the tegra chips. I equate it to the “Bootloader” level on my HTC android phones. That comparison may not be entirely accurate because it seems APX Mode is at an even lower level than a Bootloader. The important point is both exist before any Recovery Mode (for example; Stock Recovery or ClockWorkmod Recovery).
NVFLASH is a program used to “flash” partitions (one or more) from a computer to the G Tablet when the gtablet is in APX Mode. NVFLASH can be used to flash just one or multiple partition images. NVFLASH should be run from a terminal session (command prompt in windows) since it needs various expressions and/or options defined when it is executed. The NVFLASH program can also be called from a script file (filename.sh) in Linux or a batch file (filename.bat) in windows. In the steps presented above, NVFLASH is run through script files.
----------------------------------------------------------------------
01 ) APX MODE TIPS
----------------------------------------------------------------------
Understanding APX Mode and how to use NVFLASH when in APX Mode was the most confusing piece for me to learn. It seems that others also struggle with the relationship between the two and how they are used.
To place the G Tablet in APX Mode I held down volume minus key and then pressed the power button for a second or two before releasing both. I did this with the G Tablet connected to my laptop via usb (mini usb port on the tablet and standard usb port on the laptop).
Validating a connection in APX Mode involved opening a terminal session (on the laptop) and typing the command lsusb. If the resulting output included a line containing “ID 0955:7820 NVidia Corp.”, then I knew I was connected to APX Mode with the laptop.
The G Tablet never gave me an indication that I was in APX Mode other than maybe a brief flash of light. Mostly I was staring at a blank screen and did not see any splash images. That is why I would validate the connection with the lsusb command.
Sometimes it would take a couple of attempts for me to get into APX Mode and establish a connection.. To set up a second attempt I would press the power button and then hold the volume minus and press power again. After each attempt I would check connection with lsusb.
IMPORTANT - An APX Mode connection is all that is needed to start the G Tablet restore steps. Recovery Mode (Stock or ClockWorkmod) and ADB are not needed to start. If the early APX Mode steps are successful then you will have access to those tools later on. When I messed up my G Tablet, the only thing I had to work with in the beginning was APX Mode and early on I didn't even know I had that. From my perspective all I had was a blank screen.
If APX Mode and connection to your PC cannot be obtained the first thing to do is check your drivers assuming your OS is windows. I never had a driver issue running Linux Mint Debian. You can find windows driver information at this site -Viewsonic GTablet For Dummies - nvflash.
If you think the drivers are ok and you still can't put the G Tablet in APX Mode, then you next step would be to research some “hard reset” options like “battery draining” and/or “unplugging the battery and shorting connections”. I am not addressing these methods in this post, but you can find techniques and information on this site and others with a little searching.
----------------------------------------------------------------------
02 ) NVFLASH TIPS
----------------------------------------------------------------------
NVFLASH is used when a G Tablet is in APX Mode. Do not use just any ROM download when using NVFLASH! It is important to make sure the ROM being used was set up for NVFLASH. When you extract a NVFLASH ROM download you will see the multiple files with the .img extension.
A “regular” ROM image usually just contains an “update.zip” file along with a “recovery” folder. Within the “recovery” folder there is usually a “command” file. A “regular” ROM image is applied using Recovery Mode, NOT nvflash. Again, make sure you are matching the downloads with the right application tools.
If you want to start learning about backing up with nvflash, here are a couple links to get your started:
[STICKY][GUIDE] Backup of your BCT AND Partition with NVFLASH on the gtab
Automated NVFlash backup for Linux
======================================================================
N ) WINDOWS USER NOTES
======================================================================
The major steps and sub-steps in this guide can also be executed from a windows computer. Here are the minor differences when using windows:
Download and use the contents of nvflash_windows_2010110500.zip instead of nvflash_linux_2010110500.tar.gz from [RECOVERY] nvflash FULL restore, using either 1.1 or 1.2 based images - [G-TABLET]. This is the same link provided earlier. Note that roebeet's post covers windows setup.
windows users will be using batch commands instead of shell scripts.
In one step above a script is edited. windows users will edit the batch (extension .bat) file instead. Be sure to use the right syntax for batch files, it is not the same as the script syntax illustrated in this guide. The downloaded batch file could be used as an example.
use the windows "command" window (aka; dos prompt, c:\> prompt) where ever a reference to "terminal" is made above.
some windows users report usb driver issues when trying to connect to a tablet in APX mode. Here is a place to begin searching for a solution if you have driver issues - Viewsonic GTablet For Dummies - nvflash
Here is a guide that may help windows users set up ADB - [STICKY][GUIDE] adb for your gtab (windows)
[GUIDE] Restoring from "APX mode only access" after a failed ROM update or flash
.....reserved in case more content is needed in the future
[GUIDE] Restoring from "APX mode only access" after a failed ROM update or flash
.....reserved in case more content is needed in the future
.....reserved in case more content is needed in the future
Hi,
I wish to help out too by giving the steps in which how i recover my gtab.
Background:
I flashed woot gtablet using clockwork mod recovery 0.8 and i realised i'm on 1.2.
Ultimately, i'm stucked with the 3birds splash screen with the top left hand reading loading recovery kernel image. Knowing that i'm in a bootloop, i used NVflash on it.
Thankfully, my gtab recovered, however, i realised once i switch off my gtab, i can't switch it on by pressing the power button.
My steps (may not be applicable to everyone)
My steps are purely discovered by chance. It really simple, just flash using NVflash.
This NVflash consists of:
1. 1.2 Branch (4349) preloaded with CMW
2. alternate nvflash for gtablet zip file from part 3
Taken from (http:__//__viewsonic-gtablet-for-dummies.webs. __com/nvflash.__htm) please remove the _, many thanks to this brilliant website!
Combine the 2 folders together into 1 NVflash folder and doing the same procedures as NVflash-ing.
PS: I have no idea why it works for me and perhaps use this mod if you're in desperate and panicking state
After restoring with this NVflash, my gtab is back to 1.1. However, i went ahead and flashed cyanogenmod7.03. Now my gtab is working way above my expectation!
If you need any clarification, please don't hesitate to ask.
Thank you for all the work that went into getting this together! I was about half way through the "Working it Out" process when I found your thread.
I had "jumped and the bridge wasn't there".
And, EVERYTHING in your guide was spot-on. I actually converted the guide into a "checklist" of sorts. Then went about creating the file & directory hierarchy. Now, I've got the entire thing on a flash drive. So, if (when) I screw it up again it'll be like a "get out of jail free" card.
The whole process, once the files were in their happy places, took less than an hour (with a few interruptions).
Again, sincerely - Thank you!
VinMee said:
Hi,
I wish to help out too by giving the steps in which how i recover my gtab.
Background:
I flashed woot gtablet using clockwork mod recovery 0.8 and i realised i'm on 1.2.
Ultimately, i'm stucked with the 3birds splash screen with the top left hand reading loading recovery kernel image. Knowing that i'm in a bootloop, i used NVflash on it.
Thankfully, my gtab recovered, however, i realised once i switch off my gtab, i can't switch it on by pressing the power button.
My steps (may not be applicable to everyone)
My steps are purely discovered by chance. It really simple, just flash using NVflash.
This NVflash consists of:
1. 1.2 Branch (4349) preloaded with CMW
2. alternate nvflash for gtablet zip file from part 3
Taken from (http:__//__viewsonic-gtablet-for-dummies.webs. __com/nvflash.__htm) please remove the _, many thanks to this brilliant website!
Combine the 2 folders together into 1 NVflash folder and doing the same procedures as NVflash-ing.
PS: I have no idea why it works for me and perhaps use this mod if you're in desperate and panicking state
After restoring with this NVflash, my gtab is back to 1.1. However, i went ahead and flashed cyanogenmod7.03. Now my gtab is working way above my expectation!
If you need any clarification, please don't hesitate to ask.
Click to expand...
Click to collapse
I did not quite understand what you said. If your Gtab was a 1.2 then when you flashed it back then it went back to a 1.2. You stated that after you flashed it, that it was restored back to a 1.1 version. That's impossible. I think you mistyped..
Dear Devs, the link to "nvflash_windows_20100500.zip" is not available. It is not opening. Can anyone please provide a link to download this file
Hi,
My mobile name is "Walton Primo-GF4" it's Android version Lollipop 5.1 and Chipset "MTK6580" I want to ROOT my phone!! I also tried many kind of ROOT Apps.. Like: Framroot, Kingroot, iRoot, Baidu Root, A-Key Rootmaster etc but all apps didn't worked!!
NOTE: MY PHONE ALSO UNLOCKED BOOTLOADER
My Acer tablet runs Android version Lollipop 5.1 with CPU MTK8151. I also tried many kind of root Apps including Framroot, Kingroot, and Kingo Android Root but none of the apps worked. I would welcome any suggestions.
How to install and recowery TWRP ROOT - as I do.
On the drain insertion rekaveri I did not run after the entry androyd lying belly to the top with an exclamation mark.
1) Put Flash Tool 5
1.1) Put the USB driver on the PC (It is advisable to disable the driver signature verification in windows- google to help)
2) Download Recovery - TWRP
3) Fail scatter
------ = 2.3 points lozhish files in a separate folder ---
4) I can not remember without root works or not, but just in case I will write. If you need a backup of your phone (need Flash card gigs 4-8) is placed on the phone titanium backup - you come - Click on the second tab (backups) from the top of the icon sheet daw - choose "Make RK entire user software." move to backup to a different folder, and once again do but to "make all RK custom software and system data" - this just in case.
5) Turn off the phone
6) includes a program Flash Tool
7) specifies the path to the file scatter
8) Should Fail recovery stand daw
9) Put Download only
10) Press Download
11) Connect the power cord to the body.
After excluding telephone (ALWAYS !!!!) Press VOL +, and ON. together, should see boot menu, select the button and press the + recovery - to go to TWRP
In the TWRP - press "backup" in the next window, you put all the jackdaws and snap your top do not remember exactly where, but there you can select the external sd card to record backup. and backup for 10 more minutes.
All of us do not care at all, you can do what you want =))
Then do in TWRP reboot in normal mode (need WI-FI), should appear with an offer to make a root or not to do - disagree. body boot turn on the 'Net WI-FI and start downloading the patch for the root, then as a patch will be downloaded will choose the menu that appears after installation TWRP, body restarts itself do everything.
ALL! Ruth received.
use CF-auto-Root
Hey, guys New kingroot app version is worked mt6580.. now my Walton-GF4 is ROOTED, Thanks Everyone!!
can you give me link new version kingroot . i have kingroot 4.9.0 its not work my mt6580 Android 5.1
magik235 said:
My Acer tablet runs Android version Lollipop 5.1 with CPU MTK8151. I also tried many kind of root Apps including Framroot, Kingroot, and Kingo Android Root but none of the apps worked. I would welcome any suggestions.
Click to expand...
Click to collapse
Try downloading latest MTK droid tool and see if it detects your phone. If it detects, then you could just root by clicking root button. If you do not know how to use MTK droid tool, just search for the instruction on XDA. Pretty easy.
twrp-custom-recovery-for-wiko-sunny
tlysovych said:
How to install and recowery TWRP ROOT - as I do.
On the drain insertion rekaveri I did not run after the entry androyd lying belly to the top with an exclamation mark.
1) Put Flash Tool 5
1.1) Put the USB driver on the PC (It is advisable to disable the driver signature verification in windows- google to help)
2) Download Recovery - TWRP
3) Fail scatter
------ = 2.3 points lozhish files in a separate folder ---
4) I can not remember without root works or not, but just in case I will write. If you need a backup of your phone (need Flash card gigs 4-8) is placed on the phone titanium backup - you come - Click on the second tab (backups) from the top of the icon sheet daw - choose "Make RK entire user software." move to backup to a different folder, and once again do but to "make all RK custom software and system data" - this just in case.
5) Turn off the phone
6) includes a program Flash Tool
7) specifies the path to the file scatter
8) Should Fail recovery stand daw
9) Put Download only
10) Press Download
11) Connect the power cord to the body.
After excluding telephone (ALWAYS !!!!) Press VOL +, and ON. together, should see boot menu, select the button and press the + recovery - to go to TWRP
In the TWRP - press "backup" in the next window, you put all the jackdaws and snap your top do not remember exactly where, but there you can select the external sd card to record backup. and backup for 10 more minutes.
All of us do not care at all, you can do what you want =))
Then do in TWRP reboot in normal mode (need WI-FI), should appear with an offer to make a root or not to do - disagree. body boot turn on the 'Net WI-FI and start downloading the patch for the root, then as a patch will be downloaded will choose the menu that appears after installation TWRP, body restarts itself do everything.
ALL! Ruth received.
Click to expand...
Click to collapse
I wish it could work for me to?
but ´till now noppes nada nothing,, I'll try to send up some files like the scatter file and custom recovery rom, maybe you´re able to check them out, what is wrong with it.?
I recently ordered an Onda obook10 dual booting tablet (Android 5.1 +Win10) from GearBest, and received it a week (and a half) ago. It is the V5 version (9th and 10th digits of S/N). Booted into Android at first, swiped around a little, and then left it alone for when I was free. Day before, I booted into Windows, and seeing that an account was already set up, hit the factory reset option (Options: remove all personal files, normal wipe (not thorough)). It rebooted, said it was resetting, then got stuck at 5% for a half hour. I then did a hard reboot, and it starting resetting again. I repeated this a few times, with different waiting periods, but it always got stuck at 5%. I wanted to see what was going on, so I opened the OS selector menu and tried to boot into Android, but that put the device into a bootloop, and it's stayed that way since. I downloaded the recovery WinPE from their website, and tried running it; all went well until the last step (installing the install.wim file), which succeeded, but when the batch file tried to set the boot options/flags, it threw an error about not being able to access D:, and failed. Tried making the recovery USB and installing multiple times, but it failed every time. I then tried Gandalf's WinPE image, which booted, and tried using imagex to install the .wim file to C: manually, as detailed here. This failed too.
I'm at my wits' end, honestly. I have no idea what else to try. There's another WinPE file available for download, but it's dated only a couple of weeks after the one I already have, so I'm hesitant to download it if there's any other option (I have very low bandwidth, it would take me at least two days). Also, it's hosted on Baidu, and the download times out after about an hour, and cannot resume. If anyone could give me any ideas, or point me towards a guide I haven't found yet (I've read all the relevant ones I could find on the Onda forums, but please post them anyway if you think they would be helpful), that would be great.
What would be perfect is if someone could upload, or point me toward a system dump/partition clone of at least the Windows partition and boot partition; I have the tools needed to flash those.
Thanks in advance.
EDIT: I managed to fix this a while ago, and have put the procedure somewhere in this thread, but since people keep popping up every now and then asking for it, I'm going to put this here so it's easier to find. Copied from later in the thread, here, and modified to be more general:
This uses slightly modified commands from the Onda firmware install script, and will result in a COMPLETE WIPE and reinstall of Windows - all the files on the Windows partition will be lost. This SHOULD work for anyone whose Android is working but Windows isn't, but I can't guarantee that. I can't even guarantee that this will work (though I am pretty sure it will) - I have not tested it completely. If you can, you should make a backup of anything files on the internal storage, just in case. As always, read the whole procedure before starting.
NOTE: If your Android isn't working, you need to install that first - get the Android file from the Onda Baidu page (look for the one for OBOOK 10 (not SE), with the appropriate V1, V2, V3, V5, or V7 code - you can find your code by checking the serial no. on the back of your device, the 9th and 10th characters), and follow the instructions in the document included in the zip - they are pretty straightforward, but you'll have to use Google Translate, as they're in Chinese. This MUST be done before the Windows procedure, because the Android installer wipes the entire disk.
If you want, you can make the procedure easier for yourself and save all the commands below to a text file, put it in the root folder of the USB before booting, and open it in Notepad by using:
Code:
notepad D:\textfile.txt
Or whatever name you give it. That way, you can copy paste them all easily.
Boot into the Windows installer, and when the command window appears, press Ctrl-C. After a few seconds, it will ask you if you want to terminate batch job, type 'y' and press enter. You now have a command prompt to work with.
You have to delete your Windows partitions first. The below partition numbers should be correct, but you should make sure first by running "list partition" and checking if it corresponds with the last 3 partitions, which should be your Windows partitions - their sizes are usually 128 MB, 35 GB, and around 800-1024 MB, and their types are Reserved, Primary, and Recovery (DO NOT delete the Primary partition at the beginning of the disk). DO NOT delete the Unknown partitions - those are Android's.
Code:
diskpart
sel disk 0
sel partition 14
delete partition
sel partition 13
delete partition
sel partition 12
delete partition
Your Windows partitions are now completely gone, so you'll have to recreate them first.
Change directory to the images folder.
Code:
cd D:\images
Get filesizes of .wim files to create partitions accordingly:
Code:
for %I in (Install.wim) do set INSTALL_SIZE=%~zI
set /a INSTALL_SIZE_MB=%INSTALL_SIZE:~0,-6%
for %I in (Winre.wim) do set RE_SIZE=%~zI
set /a RE_SIZE_MB=%RE_SIZE:~0,-6%
if %RE_SIZE_MB% LSS 430 (set /a RE_SIZE_MB=480
) else (
if %RE_SIZE_MB% GEQ 430 (
if %RE_SIZE_MB% LSS 680 (
set /a RE_SIZE_MB=%RE_SIZE_MB%+320
) else (
set /a RE_SIZE_MB=%RE_SIZE_MB%+1024
)
) )
Make sure to preserve all the spaces and brackets in the above code.
Enter diskpart, run the following:
Code:
sel disk 0
create partition msr size=128
create partition primary
shrink minimum=%RE_SIZE_MB%
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
You should now have 14 partitions when you do "list partition".
Exit diskpart.
Now for the actual installation:
Code:
md w:\recycler
md R:\recovery\windowsre
DISM /Apply-Image /ImageFile:"D:\images\Install.wim" /ApplyDir:w: /Index:1 /Compact /ScratchDir:w:\recycler
xcopy D:\images\Winre.wim r:\recovery\windowsre /y
Create boot entry:
Code:
bcdboot w:\WINDOWS
If that doesn't work, then:
w:\WINDOWS\SYSTEM32\BCDBOOT w:\WINDOWS
Set recovery environment:
Code:
w:\windows\system32\reagentc.exe /SetREImage /Path R:\recovery\windowsre /target w:\windows
And that's it! You should have both OSes operational now.
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
EDIT: I've put the guide in the first post.
Flashing Help
SirVer said:
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
Click to expand...
Click to collapse
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
[email protected] said:
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
Click to expand...
Click to collapse
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Widows swith icon
SirVer said:
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
[email protected] said:
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
Click to expand...
Click to collapse
Is the partition still there, or is that just free space you're seeing? For me, the partition was gone, with unallocated space in its place. If the partition is still there, then your job is relatively simple.
1. Make a WinPE recovery drive from another Windows machine, or just use a custom one (like Gandalf's WinPE, Google it).
2. Boot into it from the BIOS menu.
3. Load a command prompt.
4. Type "diskpart" (no quotes). Wait until you get a prompt like: DISKPART>
5. Enter the following commands:
a. select disk 0
b. list partition
c. select partition xx (where xx is the number of the Windows partition. If it's not labelled, it'll be the one about 36 gigs in size.
d. assign letter=c
e. exit
6. Now just run "bcdboot C:\Windows"
7. Reboot, and you should see Windows in your BIOS menu once more, and the button should pop up on Android as well.
If the Windows partition is not there, and it's just free space, things become more complicated. You'll need to get your hands on the Windows installer image. There is an older version on the Onda website (December 2015) that should do the job - or rather, there's a link to their Baidu account. You can find the more recent version in their account as well. The issue is that Baidu doesn't allow you to download files that large without installing their crapware. I got around it by registering an account and some URL-fu, but it's a PITA, especially if you have a slow connection. There's a Yandex mirror somewhere, but I'm not at home, so I don't have the link right now. I'll post it when I get back. EDIT: Here it is.
After you get the files, DON'T install it; it might wipe your Android install (did for me). There's an issue in their install script that made the command that hides the Android partitions from getting deleted not work. What I did was terminate the automatic install, and selectively apply the relevant portions of the script manually. You could probably do the same, but it could take you a while; took me two days and a bunch of background reading. If you're used to messing with Windows installs though, it'd probably be a cakewalk for you. I'd prepare some instructions for you, or even try and write a script myself using that one as a base, but I have exams right now, and I wouldn't have time for at least a week. If you haven't figured it out by then, just ask, and I'll do it.
Sent from my LG-D855 using Tapatalk
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Frezza said:
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Click to expand...
Click to collapse
You can enter the BIOS menu by connecting a keyboard and holding down ESC while booting up.
Sent from my LG-D855 using Tapatalk
Help
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
[email protected] said:
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
Click to expand...
Click to collapse
I don't remember exactly what it's called, but I think it was the second menu entry - Boot <Something>. In that menu, you should see your USB drive USB EFI device or something like that listed - it might also show the manufacturer name (it showed my USB as a Sandisk). If you don't see it, you may have made a mistake when making the bootable USB - try it again while reading the instructions on Gandalf's site carefully. If you used Rufus to make the bootable, maybe try Unetbootin this time - it worked fine for me.
P.S. In case you meant boot into the file - you can't. You have to write it to a USB drive first. Instructions are on the same site you downloaded it from.
Sent from my LG-D855 using Tapatalk
Can I install Windows 7 by Gandalf on this Tablet?
Frezza said:
Can I install Windows 7 by Gandalf on this Tablet?
Click to expand...
Click to collapse
Install? Maybe, but you wouldn't have any of the necessary drivers, so touch and WiFi and stuff wouldn't work. However, you can download the drivers and try installing them, which might work, though it probably won't since they're made for Windows 10.
Sent from my LG-D855 using Tapatalk
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Frezza said:
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Click to expand...
Click to collapse
Depending on certain things, you may be able to just run the installer without doing anything extra. Are you able to boot into Android? Open a CMD window, and run the following commands:
1. diskpart
2. sel disk 0
3. list partition
Post the output of these here. A screenshot will also be OK.
Sent from my LG-D855 using Tapatalk
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
betsesv said:
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
Click to expand...
Click to collapse
When you extract that, you'll get a bunch of files and a DOC in Chinese explaining the procedure to make the recovery disk. Once you've made that, a WARNING before you boot into it: it will automatically open a CMD and start a delay counter, after which it will start the install automatically. Since this might break the Android side, you'll have to cancel it with Control-C in that delay period, which will give you a normal CMD to work with. You can use this to run the commands from my last post. If you want to be extra safe, also download a different WinPE recovery file (like Gandalf - actually you should download this anyway, it has some useful tools you might need later on), and boot into that instead. Depending on the output of those commands, you may be able to just run the automatic installer without worries.
Sent from my LG-D855 using Tapatalk
obook20 crashed
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
alexander137 said:
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
Click to expand...
Click to collapse
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
SirVer said:
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
alexander137 said:
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
Click to expand...
Click to collapse
Just press it down for a long time, at least 10 seconds, that'll do it. For some reason it takes a really long time to force shutdown. If that doesn't work, then there might be an issue with your hardware. Also try typing the "exit" command - it should put you into the BIOS menu directly.
Sent from my LG-D855 using Tapatalk
[GUIDE/TUTORIAL] Asus Transformer Prime to Android 7.1/LineageOS 14.1
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat/LineageOS 14.1
This detailed step-by-step guide helps you transform your Asus Transformer Prime with Android 4.1.1 to a powerful one with Android 7.1 (Nougat).
### I'll make a few comments like this, read these or you may miss something.
### The Asus Transformer Prime codename is TF201.
Try to prefer USB2 connections, but USB3 works fine too.
CHANGELOG
v11. Improvemed unlock section
v10. Updated links
v9. ROM v39 and removed obsolete info
v8. ROM v35 and enhenced link for OpenGapps
v7. Refresh pack for ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification
v5. Updated djibe pack for easier install (kang recovery 3.1.0-1, SuperSU, drivers if fails at Step 6) + switched to v26 of Katkiss
v4. TWRP Kang recovery 3.1.0-1
v3. Tweaks and walkthrough
v2. Android 7, many hints added for more accurate tutorial
v1. Initial release
BEFORE STARTING
Make sure you have the latest official updates for your tab :
In Android, go to Settings -> About tablet -> System Update
### Make sure you read all comments starting by ###
To make sure your tab is the correct model, go to Settings -> About tablet.
The details below are listed :
• Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot)
bootloader V 10.4.2.18
### To verify bootloader version, shut down tab. Then hold Power + Volume- for 3 seconds and release.
### You are in bootloader : on top left corner is written Android (...) epad-10.4.2.18.
### To quit bootloader, press Volume- to go over the Android icon, then Volume+ to confirm.
### If not V 10.4.2.18, check official updates for your tab before starting this tutorial
### or check more info on Asus support web page and download the version identical to the Firmware Description written top left corner of the bootloader
### Asus support is here : https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_BIOS/
• GPS 7.9.13
• Wi-Fi 7.1.0.24
• BT 10.33
• Camera FT201-0x9900
• Ecran MXT-2.0 build-170
• Kernel 3.1.10.00002-9599d0cf [email protected]
o #1 SMP PREEMPT Thui Nov 22:12:01 CST 2012
• Build nr JR003C.WW_epad-10.4.2.18-20121122
Still in Settings -> About tablet, tap 7 times on build number to unlock Developer menu.
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card.
Then copy the backup on your PC.
1) DOWNLOAD
djibe Transformer Prime pack v2: http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
+ ROM KatKiss Nougat v39 Android 7.1
XDA Thread: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Download here: https://downloads.timduru.org/android/tf201/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=14943124697586357425
+ OpenGapps ARM 7.1 ARM Pico (NO OTHER DISTRIB THAT ARM PICO please): https://opengapps.org/?arch=arm&api=7.1&variant=pico
You must have a microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps and SuperSU.
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped earlier (on Windows desktop).
Select file android_apxusb.inf, then right click -> Install.
Force driver installation and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Then plug tablet to PC (USB2 port) to end driver installation.
### If it fails to install you may try using Windows device manager :
### In Windows Device Manager menu -> Right-click on Asus Android Device -> Update Driver Software -> Let me pick -> Have disk -> Browse to the .inf file and install BOTH .inf files.
### See this post if still doesn't work : https://forum.xda-developers.com/showpost.php?p=75240547&postcount=166
- For Linux, I have no experience. Every tools should be here : https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
- Copy the UnLock_Device_App in tablet's internal memory
Tab should normaly be seen in Windows explorer as TF201.
Check MTP file transfer protocol is active on the tab.
Copy the UnLock_Device_App_V6.apk in the root folder of the tab.
3) UNLOCK BOOTLOADER OF ASUS TF201
Tablet must be fully charged to 100 %.
In Android, go to Settings -> Security -> Check Unknown Sources.
Then Settings -> Developer options -> Enable USB debugging.
Launch the preinstalled app File Manager to install UnLock_Device_App_V6.apk.
### If it fails to install, delete your Google Account. Go to Settings -> Accounts. Delete the Google Account.
Launch the UnlockApp.
Accept User agreements. Your warranty is now void.
Accept and click to unlock the tab,
let the tab restart and work.
After reboot , "This device is unlocked" is written on top left screen.
### It probably won't work that simple.
### The solution is here, but I didn't have to test it: https://forum.xda-developers.com/t/howto-unlock-tf700t-in-2020.4157143/post-85255809
4) PREVENT BRICK : NVFlash
This step is optionnal but highly higly highly recommended, your tab will never be bricked after it !!!
1ST PART --------------------
Tab shut down, press Power + Volume- for 3 seconds and release, you are in the bootloader.
Use Volume- to move cursor over the USB logo, confirm with Volume+, you are in the fastboot mode.
Connect Transformer Prime to PC.
Select the "Files" folder you you unziped earlier.
Do Shift + right click on folder -> Open a Command Line.
Type:
Code:
fastboot -i 0x0b05 flash recovery flatline_tf201.img
and confirm with Enter.
### If you get error "fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program",
### type the command starting with a dot :
Code:
.\fastboot -i 0x0b05 flash recovery flatline_tf201.img
A blue bar appears on the tablet indicating flash success.
Wait until command line reports the flashing success.
then type :
Code:
fastboot reboot-bootloader
and confirm with Enter.
This time in Bootloader, use Volume- to select RCK (recovery) and confirm with Volume+.
You are in the flatline recovery.
Use Volume- to go to Advances, confirm with Power.
then wheelie, confirm (Power button),
then i accept the above statement (Power button),
then Step 1: flash AndroidRoot BL, tab powers down.
Start tab with Power only,
let the blue bar fill completly and start Android normally.
Once in Android, shut it down.
Start tab in bootloader Mode again (still Power + Volume- ;-) ), go to recovery again (RCK).
Connect tab to PC.
In recovery, return to Advanced -> wheelie then select Step 2: generate wheelie blobs.
It generates the backup files !!!
Open another Windows command prompt for fastboot mode and type :
Code:
adb pull /data/media/AndroidRoot
.
Backup files are stored in your "Files" folder. Make another backup of these files in a safe place.
(7 files are saved : recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log)
### If
Code:
adb pull /data/media/AndroidRoot
doesn't work : start Android normally, connect to PC as multimedia storage and
### navigate to My Computer -> Transformer Prime TF201 -> Internal Memory -> Android Root and copy the files in here.
Shut down tab.
2ND PART, NvFlash ----------------
Copy these 7 files in the folder "files/nvflash" (Another copy, in addition to the backup you made).
Connect tab to PC.
Start tab in Nvidia APX Mode : Hold Power + Volume+ for 3 seconds.
Anything happens, it's normal, screen stays black.
The tab is visible as an external drive and is called APX.
Open another Windows command prompt on the nvflash folder.
Type :
Code:
wheelie --blob blob.bin
and confirm with Enter.
If successful : the tab launches in bootloader mode and the Command prompt writes a few lines.
Type in command :
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
then :
Code:
nvflash --resume --read 14 factory-config.img
then :
Code:
nvflash --resume --read 7 unlock-token.img
You have to backup 3 new files : bricksafe.img, factory-config.img and unlock-token.img.
Copy these files in a safe storage with your blobs for future repair if needed.
### If you need to restore those backups one day, follow the tutorial of craigacgomez : https://forum.xda-developers.com/showthread.php?t=1927818
### If you have error "not enough space for GApps (error 70), follow this tutorial https://forum.xda-developers.com/showpost.php?p=73403429&postcount=137
5) RECOVERY
(Only applies to stock bootloader V 10.4.2.18).
Charge tab to 100% before continuing.
Start it in bootloader mode (Power + Volume-).
Connect it to PC.
Set the icon over the USB selection.
Confirm with Volume+; you are again in fastboot mode.
Open a command prompt on the /files folder.
Type :
Code:
fastboot devices
.
if the serial number is written, tab is well connected.
### Or check driver installation if not.
then type :
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
and wait for the "finished" success message,
then type :
Code:
fastboot -i 0x0b05 reboot-bootloader
,
and confirm with Volume+ to get into RCK (recovery, again), it is now TWRP 2.6.3.0.
6) BOOTLOADER
Once in TWRP recovery, type in command prompt :
Code:
adb devices
-> terminal returns : 012345678ABCDEF recovery.
Type :
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now on the tab, still in TWRP recovery, go to Install then click on HairyBean_Bootloader_TWRP2.5.zip
(file is in Internal memory, in folder /sdcard).
Swype to the right to confirm flashing, wait until Successful message appears.
Now click Reboot System and Do Not Install when SuperSU is proposed.
Let the tab reboot with another blue bar. Let it work.
The tab reboots and launches the HairyBean TWRP recovery (androwook).
In Windows command prompt, type :
Code:
adb reboot-bootloader
,
tab reboots in bootloader mode and the USB icon is gone, it's perfect.
### If Windows doesn't recognize your tab, or recognizes it as VID_0B05&PID_4C83, try the fix from XTCrefugee included in my pack : folder \Drivers android_winusb if hairybeen TWRP not recognized
### Install this .inf driver file as you did earlier
###
### YOUR BOOTLOADER IS NOW IN 10.6.1.27.1 VERSION
###
In command prompt, type :
Code:
fastboot -i 0x0b05 flash recovery twrp-3.2.3-0_KANG-tf201t.img
Wait till blue bar completes.
When finished message appears in terminal,
type :
Code:
fastboot -i 0x0b05 reboot-bootloader
, tab reboots.
Now enter in new recovery with Volume+ : recovery is now TWRP Kang 3.2.3-0 Recovery
### Your tablet will be seen by Windows as a TF201T now !
7) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Go to Wipe -> Advanced Wipe, select only the Data partition,
then tap on Repair or Change File System -> Change File System and tap on F2FS.
Swype to force partition system as F2FS. Wait till done prompts. Then go back to Advanced Wipe.
### If TWRP sends you this log in red : E:Failed to get default contexts and file node for storage files,
### Reboot to TWRP recovery again before going any further.
Repeat the operation of F2FS conversion for the Cache partition.
8) INSTALL ANDROID NOUGAT 7.1
Still on TWRP Advanced Wipe menu,
select Dalvik Cache, System, Cache, Data AND Internal Storage and Swype to force cleanup. Wait till completion.
Back to Home screen, tap Install, then Storage: Internal Storage and change it to microSD card -> OK.
Select KatKiss* .zip, and Add More Zips,
select SuperSU.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swype to force install. Be patient.
### Make sure once again you have the Pico Gapps version or system will hang.
### If TWRP crashes to its Home screen, you microSD might be in cause. Find another one, and then try to install Zips 1 by 1.
### If error installing Gapps, see this thread : https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Go back to Home when done.
Then Reboot -> System.
Let the tab start during at least 15 minutes.
9) START ANDROID N 7.1
### During first setup, manually toggle Wifi ON using the Wifi icon on the bottom right corner. If you don't, the setup app will crash.
### It can crash a few times before turning on, keep activating it.
Configure Android as you like.
In Settings -> Mediascanner filters, uncheck Scan.
In Settings -> About, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, try both GPU rendering active and disabled.
I can't figure which one works best. Share with us.
Good to know about this ROM:
Bluetooth requires to be turned on twice before it turns on.
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner.
AND more on XDA Katkiss thread (See DOWNLOAD CHAPTER ABOVE)
10) ROOT
Open app SuperSU to see more details about the Root access.
After ROM first launch, go to Settings -> About tablet.
Tap 7 times on build number, it will unlock the Developer menu.
In the developer menu -> Try to turn ON and OFF the Force GPU option and tell me what is the faster one.
(I think I prefer when GPU forcing is disabled).
11) PERFORMANCES AND OVERCLOCK
Source of benchmarks: http://androidmodguide.blogspot.fr/p/blog-page.html
Install Kernel Adiutor app from Google Play Store.
Launch app and go to Settings -> Kernel -> CPU :
Check Apply on boot and change CPU Maximum Frequency to 1600 or 1700 Mhz, set Governor to Interactive
Now Kernel -> I/O Scheduler :
Check Apply on boot and set Scheduler to Zen, then Readahead to 1024 Ko (or 2048. Try yourself)
Now Kernel -> Various :
Check Apply on boot and set TCP congestion to Cubic (or Westwood)
12) VARIOUS FIXES
### Your tablet doesn't see the Wifi ? (that is on Channel 13 by example).
Try this first : in the Wifi screen (where you see all visible networks), tap on the three-dots icon to open the menu -> Advanced wifi parameters.
Tap on the Wifi region code item to select the region : chose the corresponding region.
Now verify your Wifi network is visible.
If not, try this :
Open Kernel adiutor, Menu -> Build.prop editor.
In key search field, type wifi.
Click ro.wifi.channels -> Edit -> in the value field, set 13. Confirm with OK.
At the same time, you can set wifi.supplicant_scan_interval=180 to 180 (seconds) to reduce number of scans and reduce battery usage.
Restart tab, your wifi network should be visible again.
### Your keyboard isn't in the correct language
Go to Android Settings menu -> Languages & inputs -> Physical keyboard -> Android keyboard
Enjoy your new tab ;-)
djibe
Thanks : @timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
HorthLithperer said:
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks for your support. It was a tough job to explain step by step.
Took me 3 days to discover all the details.
thanks
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
yo29570 said:
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
Click to expand...
Click to collapse
Thx for feedback.
I had the same problem and used the tab factory reset.
I've updated tutorial and told to delete the Google Account.
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Woodrow256 said:
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Click to expand...
Click to collapse
Glad you liked it and tab is healthy again !
I've made tuts for Xperia Tablet Z and Samsung devices too if you are interested
Problem with step 8 - INSTALL Android 6 ROM
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
deltabert said:
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
Click to expand...
Click to collapse
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
djibe89 said:
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
Click to expand...
Click to collapse
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today (27 dec.) i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
Got the tab in APX mode again (Windows Device Manager shows Asus T. P. APX..)
So i went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
deltabert said:
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
But unfortunately i am not able to get the tab in APX mode again.
Then i skipped this en went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
Besides this, I am still worried that NvFlash might be no longer on the tab...
And i don't get the FlatLine booting with volume-up and power anymore...
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
Click to expand...
Click to collapse
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
ALDO_MAC12 said:
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
Click to expand...
Click to collapse
Hi ALDO-MAC12,
Unfortunately, i have not yet got my TF201 working. I'l wait now until djibe89 has time to react.
(When i opened his zip file i noticed he has also a France language description, and he is at the moment in France, So i guess he is a French-Canadian, on vacation in France.)
I did study the original posts from timduru and TacoNikky, but i can find no differences with the description of djibe89. Noticed there is also a Android 7 rom from timduru. But i think i should first get to manage the hole process.
For me all this is new. My tab became so horribly slow that i only sparsely used it anymore. So that's why i would like to give it a try.
BTW, i do get the tab in APX mode; with volume up and power, i get a black screen but in Windows Device Manager there shows up the Asus Transformer Prime APX ... driver.
If you're running Windows 10, you need to delete all your other android drivers, then disable the signature checking on your driver installation and install the Naked Universal driver.
Super SU wants update
Works for me on windows 10. Make sure tablet is plugged in directly and not into keyboard also. Although Super SU is now reporting an update in necessary. Is it recommended in update Super SU after installation? Btw thanks for bringing new life to my tablet!
Have you tried not to change /cache partition to f2s2. The original KatshMallow thread says:
This ROM is for TF201 and F2FS only
Convert just /data partition to F2FS
Click to expand...
Click to collapse
...
Hello all,
Thank you for thinking with me, I appreciate this very much! I will react to the suggestions given.
@lazuhrus, I think the Universal Naked Drivers 0.72 are correctly installed on my Win-10 PC. I followed the procedure for Win-10 to disable driver control. To confirm this: I am able to use fastboot from Win-10; fastboot devices gives me the serial number of the tf201.
Also the command adb devices gives me: 012345678ABCDEF recovery.
Further, when I bring the tf201 (with volume UP and power) in APX mode, I get a dark screen on the tab, but in Windows Device Manager there shows up the Android device: Asus Transformer Prime APX Interface.
So for me this seems OK. This lets me conclude that the Universal Naked Drivers 0.72 are correctly installed and working. Or am I overlooking something here?
Btw, I do this on the bare tablet, without the keyboard dock.
With volume DOWN and power, I get the tab in TWRP version 2.8.3.0.
And installing KatKiss seems to go well (see the screenshots I posted in #10 from the TWRP format and install process).
@ shaDNfro, I did change the /cache partition to f2fs, as the screenshots are showing too.
However, there is one strange thing. After the last install (post #10) when I am in TWRP and connect the tab to my PC (win10) I see in the File Explorer an entry for an ASUS Transformer Pad TF300T; while mine is an TF201!!
Picture File Explorer: https: // deltabert.stackstorage.com/s/Nj1C01jTyZ5MoWB
And in the Device Manager I see also references to the wrong tab type!
(But you can see the Asus Android Composite ADB Interface.
Picture Win10 Device Manager: https: // deltabert.stackstorage.com/s/zK2LIoAthr4jKJ7
(added spaces around // because i am as novice not (yet) able to post links)
Hopefully anyone can help me with this...
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
djibe89 said:
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
Click to expand...
Click to collapse
Thank you djibe89,
I really hope you can help me with this, I become a little desperate...
I wonder if there is something wrong with the bootloader (HairyBean_Bootloader_TWRP2.5.zip). When I boot the tab with vol-down and power I get the following bootloader info: Android cardhu-user bootloader <1.00 e> released by “WW_epad-10.4.2.15-20120917†A03
Do you know if this is correct?
OK, I put the tab in TWRP 2.8.3.0 mode.
Formatted the /Cache partition using make_ext4fs
Then I wiped Dalvik Cache, followed by /System, which formats to ext4fs.
Then format /Data, first with make_ext4fs, and when finished, I change the filesystem of /Data to f2fs. Wiped all other partitions, except Micro SDcard (not sure if this is the internal or external SDcard)
Then I installed the three .zip files. KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip and BETA-SuperSU-v2.52.zip.
I also put the MD5 checksum file of KatKiss-6.0_TF201_029.zip on the sdcard and the install procedure checks the .zip successful.
When install is done: Successful, I wiped Dalvik Cache and rebooted the tab.
But then I have the same reboot problem: First i see a blue bar for one second, then the tab boots with the ASUS splash screen at medium intensity, then switches for a moment to high intensity and back to medium intensity, and after a few seconds it reboots and it starts over again.
When I leave the tab booting for two hours, I can feel it is doing something; the backside is becoming slightly warm; processor: ~ 45°C.
The bootloader is part of HairyBeen isn't it? Could I re-install the correct HairyBean_Bootloader_TWRP2.5.zip again, by putting it on the external sdcard and selecting it from TWRP 2.8.3.0?
fastboot, adb and Nvidia APX Mode are still functioning, so there must be a solution...
Hopefully you have a good suggestion?
Kind regards, Bert
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
djibe89 said:
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
Click to expand...
Click to collapse
Hi djibe89,
I will look into the restoration option. I do have the APX backup files.
Will be continued....