Related
Hi there,
I just came up to Android with an Orange branded HTC Desire. Until now, I was using a HTC Diamond 2 with WM and tried some cooked ROM. But it was really easy with WM. Now, I need to understand more or less how my Android phone works to be able to play with it the same way I played with my Diamond 2.
As I'm a bit lost with some Android terms and concepts and I would like to purpose a kind of glossary for newbies like me. The goal is to explain common concepts with a functional and a technical point of view. I try to give example based on Nexus One and Desire based on personal experiments.
I'll start with what I've understood last few days and believe to be right. I'll ask you to correct my mistakes and to complete this FAQ. I'll keep this post updated.
For the moment following lines may contain big mistakes. I will try to flag validated information.
ROM
A ROM contains the OS on your phone. It can be installed like Windows or Linux on your desktop PC. A ROM contains the kernel and a pack of applications already installed for you. You can find a lot of cooked ROM (ROMs made by great people who would like to share with you optimizations they've done on their phone) on Internet. Normally, Android phones only accept ROM which are signed by the reseller. So you can only put Orange ROM on Orange branded phone.
Moreover, installing a new ROM is a way to update your phone. However, Android phone include an internal updating system (it's just a program like Windows update) so you can receive updates without installing a new ROM. It's called OTA (On The Air) update. OTA update is the way for basic customers to receive update for their phone.
Functionally :
Install a ROM is as easy as execute an exe on you Windows PC. It very easy and fast. You can also install a ROM by using the Recovery Menu.
GoldCard
A GoldCard is a modified SDCard which allows you to put the original unbranded ROM on a career branded phone (installing the original HTC Desire ROM on an Orange HTC Desire). Normally, if you try to execute a HTC ROM updater with a Orange phone, you'll be stuck after 4 or 5 clicks on next. With a Goldcard in your phone, you can archive the process.
You can't install a ROM built for an other device just using a GoldCard (installing a Nexus One ROM on a Desire is not possible).
GoldCard is only needed if you have a carrier-branded Desire, even for rooting process. Unbranded phones never need it.
Be sure to keep your GoldCard because it will be needed for each ROM modifications. You can use a GoldCard as a normal SDCard without problem. However, if you create new partitions for app2sd, your GoldCard will ruined.
Functionally :
Create a GoldCard is easy. It will take you 30 minutes. Not all SDCards work to create a GoldCard. Mine (SanDisk 4Go) included in my Orange package worked perfectly.
Instructions can be found here or here.
Technically :
If I'm right, while you are installing a ROM from the executable on your desktop PC, the phone checks if the ROM you're trying to install match a hard coded key on the phone. With a GoldCard, you make the phone believe signature is good.
CID
The serial number of your SDCard. You'll need to retrieve it with ADB Shell to create your GoldCard.
Functionally :
In ADB Shell (see ADB section), following command line give you your CID :
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Fastboot
It's like the BIOS on your desktop PC. You can access the fastboot with a keyboard combo while starting your phone. It give you access to some function like Recovery Mode or SIM Unlock. With fastboot, you can also install a new ROM using a zip placed on your SDCard.
Use can easily unlock Fastboot on the Nexus One using a ADB shell command.
Fastboot give you access to the recovery mode. In this mode, you can gain write permission in the /system partition which is not possible in Disk Drive mode, event with USB Debugging enabled. With this access, you can easily remove applications which are included in the ROM (like FriendStream in HTC ROMs).
Functionally :
To reach Fastboot on Desire : Hold down back button while pressing power.
Technically :
When you connect the phone to your PC in Fastboot, you will establish a special connection with the device. It uses "Android Bootloaded Interface" driver.
Fastboot unlock
An operation to unlock Fastboot. It's the first step to root your phone. It's easily done for the Nexus One via ADB (see here). It much more difficult with the Desire (possible thanks to Paul).
HBoot
An other boot menu.
Functionally :
To reach HBoot on Desire : Hold down volume down button while pressing power.
ADB
ADB means Android Debug Bridge. You can read this. When you connect your phone to your PC, you can choose different modes :
Charge only : No interaction with your PC
Internet tethering (only if you have a HTC standard ROM, Orange & Co disable this option) : Your PC will see your phone like a modem.
HTC Sync (if you have a HTC standard ROM) : Use to synchronize you data with HTC Sync software
Disk drive : Your PC will see your phone as a USB key allowing you to access to your SDCard
If you're in Disk Drive mode (or even if you're in Charge only mode), you can activate USB debugging (setting > applications > development on your phone). In this mode, your PC will use a ADB driver to establish a special connection. With ADB drivers, you have access to ADB Shell.
With ADB Shell, you can list every file on device and deploy your own application.
Functionally :
Activate USB debugging on your phone to play with ADB Shell.
ADB Shell is accessible from Windows or Linux.
For people who don't use to play with command line, on windows, you must either open a cmd.exe and move in the "tools" folder (with cd command) of your unzipped ADB package or add this repository to your path (instructions here[URL].
Then you can check that everything is alright with following command :
Code:
adb devices
You should see :
Code:
List of devices attached
HTxxxxxxxx device
Then you can type "adb shell" to enter the shell. All Unix basics commands are available and you can do whatever your want... almost nothing since you're not root.
Rooting
Rooting a device is a process to become root on its OS. It allows you to install very nice apps like app2sd (to install application on SDCard), SetCPU app (to overclock or downclock your device) or OpenVPN. This kind of apps can not run if your device is not rooted.
With a rooted device, you can install apps which are not yet validated for your phone on the market by modifying the ID of your device (like the user-agent of your browser). It's easier than downloading the apk file from somebody who extracted the application on a device accepted by the market for this application.
Finally, with a rooted device, you can install ROM from an other device (installing a Nexus One ROM on a Desire).
Functionally :
On Desire, become root is now possible thanks to Paul from Modaco. On Nexus One, it much more easy.
Process is easy if you follow guides step by step. Warning, it will remove all data and configuration on your phone. However, your SD card won't be modified.
If you follow the guide to root the Desire, one of the first steps is to put a big zip file on your SDCard (often rootedupdate.zip). In fact, this zip file contains the ROM you'll have on your phone at the end of the process. Guides generally provide an almost generic ROM. The only modification made to this ROM is the addition of the Superuser Permissions app (the Ninja icon) which will help you to grant root access to applications asking for permission. Installing this ROM is the easier solution. However, you can use every ROM you want (you will find some very interesting ROM on this forum). Just put the file on your SDCard at the beginning of the process and point to the good zip file in the last step. Warning, if you want to install a ROM with app2sd in it, you must know that this application requires a special partition on your SDCard, so you must format your SDCard before the first boot of your new ROM. To do this, just after installing the ROM zip file (the last step of the rooting process), you have to stay in the Recovery Menu and use the good option to create partitions on your SDCard. Of course, your SDCard will be formated.
Technically :
I have no idea what are tricks to become root. You have to find a hole in the phone software. It's not easy.
The process itself requires several steps :
The first step is to unlock the bootloader. This step is easy on Nexus One. On Desire, this step is archived by installing a kind of ROM from Fastboot on your phone.
Unlocking bootloader will give you access to the Recovery Menu and will make your phone accept non-HTC-signed updates (for Desire).
Then, you have to connect your device in HBoot mode to your PC in order to write some files on the phone. These files are used to launch the Recovery Menu. From this menu, you can wipe all data and some caches (I don't know differences between all caches)
Finally you can install a new ROM on your device using a zip file on your SDCard.
Recovery Mode
The Recovery Mode is a special mode accessible from HBoot. You'll need to access this mode to push files needed for the Recovery Menu. It's an important step in the rooting process.
Functionally :
When your phone is in Recovery Mode, you'll see a little red triangle on your screen.
Technically :
Recovery Mode is a special provided by Android to do special operations. In fact, I don't know what's the real usage of this mode.
Recovery Menu
The Recovery Menu is a small tool accessible from Recovery Mode. It purposes some options such as wipe your data, format your SDCard and the most important option : deploy ROM or files from a zip file previously dropped at the root of your SDCard.
Functionally :
The Recovery Menu is a green menu you have to use in the root process.
Technically :
On the Desire, Recovery Menu is the only way to write files on /system. Put a zip file on the root of your SDCard and the Recovery Menu will unzip the package and deploy files on your phone for you. You will have to use this menu to install OpenVPN because this application requires to put some file in /system partition. In the last step of the rooting process, Recovery Menu will deploy your ROM (which is nothing more than just a bunch of files) on your phone.
SIM Unlock
SIM Unlock in a process different from all others. If I'm right, you'll have to use Fastboot, put some files on your SDCard and press SIMUnlock. Required files can be provided by your operator. This process works with all ROMs and don't required a root access.
Nandroid Backup
The Nandroid backup process creates binary images (.img) of the boot, data and system partitions (and ext also, if you choose nand+ext). Needless to say you need root in order to be able to perform this kind of backup.
Later, you can use those image files to restore those partitions, in a very similar way you restore a hard-disk partition from a ghost created image. Practically the restore process erases all their content and replaces it with the data saved in the img files, thus reverting the phone's software to the state it was when you performed backup.
Nandroid backup doesn't include the radio image; you can only change (or revert) the radio by flashing it again.
If you want to go back to stock software, you need to use a RUU, which overwrites all the modifications you made into the phone's software (and of course removes the root access as well).
APK
This is the file format for applications. Each application is packaged in an APK file. When you install an application from the market, you're just downlading an APK file which is then automatically installed on your phone.
You can also find APK files on Internet, put them on your SDCard (or directly download them from your phone) and install them.
Deodexed
Technically :
By default, applications are odexed. This allows Android to preload some parts of an application to optimize its launch time. Unfortunately it makes application resources be dispatched outside the APK. Deodexing is a process of gathering all resources inside the application.
Functionally :
Some applications apply a theme on other applications. You need a deodexed version of the targeted application to use this. However, deodexing applications is not a process you should take care of. You'll find some custom ROMs in which all applications have been deodexed for you.
That's all for now. I really want to complete technical information on above lines. It will be great if somebody could explain why you can not install a Nexus One ROM on a HTC Desire using only a GoldCard. Moreover I would like to know how works Fastboot with SDCard. It seems that SDCard plays a really important role (used to update ROM, SIM unlock and GoldCard).
PS : English is not my native language, please be indulgent.
Many thanks to The Professor and silvake for some precisions.
Matco.
Great topic idea, thank you!
Great idea!
Just found out that you need to be in recovery mode in order to have write permissions to the /system partitition (Disk Drive with USB debugging enabled won't work).
More details in the link below, if you want to include them:
http://forum.xda-developers.com/showpost.php?p=6347071&postcount=2
(credits go to emdzej)
Thank your for your support. I just updated the post with your details.
I would like to add some links but I don't have enough rights to add the url tag in my posts.
CID register - serial number of your sd card
Perhaps time to move the info to the wiki ?
Greetings from a vastloper
This should deffinatley get a sticky + be added to the wiki. Great info, so many new terms to learn now that i'm experimenting with android on my blackstone and seriously considering a Desire
Thank you for your replies. I just made some improvements.
It will be ready for the Wiki as soon as someone will confirm informations and help me to complete blanks.
I would really like to have more technical informations. Feel free to share what you know !
For moderators, is it possible to allow me to add URL ?
Matco said:
Thank you for your replies. I just made some improvements.
It will be ready for the Wiki as soon as someone will confirm informations and help me to complete blanks.
I would really like to have more technical informations. Feel free to share what you know !
For moderators, is it possible to allow me to add URL ?
Click to expand...
Click to collapse
matco my desire was not branded by any network.. does this mean to root I should just go ahead with the root process ignoring the goldcard step?? thanks
Yes, you're right (check [Guide] Rooting in this forum, page 4 post 39). GoldCard is only needed for branded phone.
Anyway, the website which generated the .img has been disabled. So you can't create easily a GoldCard right now...
Negative, it's back online:
http://psas.revskills.de/?q=goldcard
guys stuck on the red exclamation mark.. using vista, i ran recovery bat but the recovery mode is not going green. what other files hould be in the same folder as recovery bat?
Everything that was in the original pushfiles.zip along with adb-nilezon. Not sure if they're still there, but if they are, here's where you should be able to find them.
I just updated the FAQ as I successfully rooted my Desire. Rooting process helps me to understand what are Fastboot and HBoot for.
It would be nice if someone can tell me if you can put any zip you want on your SD Card for the last step of the rooting process or if you have to use special ROM included in the file package (rootedupdate.zip).
Thanks by advance.
You can put any full ROM on as the last step, it doesn't have to be rootedupdate.zip. That one will be exactly stock + root, though - so for people who like the phone as is but want root, that's the ROM they want.
You can download anybody else's ROM and throw it on for the final step if that's your cup of tea, though. May want to mention that if they're picking a ROM with A2SD in it, that they need to perform the SD setup before booting, or they may run into trouble with that.
Thank your for your reply.
I will add a warning for people who want to install a ROM with app2SD in it (if I'm right they can use the little "green" menu just before installing the zip file to create partitions on SD Card).
As you seem to have a good understanding of the rooting process, could you explain me what is the goal of the first step (installing a fresh ROM from RUU Installer with phone in Fastboot Mode)? And what are pushed files for ? Is it for green menu?
You need to partition the SD card (using the partition options in the recovery (green) menu) after your ROM and A2SD are installed - if you partition beforehand, you'll lose the zip files you need to flash.
The first step unlocks the bootloader so it'll allow low-level access and recovery mode and so the phone will accept non-HTC-signed updates, I believe. The pushfiles in the second step are forcing the recovery menu (the green menu you mention) onto the device - but since we can't have write access to /system while the device is outside of recovery mode, we have to push the files every time.
very helpful for winmo converts thanks
it took me some time to figure that out
I've done some updates thanks to The Professor.
Great thread, thank you
Last edit: Jan 2, 2018
The information here can be found in many places on the web and several forums. But when I started flashing custom ROMs about two years ago, I got frustrated many times because I found that information to be scattered, fragmented and in many cases outdated.
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF700 involves three steps:1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recoveryRooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step since any custom ROM you flash will be rooted anyway.
But if you want to root the TF700 on stock firmware there are three ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK).
And then there is Towelroot, a one-click-root exploit. It's an apk, so no PC necessary. Only Towelroot v1 works for the TF700 and it's hard to find. My dog ate the copy I had..
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Download the Asus Unlock Tool v7 from here: https://www.androidfilehost.com/?fid=817550096634776735
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
If you get an unspecified "network error" you could be in for some major headaches. Many tablet's serial number and/or the mac address of the mainboard seem to be registered incorrectly in Asus database. This problem is widely discussed on several forums, just google: "cannot unlock TF700" or similar and read the threads. Too many variables to discuss this here...
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
To determine if you need to update your bootloader read post #3
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8.+ you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
TROUBLE WITH ADB FASTBOOT DRIVERS? SALVATION IS NEAR!! (May 2017 edit)
And it is called FWUL (F-orget(?) Windows Use Linux) a great Arch Linux distro that you can boot off a USB stick or CD with simple adb fastboot all setup for you. Follow the instructions, set your boot sequence to boot from USB or SD drive first and disable Secure Boot in your BIOS Security settings. I have fought with Windows driver problems as long as I have been using Android devices and some stuff I never got to work. With this baby I was able to connect to 4 different Android devices with no problems at all. A beauty! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Inside that folder Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
If all of the above fails follow these instructions: https://www.michaelcrump.net/power-tip-for-windows-users-open-command-prompt-here/
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://twrp.me/devices/asustransformerinfinityTF700T.html
Download the latest version of TWRP. Version 2.8.0 or later is ready for KitKat and Lollipop custom roms as well as backward compatible with JB ROMs.
FYI ONLY: If you for whatever reason want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Formatting data is only necessary in cases of data corruption.
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
This will flash the recovery to the recovery partition
Example:
If the file is named TWRP_2.8.6.2_TF700_recovery.img, the fastboot command is:
Code:
fastboot -i 0x0B05 flash recovery TWRP_2.8.6.2_TF700_recovery.img
You can rename the file to something easier to type, but file name and fastboot command have to match.
So if you renamed the file to twrp.img:
Code:
fastboot -i 0x0B05 flash recovery twrp.img
If your recovery comes as a blob:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock rom you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers or check out post #2. There's a description of the most popular roms for this tablet.
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
ROMs for the TF700
Update June 2017:
Time moves on and this tablet is till alive....
Most of the roms below are ancient by now. One dev, the legendary timduru, is still working for this tablet and currently supporting Nougatella, Android 7.1.2 for this tablet.
Skip to here if you are thinking about a current rom: https://forum.xda-developers.com/showpost.php?p=72540013&postcount=346
Click to expand...
Click to collapse
KatKiss-KatshMallow by timduru (MM on the TF700 - who would have thought?) is still under intermittent but active development and it is a beauty. Multi-window support anyone?
http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements, but since there have been no further Asus updates, development on this rom has stopped. This rom would give you the most Asus-like experience on this tablet.
http://forum.xda-developers.com/showthread.php?t=2425383
And here is the recent incarnation of this rom: CROMi-X Resurrected: http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
@LetMeKnow still releases a new teak here and there, so keep following the thread.
Development on all of the following roms has stopped. The devs have moved on to other devices
CROMBi-KK is based on CM11 and tweaked for this tablet but a little buggy. The later LP based roms from the same team are definitely better.
http://forum.xda-developers.com/showthread.php?t=2672751
CyanogenMod is build from the ground up, CM10.x emulating JB 4.3, CM11 emulating KitKat (JB 4.4). CM was not build with a transformer (keyboard) in mind, but the dev has ironed out most of those bugs.
http://forum.xda-developers.com/showthread.php?t=1957660
ZOMBi-X: From the same team that developed CROMi-X and CROMBi-KK. Based on OMNI rom with multi-window support.
http://forum.xda-developers.com/transformer-tf700/development/rom-t2857931
ZOMBi-POP The (almost last) project from the CROMI/CROMBi/ZOMBi team. It's Omni based Lollipop for the TF700
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
A note: This rom will run with data formatted to ext4, which is the OEM default. But it benefits from /data on F2FS, the new file system developed by Samsung, more than any other rom before it. Changing the file system for /data to F2FS has become very easy since the TWRP team build support for it into their recovery. I wrote a guide for converting your data partition to F2FS here:
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
That same team took one final stab at a 6.0 rom for this tablet: http://forum.xda-developers.com/showpost.php?p=65968239&postcount=3719
But I would call this definitely an unfinished product with a doubtful future.
CM12 I don't run CM roms - try it for yourself
http://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
OmniROM by lj50036 who's on the ZOMBi team
http://forum.xda-developers.com/transformer-tf700/development/rom-omnirom-tf700t-t3056438
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
AND IF YOU LIKE YOUR NEW ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Alternative methods to install TWRP
Edit February 2015
In this section I originally explained how to flash TWRP to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work sometimes (and if you have root), but I will not recommend or promote them any longer.
Why?
Because I'v read too many stories about these apps failing, even flashing to the wrong partition - you name it.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
I have spent quite a few hours helping users who got themselves into a situation where the only thing they could access on their tablet was recovery, but they did not know anything about adb/fastboot and did not set it up when the tablet was still working. To get it to work with a soft bricked tablet is much, much harder!!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
HOW TO UPDATE YOUR BOOTLOADER
The last official Asus firmware update to JB 4.2.1 brought us to the 10.6.1.14.10 bootloader - and it will be the last one we ever get since there will not be any Asus firmware updates anymore.
If you are on an older bootloader and want to run a KK or Lollipop ROM, you should update your bootloader to this version.
Determining which bootloader you currently have
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.14.10-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.14.10 is your bootloader version
20130801 is the build date (and immaterial in most cases).
Updating your bootloader
Still on stock with stock recovery:
Just OTA update to the last Asus firmware or flash it manually.
Custom ROM with custom recovery
Either:
1. Flash Asus stock firmware in your custom recovery
Download the official Asus firmware, unzip it once, flash that second zip in TWRP or CWM.
The distinct disadvantage of this method is that you will loose your custom ROM and your custom recovery and you will have to reflash them, but it works to get you onto the latest bootloader - or the latest stock rom if you desire to return to stockOr:
2. Flash only the bootloader in recovery
This is what I would recommend you do.
Go here for a collection of flashable bootloader/recovery packages: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
If all you need is the latest US bootloader, go to post #3.
The packages (bootloader + recovery) will replace not only your bootloader, but also your current recovery with whatever the TWRP version in the package is.To flash a KK or Lollipop ROM afterwards you need TWRP 2.8.+.
If you choose a bootloader package with an older recovery, you need to flash the latest TWRP version after you flashed the above bootloader package. In between you have to reboot (do not skip this step!)
sbdags said:
@moderator could we sticky this please.
Brilliant post Bernd
Click to expand...
Click to collapse
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
berndblb said:
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
Click to expand...
Click to collapse
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Mod edit: I deleted your previous post to give the third post to OP. I will copy paste it here.
@stamatis could we sticky this please.
Brilliant post Bernd :good:
sbdags said:
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Click to expand...
Click to collapse
No problem. You "jumping the gun" is an honor to me.
Thanks
Well written and very informative post. Thread stuck.
please help
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported. So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh.. So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
blackc3 said:
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported.
Click to expand...
Click to collapse
I think you mean v8, v7 for the Asus Unlock tool?
You have to extract it. On the tablet you can use the app ES File Explorer from the Play Store. It downloads as a .rar file, the result has to be an apk
So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh..
Click to expand...
Click to collapse
You have to get the drivers working - no excuses
Without working drivers you cannot push a recovery to your tablet. What Windows version do you have?
Try installing the Asus PC Sync Utility, try the Google Naked Drivers, try the ones attached to this post (note: I have not tested these myself) - you will have to find the correct combination for your PC yourself.
Here are a few links that may be helpful.
http://www.addictivetips.com/window...-or-device-drivers-manually-in-windows-vista/
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
Click to expand...
Click to collapse
No. You just got started!
Here are a couple of different approaches if you cannot unlock:
http://www.transformerforums.com/fo...discussion/42587-my-unlocking-experience.html
http://forum.xda-developers.com/showpost.php?p=51210808&postcount=6
Thanks for the guide,
everything went smooth until this step:
fastboot -i 0x05B0 flash recovery twrp.blob
Now my cmd just hangs there (been like 10 mins), not sure if i should restart tablet or cmd? Tablet still in fastboot screen. Thanks.
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
berndblb said:
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
It recognizing it correctly (atleast from what I understood from the guide). If it matters, I installed twrp 2.7 instead since it indicated 2.6.3.2+
I get:
015d2bbce9141e18 fastboot
Can I safely reboot/close cmd and try again?
Yes. Ctrl C will cancel the command, you should get the command prompt back.
Strange... twrp.blob is in the same folder as your fastboot.exe, right?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
OP updated
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
berndblb said:
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
A question for @_that as I always thought you needed the ID. Maybe not?
sbdags said:
A question for @_that as I always thought you needed the ID. Maybe not?
Click to expand...
Click to collapse
Apparently there was an older fastboot version that needed it. I've not used the ID for a long time.
It doesn't matter if you use 0x0B05 or 0xb05, it's the same number.
Great tut.
Thanks for posting. Good info, very concise.
berndblb said:
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here or if my instructions are dead wrong. I may be a fiend who's going for the world record in tablets bricked. Do your own research, read thrice, ask twice, flash once.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using the custom recovery
Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step. However - as of today, Feb 27, 2014, another path to installing a custom recovery opened up (again) and that method (using GooManager to install TWRP - see below) requires you to be rooted.
So if you want to root the TF700 on stock firmware there are two ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK). There was some controversy around Kingo. Late last year their threads on XDA got closed because they used the vroot method which had a sniffer component that collected information and sent it to servers in China. The developers of Kingo removed vroot and worked it out with XDA. Their threads got re-opened in December. So I believe Kingo is safe to use - but you be the judge of that....
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: ASUSTeK Computer Inc. -Support-
Select your device, choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v8 (I assume you are on JB 4.2 firmware)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you or use ES File Explorer on the tablet
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. For now I assume it goes ok.
To check if you are unlocked, boot the tablet and read the tiny script. It should say: This device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up.
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows 7/8:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
This is not confirmed to work on Win 8.1, but that may be due to the driver signature verification in Win8. Google how to turn it off.
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for the adb folder) and the corresponding drivers. Takes about 15 seconds
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Linux and iOS: Check out this site https://code.google.com/p/adb-fastboot-install/ or this [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers
The fun begins
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
In Win XP select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
All Windows versions: In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers.
Let's assume everything is good:
On your computer go here: Techerrata Downloads - Browsing tf700t
Download the correct TWRP version for the ROM you intend to flash (see list below)
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock ROM you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom ROM and they are rooted anyway.
Alternative methods to installing TWRP
A) The app GooManager, free in the Play Store, downloads and installs TWRP (currently version 2.6.3.1) on the TF700. But GooManager requires root AND the bootloader to be unlocked. For users who are rooted already or those who cannot get ADB and fastboot to work on their PC, rooting with Motochopper or Kingo and then using GooManger to install TWRP may be a good alternative.
B) sbdags, the developer of CROMi-X (probably the most popular ROM for this tablet) provided a tool that automates the fastboot commands necessary to install a recovery..
I personally believe it is essential to have a working fastboot connection from PC to tablet and becoming familiar with basic fastboot commands when you develop a flashing habit, but if you want to take a shortcut his tool is here: http://forum.xda-developers.com/showthread.php?t=2646279
ROM – Recovery combinations
I assume you are on the 10.6.1.14.10 bootloader
CROMi-X – TWRP 2.6.1 or later http://forum.xda-developers.com/showthread.php?t=2425383
CROMBi-KK – TWRP 2.7.0 http://forum.xda-developers.com/showthread.php?t=2672751
NOTE: Formatting data in TWRP 2.7 takes a lot longer than in previous versions (up to 90 minutes). DO NOT INTERRUPT THE PROCESS if you format /data (usually only necessary with data corruption)
CM11 – CWM 6.0.4.6+ http://forum.xda-developers.com/showthread.php?t=1926286
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Installing a custom ROM
The most popular custom ROMs for the TF700 are CROMi-X, CROMBi-KK and CyanogenMod (CM).
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements.
CROMBi-KK is a mix of CM11 and CROMi-X and at this point still in beta.
CM11 is build from the ground up, emulating KitKat (JB 4.4).
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
Note: Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers
Note: It is recommended (mandatory if you go for CM) to do a Factory Wipe in TWRP before installing a custom ROM.
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
From here on out it's as easy as downloading the installation file of your custom ROM, booting into recovery, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you go for CROMi-X and TWRP as your recovery, make sure you check "verify zip signature" under the Install menu. sbdags signs his ROM zips - a better way to ensure file integrity than md5 sum.
For a general overview and comparison of ROMs check out Gtanner00's thread, post 2 + 3. Note that he describes roms for the TF300, but since the framework for the TF300 and TF700 is very similar there is usually an equivalent rom for the TF700 at the XDA Developers forum.
http://www.transformerforums.com/forum/showthread.php?t=41508
Do not follow or download from any of the links he provides! I only link to his thread for general information!
Any questions - please ask.
AND IF YOU LIKE THE ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Click to expand...
Click to collapse
droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
Same thing happened to me. Fastboot recovery command did not return after over 10 minutes. I did Ctrl-C. Ran the command again and got the invalid argument error. Tried a couple times with same result. Unplugged and replugged USB cable (to same USB port). Ran the command again and it worked. When it worked, it took 11 seconds to flash recovery.
Also probably worth noting in the guide is that the Asus boot unlocker requires Google sign-in. If you have 2-step verification setup on your Google account, you need to use a one-time app password to sign-in.
Code:
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
^C
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
OKAY [ 2.704s]
writing 'recovery'...
OKAY [ 8.026s]
finished. total time: 10.731s
I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)
FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...
Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing
RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108
ROMS
Not yet but soon.....
I'd swear I've seen all this somewhere before... lol
Good job, brother!
Now , let the roms...begin.....
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here
Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...
You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.
i get nothing when sniffing the USB bus on my MBP.
Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
QLink Scepter 8 Tablet
Gen 1 & Gen 2 Models
Factory Firmware Restoration
And Upgrading Guide
{
"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"
}
OVERVIEW:
The manufacturer of this tablet, Hot Pepper Mobile, has graciously provided me with some factory firmware images for the Gen 1 and Gen 2 models of the QLink Scepter 8. Accordingly, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
This guide will be outlined to provide four firmware installation methods, all of which will focus on a Windows-based setup: (1) PhoenixUSB Pro; (2) LiveSuit; (3) PhoenixSuit; and (4) PhoenixCard. These four utilities were developed and released by Allwinner Technology Co, LTD. As such, each proprietary tool provides a comprehensive solution for restoring your device to its stock factory state. While any of the four outlined methods will ultimately achieve the same end result, members may find that one particular utility is simpler to use or works better than the others. In short, versatility is the focal point. The first three methods are standard proprietary strategies for flashing vendor-specific firmware images to eMMC NAND storage. These tools flash your tablet from a powered-off state known as FEL mode, a proprietary flashing protocol based on BROM. It should be noted here that some members have experienced device recognition issues while using PhoenixUSB Pro, PhoenixSuit and LiveSuit. For members who are experiencing insurmountable device recognition issues, I e. the flash tool not recognizing your tablet once it is in the powered off FEL flash mode, I have included a new section in the instructions for installing the proper Allwinner FEL mode drivers. This section should remedy any such device recognition problems. Also, the 4th method, PhoenixCard, may provide you with a viable solution to device recognition problems. PhoenixCard enables users to write a full firmware image to a micro SD card which, in turn, is inserted into the tablet's micro SD card slot. The tablet is then booted, at which time the firmware image on external storage is written to NAND/eMMC flash memory, thus fully restoring the tablet to its factory state. The PhoenixCard method is ideal for users with unresolved device recognition issues, or in scenarios where the partition index has incurred major corruption and fails during standard firmware restoration procedures.
HARDWARE VARIANTS:
There are a four (4) different variants of the QLink Scepter 8, categorized under the two (2) primary hardware models Gen 1 & Gen 2. The original Gen 1 model, released in April, 2021, shipped with an Allwinner-A100 chipset, 1 GB RAM, and Android 11 (Go Edition) preinstalled. The latest Gen 2 model, released in mid-July, 2022, ships with an upgraded Allwinner-A133 chipset, 2 GB RAM, and runs on Android 12 (Go Edition). Regardless of which gen model you own, your device serial number will begin either with the two letters MD or the two letters CF. Hence, there are two variants of the original Gen 1 model, and two variants of the latest Gen 2 model. I am referencing these models and variants in order to emphasize that they are not intercompatible in terms of firmware. Determining your variant is very simple: if your tablet has Android 11 (Go Edition), you have the original Gen 1 model. And, if you are running on Android 12 (Go Edition), you have the latest Gen 2 model. Once you determine which model you own, simply check the first two letters of your device S/N to determine the variant. To avoid confusion and potential firmware mismatches, I have categorized the firmware images under their corresponding models in the downloads section. These sections have further been subdivided under the appropriate S/N variants. Ensure that you download the correct package based on your S/N variant. Otherwise, the Allwinner proprietary flash tools used in this guide will not commence with the flashing process.INSTALLING ADB & FASTBOOT:
While this step is not absolutely required in order to perform a firmware restoration of the QLink Scepter 8, it's a good idea to go ahead and get this taken care of for future needs (e.g., unlocking the bootloader and rooting, if you plan on performing those tasks later on). All of the flash tools referenced in this tutorial are capable of restoring a QLink Scepter 8 which is bricked (a tablet which is unable to boot to the Android OS, and/or unable to boot into either recovery or fastboot mode).
If you have previously installed ADB & Fastboot, as well as the relevant USB device drivers on your Windows computer, skip down to the next section. Otherwise,
Download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory.
Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers.
Select "Y" again when prompted to install ADB as system-wide.
Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched.
Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer.
It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the ADB & Fastboot tools as well as the Google universal device drivers.
INSTALLING ALLWINNER USB DRIVERS:
The first three firmware flashing tools outlined in this guide -- PhoenixUSB Pro, LiveSuit and PhoenixSuit -- restore factory firmware by flashing the NAND/eMMC directly, with the device in a powered-off emergency flashing state known as FEL mode. FEL mode is the Allwinner proprietary firmware flashing protocol based on the hardware embedded Boot ROM (BROM) implementation. All three of these tools utilize FEL mode when flashing firmware to your tablet's NAND/eMMC internal storage device. FEL mode is initiated one of two ways: (1) if the tablet is booted into the Android OS while connected to your computer, the tool will recognize your device, via USB Debugging, and once firmware flashing is ready to commence, the tool will boot your tablet into FEL flash mode which, again, is a powered off state; or (2) if your device is bricked, stuck in a boot loop, or is otherwise unable to boot up, FEL mode can be initiated manually by performing a particular hardware key sequence while connecting the powered-off device to your computer. This key sequence is outlined below in the instructions. In either scenario, your tablet will not be recognized by whichever flash tool you are using unless the proper drivers are installed on your Windows PC or laptop.
Typically, on both Windows 10 and 11, generic drivers bundled with the operating system will enable proper recognition of your tablet while in FEL flash mode. However, because some members have encountered issues with the Scepter 8 being recognized by these flash tools (while in FEL mode), I am including this section to ensure proper Allwinner USB driver installation on your Windows computer, before we get started with the flashing procedure.
Download the Allwinner FEL Driver v1.0.0 from the link provided below, and extract the contents of the archived file to your desktop or another convenient directory;
Right click on either the dpinst_x86.exe file (for 32-bit Windows), or the dpinst_x64.exe file (for 64-bit Windows), and choose to run the application as an administrator;
Follow the prompts on the driver installation wizard to install and configure the drivers on your computer. Once complete, a notification will indicate that the installation was successful;
Select Finish and reboot your computer. Your tablet should now be recognized by the respective flash tool while in FEL mode, thus enabling the firmware restoration process to properly commence.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
Furthermore, some of the firmware restoration methods outlined below will result in all user data being wiped on your device. Before proceeding, and if possible, make a backup up any important files and media that you wish to preserve.
I. METHOD 1
PhoenixUSB Pro For Windows
PREREQUISITES:
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image that corresponds with your tablet variant (links provided below). In this first section, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state, via FEL mode.
Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware in the event you are running an older firmware build version.
Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
Power off your Scepter 8 tablet;
In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
Now, click the Start button located in the upper section of the interface. A large green checkmark will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
Connect the USB data sync cable to your computer, but not yet to your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key continuously until PhoenixUSB Pro recognizes your device, then release Volume Down. You will know your device has been recognized by an on-screen prompt indicating that the firmware installation is initiating;
The flashing process typically takes about four minutes. A progress bar on the PhoenixUSB Pro interface will show the percentage of completion in real time. When complete, you will see a green checkmark and a notification that the installation has finished;
Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on an unmodified stock firmware build.
DOWNLOADS:
• 15-Second ADB Installer v1.5.6
• PhoenixUSB Pro v4.0.0
• PhoenixSuit v1.10
• LiveSuit v1.11
• PhoenixCard Image Burning Tool v4.2.4
• Allwinner USB Driver Installer v1.0.0
Factory Firmware ImagesGen 1 ModelsMD SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v11_20221213
CF SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v13_20221212
*** *** *** *** *** *** *** *** ***
Gen 2 Models CF SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v03_20221126
MD SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v01_20220915
$$ DONATIONS $$
I do not expressly request or expect donations from members for my work. I adhere firmly to the open source and free use spirit of the Android OS. With that said, for any members who want to donate something, it would be a huge help. Firmware images for both the Gen 1 & Gen 2 Scepter 8 tablet models were previously unreleased to the public. It took several weeks of discussions with Hot Pepper Mobile Tech Support and its CEO, Mr. Shawn Sun, to obtain official firmware images for this tablet.
This is my CashApp link where you can give as little as $1. For those unable to help financially, I understand. A tap on the thanks button, however, doesn't cost a thing.
PayPal Donation Link
CashApp Donation Link
II. METHOD 2
PhoenixSuit For Windows
PREREQUISITES:
As with the previous section, you will need a PC or laptop running Windows 7/8.1/10/11, the OEM-supplied or a quality equivalent micro USB to USB-A data syncing cable, the PhoenixSuit v1.10 flashing utility (link provided below), and a factory firmware image for your QLink Scepter 8 variant (links provided above). This section presumes that the correct USB device drivers are installed on your Windows computer. If you have not installed these, see my section above titled INSTALLING ALLWINNER USB DRIVERS, then return here once you have completed those instructions.
FIRMWARE RESTORATION/UPGRADE:
Download PhoenixSuit v1.10 from the link above and extract the contents of the archived file to your computer desktop, or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link above, and extract the firmware image (.img file) to a convenient directory on your computer;
Launch/Open PhoenixSuit by double clicking PhoenixSuit.exe from the directory you extracted in the first step;
Click on the Firmware tab in the top section of the interface and click on the blue Image tab. Windows File Explorer will be launched; navigate to the location of the firmware .img file you downloaded and extracted in the second step;
Power off your tablet;
Connect your data sync cable to your PC but not to your tablet. Hold Volume Down and, while continuing to hold the key, connect the micro USB end of the data sync cable to your tablet. Now tap the Power button (up to ten times) until PhoenixSuit indicates recognition of your device;
You will be prompted to perform a mandatory format. Select Yes to proceed;
PhoenixSuit will initiate the firmware installation. Once complete, an Upgrade Firmware Succeed notification will be displayed. Press Ok to finish the process.
Disconnect and reboot your device. . Your tablet should be now be restored to its factory stock state.
III. METHOD 3
LiveSuit For Windows
Like the previous two methods, LiveSuit is a proprietary NAND flash tool developed and released by Allwinner Technology. LiveSuit is available for the Windows, Mac and Linux operating system platforms. This particular guide, however, will focus strictly on a Windows setup. You can download LiveSuit for both the Mac and Linux platforms here: https://androidmtk.com/download-livesuit-all-versions
The tools available for download are trusted, verified, and have been thoroughly scanned for viruses and other types of malicious code. A comprehensive guide for using LiveSuit for Linux can be found here: https://linux-sunxi.org/LiveSuit
Without further ado,.let us proceed with LiveSuit for Windows.
PREREQUISITES:
Once again, you will need a PC or laptop running on Windows 7/8.1/10/11; the factory-supplied or a quality equivalent micro USB to USB-A data syncing cable; LiveSuitPack v1.11 (link available above); a firmware image compatible with your model/variant of the QLink Scepter 8 (links provided above); and the proper USB device drivers installed on your Windows computer. If you have not yet installed the driver's, follow my section above titled INSTALLING ALLWINNER USB DRIVERS. Return here after following those steps.
FIRMWARE RESTORATION/UPGRADE
Download LiveSuitPack v1.11 from the DOWNLOADS section above. Extract the contents of the archive to a folder on your desktop or to another convenient directory;
Download a firmware package compatible with your model/variant of the Scepter 8. In the simplest terms, if your tablet shipped with Android 11 Go Edition, then you must use a firmware package that corresponds with the Android 11 Go Edition build. If you have the newer variant that shipped with Android 12 Go Edition, then use firmware from that heading only. Once downloaded, extract the .img firmware file from the archive and save it to your desktop or another easily accessible location;
Open the LiveSuit flash tool by double clicking LiveSuitv1.11.exe in the directory you extracted in the first step. Once launched, select YES to follow the Upgrade Wizard;
Click the Upgrade Mode tab and then select Mandatory;
Disconnect any connected mobile devices from your computer, and select Next;
Select the Yes option, then.Next, and select the firmware .img file you extracted in the second step. Now click Yes but do not select Finish;
Ensure your tablet is powered off. Connect the data sync cable to your PC but not yet to your tablet. Hold the Volume Down button on your tablet. While continuing.to hold the botton, connect the micro USB end of the data sync cable to your tablet. Without releasing the Volume Down button, press the Power key 5 to 10 times, or until you are notified by LiveSuit that your tablet has been recognized. Click Yes to proceed with firmware installation;
A progress bar on the LiveSuit interface will reflect the percentage of completion in real time. Once complete, an Upgrade Succeeds notification will be shown. Click Ok and then Exit.
Reboot your tablet, which should now be restored to its stock factory state.
IV. METHOD 4
PhoenixCard for Windows
PREREQUISITES:
As referenced previously, PhoenixCard is an Allwinner proprietary tool for burning a factory firmware image onto an external storage medium such as a micro SD card. In turn, the micro SD card is inserted into the tablet's card slot. Once the tablet is powered on, the firmware image burned to the micro SD card will then be written to the tablet's eMMC flash storage, thus restoring the device to its stock factory condition
As you may have guessed, you will need a PC or laptop running Windows 7/8.1/10/11; a micro SD card with a recommended minimum capacity of 8 GB; a USB-type micro SD card reader/writer; a compatible factory firmware image for your tablet (links provided above); and the PhoenixCard v4.2.4 image burning tool (link provided above).
FIRMWARE RESTORATION/UPGRADE
Ensure that you have no external storage devices, mobile devices, or any other USB-type devices connected to your PC or laptop;
Download a factory firmware image from the downloads section above that is compatible with your tablet variant. Save the image on your computer desktop or another convenient directory;
Download the PhoenixCard v4.2.4 image burning tool onto your Windows computer. Extract the contents of the archive to a folder on your desktop or to another easily accessible location;
Double click PhoenixCard.exe to launch the tool;
Place your micro SD card into a suitable card reader/writer and connect it to your PC or laptop;.
Click on the Img File box located in the upper-left section of the PhoenixCard interface;
Select the firmware image (.img file) you downloaded in the second step;
Click the box marked Burn in the lower left section of the interface. The firmware image will be burned to the micro SD card. The process can take from 5 to 10 minutes to complete, at which time the output window of the interface will indicate Burn End;
Remove the micro SD card from the card reader and insert it into the micro SD card slot of your QLink Scepter 8.tablet. Ensure that your tablet is powered off;
To begin the firmware installation process, long press your power button. Your tablet display will show a progress bar indicating that the firmware image on the micro SD card is being written to eMMC flash memory;
Once the process is complete, remove the micro SD card from your tablet and boot the device normally.
Upon reboot, your QLink Scepter 8 should be restored to its factory stock state.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5554999OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for installation using the Phoenix Suite flash tool. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide also outlines the procedure for upgrading your QLink Scepter 8 to a newer firmware build.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using Phoenix Suite v1.10 for Windows. Accordingly, you will need a PC or laptop running on Windows 7/8.1/10/11, the Phoenix Suite flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. Should you have difficulties in this regard, I have outlined the steps for manually updating your drivers below.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
I. FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 if you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download Phoenix Suite 1.10 from the link below and install it on your Windows computer. Once installed, open the tool and grant any prompted permissions;
2. Download the V9 stock firmware image from the link below and save it on a convenient directory on your PC or laptop. The firmware will be in an archived .rar file format. Use WinZip, WinRAR or other utility to extract the firmware image from the archive. Safe the image to a convenient directory on your computer;
3. Ensure that USB Debugging is enabled in the Developer Options menu on your tablet;
4. Connect your tablet to your Windows computer using a proper data sync cable. Watch your device display for the USB Debugging authorization prompt, then grant the request;
5. If your tablet is being properly recognized by Phoenix Suite, an indicator in the bottom-left of the interface will indicate Device Connected.
6. Click on the Firmware option in the upper panel of Phoenix Suite. Click on Image and then select the saved location of the firmware image you downloaded. Highlight the firmware image by clicking it, then select Open in the bottom-right of the interface.
7. When ready to begin the restoration process, click the green Upgrade button in Phoenix Suite. Your device will automatically boot into a low-level flashing mode. When prompted, choose the option for full format. The firmware will begin installation. Phoenix Suite will indicate the progress of the installation and your tablet will automatically reboot to the OS once the process is complete. The flashing process will take between 3 and 4 minutes in duration. You are finished. Your device should now be fully restored to its factory stock state and running on the V9 firmware build.
8. If the firmware did not commence installation due to a no-device-connected error, see the next section below on drivers.
UPDATING USB DEVICE DRIVERS:
Perform these steps only if the firmware did not install and you are receiving an error that no device is connected. As mentioned previously, once you select a firmware image, Phoenix Suite will boot your device into a low-level flashing mode (Download Mode) to begin the flashing process. Leave the device in this mode and keep it connected to your Windows computer. Right click the Windows Start button and select Device Manager. Your tablet should be listed under the Portable Devices heading as Unknown Device. Right click Unknown Device and choose Update Driver. On the next screen select the option to Browse My Computer. Next, click on the Browse icon box in the upoer-right of the menu. Navigate to the saved location of the folder from which you open the Phoenix Suite flash tool. It should have a folder name of PhoenixSuite_V1.10. Left click on the folder and look below it for a folder named Drivers. Select Drivers and then choose OK. Now click Next at the bottom-right of the menu. You may get a warning notification that the drivers are unsigned. Select the option to install anyway. Once installed, Phoenix Suite will immediately recognize your device on flash mode and the firmware installation will start automatically. Return to the Phoenix Suite flash tool interface to see the installation progress.
DOWNLOADS:
PhoenixSuite v1.10
Stock Firmware Image V6
Stock Firmware Image V9
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. PhoenixSuite is not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
Click to expand...
Click to collapse
Thank you very much for all the work you've done on this. It has been a big help. I've been following along since the beginning of this topic and I've been using XDA for years but this is my first post, I think, maybe second, idk.
I have been able to do pretty much everything but get this firmware to flash, it consistently gets to the part where it says on the bottom left of the phoenix suite window "beginning flash operation" or something similar, the selection form is replaced with an empty progress bar and i can't recall exactly whats written under the progress bar but it something to the effect of "firmware flash starting". But that's it it does nothing after that, I've left it 20 and 30 mins and nothing, no error message or any message but If I unplug the USB cable from the tablet, I get a message about the device being disconnected.
I rooted the tablet without issue close to the day after the stock firmware was posted. I used a program called "ImgRepacker" to extract the contents of the firmware image which were mostly ".fex" files. I read somewhere that you can simply rename the boot.fex file to boot.img and that worked. I patched it with Magisk and flashed it using fastboot and just like that, rooted.
And its been working fine until yesterday when i was messing with the build.prop file. I think its you who posted some performance tweaks in a different thread. I think I may have entered something incorrectly and rebooted and now it gets stuck right where the boot animation would normally start.
Its not an emergency but I just can't get this stock image to flash.. I have deleted the pheonix tools i was using and I downloaded the one posted here.
Bootloader is unlocked
USB ADB Debugging is enabled (well last I was booted up)
I can boot to recovery.
I can boot to bootloader (fastboot).
i can boot to fastbootd.
drivers have been a bit tricky:
when i was connected via usb to my pc (i'm using windows 11 btw)
with adb debugging enabled, as and also i had to enable file transfer mode to get "ADB Device" to appear. I would then have an "ADB Device" under the NEW heading "USB Devices" as well as "Scepter 8" under the heading "Portable devices" ADB commands seemed to work perfectly and I could copy files to "internal storage " so I didn't bother too much but I tried to update the drivers for "ADB Device" with the Google Android drivers and also with the ADB drivers included with Pheonix Tool but on both counts I was not able to and the message from windows was the driver files I selected were not the correct files for the selected device (period). Like i said that was working so...
Booting into recovery I was then able to install the ADB Drivers in the pheonix tool directory
Under "Android" heading was " Composite ADB Interface"
Booting Bootloader or fastbootd I was able to install "Bootloader Interface"
The Pheonix tool would recognize my device with ADB debugging, then i click upgrade with the v9 firmware selected and my tablet will reboot to download mode presumeably and the driver i was able to install for it shows up under the heading
"Universal Service Bus Controllers" as "USB Device(VID_1f3a_PID_efe8)"
Any Idea why I can't get the stock image to flash?
Why it looks like its about to start the flash but never does?
(sorry if that's too much info... and thank you for any help you are able to offer)
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Viva La Android said:
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Click to expand...
Click to collapse
I will give that a try and post back after. thank you!
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Shady8550 said:
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Click to expand...
Click to collapse
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Viva La Android said:
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Click to expand...
Click to collapse
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Shady8550 said:
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Click to expand...
Click to collapse
You definitely need to use PhoenixUSBPro if those instructions didn't work. With it, you don't need ADB Debugging to be enabled, nor do you need to manually.configure drivers. I plan on revising this guide later today with inclusion of PhoenixUSBPro v4.0.0, replacing PhoenixSuit.
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5568185
OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state.
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. If you have not, or if you are experiencing issues with device recognition, I have included a section below on installing the drivers.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
INSTALLING USB DEVICE DRIVERS
If you have previously installed ADB & USB device drivers on your Windows computer, skip down to the next section. Otherwise, download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop. Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers. Select "Y" again when prompted to install ADB as system-wide. Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched. Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer. It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the proper drivers.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 in the event you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
2. Download the V9 stock firmware package from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
3. Power off your Scepter 8 tablet;
4. In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
5. Now, click the Start button located in the upper section of the interface. A large green will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
6. Connect the USB data sync cable to your computer, but not yet your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key three times and then release Volume Down;
7. PhoenixUSBPro should recognize your device, initiating the firmware installation automatically. The flashing process typically takes about four minutes. When complete, you will see a green checkmark and a notification that the installation has finished;
8. Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on the V9 firmware build version.
DOWNLOADS:
15-Second ADB Installer v1.5.6
PhoenixUSBPro v4.0.0
Stock Firmware Image V6 **
Stock Firmware Image V9 (Latest)
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. Allwinner-based devices are not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
THANKS & MENTIONS
The PhoenixUSBPro tool was created and distributed by AllWinner Technology Co., LTD. Full credit for this tool goes to AllWinner. Thanks to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing factory firmware images for the QLink Scepter 8. Last, but not least, thanks to @13lack13ox for providing input and recommending the benefits of using PhoenixUSBPro in lieu of PhoenixSuit.
Click to expand...
Click to collapse
After trying all the software in Windows and in Linux, I
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
hayesy said:
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Click to expand...
Click to collapse
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
yup. Thank you. That did get it working again. I had actually figured that out previously. I had a super.img that i was able to dump previously and had already flashed it but i did not erase UDISK. I wonder if i should go back and do that.
Also because I never saved my original boot.img, I only have a the patched boot.img so i can't update but I'm really not worried too much about that. I doubt there will be many updates. (when I tried to restore stock using the boot.img i extracted from the firmware image v9, which is the one i patched with magisk to gain root, I end up in a boot loop. weird. --is that because i need to erase UDISK after flashing boot_a.img? P.S. just an observation, when i flash boot.img in fastboot, it gets written to the device as boot_a.img automatically for some reason.)
Thank you very much for taking the time to upload those files for me, that was really very nice of you. much appreciated!
comm-ents said:
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
Click to expand...
Click to collapse
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
hayesy said:
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
Click to expand...
Click to collapse
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Update: I am diligently working on the TWRP port for the Sceptre 8. Android 11 support for TWRP (primary, the dynamic partitioning scheme) is an absolute nightmare. Because A/B devices do not utilize an actual /recovery partition, TWRP must be installed to /boot. Although my TWRP port is booting and the touch GUI is functional, I am trying to iron out some mounting issues and decryption of some key partitions. I am hoping to get some one-on-one aide from a TeamWin dev and maintainer later this week. Once I iron out these issues, I'll be posting the TWRP build.
Viva La Android said:
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Click to expand...
Click to collapse
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
hayesy said:
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
Click to expand...
Click to collapse
Exactly. I need to take the time to write a flash-all batch file for fastboot installations. A flash-all batch script executes the fastboot commands and acts as an auto installer. Takes the work out of executing back-to-back fastboot commands. Your reasoning is correct.
Viva La Android said:
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
Click to expand...
Click to collapse
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
pyrohydrosmok said:
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
Click to expand...
Click to collapse
I'll need some more info. What exactly did you perform that caused the hang up at the lock screen?