Database Info

Beginners Guide to root and flashing a custom ROM on the TF700T

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 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 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 stock​Or:
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

[Guide][TWRP] Lets make Blackphone 2 great again

IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...

Nice work.
Does this stop the phone checking update servers?

loaded2107 said:
Nice work.
Does this stop the phone checking update servers?
Click to expand...
Click to collapse
Yeah It removes all blackphone apps, but you can modify the script

great work although I have encountered a problem in the pixel laucher that gives me error

script not ok
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot

But how is the phone?
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!

carlosinf said:
great work although I have encountered a problem in the pixel laucher that gives me error
Click to expand...
Click to collapse
Hi, I actually move to another phone, I had Lawnchair installed on bp2
Enviado desde mi PRO 5 mediante Tapatalk

notelinos said:
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
Click to expand...
Click to collapse
Hello, that's a big problem. You must flash files from SD card instead of internal, if you flash from internal storage youll get boot loop and I don't know how to solve that
Enviado desde mi PRO 5 mediante Tapatalk

storkinsj said:
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
Click to expand...
Click to collapse
Sorry mate but I don't know, I'm not a dev. I only posted this to help.
Enviado desde mi PRO 5 mediante Tapatalk

chape199 said:
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Click to expand...
Click to collapse
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks

dgc1 said:
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
Click to expand...
Click to collapse
Hi, i dont use the bp2 anymore since past year but i remember that you have to flash the zips from external sdcard, never use twrp to flash files trough internal. Maybe thats the problem. Hope ive helped you.

Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF

kenfalco_14 said:
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
Click to expand...
Click to collapse
To unlock the bootloader I suppose, but how?

kenfalco_14 said:
To unlock the bootloader I suppose, but how?
Click to expand...
Click to collapse
settings
developer options
oem unlocking - on
restart phone
hold volume down (bootloader mode)
connect usb and do command from PC:
fastboot oem unlock-go
## Your DATA will be DELETED ### make backup

I personally have another problem. I can't see TWRP.
Just black screen.
So i'm trying to fight with it using adb shell...
If I have a root and run all scripts mentioned here, I will explain it here later...

BP2 boot to TWRP
Hi All,
I have read several thread and web pages on how to root, install twrp, rom etc and I can not get it to work.
I was able to update the BP2 to 3.0.14 from .9
All I want to do is change to a custom rom.
I did the following:
-enable USB debugging
-enable oem unlock
-installed platform tools on PC
-adb reboot bootloader
-fastboot devices - phone is there
-fastboot oem unlock-go
-reboot - phone appears to be unlocked
-fastboot flash recovery twrp.img
>Sending 'boot.img' (17392 KB) OKAY [ 0.545s]
>Booting OKAY [ 0.040s]
>Finished. Total time: 0.596s
-fastboot reboot
reboots to blank screen
Do over, and when fastboot reboot, I hold down Volume+
still get blank screen
Any ideas?

David_h99 said:
Hi All,
still get blank screen
Any ideas?
Click to expand...
Click to collapse
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.

speed_boy said:
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
Click to expand...
Click to collapse
Thanks for response.
When I do fastboot devices, it shows thone
Once i do the fastboot.exe boot twrp-3.4.0-0-bp2.img command, it reboots and blank screen.
When I do adb shell, i get "adb.exe: no devices/emulators found"
I do adb devices, and it shows no devices attached
I do have installed "Google Nexus ADB interface" device installed

David_h99 said:
I do have installed "Google Nexus ADB interface" device installed
Click to expand...
Click to collapse
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.

speed_boy said:
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
Click to expand...
Click to collapse
I am not able to find where to change this to "adb interface"
do you know how I can change this?

[GUIDE] Unlocking, rooting & Pixel OS install guide for Pocophone F1

There are already many guides explaining how to unlock, root and install a custom ROM on your Pocophone F1.
But even following the guides, I met multiple issues (access denied to data partitions, boot loops, ADB recovery stopped working ...).
Here is the full procedure that worked for me.
You will need a computer running under Windows for unlocking your phone because Xiaomi only provides a Windows version of its unlocking tool.
I performed the Fastboot and ADB steps under Linux (Ubuntu) because the installation of the tools under Linux is straightforward whereas I had hard times installing ADB under Windows. Moreover, my ADB client sometimes fails to connect under Windows whereas I have no issues under Linux.
Windows steps
-------------------
1/ backup all your personal information (pictures, videos, docs ...) because unlocking will erase all your data.
2/ you have to create a MIUI account from the stock ROM:
- fill in your email address
- set your phone number otherwise Xiaomi won't let you unlock your phone​
3/ Xiaomi constrains you to wait for 72 hours after your MIUI account is created before you're able to unlock.
You have no choice but waiting (users reported that the classical fastboot oem unlock does not work).
The delay may differ from one user to another. Some users even reported a ridiculously long unlocking delay of 720 hours (~ 30 days).
It may depend on your country, phone operator etc ...
4/ download the official Xiaomi unlock tool:
miflash_unlock-en-3.3.827.31.zip
MD5: 8812104e1f6859087f1a9d66481ce9e5
SHA256: 4644878fcaa794d8c0bee67900df80efb28b0d8bd63669d943c043412b06790d​
5/ run miflash_unlock.exe while connected to Internet.
The Internet connection is required because the tool performs a user permission checking before allowing you to unlock your phone.
- fill in again your email address & password
- accept all the annoying Xiaomi disclaimers​
6/ finally you will get a screen with 3 green checkboxes telling you that your phone was successfully unlocked:
{
"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"
}
Linux steps
--------------
7/ install ADB and Fastboot on your Ubuntu system as superuser:
$ sudo apt-get install android-tools-adb android-tools-fastboot​
This simple command is enough for installing all the ADB stuff. Unlike with Windows, you don't need to spend time installing multiple drivers and waste time trying to understand why it doesn't work.
I recommend that all the 'adb' commands are launched as superuser using 'sudo'.
Indeed, some ADB commands will only work as superuser.
Most likely, the ADB path is not set in the superuser environment.
Consequently, you will have to locate the 'adb' path with the 'which' command then launch 'adb' with its absolute file path:
Example with ADB installed under /usr/share/android-sdk/platform-tools
Find 'adb' location:
$ which adb
/usr/share/android-sdk/platform-tools/adb​Launch 'adb' using the found path:
$ sudo /usr/share/android-sdk/platform-tools/adb devices
​
8/ download the following packages and store them all in a new directory called 'adb':
twrp-3.2.3-2-beryllium.img
This is the latest TWRP recovery for the Pocophone F1.
MD5: 3fbf82042f5ea4e332c24cffc6ac1a4b
SHA256: 71a2fb92813fc7c77e7caf2e4b6716dda6cd688d175c56ec6dcdf34a458223b5
beryllium-9.1.24-9.0-vendor-firmware.zip
Under recent versions of Android, the vendor now provides a unified hardware abstraction layer.
Android now relies on this HAL so it can now be released independently from the hardware layer. This new architecture is also called 'Trebble'. The PixelExperience 9.0 released by jhenrique09 on 05/02/2019 relies on the Pocophone Pie 9.1 vendor firmware which must be installed first.
MD5: e931fb719c86f54b12ab4b91857335af
SHA256: 35cd48bab31755287a742ce7dfba4b75343daece2dcf31a27e1a650851e46ae9
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip
This version requires that the Pie 9.1 vendor firmware is installed on the phone.
If you don't, you won't be able to go further and will get the Updater process ended with ERROR: 7 error when trying to flash.
MD5: 804305f334dcb6c1a41b9b2ab91a0ce6
SHA256: 0b8ae9f849971ea14d12065d82fa86fe0051d9570ad08e1008c095757b1fab55
DisableForceEncryption_Treble.zip
This tool will disable automatic encryption which occurs at first OS initialization.
This package includes Magisk 16.7 which will be installed by the script.
This is not the latest Magisk version so we will upgrade it later with the latest Magisk 18.1.
MD5: bb2b91c92aa9d441f41a325438d4a081
SHA256: ba0d9de4474594f01837eebf06edac1daa38775cfa78840cd885c28c5032fae2
Magisk-v18.1.zip
Magisk will allow applications to gain root access to your phone. It does quite the same as SuperSU but it does it better. Magisk pass the SafetyNet test whereas SuperSU generally doesn't. It can also hide itself from apps so they will run as on a stock phone.
MD5: 3ab4d455e6f27f0098c1a723705c6ea1
SHA256: eb06176ea1a2a564a82167902e8159fab13af330f3224c725f04b653232bb527
Magisk-uninstaller-20190204.zip
We will use the uninstaller later to uninstall Magisk 16.7 properly before installing Magisk 18.1.
MD5: 34745c7f3c0d13dbeb5f4223ad887b7b
SHA256: ac80eb0131983c8810fab23d092342e07d1b69b2d91035c027cb7a34ed18f9eb​
Personally, I chose the PixelExperience ROM because it is surprisingly stable and fast for one of the first custom Pocophone F1 ROM.
Moreover and specially if you disable auto-encryption, the phone runs much faster than the stock ROM.
The basic Google Apps are included in the ROM so you don't have to install them separately like you have to do with LineageOS.
Finally, the Pixel interface is very ergonomic and much pleasant to use than MIUI.
Before this, I tried LineageOS 15 then 16 but none of them worked for me. I got some boot loops and it even corrupted my bootloader (look at the troubleshooting section here if you meet the same issue).
9/ if present, remove the SD Card because the system can mess up between the apps installed on the internal storage vs external sdcard.
10/ open a terminal shell
11/ change directory to your 'adb' directory created for storing your packages
12/ with phone unplugged, power off then hold Volume Down & Power to enter FASTBOOT mode
13/ connect your phone to computer using your USB cable
14/ run fastboot devices as superuser to check if your phone is correctly connected:
$ sudo fastboot devices
ad5e3f6 fastboot​
If you see your device listed like here then everything worked fine.
15/ flash the TWRP 3.2.3-2 bootloader:
$ sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
target reported max download size of 536870912 bytes
sending 'recovery' (31004 KB)...
OKAY [ *1.251s]
writing 'recovery'...
OKAY [ *0.312s]
finished. total time: 1.563s​
The flash command will reply 'OKAY' twice if flashing is successful.
16/ you now have to reboot to recovery directly from FASTBOOT mode otherwise your recovery will be overwritten by stock ROM if you reboot to system. This is performed by invoking fastboot with the boot argument.
$ sudo fastboot boot twrp-3.2.3-2-beryllium.img
downloading 'boot.img'...
OKAY [ *1.216s]
booting...
OKAY [ *0.064s]
finished. total time: 1.280s ​
The TWRP splash screen should now show up.
17/ TWRP 3.2.3-2 handles decryption but I chose to work without encryption for several reasons:
- you might be unable to use your external SD card outside your phone because of encryption,
- your phone will run faster,
- certificates could probably be revoked remotely by manufacturers or Google so you can lose access to your phone and data.
If your partitions are encrypted (which is the case if you're coming from MIUI), you should format your data partition to restart from an unencrypted partition. Formatting will erase all your data so check you're backed up before doing it.
18/ you now have to reset your phone to perform a clean install.
As far as I am concerned, I advise wiping everything to start from a fresh brand new system.
To do so, tap Wipe, tap Advanced Wipe then check:
* Dalvik / ART Cache
* Cache
* System
* Data
* Internal Storage​Finally, swipe to wipe.
19/ tap Back arrow then Reboot and finally Recovery
20/ plug your phone with USB cable to your computer.
21/ first of all, kill any running ADB daemon. We do it to be sure ADB daemon is started as superuser.
Indeed, some ADB commands won't work if not superuser.
$ sudo adb kill-server
​Then check that ADB is working from recovery by typing the command:
$ sudo adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ad5e3f6 recovery ​
The 'daemon started successfully' output notifies you that ADB daemon just started.
If your device is listed then everything is fine.
22/ go to your 'adb' directory then type the following command to copy all the packages to the /sdcard phone directory:
$ sudo adb push beryllium-9.1.24-9.0-vendor-firmware.zip /sdcard
beryllium-9.1.24-9.0-vendor-firmware.zip: 1 file pushed. 21.5 MB/s (442907715 bytes in 19.651s)
$ sudo adb push PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip /sdcard
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip: 1 file pushed. 21.4 MB/s (1065939977 bytes in 47.478s)
$ sudo adb push DisableForceEncryption_Treble.zip /sdcard
DisableForceEncryption_Treble.zip: 1 file pushed. 21.3 MB/s (4447302 bytes in 0.199s)
$ sudo adb push Magisk-v18.1.zip /sdcard
Magisk-v18.1.zip: 1 file pushed. 21.4 MB/s (4362466 bytes in 0.194s)
$ sudo adb push Magisk-uninstaller-20190204.zip /sdcard
Magisk-uninstaller-20190204.zip: 1 file pushed. 21.2 MB/s (2290127 bytes in 0.103s)​23/ go to main TWRP main menu then tap Install then tap beryllium-9.1.24-9.0-vendor-firmware.zip to install.
The vendor firmware must be installed prior to the ROM which relies on it.
If you forget this step, you will get a Updater process ended with ERROR: 7 error when trying to flash the ROM.
24/ go to main TWRP main menu then tap Install then tap PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip to install.
25/ go to main TWRP menu then tap Install then tap DisableForceEncryption_Treble.zip to install.
DisableForceEncryption_Treble will prevent the ROM from auto encrypting your phone upon first initialization. It also install Magisk which will give you root access.
Note that you can skip this step if you want to keep your phone encrypted.
26/ go to main TWRP menu then tap Install then tap Magisk-uninstaller-20190204.zip to uninstall any existing version of Magisk. The DisableForceEncryption_Treble also installs Magisk 16.7 so this step is required for a proper removal.
27/ go to main TWRP menu then tap Install then tap Magisk-v18.1.zip to install.
28/ now, boot to System.
29/ If you installed DisableForceEncryption_Treble then your phone will initialize without encryption.
30/ you now have to link your Pixel OS phone to your Google account and install your apps.
YOU ARE ALL DONE
Congratulations !!! you now have a Pixel OS and rooted system installed on your Pocophone F1.
TROUBLESHOOTING
-------------------------
Before installing Pixel OS, I had hard times trying to flash LineageOS on my Pocophone F1.
For a reason, it corrupted the bootloader and ADB server stopped communicating with my computer.
I thought I bricked my phone but I successfully restored everything by following those steps:
1/ boot to TWRP by holding Volume Up & Power
2/ tap Wipe
3/ tap Advanced wipe
4/ check everything except USB-OTG then swipe to wipe all.
5/ hold Power button for a long time, the phone will then try to boot to System but fall back to FASTBOOT because we just erased the system partition at the previous step.
I advise that you follow exactly this procedure. I can't explain why but I first reboot to FASTBOOT from the TWRP menu but doing like this did not fix the ADB recovery server which still kept unresponsive after reflash.
6/ reflash TWRP by running again sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
7/ hold Volume Up & Power buttons to boot again to TWRP recovery.
8/ connect your phone to computer with USB cable.
9/ type adb devices and you will see your device again.

Cristobal2018 said:
$ adb push beryllium-8.11.7-9.0-vendor-firmware.zip /sdcard
beryllium-8.11.7-9.0-vendor-firmware.zip: 1 file pushed. 22.3 MB/s (402068528 bytes in 17.164s)​
Click to expand...
Click to collapse
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?​

kousarali said:
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?
Click to expand...
Click to collapse
You're absolutely right.
If you forget flashing the vendor firmware before PE, you'll get a system error 7 when trying to flash the PE ROM.
Many people encountered this error when this ROM was released.
I updated the tutorial.
Thanks!

Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
The other way to find the link is searching Google for the MD5 or SHA256 signature.

Cristobal2018 said:
The other way to find the link is searching Google for the MD5 or SHA256 signature.
Click to expand...
Click to collapse
akashkyh said:
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy
Click to expand...
Click to collapse
Thanks a lot guys.

I updated the guide with the official links to the packages.
The package names are now all clickable.

if i already installed disable force encryption zip during rooting procedure do i need to flash it again in step 27

Hi, even though i have flashed the vendor firmware, i got error 7 for pixel rom. I dont know what is the problem. I do wipe for all and flash vendor zip. But got error7 in pe Rom

Question
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance

Antidote03 said:
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance
Click to expand...
Click to collapse
I just tried to flash the latest PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL and it raises a system error 7 complaining for the missing vendor 9.1 firmware.
According to the https://downloads.akhilnarang.me/MIUI/beryllium/ download page, you will notice that akhilnarang released vendor beryllium V10.1.3.0-9.0 vendor firmware a long time ago (december 2018).
Consequently, for flashing the latest PixelExperience ROM (20190205), I would advise to first flash vendor 9.1 available here: beryllium-9.1.24-9.0-vendor-firmware.zip

Is it really necessary to flash DFE (step 27)? Thank you.

Thank you so much for the comprehensive guide. I got my Poco F1 yesterday and I have a good idea what I need to do, but there's always some uncertainty.
DFE being the one question I have, but you explained it etc, so it looks like at this point it is recommended, but not necessary as such - if I understand.
Vendor firmware is another question mark for me, but it makes a bit more sense.
Right now, I am just going to look at rooting my phone, once I'm done with that I will start looking at custom ROMS.
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
I almost think that if it's just rooting via magisk you don't need to swipe right. since I don't think magisk touches system (but not sure).
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).

autisticarvin said:
Is it really necessary to flash DFE (step 27)? Thank you.
Click to expand...
Click to collapse
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.

Cristobal2018 said:
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.
Click to expand...
Click to collapse
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.

autisticarvin said:
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.
Click to expand...
Click to collapse
Of course, I should have written 'flash' instead of 'root'

d.casper.b said:
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
Click to expand...
Click to collapse
Rooting allows the applications to run as root so the only requirements for doing it is having the root permissions. In recovery mode, TWRP already has the root permission so it should be enough.
I can't tell for sure because I did not test it but I would say as long as you don't require to write to the system partition, you don't have to swipe right. Magisk is not installed on the system partition so swiping should not be required.
d.casper.b said:
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).
Click to expand...
Click to collapse
Installing TWRP while leaving the stock ROM installed is not a good idea.
Indeed, the stock MIUI performs an integrity test at boot time and it restores the stock ROM if a different one is found (like TWRP). At reboot, your TWRP will be overwritten with the stock one.

Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!

CobraStrike said:
Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!
Click to expand...
Click to collapse
You can do this by using the ADB tools for Windows

TWRP on HTC U11 Life

Hi!
I unlocked the bootloader on my HTC U11 Life. I would like now to put TWRP on my phone. I read many tutorials and understood that I should simply download the .img file and then run:
Code:
adb reboot download
fastboot flash recovery twrp.img
But if I do so, I obtain the following error:
Code:
target reported max download size of 1147200000 bytes
sending 'recovery' (46444 KB)...
OKAY [ 2.724s]
writing 'recovery'...
(bootloader) HOSD CL#1055045
(bootloader) [email protected]
(bootloader) ERR flash_partition_by_file, partition recovery is not foun
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 23 RU_READ_PARTITION_FAIL read/open partition fail )
finished. total time: 4.844s
My issue is then really similar to the one reported at https://forum.xda-developers.com/t/need-help-to-put-twrp-on-htc-u12.3835381/
But in my case, the answer given by Tachi91 does not apply as it only valid for HTC U12.
Could someone please help here?
Best,
Lucas
EDIT:
I found this post https://forum.xda-developers.com/t/htc-u-11-life-twrp-problems.3872208/ with a similar problem. I bought the HTC U11 reconditioned, I can't tell if it comes from Germany (I'm French).

Hello there, I've just had the same problem. There is no TWRP version that I could flash on U11 life. It might not have a recovery partition and you probably can't do it this way.
You can just boot it though. Give this recovery a try. Reboot your phone into bootloader mode, then use fastboot boot <name of the image>. This worked for me, but I had less luck with a Lineage GSI ROM.
Also, you may want to read about my trial in this thread.

Hi!
Thanks for your anwer. Well that's too bad, I chose this mobile because it seemed easy to me to install Lineage OS ... I guess I will have to keep Google on my phone.
Thanks !

LucasPa said:
Hi!
Thanks for your anwer. Well that's too bad, I chose this mobile because it seemed easy to me to install Lineage OS ... I guess I will have to keep Google on my phone.
Thanks !
Click to expand...
Click to collapse
No! You don't have to keep Google on your phone, there is a solution that works with your stock ROM!
You can achieve a systemless root with Magisk and then you can disable or even delete any Google app you desire. Always get Magisk only from the GitHub page (Downloads section, Magisk button, download the APK)!
Start with this TWRP recovery. You most likely won't be able to flash it, but you can surely boot it. From bootloader mode run fastboot boot U11_twrp-3.2.1-0.img. Then install the Magisk APK. I used ADB sideload from some Advanced menu of TWRP recovery. Once your phone is ready, execute adb sideload Magisk-v22.0.apk on your PC. A console should appear in the recovery detailing installation process. It should write about some bootloader modifications or something. Should complete without errors.
After this, you should have achieved root when you reboot the phone. You will also have Magisk app installed, should display Magisk installation info and it also comes with a neat prompt, that displays when an app requests root privileges. The only thing left to do is to disable/uninstall **** you despise with an app like Package Manager. A word of advice: always disable a suspicious app first and see what happens. If it is indeed necessary for something, you can re-enable it. If you delete it, there is probably no way back save for factory reset, or maybe even that would not bring it back. In the latter case you'd have to reinstall the stock ROM, I'd say.
Common things you'll probably want to get rid of are Google app, Play Store, Play Services (you need the services enabled for phone update menu to appear!), Google keyboard, some OK Google and other consents, partner setup, Google phone, contacts and messaging apps (you can use Simple Dialer, Simple Contacts and QKSMS instead; for Simple Apps also install Simple Thank You so you can set a common colour theme for them), and Carrier Services (this one also complains if Google Play Services are disabled). There's also some Qualcomm Mobile Security, which seems like a telemetry service, and Qualcomm QMMI (you should probably leave this one, saw some information on the net).
Long story short, you'll be able to disable and delete anything. I recommend you stick with disable, though I've crossed that line for some Google nonsense.

[Solved]TWRP on Blackview BV 4900 Pro

(Sorry if this is the wrong place to post, I could not find a forum for the blackview bv 4900 pro)
I am trying to install TWRP (unofficial build at https://unofficialtwrp.com/twrp-3-5-2-blackview-bv4900-pro/ ) on my Blackview BV 4900 Pro, seems to be able to transfer it to my phone, but cannot start it. The files vbmeta.img and recovery.img come from the previous link, respectively https://unofficialtwrp.com/wp-content/uploads/2019/11/vbmeta.zip and https://www.mediafire.com/file/hq4sq1xlnkafduv/352_BV4900_pro_lopestom.rar/file .
Firmware: BV4900Pro_US_ZN128e_V1.0_20211119V08_20211119-2023
What I have done:
- USB debugging on,
- OEM unlocking,
- Re-start in fastboot mode,
- Plug phone to computer
- In terminal:
Code:
fastboot flashing unlock
< waiting for any device >
...
(bootloader) Start unlock flow
OKAY [ 4.394s]
finished. total time: 4.394s
(I confirmed on the phone that I wanted to unlock by pressing the volume + button),
-
Code:
fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.011s]
finished. total time: 0.011s
-
Code:
fastboot flash vbmeta vbmeta.img
target reported max download size of 134217728 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.007s]
writing 'vbmeta'...
OKAY [ 0.002s]
finished. total time: 0.009s
-
Code:
fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (23588 KB)...
OKAY [ 0.762s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 1.075s
- Unplug phone
- Turn off phone by pressing & maintaining power + volume +,
- Keep pressing power + volume +,
- See the "Select boot mode" page (that gives me the options to select Recovery mode / Fastboot mode / Normal boot),
- Select "Recovery mode",
- See Blackview's logo + the message "Orange state", then the phone becomes irresponsive. It is still turned on, but nothing on display. I can run
Code:
adb reboot recovery
and it will reboot, but again in orange state, then it reboots to the "normal" system.
What am I missing? Is this version of twrp unsuitable for my phone?
Apparently there used to be a twrp at https://4pda.to/forum/index.php?showtopic=789936&st=2060#entry110507536 but it is not available anymore :-(

Apparently there was another twrp developed for this phone, shared at https://4pda-to.translate.goog/foru...=fr&_x_tr_hl=fr&_x_tr_pto=wapp#entry111020420 but the link is in error too :-(

I was able to flash a different firmware on the phone ( BV4900Pro_S1_210909 ), but the result is still the same.
Once rebooted (in recovery), the screen is still black (after a green line briefly flash at the top of the screen). The phone is still on :I can do
Code:
adb shell
BV4900Pro:/ #
But then if I try, following this post ( https://forum.xda-developers.com/t/guide-flashing-roms-with-twrp-black-screen.3913052/ ), I try to use twrp from the command line, then it seems that it is not started:
Code:
BV4900Pro:/ # twrp wipe cache
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.

The files at
Стол заказов кастомного рекавери - 4PDA
Стол заказов кастомного рекавери
4pda.to
works, but you have to create an account to download them.
There is a tutorial on how to pass those captcha at https://doorsgeek.blogspot.com/2015/08/4pdaru-loginregister-captcha-tutorial.html

Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).

WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse
Hey! Sorry for the very late reply. They are attached. I am sorry they are not working on more recent versions of that phone, and honestly have no idea how to update them :-(
Keep us posted!

WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse
Hey btw you don't neeed twrp to flash GSI, just so you know…
Not as good as lineageOs, bat with fewer bloatwares and more up-to-date than what your phone cme shipped with.
[SOLVED] GSI on BV 4900 Pro: "Cannot load Android system. Your data may be corrupt. "
tl;dr: I followed the procedure to flash Android's Generic System Image (gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1) on my Blackview BV 4900 Pro, but I am stuck in a bootloop that ends with "Cannot load Android system. Your data may be...
forum.xda-developers.com

I have the 2022 Version too. I try to flash the 2021 Version lk.bin (bootloader) and hope it works. Because the 2022 lk.bin don't play nice with a empty vbmeta.
WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse