Related
I finally did what Archos support said couldn’t be done. I was able to downgrade my firmware from the extremely buggy (and non-rootable) 2.0.71 firmware, to the 2.0.54 rootable firmware.
Warning: This process involves downloading and installing the Archos SDE firmware. This WILL void your warranty. Proceed at your own risk!
This process was done using a Windows 7 machine (and the Archos tablet, of course).
Phase 1 – Removing the 2.0.71 firmware and replacing it with the Angstrom OS
1. If you do not have your Archos plugged into the AC Adapter, plug it in now.
2. Download the SDE Developer Edition firmware here:
http://www.archos.com/support/download/firm_dev/firmware_archos_android_gen8.aos
3. Power off your Archos (if powered on). Then boot your Archos in Recovery mode by holding the Volume – button and pressing the power button. Release the power button, but keep the Volume – button held down. It will boot into recovery mode.
Recovery Mode navigation works as follows:
Volume + moves up
Volume – moves down
Pressing Power is Enter
4. Press Volume – to Format System and Press Power.
5. Press Volume – to Reformat Device and Press Power.
Warning: Make sure you have backed up any critical data on your Archos tablet prior to proceeding any further. If you have not backed up your data, select No and press Power, and No on the previous menu. At that point it will reboot the device and you can back up your data.
6. Press Volume – to I understand and press Power. It will then reformat the partitions.
7. When the USB Connection menu appears, plug in the Micro USB cable into your computer and into the Archos tablet. Windows (or your mac, I suppose) will recognize the tablet as a drive letter in My Computer - Mine was A101IT (I). Copy the SDE firmware file firmware_archos_android_gen8.aos to the tablet (e.g. drive I: on my computer). Copy to the root directory ( /) folder on the tablet.
8. Once the copy is done, press Power on the Archos Tablet (and remove the Micro USB Cable)
9. It will install the SDE firmware, then reboot.
10. It will boot into the AngStrom OS. At first this OS looks intimidating, but it is quite harmless.
11. It will come up with a new user details screen. Type in a user name, a password, and confirm the password. Then press OK. It will then log in and take you to the desktop.
12. Press the ^ key in the lower left hand side of the screen, and press Turn off. You may have to press a few times to get it to respond as the touch responsiveness was NOT very good for me.
13. Press Yes to log off. It will then power down
Phase 2 – Installing the 2.0.54 firmware onto your tablet.
1. If you do not have your Archos plugged into the AC Adapter, plug it in now.
2. On your pc, download the Archos 2.0.54 firmware from here:
http://www.arctablet.com/assets/archos-firmware/gen8_2.0.54-firmware_archos_android_gen8.aos
3. Rename the file firmware_archos_android_gen8.aos. (If you downloaded the file in the same place you downloaded the SDE firmware file, just overwrite it.)
4. Then boot your Archos in Recovery mode by holding the Volume – button and pressing the power button. Release the power button, but keep the Volume – button held down. It will boot into recovery mode.
Recovery Mode navigation works as follows:
Volume + moves up
Volume – moves down
Pressing Power is Enter
5. Press Volume – to Format System and Press Power.
6. Press Volume – to Reformat Device and Press Power.
7. Press Volume – to I understand and press Power. It will then reformat the partitions.
8. When the USB Connection menu appears, plug in the Micro USB cable into your computer and into the Archos tablet. Windows (or your mac, I suppose) will recognize the tablet as a drive letter in My Computer - Mine was A101IT (I). Copy the 2.0.54 firmware file firmware_archos_android_gen8.aos to the tablet (e.g. drive I: on my computer). Copy to the root directory ( /) folder on the tablet.
9. Once the copy is done, press Power on the Archos Tablet (and remove the Micro USB Cable)
10. It will install the 2.0.54 firmware, then reboot.
11. Congratulations, you now have the 2.0.54 firmware installed.
Enjoy,
Jason Andreas
I can confirm this guide is correct. Downgrade working. Only for 2.0.54 . Downgrade to 1.0.84 has failure message .
2.0.54 with z4root and setCPU 1000 gives faster A70IT than 2.0.71 fw Overdrive mode. And less screen decalibration issues.
EDIT : Original guide was posted in androidtablets.net forum
For some unknown reason my 101it can't see my home network after downgrading! It's able to see my neighbours wep encrypted network but not mine which is wpa encrypted? Anybody else having this problem and any solution would be appreciated.
Need some help guys;
Step 10 of the phase 2 :
I have copy/paste the .aos file in the root directory but I have this message : "Update failed: (1)"
Sry for bad English, I'm french..
PS : This is not the first time I do that kind of skill =X
1. It only sees WEP encrypted networks. (2.0.54 problem) , change your to WEP and everything is ok.
2. Are you sure you copied 2.0.54 aos file and not the 1.0.84 ??? Download again and copy it again. and carefull to lace it in root (not in folder by accident)
thanks for the quick reply.bit ****e that it only see's wep networks though . anybody know of a workaround to get wpa recognised?
lagoskon said:
1. It only sees WEP encrypted networks. (2.0.54 problem) , change your to WEP and everything is ok.
2. Are you sure you copied 2.0.54 aos file and not the 1.0.84 ??? Download again and copy it again. and carefull to lace it in root (not in folder by accident)
Click to expand...
Click to collapse
2.0.54 and WPA2 PSK running fine here.
iznogooood said:
2.0.54 and WPA2 PSK running fine here.
Click to expand...
Click to collapse
Confirmed ...
I tried WPA/WPA2 combined in my router . I turned to WPA2 PSK and it connects fine. Thanks
I am able to get connected via WPA2 with my A101 without any problems.
@apr24991, thanks a lot for this guide! I did not downgrade to 2.0.54, but i've used your guide to permanently boot to urokdroid's kernel. I'm now able to boot urokdroid's 2.0.71 without going through the recovery menu. Now I don't need to press volume - while powering up or rebooting to up bring up the modified kernel/initramfs. It now always boot to urokdroid's kernel which is what i want.
@constant7010 : Bravo ! And ... how did you do so ?
I'm quite interested but how did you converte the urku files to .aos file ?
if i could have urku native on my a101 it should be e great thing !
I'll try to retrace the steps I did, and put more detailed/clear instructions if i have a chance, but basically here's what i did:
1) follow uruk's instructions on installing to sd card. create 2 ext4 partitions 1 for root 1 for data.
2) create additional 2 ext4 partitions on the SD.
3) boot into uruk's kernel.
4) use adb to mount the 2 partitions (/tmp/rawfs, /tmp/system), and copy the contents of /mnt/rawfs to 3rd partition and the contents of /mnt/system to 4th partition (cp -a /mnt/rawfs/* /tmp/rawfs/, cp -a /mnt/system/* /tmp/system/)
5) extract and modify initramfs.cpio.gz. i edited etc/moutpoints change the devices for rawfs, system and data to the devices of sd partitions (e.g. mmcblk0p1 to mmcblk2p3, etc). change mount type to ext4 with noatime option.
6) repackage initramfs.cpio.gz.
7) follow the phase 1 downgrade instructions here. this will natively boot the developer edition.
8) go to recovery menu, developer menu, then go to flash kernel/initramfs. flash uruk's kernel and the modified initramfs.cpio.gz.
after this everytime you boot or power on it will always boot to sd card.
USB host gone
Hi, anybody having problems with the USB host after downgrading?
I can´t connect anything anymore, no mouse or memory stick.
@constant7010 : tx for you guideline.
So i assume that IF i want to boot with the original system i just have to boot in recovery mode and select Android Boot ?
I asked just to know if i keep the choice to boot a proper systeme if something goes wrong with the sd card
@foxtrotter,
I'm not sure about but this is what I have observed. After you apply Phase 1 of the instructions in post#1, you actually lose your android firmware, and will be replaced by developer mode firmware (Angstorm). So everytime you boot it always boot in developer mode. In fact after this, you will no longer see Android as one of the boot options in recovery mode. However you can always reapply the Android firmware in the recovery menu to bring back the original OS.
Actually on my first try after doing phase 1, i thought applying urok's kernel and initramfs.cpio is enough. But my system just kept on rebooting. Since Android was no longer accessible in recovery menu, I had to reapply the Android firmware, which is phase 2 on post#1, but using 2.0.71 firmware. And then I traced the Android boot process, and it looks it's accessing the contents /mnt/rawfs and /mnt/system which were missing after you apply phase 1. So I tried copying the contents of /mnt/rawfs and /mnt/system to 2 new partitions in my SD, and modify initramfs to use these partitions. And after applying phase 1 again, and putting urok's kernel and my modified initramfs, it now successfully boots to SD.
flo44 said:
Need some help guys;
Step 10 of the phase 2 :
I have copy/paste the .aos file in the root directory but I have this message : "Update failed: (1)"
Sry for bad English, I'm french..
PS : This is not the first time I do that kind of skill =X
Click to expand...
Click to collapse
@flo44,
Make sure that you renamed the Gen8_2.0.54-firmware_archos_android_gen8.aos file to just firmware_archos_android_gen8.aos. Then copy the renamed file to your Archos. Make sure the file is placed in the root folder (/) of the device.
Look at step 3 under Phase 2.
If you just copy the file over without renaming it, you will get the (1) error.
You can always power the unit off and boot back into recovery and start Phase 2 over.
k1nk33 said:
For some unknown reason my 101it can't see my home network after downgrading! It's able to see my neighbours wep encrypted network but not mine which is wpa encrypted? Anybody else having this problem and any solution would be appreciated.
Click to expand...
Click to collapse
k1nk33,
I was playing around yesterday trying to get different 1.x firmwares to work with no avail. So then I decied to go back to the 2.0.54 firmware. When I did, I noticed that my wifi was not working. So I upgraded to the 2.0.74 firmware, then went through the whole downgrade process again. That fixed my problem.
@constant7010 : ok so i can see you rule to manage the Archos SDE boot.
I'm not so confident so i will keep my backup solution with multi boot.
But plz don't hesitate to keep us aware of the stability of your new configuration with those added partitions !
can i downgrade from 2.1.4 (froyo2.2.1) to 2.0.54 following this tutorial?
thanks in advance!
regards.
Write Protected
Hi there,
i tried that tutorial, but i cant copy any files on the root file system of the pad. It says "Device is write protected."
What did i do wrong?
Regards
Serpens
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 to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
I wanted to get rid of some apps that I dont use at all e.g Amazon Kindle but found out with research that I can do that. Also tried to use apps like Titanium Backup again I couldnt. I am new to the Tablet world this is my first. So I did some research and terms of root, unlock etc came up. So I know the difference between them. In order not to lose my warranty and since I just want to be able to delete certain unwanted apps and add other apps, I just want to for now root my TF201.
Did more research but I still cant get an answer or get some of the methods to work for me.
Below is the specs for my Asus TF201
1. So I have JB (Android Version 4.1.1), dont know if it came with it or got updated like I said I didnt mess with the tablet alot
2. Build #: JRO03C.US_epad-10.4.2.17-20121018
I plugged in the USB to my Windows XP laptop for the first time today and ofcourse I am missing the drivers. I went to ASUS website and couldnt figure what I need.
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
ramez75 said:
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
*SNIP*
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
Click to expand...
Click to collapse
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
TWRP Page
On that page are instructions including a download link for JB BOOTLOADER ONLY! MAKE SURE YOU GET THE RIGHT TWRP FILE FOR YOUR DEVICE. THE ICS ONE IF YOU ARE ON ICS, OR THE JB ONE IF YOU ARE ON JB:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
When that is downloaded you can compare the MD5 hash because its a good idea to do that. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it saysthe files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Copy the unlocker APK to the SD card. Run a file explorer on our tables and browse to the SD card (/Removable/MicroSD). Tap the APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
if you don't get the command window here option then you will have to open a command prompt. open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tab must be plugged in to the USB port of the computer of course.
If you installed the SDK tools it is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Edits:
I have editted this based on questions below to make it more complete..
First Thank yo uso much for taking the time and sharing the good info. Ofcourse there is alot of foreign terminology you have used and I will need to read you reply a number of time till it soaks in and I am sure I will have follow-up questions.
So it seems the only way I can get to root my TF201 (running JB) is to unlock it which means losing the warranty. Well if thats the only route then so be it....
I guess first thing is to successfully unlock the TF201
hx4700 Killer said:
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Run the unlocker tool you downloaded. For here its fuzzy for me because I found the APK file I got from the Asus download and copied it over to my tablets SD card via USB. Then I used the built in file browser to find it on my SD card and ran it. By whatever means you will need to run the unlocker tool on your tablet to unlock. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed. ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
Yes, unlock it. There is no root method for tf201 on JB outside of unlock. An exploit may come up some day but nothing soon I would wager.
I tried to organize it by Al the stuff you need to download first. Then steps to use what you downloaded. It you follow it precisely things would become clearer.
Hi,
Ok I was going through the instructions and downloading all the necessary files and I ran into an issue with downloading the TWRP for JB. Well the link you have allows me to download either the *.img or the *.blob extensions. So I went ahead and downloaded the *.blob extension. I did the MD5 as you recommended and visually checked it with the image on the website and they dont match. I got the below
"b6bae17dac81a126d5d3ad8e27fd5007" which is entirely different than the one on the webpage. I also tried the *.img and no luck there. So I stopped. What do I do now where can I get the TWRP
Thanks
hx4700 Killer said:
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Click to expand...
Click to collapse
hx4700killer
I did some googling and found the below link
http://forum.xda-developers.com/showthread.php?t=1510737
the link has "Direct apk link (dropbox)"....Is this what you referred too? I downloaded the file, should I move it to the SD card and run it from within the tablet?. Is there a way to run an apk file.
Also
I downloaded Android SDK on my laptop. I run the eclipse.exe as per the instructions on the website but nothing happens
Thank you
RB
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
ramez75 said:
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
The second link that says it is for the unlock tool is the APK.
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
hx4700 Killer said:
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
Click to expand...
Click to collapse
ramez75 said:
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
Click to expand...
Click to collapse
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
hx4700 Killer said:
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Click to expand...
Click to collapse
ramez75 said:
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
Click to expand...
Click to collapse
This is the MD5 hash that you should get:
19d93f4ec4685b8124468684eb2913fc
This is the exact download link I used for my TF201 running the most recent JB Update:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
The file you get is: openrecovery-twrp-2.3.1.0-tf201-JB.blob which is the one I say to rename to twrp.blob
I would NOT flash anything not from the source on this one. If its wrong your device is trash.
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
hx4700 Killer said:
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
...
Click to expand...
Click to collapse
Yes, just open CMD and "cd" your way to the directory. Just make sure you end up inside the directory (ie. "...\UBTv1.3.2>")
ramez75 said:
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
Click to expand...
Click to collapse
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
hx4700 Killer said:
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
ramez75 said:
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
Click to expand...
Click to collapse
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
hx4700 Killer said:
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
Click to expand...
Click to collapse
ramez75 said:
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
Click to expand...
Click to collapse
What I meant was I use ADB from that root method from bin4ry. He includes ADB.EXE and needed DLL files so its a quick one stop shop for ADB.
Does the adb shell command give you anything? No its just proves root is available. Rootcheckers can also do it. ADB is just a way in to your device from a desktop machine.
I have never removed an APP but I believe removing its APK file from /system/app folder allows it to be removed or does remove it. ( i would save it somewhere in case you need/want it back)
Thank you for an easy to follow way to root a 4.1.1 JB OTA TF-201. It worked exactly as you described.
You may want to let some of the noob users know what in each zip file they need. It really helps if all the files you download are in one location unless you are familiar the windows command line.
[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....
Finally ported TWRP to the Medion Lifetab P10505 with working touch.
No guarantees are given, if you damage your tablet, all you do is on your own risk. I have the original ROM from Medion, if you need a full restore.
Please note that the TWRP recovery was not much tested and may be buggy. I didn't test with encryption or the restore process.
Please follow these steps:
1. Download all the files from Mega:
https://mega.nz/#F!pvQCQCxL!dfCHhGkliNSj-Wd3NcRV2ghttp://
2. Unpack all files into the same directory
3. If not done already, install the Intel Driver Package and reboot your PC
4. Unpack the ADB Tools into the directory
5. On your tablet go to your settings and enable USB debugging in the developer options. If you don't see the developer options menu under settings, goto about tablet and tip the build number seven times fast which will reveal the Developer options in the Settings.
6. Copy the file UPDATE-SuperSU.zip to your tablet (via USB or to memory card)
7. Switch off your tablet
8. Press and keep pressed the On/Off button and Volume Down button until you see the bootloader menu. Please press the buttons at the same time.
9. Now connect the table via USB cable to the PC.
10. Open a command window on your PC and change to the above created directory .
11. type the command: fastboot oem unlock (you can lock it again after the whole process if you want)
If this doesn't work goto the below section: Install recovery through flash
12. next type: fastboot flash recovery final_P10505_working_TWRP_3.0.2.0.img
13. Use the volume up or down button until Recovery mode is displayed.
14. Press the On/Off button shortly to start the new TWRP recovery menu. Please be patient until it fully loads. May take a couple of minutes.
15. Now choose install from the menu.
16. Proceed to the folder where you store the UPDATE-SuperSU.zip and select the file and swipe to install.
Note: If you forgot to copy the file to the tablet you can use the windows explorer to copy it to your tablet. There is a new device called Vi10 plus
(as mentioned it is only a port not build from source)
17. The Zip file should install
18. Use the back button to go back to the main menu of the recovery and select reboot and then system.
19. Now you have rooted the device and can create backups in the TWRP recovery.
20. To verify use any root checker tool from play store.
21. Feel free to hit the Thanks button
Install recovery through flash:
If there are any errors you can download the original ROM from Medion.de. You need then the Intel Platform Flash Tool Lite to install the ROM from Scratch (all your data will be lost).
When you run the flash tool, open the file from Medion.de and it will unpack the zip-file in the folder C:\Users\Your account name\.flasher\.download\p1050x-6.0-factory-v2.3
Proceed to the folder Just rename the file final_P10505_working_TWRP_3.0.2.0.img to recovery.img and replace the original file from Medion. Then hit the flash button.
Actually the Intel tool will perform the same command as above.
PS: I read that P10506 is hardware like the same as P10505, so it may work there as well, but no guarantees.
PPS: Credit go to the creators of the TWRP file for the Chuwi Vi10 plus (Highbook), which I don't know their names.
thank you for this, I used it on my P10506, the only difference was thead the command in section 12 has changed to:
fastboot flashing unlock
Cooool!
Did everything on my P10506.
Now waiting untill booting is finished...... CHECK!!
Testing with a root checker........ CHECK!!
That is great!
Thank you!
simplex3 said:
Did everything on my P10506.
Now waiting untill booting is finished...... CHECK!!
Testing with a root checker........ CHECK!!
That is great!
Thank you!
Click to expand...
Click to collapse
You're welcome,
but surely room for optimization of this tablet. On mine it happens after quite some that it becomes very laggy.
Hope yours is running better.
Bernie_W said:
You're welcome,
but surely room for optimization of this tablet. On mine it happens after quite some that it becomes very laggy.
Hope yours is running better.
Click to expand...
Click to collapse
Seems to work fine.
No lags. Okay, not more laggy then it was before rooting.
But now i'd like to flash a custom rom... Any suggestions?
Regards.
simplex3 said:
Seems to work fine.
No lags. Okay, not more laggy then it was before rooting.
But now i'd like to flash a custom rom... Any suggestions?
Regards.
Click to expand...
Click to collapse
I haven't seen any custom roms for this tablet, but I actually didn't look much. The problem is that it is nearly impossible without sources to create one.
any new mirrors available? mega zip file offline...
P10506
Thanks for the wonderful news! If anyone (Bernie?) could make the files / TWRP image available again, they'd make me and the previous poster even happier
Looking to root and TWRP my familys two P10506s - one still on 5.1 - should I update it to 7.1.1 (last available image from Medion) first?
Download Link
Somebody here who have the files available and can upload it again?
Would be great.
Thanks
Bye
Amy New version for P10506? My tablet Constantly crasing on original software
Asciola said:
P10506
Thanks for the wonderful news! If anyone (Bernie?) could make the files / TWRP image available again, they'd make me and the previous poster even happier
Looking to root and TWRP my familys two P10506s - one still on 5.1 - should I update it to 7.1.1 (last available image from Medion) first?
Click to expand...
Click to collapse
Maybe you can flash android x86.
1,Flash tw08a-87z8 bios using flashrom in ubuntu.
2,Push esc key to enter bios.
3,Install android ,linux or windows using usb/sd boot.
Some medion and onkyo tablets are compatible.
I have written more details on my wiki.
TA2C-74Z8 - SmileTabLabo
Onkyo TA2C-74Z8はODS株式会社製造のAndroidタブレット。スペック 型番 TA2C-74Z8 製造元 オーディーエス株式会社 CPU Intel Atom Z8350 G...
wiki3.jp