Database Info

[ROOT][FIRMWARE][BOOTLOADER][RECOVERY] RCA Viking Pro (RCT6303W87DK) One Stop Shop!

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.

Root (almost) every device with Magisk + Fastboot

ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3

richarshub said:
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
Click to expand...
Click to collapse
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])

PoochyX said:
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Hi PoochyX,
Thanks for your reply, could you be more specific, please? Does it mean that this method cannot work on a/b devices?
I will edit my instruction again if needed.
Thanks for your suggestions!

"device is corrupt" solution guide for Nubia Red Magic 3 / 3S

Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android 9 again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Looks like you've been using another cell

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
give me something i can contact with u in to help u

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
[email protected] u can contact me here sir

I need some help,
Last time i updated my phone to 5.09 cn rom after that when i got bugs i tried to downgrade to 3.34 and i bricked my phone , then i use unbrick tool and get back to asia version but now my phone doesnot have the charging animation in power off mode and also fastboot device is can't get the device in win7/win 10. I also tried 2-3 times by reflash the cn rom and again back to asian version.
Need help any guide please.
Thanx in advance..
I forgot to mention that adb is working, bootloader is unlocked, i can access bootloader by using keys and adb reboot-bootloader command, but can't get device in device manager in fastboot mode , i can also access 9008 mode and recovery mode. Everything working fine but i have that two issue now, also i have my device in 5.11cn rom now.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
I think I encountered this problem also when going from Android 11 (V5.11) to Android 10 (V3.34). What worked for me is the tool posted on nubia bbs.
It's on chinese but I put some screenshots on this link to be able to use it.
Red Magic 3 - Mediafire
To use the tool, put your Red Magic 3 on fastboot mode.
How to boot on Fastboot
1.) Turn off your NRM3.
2.) HOLD Volume down and power
3.) Your NRM3 should boot on fastboot
And for google play store, I'm currently using 5.09 and successfully root it with g-apps. Flashing magisk and g-apps is working ong V3.34 and V5.09.

I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now

cacaocaca said:
I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now
Click to expand...
Click to collapse
Have you tried to on the developer options and turn on USB debugging on your Red Magic 3?

How can I activate the debug if just show me that
{
"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"
}
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance

Maybe it hardbrick

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
can u help me too pls

cacaocaca said:
How can I activate the debug if just show me that View attachment 5173669
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance
Click to expand...
Click to collapse
I think you should try service centre once.

jhonangelo30 said:
can u help me too pls
Click to expand...
Click to collapse
Okay pm me

3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school

johnbrinan1 said:
3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school
Click to expand...
Click to collapse
don't worry it can be fixed

RoseRahman said:
I think you should try service centre once.
Click to expand...
Click to collapse
My phone was in assistance and now it come back and work fine , no more device corrupt and no more slow charger , they did exachange the motherboard on my phone , if you will not ear the sound while plug the device to windows this mean problem motherboard maybe like me

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?

ZephyrOne said:
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?
Click to expand...
Click to collapse
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.

leipnacht said:
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.
Click to expand...
Click to collapse
Hello thanks for your help, the problem is that I do not enable oem unlocking in the system. Do you know if twrp can be installed without that option?

[OnePlus6] Phone frozen (bricked?) while installing Kali NetHunter.

Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.

To fix your phone, you should use this recovery tool.
https://forum.xda-developers.com/t/op6-latest-10-3-8-collection-of-unbrick-tools.3914109/
You can follow a tutorial like this one
Good luck

You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.

d
CarlosTime said:
You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.
Click to expand...
Click to collapse
Thank you. I am trying the suggested video right now.
Do you also know why I get the storage error while trying to flash nethunter?

take it easy, relax i have a long story with oneplus too
send me msg on telegram so i can help u 98%
uaername : NotReal0
stay safe bro, and dont worry i dont need you money just bc im noob with english so i just know that u damaged ur phone and i know how to fix

saffron_jedi said:
Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.
Click to expand...
Click to collapse
I had the same issue after trying to install nethunter myself. Unfortunately for me the MSMDownload tool wouldn't work because I couldn't get the phone to stay off, it would just boot back up into bootloader/fastboot mode as soon as I connected to the computer via usb cable.
Here's the solution that will work 100%. Go to this website below and download the stock OOS zip file for your phone, in my case it was the Oneplus 6T fastboot ROM. Unpack the files into your platform-tools folder, click skip all if it asks you if you want to replace any files in that folder, then run the flash-all.bat and it will unbrick your device. Keep in mind that it will unroot your device and remove twrp as well. There's a thread here that explains how to do it manually so that doesn't happen but its a bit of work to get it done that way.
FastbootRoms Activity
sourceforge.net

[GUIDE][FIRMWARE] QLink Scepter 8 (Gen 1 & Gen 2) Factory Firmware & Upgrading Guide

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 Images​Gen 1 Models​​MD 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 5554999​OVERVIEW:
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?