Related
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last edit: Jan 2, 2018
The information here can be found in many places on the web and several forums. But when I started flashing custom ROMs about two years ago, I got frustrated many times because I found that information to be scattered, fragmented and in many cases outdated.
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF700 involves three steps:1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recoveryRooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step since any custom ROM you flash will be rooted anyway.
But if you want to root the TF700 on stock firmware there are three ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK).
And then there is Towelroot, a one-click-root exploit. It's an apk, so no PC necessary. Only Towelroot v1 works for the TF700 and it's hard to find. My dog ate the copy I had..
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Download the Asus Unlock Tool v7 from here: https://www.androidfilehost.com/?fid=817550096634776735
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
If you get an unspecified "network error" you could be in for some major headaches. Many tablet's serial number and/or the mac address of the mainboard seem to be registered incorrectly in Asus database. This problem is widely discussed on several forums, just google: "cannot unlock TF700" or similar and read the threads. Too many variables to discuss this here...
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
To determine if you need to update your bootloader read post #3
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8.+ you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
TROUBLE WITH ADB FASTBOOT DRIVERS? SALVATION IS NEAR!! (May 2017 edit)
And it is called FWUL (F-orget(?) Windows Use Linux) a great Arch Linux distro that you can boot off a USB stick or CD with simple adb fastboot all setup for you. Follow the instructions, set your boot sequence to boot from USB or SD drive first and disable Secure Boot in your BIOS Security settings. I have fought with Windows driver problems as long as I have been using Android devices and some stuff I never got to work. With this baby I was able to connect to 4 different Android devices with no problems at all. A beauty! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Inside that folder Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
If all of the above fails follow these instructions: https://www.michaelcrump.net/power-tip-for-windows-users-open-command-prompt-here/
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://twrp.me/devices/asustransformerinfinityTF700T.html
Download the latest version of TWRP. Version 2.8.0 or later is ready for KitKat and Lollipop custom roms as well as backward compatible with JB ROMs.
FYI ONLY: If you for whatever reason want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Formatting data is only necessary in cases of data corruption.
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
This will flash the recovery to the recovery partition
Example:
If the file is named TWRP_2.8.6.2_TF700_recovery.img, the fastboot command is:
Code:
fastboot -i 0x0B05 flash recovery TWRP_2.8.6.2_TF700_recovery.img
You can rename the file to something easier to type, but file name and fastboot command have to match.
So if you renamed the file to twrp.img:
Code:
fastboot -i 0x0B05 flash recovery twrp.img
If your recovery comes as a blob:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock rom you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers or check out post #2. There's a description of the most popular roms for this tablet.
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
ROMs for the TF700
Update June 2017:
Time moves on and this tablet is till alive....
Most of the roms below are ancient by now. One dev, the legendary timduru, is still working for this tablet and currently supporting Nougatella, Android 7.1.2 for this tablet.
Skip to here if you are thinking about a current rom: https://forum.xda-developers.com/showpost.php?p=72540013&postcount=346
Click to expand...
Click to collapse
KatKiss-KatshMallow by timduru (MM on the TF700 - who would have thought?) is still under intermittent but active development and it is a beauty. Multi-window support anyone?
http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements, but since there have been no further Asus updates, development on this rom has stopped. This rom would give you the most Asus-like experience on this tablet.
http://forum.xda-developers.com/showthread.php?t=2425383
And here is the recent incarnation of this rom: CROMi-X Resurrected: http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
@LetMeKnow still releases a new teak here and there, so keep following the thread.
Development on all of the following roms has stopped. The devs have moved on to other devices
CROMBi-KK is based on CM11 and tweaked for this tablet but a little buggy. The later LP based roms from the same team are definitely better.
http://forum.xda-developers.com/showthread.php?t=2672751
CyanogenMod is build from the ground up, CM10.x emulating JB 4.3, CM11 emulating KitKat (JB 4.4). CM was not build with a transformer (keyboard) in mind, but the dev has ironed out most of those bugs.
http://forum.xda-developers.com/showthread.php?t=1957660
ZOMBi-X: From the same team that developed CROMi-X and CROMBi-KK. Based on OMNI rom with multi-window support.
http://forum.xda-developers.com/transformer-tf700/development/rom-t2857931
ZOMBi-POP The (almost last) project from the CROMI/CROMBi/ZOMBi team. It's Omni based Lollipop for the TF700
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
A note: This rom will run with data formatted to ext4, which is the OEM default. But it benefits from /data on F2FS, the new file system developed by Samsung, more than any other rom before it. Changing the file system for /data to F2FS has become very easy since the TWRP team build support for it into their recovery. I wrote a guide for converting your data partition to F2FS here:
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
That same team took one final stab at a 6.0 rom for this tablet: http://forum.xda-developers.com/showpost.php?p=65968239&postcount=3719
But I would call this definitely an unfinished product with a doubtful future.
CM12 I don't run CM roms - try it for yourself
http://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
OmniROM by lj50036 who's on the ZOMBi team
http://forum.xda-developers.com/transformer-tf700/development/rom-omnirom-tf700t-t3056438
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
AND IF YOU LIKE YOUR NEW ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Alternative methods to install TWRP
Edit February 2015
In this section I originally explained how to flash TWRP to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work sometimes (and if you have root), but I will not recommend or promote them any longer.
Why?
Because I'v read too many stories about these apps failing, even flashing to the wrong partition - you name it.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
I have spent quite a few hours helping users who got themselves into a situation where the only thing they could access on their tablet was recovery, but they did not know anything about adb/fastboot and did not set it up when the tablet was still working. To get it to work with a soft bricked tablet is much, much harder!!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
HOW TO UPDATE YOUR BOOTLOADER
The last official Asus firmware update to JB 4.2.1 brought us to the 10.6.1.14.10 bootloader - and it will be the last one we ever get since there will not be any Asus firmware updates anymore.
If you are on an older bootloader and want to run a KK or Lollipop ROM, you should update your bootloader to this version.
Determining which bootloader you currently have
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.14.10-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.14.10 is your bootloader version
20130801 is the build date (and immaterial in most cases).
Updating your bootloader
Still on stock with stock recovery:
Just OTA update to the last Asus firmware or flash it manually.
Custom ROM with custom recovery
Either:
1. Flash Asus stock firmware in your custom recovery
Download the official Asus firmware, unzip it once, flash that second zip in TWRP or CWM.
The distinct disadvantage of this method is that you will loose your custom ROM and your custom recovery and you will have to reflash them, but it works to get you onto the latest bootloader - or the latest stock rom if you desire to return to stockOr:
2. Flash only the bootloader in recovery
This is what I would recommend you do.
Go here for a collection of flashable bootloader/recovery packages: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
If all you need is the latest US bootloader, go to post #3.
The packages (bootloader + recovery) will replace not only your bootloader, but also your current recovery with whatever the TWRP version in the package is.To flash a KK or Lollipop ROM afterwards you need TWRP 2.8.+.
If you choose a bootloader package with an older recovery, you need to flash the latest TWRP version after you flashed the above bootloader package. In between you have to reboot (do not skip this step!)
sbdags said:
@moderator could we sticky this please.
Brilliant post Bernd
Click to expand...
Click to collapse
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
berndblb said:
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
Click to expand...
Click to collapse
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Mod edit: I deleted your previous post to give the third post to OP. I will copy paste it here.
@stamatis could we sticky this please.
Brilliant post Bernd :good:
sbdags said:
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Click to expand...
Click to collapse
No problem. You "jumping the gun" is an honor to me.
Thanks
Well written and very informative post. Thread stuck.
please help
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported. So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh.. So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
blackc3 said:
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported.
Click to expand...
Click to collapse
I think you mean v8, v7 for the Asus Unlock tool?
You have to extract it. On the tablet you can use the app ES File Explorer from the Play Store. It downloads as a .rar file, the result has to be an apk
So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh..
Click to expand...
Click to collapse
You have to get the drivers working - no excuses
Without working drivers you cannot push a recovery to your tablet. What Windows version do you have?
Try installing the Asus PC Sync Utility, try the Google Naked Drivers, try the ones attached to this post (note: I have not tested these myself) - you will have to find the correct combination for your PC yourself.
Here are a few links that may be helpful.
http://www.addictivetips.com/window...-or-device-drivers-manually-in-windows-vista/
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
Click to expand...
Click to collapse
No. You just got started!
Here are a couple of different approaches if you cannot unlock:
http://www.transformerforums.com/fo...discussion/42587-my-unlocking-experience.html
http://forum.xda-developers.com/showpost.php?p=51210808&postcount=6
Thanks for the guide,
everything went smooth until this step:
fastboot -i 0x05B0 flash recovery twrp.blob
Now my cmd just hangs there (been like 10 mins), not sure if i should restart tablet or cmd? Tablet still in fastboot screen. Thanks.
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
berndblb said:
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
It recognizing it correctly (atleast from what I understood from the guide). If it matters, I installed twrp 2.7 instead since it indicated 2.6.3.2+
I get:
015d2bbce9141e18 fastboot
Can I safely reboot/close cmd and try again?
Yes. Ctrl C will cancel the command, you should get the command prompt back.
Strange... twrp.blob is in the same folder as your fastboot.exe, right?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
OP updated
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
A question for @_that as I always thought you needed the ID. Maybe not?
sbdags said:
A question for @_that as I always thought you needed the ID. Maybe not?
Click to expand...
Click to collapse
Apparently there was an older fastboot version that needed it. I've not used the ID for a long time.
It doesn't matter if you use 0x0B05 or 0xb05, it's the same number.
Great tut.
Thanks for posting. Good info, very concise.
berndblb said:
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here or if my instructions are dead wrong. I may be a fiend who's going for the world record in tablets bricked. Do your own research, read thrice, ask twice, flash once.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using the custom recovery
Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step. However - as of today, Feb 27, 2014, another path to installing a custom recovery opened up (again) and that method (using GooManager to install TWRP - see below) requires you to be rooted.
So if you want to root the TF700 on stock firmware there are two ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK). There was some controversy around Kingo. Late last year their threads on XDA got closed because they used the vroot method which had a sniffer component that collected information and sent it to servers in China. The developers of Kingo removed vroot and worked it out with XDA. Their threads got re-opened in December. So I believe Kingo is safe to use - but you be the judge of that....
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: ASUSTeK Computer Inc. -Support-
Select your device, choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v8 (I assume you are on JB 4.2 firmware)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you or use ES File Explorer on the tablet
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. For now I assume it goes ok.
To check if you are unlocked, boot the tablet and read the tiny script. It should say: This device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up.
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows 7/8:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
This is not confirmed to work on Win 8.1, but that may be due to the driver signature verification in Win8. Google how to turn it off.
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for the adb folder) and the corresponding drivers. Takes about 15 seconds
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Linux and iOS: Check out this site https://code.google.com/p/adb-fastboot-install/ or this [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers
The fun begins
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
In Win XP select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
All Windows versions: In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers.
Let's assume everything is good:
On your computer go here: Techerrata Downloads - Browsing tf700t
Download the correct TWRP version for the ROM you intend to flash (see list below)
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock ROM you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom ROM and they are rooted anyway.
Alternative methods to installing TWRP
A) The app GooManager, free in the Play Store, downloads and installs TWRP (currently version 2.6.3.1) on the TF700. But GooManager requires root AND the bootloader to be unlocked. For users who are rooted already or those who cannot get ADB and fastboot to work on their PC, rooting with Motochopper or Kingo and then using GooManger to install TWRP may be a good alternative.
B) sbdags, the developer of CROMi-X (probably the most popular ROM for this tablet) provided a tool that automates the fastboot commands necessary to install a recovery..
I personally believe it is essential to have a working fastboot connection from PC to tablet and becoming familiar with basic fastboot commands when you develop a flashing habit, but if you want to take a shortcut his tool is here: http://forum.xda-developers.com/showthread.php?t=2646279
ROM – Recovery combinations
I assume you are on the 10.6.1.14.10 bootloader
CROMi-X – TWRP 2.6.1 or later http://forum.xda-developers.com/showthread.php?t=2425383
CROMBi-KK – TWRP 2.7.0 http://forum.xda-developers.com/showthread.php?t=2672751
NOTE: Formatting data in TWRP 2.7 takes a lot longer than in previous versions (up to 90 minutes). DO NOT INTERRUPT THE PROCESS if you format /data (usually only necessary with data corruption)
CM11 – CWM 6.0.4.6+ http://forum.xda-developers.com/showthread.php?t=1926286
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Installing a custom ROM
The most popular custom ROMs for the TF700 are CROMi-X, CROMBi-KK and CyanogenMod (CM).
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements.
CROMBi-KK is a mix of CM11 and CROMi-X and at this point still in beta.
CM11 is build from the ground up, emulating KitKat (JB 4.4).
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
Note: Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers
Note: It is recommended (mandatory if you go for CM) to do a Factory Wipe in TWRP before installing a custom ROM.
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
From here on out it's as easy as downloading the installation file of your custom ROM, booting into recovery, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you go for CROMi-X and TWRP as your recovery, make sure you check "verify zip signature" under the Install menu. sbdags signs his ROM zips - a better way to ensure file integrity than md5 sum.
For a general overview and comparison of ROMs check out Gtanner00's thread, post 2 + 3. Note that he describes roms for the TF300, but since the framework for the TF300 and TF700 is very similar there is usually an equivalent rom for the TF700 at the XDA Developers forum.
http://www.transformerforums.com/forum/showthread.php?t=41508
Do not follow or download from any of the links he provides! I only link to his thread for general information!
Any questions - please ask.
AND IF YOU LIKE THE ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Click to expand...
Click to collapse
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
Same thing happened to me. Fastboot recovery command did not return after over 10 minutes. I did Ctrl-C. Ran the command again and got the invalid argument error. Tried a couple times with same result. Unplugged and replugged USB cable (to same USB port). Ran the command again and it worked. When it worked, it took 11 seconds to flash recovery.
Also probably worth noting in the guide is that the Asus boot unlocker requires Google sign-in. If you have 2-step verification setup on your Google account, you need to use a one-time app password to sign-in.
Code:
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
^C
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
OKAY [ 2.704s]
writing 'recovery'...
OKAY [ 8.026s]
finished. total time: 10.731s
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.
I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!
I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.
Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip
plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk
That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....
Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....
Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!