Related
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
This will also work for the PLT1065G but you need to use different recovery/parameters. The kernel is different (looks like a different touchscreen).
Thanks for this. Got one for $50 at Loblaws today. Will attempt rooting.
Got it for my 6 yr old
Edit: Fixed boot issue
protectivedad said:
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
Click to expand...
Click to collapse
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Friko said:
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Click to expand...
Click to collapse
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
protectivedad said:
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
Click to expand...
Click to collapse
I've been fiddling with it and it seems to be completely random. So I guess it's something we'll have to live with.
I bought it for my 6 year old who's dying to play Pokemon Go. The app runs okay on it. It's just the 'GPS' (or lack of a proper GPS chip) that's a bit slow/inaccurate
Hello I to bought this tablet in Canada I successfully rooted it but is there a reason why no other cameras can be downloaded or Music players or Instagram.
Is thee any chance to unbrick this tablet?
I have one stuck in the boot logo, hard reset wont solve, is there any flash file?
Hellooooo !!
anybody here ?
---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------
ANYONE TEIED THIS FIRMWARE?
https://mega.nz/#!TVFX0CiZ!6CaGOSGZM47PQAd9KZDuKcPJaXsCL3n3JJQBtXPRHJo
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
yurais said:
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
Click to expand...
Click to collapse
There is a way to create an SDCARD and it will run from the SDCARD. I've forgotten how . I'm looking at one of my kids cracked ones right now. The touchscreen is cracked so I'm looking at build Ubuntu for it. I'll post when I figure out the SDCARD again.
Reset tablet to factory
I was able to use the factory irmware to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Let me know here as soon as you just remember anything related to this.
I got another tab like this, screen cracked and I could read off its firmware, so I now have a working firmware waiting to be written...
Enviado desde mi SM-N920T mediante Tapatalk
Thanks so much for this guide. I picked one of these up for $6 when HHGREGG was closing.
Proscan PLT7650G
Good day is there a guide and firmware for a Proscan PLT7650G
Technician
protectivedad said:
I was able to use the factory irmware[/URL] to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Click to expand...
Click to collapse
How did you flash the image? what software did you use,
Thanks.
it's not possible to change the rom or custom image of the tablet to another operating system like ubuntu or linux. It has allow OEM bootloader unlocked in the settings in developer section greyed out and it doesn't allow oem bootloader unlocking 'enabled'. You cannot enable it.
What you are doing is just resetting the factory image. or rom. you can just push the reset button with pin after charging the tablet for 3 hours.
These tablets are not 'cheap' to make and google, cell phone companies subsidize these 'cheap' tablets. so you have to use and pay them when you subscribe to their cell phone 'service' or google advertisements when you use their 'service'.
Lots of vaporware being pushed saying they can unlock something for $40 or downloading tools etc. wasted of time as it's impossible to unlock oem BOOTLOADER if the manufacture has locked it, you cannot install another operating system in the tablet, or smart phone. so don't waste your time.
Only some phones allow oem unlocking bootloader and those are the higher end phones costing $400-$600 for a tablet that are not 'subsidized' by google or you cell phone company as with 'cheap' phone or tablet.
the firmware is not available for download at the manufacture website that should raise alarms about the firmware. I've factory reset the device and now it's having reboot issues, either the firmware is defective or corrupt bootloader etc. The manufacture proscan seems to be selling the devices yet no technical support or even a direct download from the manufacture, downloading firmware from thirdparty servers is security risk. it seems like today lots bogus websites and no technical support from manufacturers in tech devices they sell. and people have to sites like XDA for 'free' technical support. Even Microsoft which makes billions in profits fail to provide proper technical support for some reason. and have to rely on 'free' technical support for bugs and issues with their software and hardware and lots vaporware apps etc.. bogus apps. that don't work.
Rooting gives the user the ability to install and change OEM software. from what i gather so don't waste your time, to root a device, allows the user to delete operating system files. if the manufacture doesn't allow changing the oem software there is nothing you can do. about so don't waste time trying root it or try to install ubuntu or linux on the tablet or smartphone if it's oem LOCKED. bootloader. you cannot unlock it. it's much harder to unlock oem software.
the method to 'restore' factory image or known as 'flashing the rom'
there is no reason to flash the rom etc.
1. just hold the power button and esc button at the same time
2. release the power button wait 2 seconds
and then release the esc button
you should now be in boot up mode.
this unit doesn't allow you to be in bootloader mode. so you CANNOT install another firmware or install linux etc. other than the proscan firmware.
3. press esc to select restore the factory settings
4. press the power button to select
this the easiest way to restore stuck in browser or need to flash the rom
again if the rom is 'corrupt' which is not likely
if that is the case
the option to "apply update from external storage" doesn't seem to work as you cannot mount to flash the rom and reinstall the .img file from the .zip file
"apply update from external storage"
where you saved your .zip doesn't work
the apply updated from ADB works you need a usb computer hooked up to you computer and terminal command to ADB to your table to rinstall the .imge file
update ,this no longer seems to work in installing the .zip file method to install the firmware.
lot of software and hardware that have no technical support or documentation and the stuff just doesn't seem to work and high security risk with no updates from manufacture as it cost them money to resolve issues. selling disposable technology tablets. that is not meant to last. basically toys. for kids.
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Donphillipe said:
I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Click to expand...
Click to collapse
Hello,
Please try posting your query here Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
If you dont have full ROM backup from your device or official ROM, dont do anything in terms of modding but to install vcom drivers (in my case they wont work without Virtual Serial Port Drivers) for bootloader, and adb/fastboot drivers, make sure theyre working, install Miracle Box / SPFlashTool (or similar ?) to be able to backup/flash your ROM/partitions from/to your device.
Check if it works for you (ie backup your ROM and try to flash something (cache) back.
Now when people are scared enough I want to tell you that it is almost impossible to kill (brick) your MTK phone, it happens mostly when people flash something that is not suppoused to be flashed (something from another device), the worst case if you flash wrong preloader or erase preloader but even after this there is a chance for resurrection. it takes time and efforts though.
++++++++++++++++++++++++++++++++++++
This is TWRP 3.2.2.0 recovery for Chuwi hi9 Pro.
Partitions available for backup:
boot, recovery, system, vendor, data (not incl. data/media = internal sd), cache and "para" (if you have got "recovery loop" - flash "para")
.img flashable - boot, recovery
look for detailed instructions for coomon things in other treads, like
- how to install bootloader vcom drivers and adb / fastboot drivers
- How to work with adb / fastboot command from your computer cmd window.
- how to use Miracle Box / SPFlashToll
This is detailed instruction how to make SPFlash backup out of your phone though Miracle Box does it in one click (well, almost)
- how to unlock bootloader (fastboot mode)
- how to use toilet paper (manual mode)
- how to install twrp recovery
- how to root
Unlock, Install, Root in one post
++++++++++++++++++++++++++++++++++++++
So, main point of this thread is TWRP, youll need:
- roll of toilet paper
- spflashtool backup (just in case)
- backup of your data (if you care) - your data will be erased during the process.
- unlocked bootloader
- twrp image
If something went wrong (highly unlikely), but "if".
Worst case scenerio: your phone will not boot into system / recovery
Solution: reflash (fastboot or flash tool): boot / recovery / system
Worst case scenerio: flash factory ROM (SPFlashTool)
Steps to do when you have all knowledge and all files ready.
IN YOUR CURRENT SYSTEM
In settings->System->About tablet -> click several times "build number" untill you see message "now you are developer"
In settings->System->Developer options: Enable USB debugging and OEM Unlock, connect cable
REBOOT INTO FASTBOOT
Power off, Power on holding "vol+"
Youll see black screen with 3 strings of menu (very small font):
- recovery
- fastboot
- system
use "vol+" for navigation, use "vol-" to confirm your choice (fastboot)
OR from your pc cmd window (shift+right click on adb folder -> choose "open command window here") type: adb reboot bootloader
press Enter
UNLOCK BOOTLOADER
on your pc (if cmd window is not ooened yet: shift+right click on adb folder -> choose "open command window here") type: fastboot oem unlock
press Enter
watch your phone and pc screen for messages
if you have vision problems, make sure you have a magnifying glass.
INSTALL TWRP
download hi9pro_twrp.img to your /adb folder
from the same cmd window type:
fastboot flash recovery hi9pro_twrp.img
*
Reboot into twrp and flash Magisk
*
Basically this is it
There is no command from fastboot to reboot into recovery (correct me)
You can power of, power on holding "vol+", choose "recovery" from menu
command to reboot into system: fastboot reboot
+++++++++++++++
* NEW *
Infect_Ed has posted TWRP recovery that he has compiled from source. DOWNLOAD FROM HERE
We don't know how to make twrp recovery work with encrypted data partition.
Read next paragraph if you are OK to trade security (encripred userdata) for functionality.
++++++++++
==========
In case you want to have your userdata decrypted (and full functional twrp), use following steps:
*** Please, note all userdata AND internal SD will be wiped during the process***
If you care
Save Internal SD card content to your ext.SD or computer
Make a Titanium backup of user apps (check Enable external data backup in Titanium settings)
If Titanium fails to write to your ext.SD than change Titanium backup folder location to int.SD
and after backup is done copy Titanium backup folder to ext.SD or PC.
Disable any passwords/pins from Settings->Security & Locations
(I know they are stored in /data/.. and will be erased anyway but just in case)
- Reboot into TWRP
- ftom TWRP -> Wipe ->Format userdata -> Confirm with "yes"
do not reboot into system
- flash encryption_prevener_hi9pro.zip to prevent system automatically encrypt userdata (it is used to insert modified fstab.mt6797 into vendor/etc)
- reboot system
- restore your int.SD content and apps
============
Link to official ROM/Firnware
*** Read this if you have Recovery Loop - no matter how you boot (buttons, from twrp recovery or from adb/fastboot shell) your device you always end up in TWRP recovery ***
- download 2018-09-29--para.zip
- unzip it - there is a folder 2018-09-29--para with 3 files inside
- connect your phone in twrp recovery mode to your computer
(you may need to turm "enable mtp" option in TWRP->mount)
- copy that folder into your sd card, the path is : TWRP/Backups/Hi9Pro
- click "Restore" (on the next screen make sure ExtSD is chosen as backup path)
- check checkbox "para", run restore, reboot
explanation: para is a partition contains last issued kernel reboot flag(command), like "reboot to recovery, reboot to system, etc." I think there is one flag that tells to kernel something like "reboot to recovery, do something untill its done", since this "something" never done, device reboots into recovery over and over again. This happend to me when I tried "factory reset" command from android settings, so android have sent my device into recovery mode where that "factory reset" command had to be performed but never done because its now not stock recovery but twrp.
**** If you have following problems:
Unknown Baseband -> Unknown IMEI -> NO sim card -> NO cell network
Look here first
****
***** If you came here from there.*****
and you are following their instructions, please, note, step 7. Unlock bootloader : DO NOT DO command "fastboot flashing unlock", just skip it.
Also, try to avoid "fastboot boot recovery.img" command to reboot into recovery (just use physical buttons for reboot). I'm not sure but something caused "recovery loop" in one case at least.
****** back-to-encr.zip if you want to encrypt your decrypted userdata (original fstab.mt6797 will be flashed, no data loss, you will not be able to mount userdata in TWRP, first boot may take long time due to encryption process - 10-60 min- depends how much data do you have)
******* twrp_recovery_chuwi-hi9pro_infectEd-XL is same Infect_Ed recovery adopted for our screen.
Hello. I made a mistake last week. I flashed accidently twrp with a scatter File from the HI9 Air through the spflashtool on the Hi9 Pro. Now it doesnt turn on etc. Is it hardbricked or can i still get it back to life?
No, its not complitely bricked if flash tool still recognizes your phone in bootloader mode. Most likely youve made same mistake I did. Depends of how you flashed that recovery - recovery only or full sisyem WITH new recovery. most likely you flashed only recovery partition. than, first, try to reflash backed recovery & next to recovery ("para") partition. in "download only mode" therell be an error "pmt has changed" than try "format & download" and "firmvare upgrade" - use scatter file contained only those two partitions. if you didnt make a backup ill put here that "para" partition and you can use hi9pro twrp img. in case this wont work, you may want to reflash the whole rom. We need to find factory rom image (from Chuwi or someone who did a back up prior he entered his credintals - thats another mistake Ive made Ive dumped a rom with all my logins information). if I have time I'll try "factory reset" to make a backup from "clean" system.
again, its almost impossible to brick mtk completely. even if flash tool doesnt recognize you phone (dead battery) there is a jump-pins method.
upd. Just looked @ Air scatter and found that Air recovery partition size is same as Pro (~16mb). now I dont know haw was that possible to overwrite next to recovery partition(s) and I think I used same Air img as you did and I've got size warning message when I flash it. anyway here is archive with scatter for recovery and para. just add twrp hi9 pro recovery (rename recovery.img to recovery.bin) and try to flash.
I didnt made a Backup (stupid me) i flashed the recovery file with a scatter file. When i plug the device in the pc the USB sound comes and its recognized as MEDIATEK USB PORT (COM8), but its removed automatic (USB Sound for disconnecting) The Screen stays black. So i have to wait for a Rom and a scatter File then?
---------- Post added at 19:50 ---------- Previous post was at 19:39 ----------
I tried your idea. I got an error Message: "Status Preloader Invalid" The Preloader File Format is invalid.
you know how to use flash tool , first you have to press "download" THAN connect usb cable.
but this is a good sign (pc recognize something), you may want to google for something like "unbrick mtk 6797 sp flash tool" for more info
this is archive w. 4 1st partitions (incl preloader)
Ive gotta go. Dont smash your tablet its 100% repairable, well 99.999%
thats how it looks
https://photos.app.goo.gl/9EK8vTwcTS3fDf1a7
---------- Post added at 20:21 ---------- Previous post was at 19:58 ----------
Still get an error Message for the PRELOADER. I read some Tutorials and dont find a Problem in my setup or my doing. Sucks :-/ But Thank you very much for your help
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Good Morning.
Bootloader is unlocked, no matter which key combinations ill try the screen stays black. When i have the usb cable at the PC (no matter which Port or cable) it the plugin - plugout sound plays every few seconds/minutes (not the same time in between). It is recognized as "MediaTek USB Port (COM4)" (different PC i tried). When ill try to install the vcom drivers i get the message that the best drivers are already installed and that are the mediatek usb port driver.
Image of the device manager: https://ibb.co/erkW6e
zelipukin said:
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Click to expand...
Click to collapse
---------- Post added at 07:34 ---------- Previous post was at 07:07 ----------
zelipukin i made a short Video about the behavior. The Device seems to activate when i push vol+ or power, but it looses connection when i stop holding the button or sometimes even when i hold the button.
https://drive.google.com/file/d/1m3YLrH5ZaVLttcSfDxx3RvL0DaXPcxzk/view?usp=sharing
...thinking
Just tried...seems like backups I made(and posted here) from Miracle Box is incompatible with SP Flash.
SP Flash doesn't like this and doesn't like that when tries to restore those backups but Miracle Box restores individual partitions or whole ROM w/o problem.
SP Flash is so inconvenient if you try to make a backup ... its also inconvenient when you try to restore.
Where did I get that Miracle Box for free ?
Let me figure out something...
....
This is something beyond my understanding but let me to describe what I did
- in SP Flash I choose scatter file and recovery.bin (like I sent to you)
- download only - no go
- download+format - no go
- firmware update - warning message about wrong partition size or something like this - Ignored - Flashed
- Bricked again (like yours - black screen - that's it)
- OK, I have several backups. Tried all of them - none of them works... except one
- Flashed that backup with SP Flash - no questions, no warnings, no errors - device came alive
- Flashed only recovery.bin - everything went fine
- Tried to find difference btw different backups - but couldn't find any
- So I tried to flash those files (to try 3.zip) several times and everything went OK, so this is 100% working backup.
Try it and see what happens, then we can go somewhere else. I still suspicious about those MTK Usb Com(8) instead of preloader usb. Also if you used "Firmware upgrade" option once, I beleive you'll need full ROM flash. Keep looking for it @ Needrom.com.
Strange things happen. Couple years ago I lost MTP connection with my MiMax. I tried everything possible but no luck - have to use UMS Enabler so I can read/write ExtSD at least, but MTP works with Chuwi.
I spent numerous hours trying to connect Chuwi in preloader mode until found that solution about Virtual Serial Port drivers.
Thanks for your help so far. Seems like my Device is half dead after 2 Hours of use
I'll tried to change the Drivers for the mediatek, it shows the device now with the preloader, but i think it doesnt work right. when i change the usb port it comes back as MediaTek USB Port (COM4). I made you a 15 Second Clip of the behavior.
https://drive.google.com/file/d/1m7wyIlIYJLN7ikmgUTzHBJtBdbZQrYaa/view?usp=sharing
Really weird. :-/
---------- Post added at 14:55 ---------- Previous post was at 14:40 ----------
and no chuwi hi9 pro rom at needrom yet. :-/
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
i think i used the upgrade one, after download only didnt work.
Ill tried the same method with changing drivers.
I will sit this one out, till you have uploaded the rom
Thanks for helping me out!
zelipukin said:
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
Click to expand...
Click to collapse
Just a few questions after using Hi9 Pro for about a week:
1) Where is the microphone ? Is it the small hole under the volume button ? (Strange position)
2) On the back side the two metallic stripes separating the plastic of the metal body are they something like antennas ? (LTE or WiFi or both ? )
3) What is the version of Bluetooth ? (4.0 or 4.1 or 4.2 ? )
4) Is it possible to use some kind of fast charging with a suitable charger or software app (firmware update) ?
MediaTek has a technology called "Pump Express" or something like that...
5) Do you have sudden, unexpected pop-ups of full screen advertisements while you are working with your tablet ?
How do we get rid of them ?
6) How do I find the LTE band the tablet is actually using while it's in use ?
I don't mean the table of supported bands, I mean the active band while using it.
Thanks!
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
2) not sure, but most likely
3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
4) too many different opinions, cant find the truth
5) none so far
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
zelipukin said:
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
Click to expand...
Click to collapse
Yes, it is a very small hole at the bottom right as you hold it, with a size of the edge of a needle!
zelipukin said:
1)3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
Click to expand...
Click to collapse
Thank you.
zelipukin said:
5) none so far
Click to expand...
Click to collapse
But how did you do that ?
Did you add an Ad Block after rooting the tablet ?
The kind of ads I get, is more of suggested apps to install from Google Play.
It is literally bombarding me with an exhaustive rate.
I went to settings to "advertisements" of Google and it says that I can't turn it off.
Could it be some app that I installed that is spamming me this way ?
Can you suggest something to stop it ?
zelipukin said:
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
Click to expand...
Click to collapse
I installed LTE Discovery and although I'm not rooted it seems that it works OK and it's showing me the bands.
The signal strength is lower than a mobile phone at the same position, same time, same provider.
Do you have an equal signal strength like your mobile phone ?
One more question:
7) Is it feasible for a developer to build a custom ROM for this device if he wants to or there are certain restrictions forbidding custom firmware ?
Is there any chance for a custom ROM in the future, because I don't think Chuwi will upgrade to 8.1 or better Android.
Thank you!
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed. I didn't do any system modifications except installing Magisk and modules - ExCard Access Enabler, init.d injector, Magisk SELinux Manager, ViperX (slightly better sound from speaker)
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
zelipukin said:
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed.
Click to expand...
Click to collapse
Me too, I got a sealed and clean tablet from GearBest but If you look closer to that setting, it says that you can turn on or off the specialized ads for you, but you can't close ads completely.
For example, during web browsing do you see ads inside various sites ?
Or when opening apps on your tablet ?
I think we need an ad-blocker for this.
zelipukin said:
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
Click to expand...
Click to collapse
I meant for mobile 4G data, not as a phone.
In my country we have three bands for LTE:
B3, B7, B20.
When the tablet rotates between 3 and 7, I have poor to zero signal.
But I saw with LTE Discovery that when it switched to 20 then the signal is very good.
So, with the help of MTK Engineering I disabled 3 and 7 bands and everything seems OK now.
I hope B20 to be used everywhere near to me.
zelipukin said:
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
Click to expand...
Click to collapse
I'm not familiar with Android internals so much, I am only using a Note II with TWRP and a custom 7.1.2 ROM and I'm missing some simple customizations not available with out Oreo 8.0 stock ROM.
I haven't even tried yet your first post regarding rooting and all the others because I'm not so sure where to find these tools and how to use them.
It could help a lot when you find some time to add more descriptions and links in your first post, if possible like Hi9 Air thread.
Thank you!
I dont know how and why, but I dont have any agressive advertisements. Checked Opera I'm using for webbrowsing - even "block popups" option wasn't checked. Had to download app yesterday (AutoNotification) from gp store and when I started it in a "free mode" there was a message like "to use this app in a free mode you have to agree to see ads", clicked "ok" , then message "downloading..." appeared...and nothing, no ads. I connect my tablet to the internet through my phone but dont think that matter.
Just a few more short questions:
8) Is there any other way to wake up the device instead of pressing the red button ?
For example double tap or maybe using the volume buttons or any other way.
Because I'm afraid of pressing the same button again and again.
9) Does this device have a WiFi 2x2 MIMO ?
I haven't found any particular info on this.
10) What is the kernel of the ROM ?
Is there any GUI compatible like Kernel Aiutor to make changes or take a look at info for the device ?
Thank you!
QLink Scepter 8 Tablet
Gen 1 & Gen 2 Models
Factory Firmware Restoration
And Upgrading Guide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OVERVIEW:
The manufacturer of this tablet, Hot Pepper Mobile, has graciously provided me with some factory firmware images for the Gen 1 and Gen 2 models of the QLink Scepter 8. Accordingly, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
This guide will be outlined to provide four firmware installation methods, all of which will focus on a Windows-based setup: (1) PhoenixUSB Pro; (2) LiveSuit; (3) PhoenixSuit; and (4) PhoenixCard. These four utilities were developed and released by Allwinner Technology Co, LTD. As such, each proprietary tool provides a comprehensive solution for restoring your device to its stock factory state. While any of the four outlined methods will ultimately achieve the same end result, members may find that one particular utility is simpler to use or works better than the others. In short, versatility is the focal point. The first three methods are standard proprietary strategies for flashing vendor-specific firmware images to eMMC NAND storage. These tools flash your tablet from a powered-off state known as FEL mode, a proprietary flashing protocol based on BROM. It should be noted here that some members have experienced device recognition issues while using PhoenixUSB Pro, PhoenixSuit and LiveSuit. For members who are experiencing insurmountable device recognition issues, I e. the flash tool not recognizing your tablet once it is in the powered off FEL flash mode, I have included a new section in the instructions for installing the proper Allwinner FEL mode drivers. This section should remedy any such device recognition problems. Also, the 4th method, PhoenixCard, may provide you with a viable solution to device recognition problems. PhoenixCard enables users to write a full firmware image to a micro SD card which, in turn, is inserted into the tablet's micro SD card slot. The tablet is then booted, at which time the firmware image on external storage is written to NAND/eMMC flash memory, thus fully restoring the tablet to its factory state. The PhoenixCard method is ideal for users with unresolved device recognition issues, or in scenarios where the partition index has incurred major corruption and fails during standard firmware restoration procedures.
HARDWARE VARIANTS:
There are a four (4) different variants of the QLink Scepter 8, categorized under the two (2) primary hardware models Gen 1 & Gen 2. The original Gen 1 model, released in April, 2021, shipped with an Allwinner-A100 chipset, 1 GB RAM, and Android 11 (Go Edition) preinstalled. The latest Gen 2 model, released in mid-July, 2022, ships with an upgraded Allwinner-A133 chipset, 2 GB RAM, and runs on Android 12 (Go Edition). Regardless of which gen model you own, your device serial number will begin either with the two letters MD or the two letters CF. Hence, there are two variants of the original Gen 1 model, and two variants of the latest Gen 2 model. I am referencing these models and variants in order to emphasize that they are not intercompatible in terms of firmware. Determining your variant is very simple: if your tablet has Android 11 (Go Edition), you have the original Gen 1 model. And, if you are running on Android 12 (Go Edition), you have the latest Gen 2 model. Once you determine which model you own, simply check the first two letters of your device S/N to determine the variant. To avoid confusion and potential firmware mismatches, I have categorized the firmware images under their corresponding models in the downloads section. These sections have further been subdivided under the appropriate S/N variants. Ensure that you download the correct package based on your S/N variant. Otherwise, the Allwinner proprietary flash tools used in this guide will not commence with the flashing process.INSTALLING ADB & FASTBOOT:
While this step is not absolutely required in order to perform a firmware restoration of the QLink Scepter 8, it's a good idea to go ahead and get this taken care of for future needs (e.g., unlocking the bootloader and rooting, if you plan on performing those tasks later on). All of the flash tools referenced in this tutorial are capable of restoring a QLink Scepter 8 which is bricked (a tablet which is unable to boot to the Android OS, and/or unable to boot into either recovery or fastboot mode).
If you have previously installed ADB & Fastboot, as well as the relevant USB device drivers on your Windows computer, skip down to the next section. Otherwise,
Download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory.
Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers.
Select "Y" again when prompted to install ADB as system-wide.
Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched.
Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer.
It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the ADB & Fastboot tools as well as the Google universal device drivers.
INSTALLING ALLWINNER USB DRIVERS:
The first three firmware flashing tools outlined in this guide -- PhoenixUSB Pro, LiveSuit and PhoenixSuit -- restore factory firmware by flashing the NAND/eMMC directly, with the device in a powered-off emergency flashing state known as FEL mode. FEL mode is the Allwinner proprietary firmware flashing protocol based on the hardware embedded Boot ROM (BROM) implementation. All three of these tools utilize FEL mode when flashing firmware to your tablet's NAND/eMMC internal storage device. FEL mode is initiated one of two ways: (1) if the tablet is booted into the Android OS while connected to your computer, the tool will recognize your device, via USB Debugging, and once firmware flashing is ready to commence, the tool will boot your tablet into FEL flash mode which, again, is a powered off state; or (2) if your device is bricked, stuck in a boot loop, or is otherwise unable to boot up, FEL mode can be initiated manually by performing a particular hardware key sequence while connecting the powered-off device to your computer. This key sequence is outlined below in the instructions. In either scenario, your tablet will not be recognized by whichever flash tool you are using unless the proper drivers are installed on your Windows PC or laptop.
Typically, on both Windows 10 and 11, generic drivers bundled with the operating system will enable proper recognition of your tablet while in FEL flash mode. However, because some members have encountered issues with the Scepter 8 being recognized by these flash tools (while in FEL mode), I am including this section to ensure proper Allwinner USB driver installation on your Windows computer, before we get started with the flashing procedure.
Download the Allwinner FEL Driver v1.0.0 from the link provided below, and extract the contents of the archived file to your desktop or another convenient directory;
Right click on either the dpinst_x86.exe file (for 32-bit Windows), or the dpinst_x64.exe file (for 64-bit Windows), and choose to run the application as an administrator;
Follow the prompts on the driver installation wizard to install and configure the drivers on your computer. Once complete, a notification will indicate that the installation was successful;
Select Finish and reboot your computer. Your tablet should now be recognized by the respective flash tool while in FEL mode, thus enabling the firmware restoration process to properly commence.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
Furthermore, some of the firmware restoration methods outlined below will result in all user data being wiped on your device. Before proceeding, and if possible, make a backup up any important files and media that you wish to preserve.
I. METHOD 1
PhoenixUSB Pro For Windows
PREREQUISITES:
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image that corresponds with your tablet variant (links provided below). In this first section, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state, via FEL mode.
Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware in the event you are running an older firmware build version.
Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
Power off your Scepter 8 tablet;
In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
Now, click the Start button located in the upper section of the interface. A large green checkmark will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
Connect the USB data sync cable to your computer, but not yet to your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key continuously until PhoenixUSB Pro recognizes your device, then release Volume Down. You will know your device has been recognized by an on-screen prompt indicating that the firmware installation is initiating;
The flashing process typically takes about four minutes. A progress bar on the PhoenixUSB Pro interface will show the percentage of completion in real time. When complete, you will see a green checkmark and a notification that the installation has finished;
Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on an unmodified stock firmware build.
DOWNLOADS:
• 15-Second ADB Installer v1.5.6
• PhoenixUSB Pro v4.0.0
• PhoenixSuit v1.10
• LiveSuit v1.11
• PhoenixCard Image Burning Tool v4.2.4
• Allwinner USB Driver Installer v1.0.0
Factory Firmware ImagesGen 1 ModelsMD SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v11_20221213
CF SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v13_20221212
*** *** *** *** *** *** *** *** ***
Gen 2 Models CF SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v03_20221126
MD SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v01_20220915
$$ DONATIONS $$
I do not expressly request or expect donations from members for my work. I adhere firmly to the open source and free use spirit of the Android OS. With that said, for any members who want to donate something, it would be a huge help. Firmware images for both the Gen 1 & Gen 2 Scepter 8 tablet models were previously unreleased to the public. It took several weeks of discussions with Hot Pepper Mobile Tech Support and its CEO, Mr. Shawn Sun, to obtain official firmware images for this tablet.
This is my CashApp link where you can give as little as $1. For those unable to help financially, I understand. A tap on the thanks button, however, doesn't cost a thing.
PayPal Donation Link
CashApp Donation Link
II. METHOD 2
PhoenixSuit For Windows
PREREQUISITES:
As with the previous section, you will need a PC or laptop running Windows 7/8.1/10/11, the OEM-supplied or a quality equivalent micro USB to USB-A data syncing cable, the PhoenixSuit v1.10 flashing utility (link provided below), and a factory firmware image for your QLink Scepter 8 variant (links provided above). This section presumes that the correct USB device drivers are installed on your Windows computer. If you have not installed these, see my section above titled INSTALLING ALLWINNER USB DRIVERS, then return here once you have completed those instructions.
FIRMWARE RESTORATION/UPGRADE:
Download PhoenixSuit v1.10 from the link above and extract the contents of the archived file to your computer desktop, or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link above, and extract the firmware image (.img file) to a convenient directory on your computer;
Launch/Open PhoenixSuit by double clicking PhoenixSuit.exe from the directory you extracted in the first step;
Click on the Firmware tab in the top section of the interface and click on the blue Image tab. Windows File Explorer will be launched; navigate to the location of the firmware .img file you downloaded and extracted in the second step;
Power off your tablet;
Connect your data sync cable to your PC but not to your tablet. Hold Volume Down and, while continuing to hold the key, connect the micro USB end of the data sync cable to your tablet. Now tap the Power button (up to ten times) until PhoenixSuit indicates recognition of your device;
You will be prompted to perform a mandatory format. Select Yes to proceed;
PhoenixSuit will initiate the firmware installation. Once complete, an Upgrade Firmware Succeed notification will be displayed. Press Ok to finish the process.
Disconnect and reboot your device. . Your tablet should be now be restored to its factory stock state.
III. METHOD 3
LiveSuit For Windows
Like the previous two methods, LiveSuit is a proprietary NAND flash tool developed and released by Allwinner Technology. LiveSuit is available for the Windows, Mac and Linux operating system platforms. This particular guide, however, will focus strictly on a Windows setup. You can download LiveSuit for both the Mac and Linux platforms here: https://androidmtk.com/download-livesuit-all-versions
The tools available for download are trusted, verified, and have been thoroughly scanned for viruses and other types of malicious code. A comprehensive guide for using LiveSuit for Linux can be found here: https://linux-sunxi.org/LiveSuit
Without further ado,.let us proceed with LiveSuit for Windows.
PREREQUISITES:
Once again, you will need a PC or laptop running on Windows 7/8.1/10/11; the factory-supplied or a quality equivalent micro USB to USB-A data syncing cable; LiveSuitPack v1.11 (link available above); a firmware image compatible with your model/variant of the QLink Scepter 8 (links provided above); and the proper USB device drivers installed on your Windows computer. If you have not yet installed the driver's, follow my section above titled INSTALLING ALLWINNER USB DRIVERS. Return here after following those steps.
FIRMWARE RESTORATION/UPGRADE
Download LiveSuitPack v1.11 from the DOWNLOADS section above. Extract the contents of the archive to a folder on your desktop or to another convenient directory;
Download a firmware package compatible with your model/variant of the Scepter 8. In the simplest terms, if your tablet shipped with Android 11 Go Edition, then you must use a firmware package that corresponds with the Android 11 Go Edition build. If you have the newer variant that shipped with Android 12 Go Edition, then use firmware from that heading only. Once downloaded, extract the .img firmware file from the archive and save it to your desktop or another easily accessible location;
Open the LiveSuit flash tool by double clicking LiveSuitv1.11.exe in the directory you extracted in the first step. Once launched, select YES to follow the Upgrade Wizard;
Click the Upgrade Mode tab and then select Mandatory;
Disconnect any connected mobile devices from your computer, and select Next;
Select the Yes option, then.Next, and select the firmware .img file you extracted in the second step. Now click Yes but do not select Finish;
Ensure your tablet is powered off. Connect the data sync cable to your PC but not yet to your tablet. Hold the Volume Down button on your tablet. While continuing.to hold the botton, connect the micro USB end of the data sync cable to your tablet. Without releasing the Volume Down button, press the Power key 5 to 10 times, or until you are notified by LiveSuit that your tablet has been recognized. Click Yes to proceed with firmware installation;
A progress bar on the LiveSuit interface will reflect the percentage of completion in real time. Once complete, an Upgrade Succeeds notification will be shown. Click Ok and then Exit.
Reboot your tablet, which should now be restored to its stock factory state.
IV. METHOD 4
PhoenixCard for Windows
PREREQUISITES:
As referenced previously, PhoenixCard is an Allwinner proprietary tool for burning a factory firmware image onto an external storage medium such as a micro SD card. In turn, the micro SD card is inserted into the tablet's card slot. Once the tablet is powered on, the firmware image burned to the micro SD card will then be written to the tablet's eMMC flash storage, thus restoring the device to its stock factory condition
As you may have guessed, you will need a PC or laptop running Windows 7/8.1/10/11; a micro SD card with a recommended minimum capacity of 8 GB; a USB-type micro SD card reader/writer; a compatible factory firmware image for your tablet (links provided above); and the PhoenixCard v4.2.4 image burning tool (link provided above).
FIRMWARE RESTORATION/UPGRADE
Ensure that you have no external storage devices, mobile devices, or any other USB-type devices connected to your PC or laptop;
Download a factory firmware image from the downloads section above that is compatible with your tablet variant. Save the image on your computer desktop or another convenient directory;
Download the PhoenixCard v4.2.4 image burning tool onto your Windows computer. Extract the contents of the archive to a folder on your desktop or to another easily accessible location;
Double click PhoenixCard.exe to launch the tool;
Place your micro SD card into a suitable card reader/writer and connect it to your PC or laptop;.
Click on the Img File box located in the upper-left section of the PhoenixCard interface;
Select the firmware image (.img file) you downloaded in the second step;
Click the box marked Burn in the lower left section of the interface. The firmware image will be burned to the micro SD card. The process can take from 5 to 10 minutes to complete, at which time the output window of the interface will indicate Burn End;
Remove the micro SD card from the card reader and insert it into the micro SD card slot of your QLink Scepter 8.tablet. Ensure that your tablet is powered off;
To begin the firmware installation process, long press your power button. Your tablet display will show a progress bar indicating that the firmware image on the micro SD card is being written to eMMC flash memory;
Once the process is complete, remove the micro SD card from your tablet and boot the device normally.
Upon reboot, your QLink Scepter 8 should be restored to its factory stock state.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5554999OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for installation using the Phoenix Suite flash tool. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide also outlines the procedure for upgrading your QLink Scepter 8 to a newer firmware build.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using Phoenix Suite v1.10 for Windows. Accordingly, you will need a PC or laptop running on Windows 7/8.1/10/11, the Phoenix Suite flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. Should you have difficulties in this regard, I have outlined the steps for manually updating your drivers below.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
I. FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 if you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download Phoenix Suite 1.10 from the link below and install it on your Windows computer. Once installed, open the tool and grant any prompted permissions;
2. Download the V9 stock firmware image from the link below and save it on a convenient directory on your PC or laptop. The firmware will be in an archived .rar file format. Use WinZip, WinRAR or other utility to extract the firmware image from the archive. Safe the image to a convenient directory on your computer;
3. Ensure that USB Debugging is enabled in the Developer Options menu on your tablet;
4. Connect your tablet to your Windows computer using a proper data sync cable. Watch your device display for the USB Debugging authorization prompt, then grant the request;
5. If your tablet is being properly recognized by Phoenix Suite, an indicator in the bottom-left of the interface will indicate Device Connected.
6. Click on the Firmware option in the upper panel of Phoenix Suite. Click on Image and then select the saved location of the firmware image you downloaded. Highlight the firmware image by clicking it, then select Open in the bottom-right of the interface.
7. When ready to begin the restoration process, click the green Upgrade button in Phoenix Suite. Your device will automatically boot into a low-level flashing mode. When prompted, choose the option for full format. The firmware will begin installation. Phoenix Suite will indicate the progress of the installation and your tablet will automatically reboot to the OS once the process is complete. The flashing process will take between 3 and 4 minutes in duration. You are finished. Your device should now be fully restored to its factory stock state and running on the V9 firmware build.
8. If the firmware did not commence installation due to a no-device-connected error, see the next section below on drivers.
UPDATING USB DEVICE DRIVERS:
Perform these steps only if the firmware did not install and you are receiving an error that no device is connected. As mentioned previously, once you select a firmware image, Phoenix Suite will boot your device into a low-level flashing mode (Download Mode) to begin the flashing process. Leave the device in this mode and keep it connected to your Windows computer. Right click the Windows Start button and select Device Manager. Your tablet should be listed under the Portable Devices heading as Unknown Device. Right click Unknown Device and choose Update Driver. On the next screen select the option to Browse My Computer. Next, click on the Browse icon box in the upoer-right of the menu. Navigate to the saved location of the folder from which you open the Phoenix Suite flash tool. It should have a folder name of PhoenixSuite_V1.10. Left click on the folder and look below it for a folder named Drivers. Select Drivers and then choose OK. Now click Next at the bottom-right of the menu. You may get a warning notification that the drivers are unsigned. Select the option to install anyway. Once installed, Phoenix Suite will immediately recognize your device on flash mode and the firmware installation will start automatically. Return to the Phoenix Suite flash tool interface to see the installation progress.
DOWNLOADS:
PhoenixSuite v1.10
Stock Firmware Image V6
Stock Firmware Image V9
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. PhoenixSuite is not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
Click to expand...
Click to collapse
Thank you very much for all the work you've done on this. It has been a big help. I've been following along since the beginning of this topic and I've been using XDA for years but this is my first post, I think, maybe second, idk.
I have been able to do pretty much everything but get this firmware to flash, it consistently gets to the part where it says on the bottom left of the phoenix suite window "beginning flash operation" or something similar, the selection form is replaced with an empty progress bar and i can't recall exactly whats written under the progress bar but it something to the effect of "firmware flash starting". But that's it it does nothing after that, I've left it 20 and 30 mins and nothing, no error message or any message but If I unplug the USB cable from the tablet, I get a message about the device being disconnected.
I rooted the tablet without issue close to the day after the stock firmware was posted. I used a program called "ImgRepacker" to extract the contents of the firmware image which were mostly ".fex" files. I read somewhere that you can simply rename the boot.fex file to boot.img and that worked. I patched it with Magisk and flashed it using fastboot and just like that, rooted.
And its been working fine until yesterday when i was messing with the build.prop file. I think its you who posted some performance tweaks in a different thread. I think I may have entered something incorrectly and rebooted and now it gets stuck right where the boot animation would normally start.
Its not an emergency but I just can't get this stock image to flash.. I have deleted the pheonix tools i was using and I downloaded the one posted here.
Bootloader is unlocked
USB ADB Debugging is enabled (well last I was booted up)
I can boot to recovery.
I can boot to bootloader (fastboot).
i can boot to fastbootd.
drivers have been a bit tricky:
when i was connected via usb to my pc (i'm using windows 11 btw)
with adb debugging enabled, as and also i had to enable file transfer mode to get "ADB Device" to appear. I would then have an "ADB Device" under the NEW heading "USB Devices" as well as "Scepter 8" under the heading "Portable devices" ADB commands seemed to work perfectly and I could copy files to "internal storage " so I didn't bother too much but I tried to update the drivers for "ADB Device" with the Google Android drivers and also with the ADB drivers included with Pheonix Tool but on both counts I was not able to and the message from windows was the driver files I selected were not the correct files for the selected device (period). Like i said that was working so...
Booting into recovery I was then able to install the ADB Drivers in the pheonix tool directory
Under "Android" heading was " Composite ADB Interface"
Booting Bootloader or fastbootd I was able to install "Bootloader Interface"
The Pheonix tool would recognize my device with ADB debugging, then i click upgrade with the v9 firmware selected and my tablet will reboot to download mode presumeably and the driver i was able to install for it shows up under the heading
"Universal Service Bus Controllers" as "USB Device(VID_1f3a_PID_efe8)"
Any Idea why I can't get the stock image to flash?
Why it looks like its about to start the flash but never does?
(sorry if that's too much info... and thank you for any help you are able to offer)
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Viva La Android said:
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Click to expand...
Click to collapse
I will give that a try and post back after. thank you!
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Shady8550 said:
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Click to expand...
Click to collapse
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Viva La Android said:
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Click to expand...
Click to collapse
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Shady8550 said:
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Click to expand...
Click to collapse
You definitely need to use PhoenixUSBPro if those instructions didn't work. With it, you don't need ADB Debugging to be enabled, nor do you need to manually.configure drivers. I plan on revising this guide later today with inclusion of PhoenixUSBPro v4.0.0, replacing PhoenixSuit.
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5568185
OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state.
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. If you have not, or if you are experiencing issues with device recognition, I have included a section below on installing the drivers.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
INSTALLING USB DEVICE DRIVERS
If you have previously installed ADB & USB device drivers on your Windows computer, skip down to the next section. Otherwise, download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop. Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers. Select "Y" again when prompted to install ADB as system-wide. Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched. Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer. It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the proper drivers.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 in the event you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
2. Download the V9 stock firmware package from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
3. Power off your Scepter 8 tablet;
4. In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
5. Now, click the Start button located in the upper section of the interface. A large green will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
6. Connect the USB data sync cable to your computer, but not yet your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key three times and then release Volume Down;
7. PhoenixUSBPro should recognize your device, initiating the firmware installation automatically. The flashing process typically takes about four minutes. When complete, you will see a green checkmark and a notification that the installation has finished;
8. Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on the V9 firmware build version.
DOWNLOADS:
15-Second ADB Installer v1.5.6
PhoenixUSBPro v4.0.0
Stock Firmware Image V6 **
Stock Firmware Image V9 (Latest)
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. Allwinner-based devices are not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
THANKS & MENTIONS
The PhoenixUSBPro tool was created and distributed by AllWinner Technology Co., LTD. Full credit for this tool goes to AllWinner. Thanks to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing factory firmware images for the QLink Scepter 8. Last, but not least, thanks to @13lack13ox for providing input and recommending the benefits of using PhoenixUSBPro in lieu of PhoenixSuit.
Click to expand...
Click to collapse
After trying all the software in Windows and in Linux, I
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
hayesy said:
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Click to expand...
Click to collapse
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
yup. Thank you. That did get it working again. I had actually figured that out previously. I had a super.img that i was able to dump previously and had already flashed it but i did not erase UDISK. I wonder if i should go back and do that.
Also because I never saved my original boot.img, I only have a the patched boot.img so i can't update but I'm really not worried too much about that. I doubt there will be many updates. (when I tried to restore stock using the boot.img i extracted from the firmware image v9, which is the one i patched with magisk to gain root, I end up in a boot loop. weird. --is that because i need to erase UDISK after flashing boot_a.img? P.S. just an observation, when i flash boot.img in fastboot, it gets written to the device as boot_a.img automatically for some reason.)
Thank you very much for taking the time to upload those files for me, that was really very nice of you. much appreciated!
comm-ents said:
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
Click to expand...
Click to collapse
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
hayesy said:
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
Click to expand...
Click to collapse
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Update: I am diligently working on the TWRP port for the Sceptre 8. Android 11 support for TWRP (primary, the dynamic partitioning scheme) is an absolute nightmare. Because A/B devices do not utilize an actual /recovery partition, TWRP must be installed to /boot. Although my TWRP port is booting and the touch GUI is functional, I am trying to iron out some mounting issues and decryption of some key partitions. I am hoping to get some one-on-one aide from a TeamWin dev and maintainer later this week. Once I iron out these issues, I'll be posting the TWRP build.
Viva La Android said:
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Click to expand...
Click to collapse
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
hayesy said:
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
Click to expand...
Click to collapse
Exactly. I need to take the time to write a flash-all batch file for fastboot installations. A flash-all batch script executes the fastboot commands and acts as an auto installer. Takes the work out of executing back-to-back fastboot commands. Your reasoning is correct.
Viva La Android said:
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
Click to expand...
Click to collapse
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
pyrohydrosmok said:
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
Click to expand...
Click to collapse
I'll need some more info. What exactly did you perform that caused the hang up at the lock screen?