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

[ROOT] [TWRP] Gigaset ME/ME Pro

Latest video: https://youtu.be/o6cpMa2Fo_c
Since 01.16 update Gigaset Me and Me pro use same ROM. So read carefully and take responsibility what you are doing on you device.
Gigaset Pure is not supported here.
GPL Source codes:
Me/MePro/ platform tools full : http://www.gigaset.com/de_de/cms/lp/open-source.html
Me/MePro platform tools uploaded in 1 file (gdrive): https://drive.google.com/uc?id=0B_81lkQEKce4bFlaRXk3dFFwQzA&export=download
Me/MePro kernel source (my repo on github): https://github.com/Eddie07/GIgaset_Me_MePro_3.10._kernel
Terms of Usage:
1. Everything posted on this post should be reposted with links to original post.
2. I'm not responsible for any damage to your phone.
3. If you are aware of bricking device by this or you don't understand some of processes described below - close this thread and leave it alone.
4. If you agree with p.1,2,3 go on to Step2.
GIGASET secret codes:
*#*#4636#*#* - phone info
*#*#2580#*#* -engineer mode (wif, bt tests, usb ports, adb root (pass:gigaset001), ota settings.
*#*#708#*#* - float system info (cpu speeds, m|b temp), shake test.
*#*#801#*#* - wifi test.
*#*#802#*#* - bt test.
*#*#803#*#* - bt test 2.
*#*#2588#*#* - factory hardware tests.
*#*#2581#*#* - Camera callibration??.
(Only ME/MEPRO)TWRP CUSTOM RECOVERY, UNBRICKING:
-FLASH CUSTOM RECOVERY ON ME/MEPRO HERE
-UNBRICK SOLUTION back to rom EU00_V1.1.20160616R ME/MEPRO (if you deleted system, recovery, boot) : BACKUPS--- UNBRICKING
(Only ME/MEPRO)CUSTOM ROMS:
LAST CM 12.1
(Only ME/MEPRO)PATCHES TO STOCK ROM TO BE INSTALLED VIA CUSTOM RECOVERY:
LAST MY "TUNED" TWRP BACKUP https://forum.xda-developers.com/showpost.php?p=71180342&postcount=371
-PATCH#1 TWRP PATCH ME/MEPRO for CPU speeds uncap (1,9ghz), Thermal config fix, Fix of display size MePro HERE
-PATCH#2 Enable 4K video recording in stock camera app HERE
-PATCH#3 Enable Callrecording button in stock dialer app HERE
-PATCH#4 READ DESCRIPTION HERE
-PATCH#5 SystemUI patch HERE
ADB ROOT FOR STOCK ROM WITHOUT ROOT AND CUSTOM RECOVERY:
- Unlocking Me/Pro abd root via factory tool hidden in rom. (usage for Gigaset Me/Pro/Pure)
1) Type in dialer: *#*#2580#*#* to get in Engin. tool
2) Select "priviledge" tab.
3) Type "gigaset001" in pw field.
Get adb root
to check if is done enable USB debugging and try adb command from PC:
"abd shell" if command prompt ends with "#" then adb is rooted, if "$"-isn't!
4) Turn off adb root- type password again.

Thank friend

GaulCrixus said:
Thank friend
Click to expand...
Click to collapse
You are able to install Supersu via abd (you can find manuals on internet).
But if you copy wrong files, or even update binary on purpose in SuperSU gui, you are risking to get bootloop or stuck on ANdroid logo.
There is no way to recover (YET). But im on my way to test something.
So you are warned!

Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?

Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.

I emailed Gigaset support and asked about the Marshmallow update and they said its not ready yet but would be at some point, I have read on German forums that no one replies when asked about updates.
Getting CM or PacROM for this would be great.
imkrl said:
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Click to expand...
Click to collapse
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
heineken78 said:
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
Click to expand...
Click to collapse
I cant expand the images in your post.

typos1 said:
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
Click to expand...
Click to collapse
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
# #ifdef GIGASET_EDIT
# /*[email protected], 2015/08/20. added. add root mode for release build */
#ifeq ($(TARGET_BUILD_VARIANT),user)
persist.sys.root.enable=none
# /* [email protected], 2015/10/29. added. add feature to reserve pictures when doing 'Factory data reset'.*/
sys.root.wipedataless=false
#endif
# #endif /*GIGASET_EDIT*/
Click to expand...
Click to collapse
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.

heineken78 said:
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
Click to expand...
Click to collapse
Yes, I realise that, I do get a #, I was just pointing out to @imkrl that nothing appears to happen on the phone from looking at the screen, but something does actually happen
After removing from adb and installing SuperSU, SuperSU says its not rooted.
I ll do the dump and upload later.
On the German forums people say that no one from Gigaset replies to messages and that support has been dropped, but that is not official, it is just people's assumptions, when I contacted Gigaset I DID get a reply saying "it will happen automatically", not "we have dropped support", so maybe support has been dropped, maybe not, nothing has been officially said by Gigaset.
But dropped or not getting support for custom ROM like CM of PACrom would be good.

typos1 said:
After removing from adb and installing SuperSU, SuperSU says its not rooted.
Click to expand...
Click to collapse
Right, root is only for adb. But advanced users could push some files in device via adb root# and get supersu working too.
But its quite risky, if you made a mistake, then device can no boot to android anymore (ex. bootloop). Then is bricked.
-You cant access partitions from fastboot - is completely factory locked. (even :"fastboot reboot" doesn't work. fastboot don't listen to any command)
-factory recovery not allows to use adb or view files.
Everything points to have custom recovery.
Another thing if you got su working by pushing files, some system files became modified by supersu and with next OTA update, by security check, OTA will fail to update (patch). So you need system partition backup to restore it on demand.
There is one way to hard unbrick to use "edl" mode (QUALCOMM 9008) (switched phone, hold vol-down, connect usb). I have idea how to but I didn't test, cos I don't want to take a risk to erase memory of my working phone.
To avoid all risks, have to flash custom recovery TWRP from android, within you will be able to restore everything and install supersu normal way. What ever you change from recovery: flashing zip's, installing backups or getting bootloops after, you will be able to load custom recovery again and fix from it. Before installing of custom recovery, backing up of recovery, boot and system partitions should be done, also have to check devinfo partition of your device to be insured that bootloader is unlocked, because if bootloader is locked it will ignore not signed recovery or any boot images.
Yes this is all backdoor and hard to do if you are rokkie in this, but 100% working methode. There is no any Kingaroot or other working roots for Gigaset, cos android security of Gigaset is very high, even with 5.1.1 version.
Why I need your files, typos1: recovery, boot and devinfo. To check them if they are same with Me pro, if not to make another custom recovery for me device.
Sure I will try to make rom ports, may be someone else will do it, cos root is found by me after on second day of device usage, while device was one year on market and lost interest of many. Btw custom recovery source was taken from OnePlus2, hardware +- is similar.

step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do

xueyaotianxia said:
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
Click to expand...
Click to collapse
Device?

reply
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.

xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
Mine came from China (they ALL do, thats where theyre made !!) and mine does have the Playstore.

xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
No way to root yet with common ways. Only via adb shell or via recovery.
But Me and Me Pro have same platform, so take a look what you have at ls dev/block/platform/f9824900.sdhci/by-name/. Use this command in adb shell and write me the list of partitions.
If you get error, Gigaset Me may have different storage name (not f9824900.sdhci as me Pro I own). so try ls dev/block/platform/ and find right name of storage, then ls dev/block/platform/STORAGENAME/by-name/ shows list of partitions.
Guys I need partitions of Me!

After I typed ls dev/block/platform, it shows this:
f9824900.sdhci
f98a4900.sdhci
what should I do now?
Thank you..
---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------
I would guess your device is made for oversea's market...so that is why it has playstore pre installed...I bought mine in China (which made for Chinese market, by law no google)...it makes life so much more difficult, as I have to install 3rd party app store...cannot root the phone now so whenever I open play store it shuts down immediately.
---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------
After I typed this ls dev/block/platform/f9824900.sdhci/by-name, it shows:
DDR
aboot
abootbak
apdp
bluetooth
boot
cache
config
devinfo
dpo
fsc
fsg
hyp
hypbak
keystore
limits
misc
modem
modemst1
modemst2
msadp
persist
pmic
pmicbak
recovery
rpm
rpmbak
sbl1
sbl1bak
sdi
sec
splash
ssd
system
tz
tzbak
userdata
that is all.
I went back tried step 2 again, it shows 01. But when I tried step 4 to do the recovery it says:
aset-me.img of=dev/block/platform/f9824900.sdhci/by-name/recovery <
0 records in
0 records out
24 bytes transferred in 2.347 secs <10504398 bytes/sec>
recovery seems still the old factory one.
---------- Post added at 09:51 PM ---------- Previous post was at 09:39 PM ----------
Hahaha I tried step 4 again it worked!! Now I am in Team win recovery project v2.8.7.0
What should I do now to root the phone??
Thank you very very much you saved the day!!!

xueyaotianxia said:
Thank you very very much you saved the day!!!
Click to expand...
Click to collapse
Download and install supersu.zip
Notice, you have to disable engineering menu root (type password again), because factory adb root and another (supersu) will have conflicts.
So confirmed that this recovery works on Gigaset Me too!
thank you

thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??

xueyaotianxia said:
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
Click to expand...
Click to collapse
You have messed up. Suggest to restore system.img or if you done system backup in twrp and try root again.

Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?

xueyaotianxia said:
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
Click to expand...
Click to collapse
You should do backwards procedure to restore system image. Better if you do it while in TWRP recovery.
1) Open TWRP recovery and connect to PC
2) In adb shell on pc: dd if=sdcard/systembackup.img dd of=dev/block/platform/f9824900.sdhci/by-name/system
Where systembackup.img name of backup image you done stored on internal memory. This will overwrite system partition to previous state.
For next time I suggest you to make backup in TWRP normal way. It will be faster.

Coolpad Rogue (3320A) Stock Recovery, Kernel, Modem & Firmware Images

Coolpad Rogue 3320A - Stock 5.1.1 Build No. 5.1.157.00.T2.150810.LMY47V
Fastboot Flashable Recovery, Kernel, Modem & Misc. Firmware Images
Disclaimer You flash these images at your own risk. I am not responsible for bricked or otherwise inoperable devices as a result of flashing any of the files provided herein.
These partition images will help you recover a soft bricked device in the event you have missing or corrupt partitions. Additionally, in the event you are having signal or connectivity issues, flashing the modem/radio firmware could resolve those problems. I have provided all partition images for the 3320A with the exception of /system and /userdata. The stock /boot and /recovery images are always good to have in case you ever need them. At a minimum, save these images to external storage in case of future need. I will provide a full /system image in future at request.
WARNING Flashing bootloader or bootloader dependent partitions can result in a hard bricked device. Please do not flash bootloader type partitions unless you are well versed in this area. Tampering with these particular partitions is best left for developers and experts. I will clearly label any bootloader type partitions, in hopes that it will alleviate any confusion.
INSTRUCTIONS:
Install Minimal ADB and Fastboot on your PC or Laptop. The installation files can be found here on XDA Forums. Install the USB Drivers for your Coolpad Rogue 3320A. (The drivers are pre-installed on the device itself. If you are able to boot up, connect your 3320A to your PC and look in your PC's directory for an installation option.) Place the .img files you need on an external SD card or in internal storage. With your device powered off, boot into Recovery Mode by holding power and +volume simultaneously until the Coolpad logo appears -- then let off of power but continue to hold +volume until the stock recovery screen appears. Use your volume button to scroll down to Bootloader and press power to select. When the Fastboot screen appears, connect your device to your PC with a suitable micro USB syncing cable and press +Volume. In your Minimal ADB and Fastboot directory open a command window (Shift and Right Click).Type: fastboot devices If you are properly connected, your device serial number will be displayed in your command window under connected devices. If your serial number doesn't appear, repeat the above steps, ensure your USB drivers are installed correctly, and try changing USB ports on your PC or trying a different cable. Once you are connected properly, the rest is simple: I have named each partition image synonymous to its corresponding partition. In other words, the name of the file is also the name of your device's partition to be flashed.
EXAMPLE If you are flashing the "carrier" partition, you simply type fastboot flash carrier carrier.img Again, I will label each partition as to the type (e.g. recovery, bootloader, modem firmware, etc.)
DOWNLOAD LINK:
https://drive.google.com/folderview?id=0B7-zQU1VihD3eXE1SjBIby02Rmc
PARTITION NAME / TYPE
tz - "Trust Zone" Bootloader Dependent Partition
tzbak - Allotted Partition Backup of tz
ssd - Firmware Partition
sec - Firmware Partition
sbl1 - Secondary Bootloader
sbl1bak - Allotted Partition Backup of sbl1
rpm - Primary Bootloader
recovery - Stock Recovery Image
persist - Firmware Partition
params - Firmware Partition
panic - Firmware Partition
pad - Firmware Partition
oem - Manufacturer/Device ID Partition
modem - Radio Firmware
modemst1 - Radio Firmware
modemst2 - Radio Firmware
misc - Carrier/Region ID Partition
keystore - Firmware Partition
fsg - Radio Firmware
fsc - Firmware Partition
devinfo - Manufacturer/Device Info Partition
ddr - Radio Firmware
config - Carrier Specific Info Partition
boot - Stock Kernel/Ramdisk
aboot - Application Bootloader Partition
Hopefully this guide will help you restore your device from an inoperable state or restore connectivity from problems originating from damaged/corrupt partitions.

Relaying A Message from MotoJunkie01
Relaying A Message from MotoJunkie01
I apologize for not being in closer contact. I have some pressing issues going on and, coupled with work, man I've been tied up something awful. I'm going to need to drop off XDA for a month or better to get my personal issues attended to. I need a huge favor from you.
My little threads I have started, if you could go on and explain I'll be gone for a month or so. I'd appreciate it.
I've Not enough time to even do that.
So if anyone needs a reply I'd figure sometime in July, and I hope you all will understand and allow this time for MotoJunkie01 to attend to his personal matters. Signed: ResistanceIsFutile

Link not working
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files

Gamesmedic said:
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files
Click to expand...
Click to collapse
Sorry about the broken link. I just added a new working link with all listed firmware images.
You are obviously extremely confused about the purpose & function of fastboot commands. Allow me to educate you a bit. First, contrary to your statement, fastboot does not "push" files. And it most certainly does not push "zip files." In fact fastboot cannot be used to manipulate zip archives at all. . If you go back and read the thread, fastboot is used primarily, and as a preferred method by many, to flash firmware images to your device. (.img, .bin, mbn, etc) The firmware images in my link can be flashed to the Coolpad Rogue, via fastboot, to restore the partitions to pure stock/factory condition, in the event of a soft brick, bootloop, corrupt OS, etc.
I hope this clears your confusion some, before you hard brick a device trying to "push zip files" with fastboot.

Sim unlock
would this help to do a sim unlock

rachinda said:
would this help to do a sim unlock
Click to expand...
Click to collapse
No. SIM unlocking involves an entirely separate procedure. I am not even sure a SIM unlocking procedure is available apart from using a remote unlocking service or requesting an unlock code through the carrier directly. This thread is merely a source for stock firmware partitions for devices which are stuck in boot loop, soft bricked, poor or lost cellular service, connectivity issues, etc.

Cubot King Kong custom ROM or Android go?

Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.

Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.

does anyone have a scatter file or custom recovery for this phone? how did you root?

CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip

aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms

Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s

What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img

i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied

Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16

Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result

LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?

Use an app from google play called Device Info HW

Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)

Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).

Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.

In gt1x its because of this:

So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.

And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.

aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance

please do a read back for boot.img and recovery.img with SP Flash Tool

Downgrade/Unbrick Huawei device (if other methods doesn't work)

This is Generic guide for Unbricking or Downgrading Huawei devices with Kirin 960 CPU. Most probably very similar steps can be done for Kirin 970, but i don't have device to test. At the end i did attach my files, that i used for CMR-W09.
This WILL WORK even if you have Black Screen with permanent Fastboot - this is common issue for those, who tried to downgrade from EMUI 9 to EMUI 8. Yes, this is also unbrickable!
Have Fun!
1. Prerequisites
- Linux installed on your PC/laptop or as Virtual Machine, with fastboot tool on it
- Board Software for your device – you can find on easy-firmware.com (about $15 for pass and reach collection) or gem-flash.com (has cheap $3 pass but less firmwares in collection)
HiKey_IDT linux tool – can be found there https://github.com/96boards-hikey/tools-images-hikey960/
- Knowledge about test point location to interrupt CPU loading routine – ask google or look on this forum
http://forum.gsmhosting.com/vbb/f1022/huawei-test-point-gallery-2291781/index17.html
- Opened device – you need access to motherboard
2. Booting device in force update mode
Small intro. Hisilicon Kirin CPUs has special mode, when they are interrupting normal boot process and opening COM port on USB to accept commands. You have chance to load your own binaries directly to device RAM before boot process will continue (still, this images has to be signed by Huawei private key)
- Disconnect battery connector from motherboard
- Short test point to ground (any big metal shield on board will work for that)
- Having test point shorted – connect USB cable. Run “lsusb” command – you should see device “USB SER” in devices
- Open folder with Board Software. Find xml file with model name in name, for ex. “CMR-W09-BD_1.0.0.19_Download.xml”. In that xml file – check section for “bootloaderimage” – you will find paths and memory addresses for all needed boot stages. Keep that open.
- Find all three boot img files – copy them to Linux machine. Note: For me, this three files didn’t work. But I found files with same names in other folder of Board Software – and that did a trick. You have to experiment a little bit.
- Go to folder, where you have HiKey_IDT tools downloaded. Copy three boot files from Board Software to same folder as hikey_idt. Edit “config” file – you should specify correct address and file name – according to Board Software
- Check “dmesg” command output – look for GSM Modem connected messages – you will see port name attached – like ttyUSB0
- Run next command “./hikey_idt -c config -p /dev/ttyUSB0”. You should see information about loaded all boot stages, with “Finish downloading” message after each. If you did everything fine – in 5-15 seconds you will have your device ready for downgrade/unbrick/killing_your_cat
- To verify that everything is fine – run “fastboot devices” command. If it will show device with proper serial number in output – you are fine to continue
3. Fixing your device
On that step – you have special fastboot booted, that has no security/validation on it. You can unbrick your device, or kill it. Do all steps carefully.
- Flash proper partition table information. You can take it from OTA package (from inside of UPDATE.APP) – normally, it has name HISIUFS_GPT. Run “fastboot flash ptable HISIUFS_GPT.img”
- Flash other partitions one by one. Skip files CRC.img, SHA256RSA.img, CURVER.img, VERLIST.img, PACKAGE_TYPE.img and HISIUFS_GPT.img (it was already flashed on previous step). To flash this files, run “fastboot flash” with partition name and image file name after it – for ex. “fastboot flash recovery_vendor RECOVERY_VENDOR.img”. Note: Partition names should be written in lowercase. You can see partition names in Huawei Update Extractor, as extracted image files sometimes has shortened names.
- Run few more commands to cleanup things around:
Code:
fastboot erase misc
fastboot erase modemnvm_factory
fastboot erase bootfail_info
fastboot erase dfx
fastboot erase rrecord
fastboot erase patch
- Flash few more files – from Board Software:
Code:
fastboot flash splash2 splash2.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase version
fastboot flash version version.img
fastboot flash reserved4 gpu_test_data_all_v2.bin (may be different for other devices – look into XML file from Board Software package for any “reserved” partitions)
- Remove USB cable, connect battery back and boot your device. Most probably your device will boot now! Or at least it will try
4. Final steps
- Make factory reset from stock recovery!
- Make 3-button flash of same or newer firmware just after restoring device!
- Make backup of your NVME and OEMINFO! Use next commands for that:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img
dd if=/dev/block/bootdevice/by-name/nvme of=/storage/emulated/0/nvme.bak
Above commands are for adb shell with root. If you will do that under TWRP – you can use “of=/sdcard” in dd commands
Note: If your device is in bootloop, but runs recovery/eRecovery fine. If recovery is showing error during factory reset – maybe, you have screwed your nvme during previous upgrades/downgrades. In that case – make NVME backup using TWRP, take nvme.img from Board software package. Using any HEX editor – open both files, and copy all variable values from your backup to nvme.img from Board – manually. After doing that – repeat all steps from beginning until getting forced fastboot mode, and flash this image with “fastboot flash nvme”
P.S. In above links you may find lovely-prepared files for CMR-W09 tablet with region C432 for recovering to b161 firmware (includes recovery.sh script to flash everything in one command) - it can be used to get $4 unlock code with DC Unlocker.
HiKey_IDT => https://drive.google.com/open?id=1EdNfHVc8japoVSe2k4iTWdyp5JyPa1LR
Recovery Files for CMR-W09 C432 B161 => https://drive.google.com/open?id=1YgwwwFITjbJ8vIepcCt0O5w_RRJcKV8F
Board Software for CMR-W09 => https://drive.google.com/open?id=1w3mfVt8ObsViiv5ov3cUAog-M8hHMaSF
Testpoint location on Mediapad 10.8 (should be same on both Pro and non-Pro)

Reserved

Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!

crckmc said:
Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!
Click to expand...
Click to collapse
Nah, i'm not looking for fast ways! Decided that i can do it by my own ))) Btw, service center will not even try to repair your tablet - they will replace whole logic board or whole tablet.

For me It gives errors, I used my own device board fw.

Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board

goodwin_c said:
Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board
Click to expand...
Click to collapse
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.

yoghurt13 said:
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.
Click to expand...
Click to collapse
But the first - try hikey_idt with my files (it is preconfigured in attached archive). If it will be still throwing errors (i had same errors with wrong boot files) - take own files from your board. But not from "bootloaderimg" or "fastbootimage" folders - i got success with files from "update_nv_bootloader_block" folder of my board software package.
Next step - after you will boot board with hikey_idt and willl have fastboot loaded (screen will be still black - this is normal) - you will have to write partition table to device eMMC. For that - extract HISIUFS_GPT.img from UPDATE.APP and flash it as "ptable" - run "fastboot flash ptable HISIUFS_GPT.img". If that will go without errors - you can flash other images one by one.

What linux should i have? It's not possible under windows?

lukastob said:
What linux should i have? It's not possible under windows?
Click to expand...
Click to collapse
Any distro that you like - will work for you. If you are newbie - you can take Ubuntu for ex. Also, virtual machine with linux will be totally fine - just you should check everytime that USB is passed from host to VM. And no - i don't know about alternative tool for hikey_idt under WIndows, and service version of IDT - is bad-bad-bad. So, Linux is your choice.

Good jobs man ))) thanks from all users for testpoint

Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.

yoghurt13 said:
Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.
Click to expand...
Click to collapse
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?

goodwin_c said:
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?
Click to expand...
Click to collapse
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.

yoghurt13 said:
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.
Click to expand...
Click to collapse
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.

goodwin_c said:
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.
Click to expand...
Click to collapse
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.

yoghurt13 said:
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.
Click to expand...
Click to collapse
Can you share somewhere files from your board? i'll look into it.

goodwin_c said:
Can you share somewhere files from your board? i'll look into it.
Click to expand...
Click to collapse
Yeah, I'll upload the thing, I'll PM you the link.

Okay, I somehow managed to get it to work, found the perfect rom for the reset, BUT, the thing is, I lost my IMEI number from the phone, is there any way to reset it?

Amazing, thank you for this
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
yoghurt13 said:
Yeah, I'll upload the thing, I'll PM you the link.
Click to expand...
Click to collapse
I think because of the relocked bootloader