Hello all, so long story short I had bought a BLU G9 Pro which came with Android 9 Pie. The only device-specific guide I could find online about obtaining root was: https://www.getdroidtips.com/root-blu-g9-pro/
The information on that guide is trivial and can be applicable to almost any device. The root method worked, however, there was an OTA update to Android 10 (and then later a security update) which I took. I then attempted to re-root the device utilizing the same method. However, now it seems that everytime I flash a Magisk modded boot.img my device gets stuck in a bootloop and will not go past the bootloader. I believe that this device may be uncharted territory but it is a great phone and I would love to have both Magisk root and the latest Android 10 firmware. I have found that Magisk supports both Android 10 and A-only devices so I do not see what is causing the problem. Additionally, I attempted to flash an AOSP GSI of Android 10 which refused to boot before I even installed Magisk. I am new to modern Android devices with Project Treble so please forgive me if there is something obvious I am missing. Any help is appreciated, thanks in advance!
@eLatErbI
Try flashing GSI like said in https://source.android.com/setup/build/gsi#flashing-gsis
May be vbmeta flashing is required for your device.
You can get vbmeta.img from your stock firmware.
It seems that Verified Boot could definitely be getting in the way. Could this possibly explain why Magisk is working on the Android 9.0 version of the stock ROM but not Android 10? However, I thought Magisk disabled verified boot in the kernel (boot.img) also I do not have a vbmeta.img in any stock firmware for this phone. Any other means of disabling verified boot? Thanks in advance!
Hi, I have the same problem with my G9 PRO, I tried to boot all kinds of GSI roms with and without magisk and it doesn't work (bootloop). I cannot find the vbmeta partition anywhere so I am hesitant to try to flash it without a backup. There is a mention of it in the fstab of the boot partition, however it is not in the stock firmware or in my own backups. Magisk did also work for me before the Android 10 update. Does anyone have an idea of how AVB works without a vbmeta partition or a verity file?
You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.
tuffasagong said:
You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.
Click to expand...
Click to collapse
Hi. Please post the link. It will be very helpful for me. I have the BLU_G0231WW android 10.
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.
&oot4peace said:
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.
Click to expand...
Click to collapse
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..
Tesh3180 said:
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..
Click to expand...
Click to collapse
Search here: BLU Stock Firmware Repository (Mediafire)
lopestom said:
Search here: BLU Stock Firmware Repository (Mediafire)
Click to expand...
Click to collapse
thanks but already tried that file and wont work..
Tesh3180 said:
thanks but already tried that file and wont work..
Click to expand...
Click to collapse
Which version were you on? The latest at the time? A little more info did you flash a Magisk patched boot image?
Blu pushed out a new update 10.0.04.08 a couple weeks ago. Reflash the stock Boot image to update. Boot image has the same length and start addresses. I just reflashed the magisk Boot image I made with 10.0.04.07 and works fine.
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue
Cathedralruins said:
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue
Click to expand...
Click to collapse
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver
lopestom said:
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver
Click to expand...
Click to collapse
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.
Cathedralruins said:
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.
Click to expand...
Click to collapse
Bootloader unlocked?
Authorization PC vs device already has with USB debugging?
If yes so look drivers.
Hello there,
My technical skills when comes to android phones is next to zero, but I have been running linux (Fedora, Endeavour, currently Debian 11), I am not affraid of the terminal.
I have bought a Blu g9 pro, like 3 months ago, it came out of the box with android 9, then It updated to android 10.
It is very close to stock android, and I am ok with it, exept for a few creepy apps that I would like to remove,
I would like your input on what is the safest aproach, can I just 'debloat' the current system? or might as well replace it with something else?
Thank you.
I attempted to flash the patched boot image from Magisk but my G9 Pro started boot looping. I've tried to flash every firmware that I can find for this model but I keep getting an error message from the Flash tool.
Any guidance?
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Saved me - TY. This worked for me for Mintt Ultramintt Y3 - basically an Aussie rebadged Blu G9 Pro. I used this method for it with Pie 9 (before allowing update to 10). Cheers
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool (5.x).
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Hi,
Thank you for uploading this, I have problems too with my Nokia 3 TA-1032. It's different case than yours, but still I can't turn it on. Can you please write down, how exactly I supposed to run your script in Python3? I have difficulties to extract files. Thank you very much forwardly
JustAGuyWithAndroidPhone said:
Hi,
Thank you for uploading this, I have problems too with my Nokia 3 TA-1032. It's different case than yours, but still I can't turn it on. Can you please write down, how exactly I supposed to run your script in Python3? I have difficulties to extract files. Thank you very much forwardly
Click to expand...
Click to collapse
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
huupoke12 said:
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
Click to expand...
Click to collapse
Thank you very much for your advice, the unpacking worked, but the flash not somehow. Here is a picture about what Error code I get.
JustAGuyWithAndroidPhone said:
Thank you very much for your advice, the unpacking worked, but the flash not somehow. Here is a picture about what Error code I get.
Click to expand...
Click to collapse
You didn't select the "Download-Agent" as the Download Agent file from the link on my post. You are using the default Download Agent file of SP Flash Tool. You may also want to download the latest version of SP Flash Tool.
huupoke12 said:
You didn't select the "Download-Agent" as the Download Agent file from the link on my post. You are using the default Download Agent file of SP Flash Tool. You may also want to download the latest version of SP Flash Tool.
Click to expand...
Click to collapse
Yes, you right, because the SP tool don't accept that. Here is a pic about that:
I downloaded the latest SP tool from the link above here in your post.
JustAGuyWithAndroidPhone said:
Yes, you right, because the SP tool don't accept that. Here is a pic about that:
I downloaded the latest SP tool from the link above here in your post.
Click to expand...
Click to collapse
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\".
Yes, I relocated as you writed down, and now the download agent is accepted (that one which you linked here above), in an earlier version from the Flashtool, not the latest one. Flashing still need authorization file somehow. ( I tried to flash a rom with Authorization file needed, probably that going to be the reason. Originally I wanted to downgrade my Nokia 3 TA-1032)
huupoke12 said:
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\"
Click to expand...
Click to collapse
Yes, I relocated as you writed down, and now the download agent is accepted (that one which you linked here above), in an earlier version from the Flashtool, not the latest one. Flashing still need authorization file somehow. ( I tried to flash a rom with Authorization file needed, probably that going to be the reason. Originally I wanted to downgrade my Nokia 3 TA-1032)
huupoke12 said:
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\".
Click to expand...
Click to collapse
I have mistakenly deleted the os of my Nokia 3. PLEASE HELP!!!
The SP Flash tool is still not accepting the download agent!
PLEASE HELP!
Nokia3root said:
I have mistakenly deleted the os of my Nokia 3. PLEASE HELP!!!
The SP Flash tool is still not accepting the download agent!
PLEASE HELP!
Click to expand...
Click to collapse
If you have done the steps exactly as in my instruction and it still fail, then I can't help you anymore. Your phone may be in a different state than mine.
I have successfully unbricked my Nokia 3 (in a constantly restart cycle) on Arch Linux (I don't use Windows). If you want to give it a try, and if you are used to Windows User Interface, I recommend Linux Mint Cinnamon (Ubuntu is another popular choice, but its User Interface is very different from Windows, and Arch Linux is not easy to install if you are not used to command line interface and have some Linux knowledge).
huupoke12 said:
If you have done the steps exactly as in my instruction and it still fail, then I can't help you anymore. Your phone may be in a different state than mine.
I have successfully unbricked my Nokia 3 (in a constantly restart cycle) on Arch Linux (I don't use Windows). If you want to give it a try, and if you are used to Windows User Interface, I recommend Linux Mint Cinnamon (Ubuntu is another popular choice, but its User Interface is very different from Windows, and Arch Linux is not easy to install if you are not used to command line interface and have some Linux knowledge).
Click to expand...
Click to collapse
ok, i will try
huupoke12 said:
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
Click to expand...
Click to collapse
I am unable to extract the files! PLEASE HELP!!!
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install `python3` if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
THANK YOU VERY MUCH, BROTHER!!!!!!!!!!!!!
It worked!!
Now just have my story..... Actually, this was my friend's Nokia 3 which he gave me to root and I convinced him that I would root it and convinced him that there was no risk in it. Then I rooted the device for him very hardly but then I mistakenly deleted the os of the phone and then I searched the whole internet and found your post.... First of all, I got many errors while unpacking the nb0 file as I was using python 3.0, so I downloaded the python 3.8 installer but it wouldn't install because it was saying that that Service pack 1 was not installed in my Windows 7 but it was, hence I got very irritated and observed the log file and downloaded an update (KB3033929). Then I installed python 3.8 and thus I come to have a working mobile! I again rooted it and gave it to my friend and told him about these happenings.
Once again thank you very much!!! You saved my respect!!
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. how can download scripte ?
majd11 said:
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. how can download scripte ?
Click to expand...
Click to collapse
Right-click on the "Raw" button at the top-right corner, and select "Save link as".
huupoke12 said:
Right-click on the "Raw" button at the top-right corner, and select "Save link as".
Click to expand...
Click to collapse
Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
please help me how do that ?? run the script with .nb0 can you make the vedio please
majd11 said:
Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
please help me how do that ?? run the script with .nb0 can you make the vedio please
Click to expand...
Click to collapse
Read #3 and #13
(#13 is correct, he just downloaded a wrong python version)
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
my nokia phone is Ta-1032 mtk 6737 and the firmware in the link is mtk 6735 can I use this on my phone MTK 6737??
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
please can i use this on my nokia 3 mtk 6737 ?
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?