Related
Hyundai 7" HyTab Plus
4G-LTE Android Tablet
Model No. 7LB1
{
"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"
}
Bootloader Unlocking
& Rooting GuideOVERVIEW:
The Hyundai HyTab Plus (7LB1) is a budget 7" tablet with 4G-LTE support, manufactured by Hyundai Technology. This tablet not only supports 4G-LTE cellular data connectivity, but is also a fully functional smartphone, with integrated Radio Interface Layer (RIL) and telephony capabilities. The sister tablet to the 7LB1 is the WiFi-only HyTab Plus 7WB1. Due to substantial hardware and firmware variations between these two models, the procedures for unlocking the bootloader and achieving root access of the Android OS will be outlined in two separate guides.
SPECIFICATIONS:
• Name: Hyundai HyTab Plus 7
• Model/SKU: HT7LB1PBKNA
• Chipset: MediaTek MT6739
• CPU: Quad-core ARM Cortex-A53
• Architecture: 32-bit
• Instruction Sets: armeabi-v7a
• Lithography: 28 nm
• CPU Max Clock: 1.5 GHz
• GPU: IMG PowerVR Rogue GE8100
• GPU Max Clock: 570 MHz
• WLAN: 802.11b/g/n/ac
• Bluetooth Version: 4.2 (Low Energy)
• LTE Modem: Cat-4 DL / Cat-5 UL
• LTE Bands: 2, 4, 5, 7, 12, 14, 17, 66, 71
• Cell Tech: : GSM, WCDMA, TD-SCDMA, VoLTE, EDGE, FDD/TDD, LTE-A
• GPS: Glonass, QZSS
• Internal Storage: 32 GB eMMC 5.1 (26.4 GB Useable)
• Ext. Storage: micro SD Slot ~ 1 TB
• RAM: 2 GB LPDDR3 (667 MHz)
• Display: 7" IPS / 1024 x 600 / 240 dpi
• Aspect Ratio: 17:10
• Cameras: 5MP Main / 2MP Front
• I/O Port: USB Type-C
• Partition Scheme: Dynamic/Non-A/B
• Battery: 2,400 mAh Li-Ion
• Project Treble: Supported
FIRMWARE INFO:
• OS/Version: Android 10 (Go Edition)
• Build No. full_tb8765ap1_bsp_1g-user.
202009191923 release-keys
• Android Build ID: QP1A.190711.020
• Radio: MOLY.LR12A.R2.MP.V135.8
• Bootloader: tb8765ap1_bsp_1g-
98d83e7--2020091923253
• Kernel Version: Linux 4.14.141
• Security Patch Level: June 5, 2020
• API Level: 29
• Build Date: September 19, 2020
NOTE: The above-referenced firmware info corresponds to the most current build available for this tablet, and likewise corresponds to the build from which the patched boot image (linked in the downloads section below) originated.
DISCLAIMER:
Unlocking the bootloader and attaining root access of the Android OS are both procedures which modify the device from its stock factory configuration. This will void your warranty. Moreover, these procedures are inherently risky to the overall integrity and operability of your tablet. It is possible, for instance, to render your device completely inoperable by botching these tasks. By proceeding further, you are assuming sole responsibility for the operability, integrity and performance of your tablet. This procedure has been fully tested and confirmed viable. Follow the steps carefully, employ patience, and things should go smoothly. Nonetheless, you have been informed of the risks. In the unfortunate event you brick your device, encounter a boot loop, or otherwise corrupt the firmware, I will provide support -- to the best of my ability -- to aide you in restoring your tablet to its factory stock state.
IMPORTANT NOTE: With the release of Android 10, a new implementation of fastboot mode was introduced, known as FastbootD, or Dynamic Fastboot. This implementation of fastboot has been relocated from the bootloader to userspace, enabling the flashing code to persist in a maintainable and testable common location, with only the vendor-specific components of fastboot implemented by a hardware abstraction layer (HAL). The sole purpose of dynamic fastboot mode is grounded in support for the dynamic partitioning scheme; added fastboot commands allow for the deleting, resizing and creating of logical partitions. However, FastbootD cannot be utilized to unlock a mobile device's bootloader. This operation must still be handled by way of traditional fastboot mode. For purposes of this guide, this will be referenced as legacy fastboot mode. Thus, FastbootD does not replace legacy fastboot mode. Rather, on devices which use the dynamic partition scheme, dynamic fastboot (FastbootD) and legacy fastboot coexist. The Hyundai HyTab Plus 7" (7LB1) is one such device. Accordingly, in the instructions below (especially for bootloader unlocking), it is imperative that you are using legacy fastboot mode, and not FastbootD. Follow the instructions closely in this regard.
REQUIREMENTS:
Both procedures outlined in this guide require a PC or laptop running on Windows 7/8.1/10/11. A Linux or Mac machine may also be used to carry out these tasks; however, for purposes of this guide, we will be focusing on a Windows-based setup. Next, ensure that your Hyundai 7" HyTab Plus has a model number of 7LB1, as this guide is model specific. This tablet integrates major hardware and firmware differences in contrast to the 7WB1 WiFi only model.
You will need to install the ADB, Fastboot & USB device drivers on your computer as well. I have provided a link below for the 15-Secomd ADB Installer, which will install and configure each of these drivers. Also, you will need the factory supplied, or a quality equivalent USB Type-C to USB Type-A data syncing/charging cable. Any additional files needed for this guide have been provided in the downloads section below.
I. SETTING UP ADB & FASTBOOT:
Configuring the ADB & Fastboot tools, as well as installing the correct USB device drivers, is tantamount to successfully completing the procedures outlined in this guide. This section sets out detailed instructions for properly setting up these prerequisites. If you have previously completed these tasks, simply skip down to the next section on unlocking the bootloader. Otherwise, let us begin.
IMPORTANT NOTE: This section entails the installation of unsigned drivers on your Windows PC or laptop. If you are running Windows 11, or a 64-bit build of Windows 8.1 or 10, your system will block the installation of unsigned drivers by default. In order to install the drivers, you will need to first disable the signature enforcement feature. Follow either of the two methods in this tutorial, then return to this section.
Disabling Driver Signature Enforcement
Download the 15-Second ADB Installer from the link below and extract the contents of the archive to your desktop or to another convenient directory;
Right click the .exe installer and opt to run the application as an administrator;
Select Y(es) when prompted to install ADB & Fastboot and hit Enter;
Select Y(es) when prompted to install ADB system-wide, then hit Enter;
Select Y(es) once again when prompted to install device drivers; press Enter. A Device Driver Installation Wizard window will be launched. Select Next to proceed. The Google USB device driver will be installed on your computer. If you receive a warning that the driver is unsigned, simply choose the option to install anyway.
Once complete, you will be notified that the drivers were successfully installed on your computer. Select Finish.
II. UNLOCKING THE BOOTLOADER
This step is a mandatory prerequisite to rooting your tablet. If you have already unlocked your tablet's bootloader, skip down to the next section on rooting your device.
WARNING: Unlocking your bootloader will trigger a native Android security feature that forces your device into a factory data reset, fully wiping all user data from the tablet. Before proceeding, make a backup of any files and media that you wish to preserve.
Open the C-Drive directory on your computer, copy the folder labeled adb and paste it to your desktop. This step merely sets up a more convenient directory from which to utilize ADB & Fastboot;
Boot your tablet into legacy fastboot mode. From the Android OS, ensure that USB Debugging & OEM Unlocking are enabled in the Developer Options menu. Connect your tablet to your Windows computer using a suitable data sync cable. Open a command window from your adb folder directory and execute this command:
Code:
adb reboot bootloader
Your display should be dark and backlit, with => FASTBOOT mode displayed in a white font at the bottom of the tablet screen;
Check for proper fastboot device recognition by executing this command in the command window:
Code:
fastboot devices
If properly connected, the command window should return an alphanumeric string consistent with your device serial number, followed by the word fastboot;
Once device recognition has been properly established, execute this command to initiate unlocking of the bootloader:
Code:
fastboot flashing unlock
Your tablet will now prompt you to press Volume Up to proceed with unlocking, or Volume Down to cancel the operation;
Once the unlock has been completed, execute:
Code:
fastboot reboot
Your tablet will now initiate a mandatory factory data reset before booting into the initial setup phase of the Android OS. Your bootloader is now unlocked.
III. ROOTING THE TABLET:
I have simplified the rooting procedure substantially by providing a boot image pre-patched for Magisk systemless root support. Once your tablet reboots following the unlocking process, complete initial setup, enable Developer Options once again, and ensure USB Debugging is toggled.
Download the patched boot image and vbmeta.img from the links below and save both files to your adb folder;
Boot your tablet to legacy fastboot mode using the procedure outlined in Step 2 of the previous section;
Flash the Magisk patched boot image to the /boot partition by executing:
Code:
fastboot flash boot patched_boot.img
Next, dm-verity/verified boot needs to be disabled. Execute this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That's it. Now simply execute:
Code:
fastboot reboot
Your tablet now has the Magisk systemless root framework installed. Upon reboot into the Android OS, open the Magisk app or placeholder stub. Grant any requested permissions; follow any prompts to upgrade Magisk to the full version, and complete any steps necessary to finish setting up the root environment. To update the Magisk version when new updates are released, use the Direct Install option within the Magisk app interface.
DOWNLOADS:
15-Second ADB Installer v1.4.3
Magisk Patched Boot Image
vbmeta.img
Onn Surf 7 (1st Gen)
Model No. 100005206
7" WiFi Android Tablet
{
"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"
}
Unbricking & Factory
Firmware Restoration Guide
OVERVIEW:
The 1st Gen Onn Surf 7 is a 7" budget Android tablet manufactured by the Walmart owned electronics brand Onn (styled onn.). It ships with the MediaTek MT8167B chipset, which integrates an energy efficient quad-core Cortex-A35 CPU clocking at 1.3 GHz max, the Imagination PowerVR Rogue GE8300 GPU, paired with 1 GB RAM. The CPU cores are built on the 28 nm process standard. The tablet ships with Android 9 Pie (Go Edition), compiled using the armv7l (32-bit) architecture. The 7" IPS display has a resolution of 1024 x 600 @ 160 dpi (mdpi), and a 17:10 aspect ratio. This device has 16 GB internal storage (12.2 GB useable). The /userdata partition employs the f2fs file system standard, which allows for faster transfer speeds than the traditional ext4 standard. There is also a micro SD card slot for up to 1 TB additional external storage space. The Li-Ion 2100 mAh battery provides around four (4) hours of power at heavy usage, and up to seven (7) hours of juice with light to moderate usage. The main camera shoots images up to 5 MP, while the front selfie cam shoots at 2 MP.
This guide outlines detailed instructions on restoring and/or upgrading the 1st Gen Onn Surf 7 (Model No. 100005206) tablet's stock firmware. This procedure can be used to fix a tablet which is bricked, stuck in a boot loop or is otherwise unable to boot into the Android OS. This guide can likewise be used by device owners who are experiencing issues attributed to firmware corruption, those who simply wish to revert to a full stock and unmodified Android OS, or those who wish to upgrade from an older firmware build. This process will remove any system level mods, root binaries, custom kernels, recoveries, etc., reverting the Android OS and corresponding firmware to an unmodified stock state.
FIRMWARE INFO:
• OS/Version: Android 9 (Go Edition)
• Build No. PPR1.180610.011
• Build Date: September 19, 2020
• Security Patch Level: August 5, 2019
• Build Type: User
• Build Tag: release-keys
• Kernel version: Linux 4.4.146
• Custom Build: alps.mp.p0.mp6-V1.134
• API Level: 28
• Partition Scheme: GPT Legacy
PREREQUISITES:
A PC or laptop running on Windows 7/8.1/10/11;
The SP Flash Tool firmware flashing software (link provided below);
A factory firmware package for the Onn Surf 7 tablet (link provided below);
The vCom MediaTek USB drivers installed on your Windows computer (link provided below);
The factory supplied or a quality equivalent micro USB to USB-A data syncing cable.
MEDIATEK vCOM USB DRIVERS:
The most common obstacle many members encounter when using the SP Flash Tool is related to device recognition. The SP Flash Tool software flashes firmware directly to the NAND/eMMC whilst the mobile device is in BROM flash mode. In other words, the flash tool is interacting directly with the MediaTek chipset during the flashing process. The user merely needs to connect the powered off mobile device to the PC or laptop using an adequate USB data syncing cable. SP Flash Tool, in turn, will initiate BROM flash mode on the mobile device and commence with the firmware restoration process. In order for your device to be properly recognized in this regard, it is crucial that the MediaTek vCom USB drivers are properly installed and configured on your Windows computer. While I will not be outlining step-by-step instructions here on installing these drivers, I have provided a link in the downloads section below for a comprehensive guide on properly installing and configuring the vCom USB drivers on your Windows machine. Once you have completed this crucial task, you may proceed with this guide. Be sure and thank the OP of that guide, @skeleton1911, if you use his work.
DISCLAIMER
This guide involves flashing the eMMC internal storage device of your tablet with a factory firmware package, thus fully restoring your tablet to its stock factory condition. The procedure outlined below is inherently risky to the overall integrity and operability of your tablet. Failure to follow the instructions properly can, for instance, render your device completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. I have fully tested this procedure on my own device. Follow the instructions carefully, employ patience, and things should go smoothly. I am not responsible if you brick or otherwise damage your tablet. Moreover, it should be emphasized that this guide is for Model 100005206 (1st Gen) only. The factory firmware package for this model is not compatible with newer generation models of the Onn Surf 7 tablet.
INSTRUCTIONS
This section presumes that you have properly installed & configured the latest MediaTek vCom USB drivers on your Windows PC or laptop. Again, I have linked a guide for installing these drivers in the downloads section below. Your bootloader does not need to be in an unlocked state. However, this procedure may relock your bootloader if it is presently in an unlocked state.
WARNING: This procedure will erase all saved user data from your device. Before proceeding, make a backup of any files, media or data that you wish to preserve.
Download the Onn Surf 7 factory firmware package from the link below and extract the contents of the archive to a folder on your computer desktop, or to a folder in another convenient directory;
Download SP Flash Tool v5.1924 from the link below and extract the archive to your desktop, or to another easily accessible directory;
Ensure that your tablet is powered off and is not connected to your PC or laptop;. Likewise, ensure that there are no other mobile devices or USB storage devices connected to your computer;
Open the SP Flash Tool folder that you extracted in Step 2. Click on flash_tool.exe, then right click and choose to Run as Administrator;
Ensure that the pull-down menu, located near the mid-left region of the interface, is set to Download only. Next, click on the Choose folder icon, located to the right of the Scatter-loading file heading.
A file explorer will be launched. Navigate to the saved location of the firmware you extracted in the first step. In the firmware directory, select MT8167_Android_scatter.txt, and then click Open;
The SP Flash Tool will now load the factory firmware package. A violet-colored progress bar near the bottom of the interface will reflect the completion status.
Once the firmware has been loaded, connect the USB-A end of the data syncing cable to your PC or laptop. Click the Download box located near the upper-left region of the interface;
Now, connect the micro USB end of the data sync cable to your tablet. If the vCom drivers are properly installed and configured on your PC or laptop, SP Flash Tool will recognize your device and initiate firmware installation via BROM flash mode. A yellow progress bar located near the bottom of the interface will reflect the percentage of completion. Once completed, you will receive a notification that the procedure was successful.
Disconnect your tablet and use the power key to boot the device. Your Onn Surf 7 should be fully restored to it's stock factory state and running on the most recent firmware build available.
DOWNLOADS:
SP Flash Tool v5.1924
Factory Firmware for Onn Surf 7
vCOM Drivers Installation Guide
THANKS & MENTIONS:
I would like to take a moment to thank @skeleton1911 for his comprehensive tutorial on properly installing MediaTek vCom USB drivers on Windows 10 & 11. I would ask any members who use that tutorial to give the OP thanks.
Viva La Android said:
Onn Surf 7 (1st Gen)
Model No. 100005206
7" WiFi Android Tablet
View attachment 5799181
Stock Firmware Restoration
And Upgrading Guide
OVERVIEW:
The 1st Gen Onn Surf 7 is a 7" budget tablet manufactured by the Walmart owned electronics brand Onn (styled onn.). It ships with the MediaTek MT8167B chipset, which integrates an energy efficient quad-core Cortex-A35 CPU clocking at 1.3 GHz max, the Imagination PowerVR Rogue GE8300 GPU, paired with 1 GB RAM. The processor cores are built on the 28 nm process standard. The tablet ships with Android 9 Pie (Go Edition), compiled using the armv7l (32-bit) architecture. The 7" IPS display has a resolution of 1024 x 600 @ 160 dpi (mdpi), and a 17:10 aspect ratio. This device has 16 GB internal storage (12.2 GB useable). The /userdata partition employs the f2fs file system standard, which allows for faster transfer speeds than the traditional ext4 standard. There is also a micro SD card slot for up to 1 TB additional external storage space. The Li-Ion 2100 mAh battery provides around four (4) hours of power at heavy usage, and up to seven (7) hours of juice with light to moderate usage. The main camera shoots images up to 5 MP, while the front selfie cam shoots at 2 MP.
This guide outlines detailed instructions on restoring and/or upgrading the 1st Gen Onn Surf 7 (Model No. 100005206) tablet's stock firmware. This procedure can be used to fix a tablet which is bricked, stuck in a boot loop or is otherwise unable to boot into the Android OS. This guide can likewise be used by device owners who are experiencing issues attributed to firmware corruption, those who simply wish to revert to a full stock and unmodified Android OS, or those who wish to upgrade from an older firmware build. This process will remove any system level mods, root binaries, custom kernels, recoveries, etc., as well as lock the bootloader if it is in an unlocked state.
FIRMWARE INFO:
• OS/Version: Android 9 (Go Edition)
• Build No. PPR1.180610.011
• Build Date: September 19, 2020
• Security Patch Level: August 5, 2019
• Build Type: User
• Build Tag: release-keys
• Kernel version: Linux 4.4.146
• Custom Build: alps.mp.p0.mp6-V1.134
• API Level: 28
• Partition Scheme: GPT Legacy
PREREQUISITES:
A PC or laptop running on Windows 7/8.1/10/11;
The SP Flash Tool firmware flashing software (link provided below);
A factory firmware package for the Onn Surf 7 tablet (link provided below);
The vCom MediaTek USB drivers installed on your Windows computer (link provided below);
The factory supplied or a quality equivalent micro USB to USB-A data syncing cable.
MEDIATEK vCOM USB DRIVERS:
The most common obstacle many members encounter when using the SP Flash Tool is related to device recognition. The SP Flash Tool software flashes firmware directly to the NAND/eMMC whilst the mobile device is in BROM flash mode. In other words, the flash tool is interacting directly with the MediaTek chipset during the flashing process. The user merely needs to connect the powered off mobile device to the PC or laptop using an adequate USB data syncing cable. SP Flash Tool, in turn, will initiate BROM flash mode on the mobile device and commence with the firmware restoration process. In order for your device to be properly recognized in this regard, it is crucial that the MediaTek vCom USB drivers are properly installed and configured on your Windows computer. While I will not be outlining step-by-step instructions here on installing these drivers, I have provided a link in the downloads section below for a comprehensive guide on properly installing and configuring the vCom USB drivers on your Windows machine. Once you have completed this crucial task, you may proceed with this guide. Be sure and thank the OP of that guide, @skeleton1911, if you use his work.
DISCLAIMER
This guide involves flashing the eMMC internal storage device of your tablet with a factory firmware package, thus fully restoring your tablet to its stock factory condition. The procedure outlined below is inherently risky to the overall integrity and operability of your tablet. Failure to follow the instructions properly can, for instance, render your device completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. I have fully tested this procedure on my own device. Follow the instructions carefully, employ patience, and things should go smoothly. I am not responsible if you brick or otherwise damage your tablet. Moreover, it should be emphasized that this guide is for Model 100005206 (1st Gen) only. The factory firmware package for this model is not compatible with newer generation models of the Onn Surf 7 tablet. View attachment 5741703
INSTRUCTIONS
This section presumes that you have properly installed & configured the latest MediaTek vCom USB drivers on your Windows PC or laptop. Again, I have linked a guide for installing these drivers in the downloads section below. Your bootloader does not need to be in an unlocked state. However, this procedure will relock your bootloader if it is presently in an unlocked state.
WARNING: This procedure will erase all saved user data from your device. Before proceeding, make a backup of any files, media or data that you wish to preserve.
Download the Onn Surf 7 factory firmware package from the link below and extract the contents of the archive to a folder on your computer desktop, or to a folder in another convenient directory;
Download SP Flash Tool v5.1924 from the link below and extract the archive to your desktop, or to another easily accessible directory;
Ensure that your tablet is powered off and is not connected to your PC or laptop;. Likewise, ensure that there are no other mobile devices or USB storage devices connected to your computer;
Open the SP Flash Tool folder that you extracted in Step 2. Click on flash_tool.exe, then right click and choose to Run as Administrator;
Ensure that the pull-down menu, located near the mid-left region of the interface, is set to Download only. Next, click on the Choose folder icon, located to the right of the Scatter-loading file heading.
A file explorer will be launched. Navigate to the saved location of the firmware you extracted in the first step. In the firmware directory, select MT8167_Android_scatter.txt, and then click Open;
The SP Flash Tool will now load the factory firmware package. A violet-colored progress bar near the bottom of the interface will reflect the completion status.
Once the firmware has been loaded, connect the USB-A end of the data syncing cable to your PC or laptop. Click the Download box located near the upper-left region of the interface;
Now, connect the micro USB end of the data sync cable to your tablet. If the vCom drivers are properly installed and configured on your PC or laptop, SP Flash Tool will recognize your device and initiate firmware installation via BROM flash mode. A yellow progress bar located near the bottom of the interface will reflect the percentage of completion. Once completed, you will receive a notification that the procedure was successful.
Disconnect your tablet and use the power key to boot the device. Your Onn Surf 7 should be fully restored to it's stock factory state and running on the most recent firmware build available.
DOWNLOADS:
SP Flash Tool v5.1924
Factory Firmware for Onn Surf 7
vCOM Drivers Installation Guide
THANKS & MENTIONS:
I would like to take a moment to thank @skeleton1911 for his comprehensive tutorial on properly installing MediaTek vCom USB drivers on Windows 10 & 11. I would ask any members who use that tutorial to give the OP thanks.
Click to expand...
Click to collapse
Is this a personal pulled from tablet firmware ? Or did you locate a factory firmware pkg ?
tek3195 said:
Is this a personal pulled from tablet firmware ? Or did you locate a factory firmware pkg ?
Click to expand...
Click to collapse
This is Onn factory firmware. Fully stock.
Viva La Android said:
This is Onn factory firmware. Fully stock.
Click to expand...
Click to collapse
Ok, where did you get it ?
tek3195 said:
Ok, where did you get it ?
Click to expand...
Click to collapse
It's from Onn's software support server. This isn't a dump or a homemade package. The firmware is directly from Onn. Where I got it has no relevance to the firmware's origin. Even if I'd got the file at a firmware repo, this would not change anything.
For future reference, if a thread is titled with the term factory firmware, the package originated from the manufacturer. Otherwise, the firmware will be referenced as a partition dump, firmware pull, partition images, or another similar name. The fact that it's called factory firmware infers where the package came from.
Viva La Android said:
Your thread may be titled correctly but not everyone does that. We have looked for Onn firmware for a few years now so I was wondering if you had found a site to download from. If you have it would be nice to share it. If you are getting from OTA then not factory firmware. You could be a little more forthcoming about source, and a little less with the attitude.
Click to expand...
Click to collapse
Attitude is a good thing. It encourages people to read plain print, comprehend basic grammatical structure, etc As far as source, I share all of my sources. Check any of my dozens of device threads. I always specify the origin, build type, etc. As far as how I obtain factory images, that isn't the least bit relevant to the threads and, quite frankly -- and perhaps a bit attitude coated --it's not any of your business. Indeed, OTA packages and factory firmware images are not the same. You are correct, good sir. Sort of makes my point. That's why one is called OTA while the other is called factory firmware.
By the way, Onn factory firmware is all over the internet in various repos and sources. It isn't elusive by any means.
But yes, if it's called "FACTORY FIRMWARE," guess where it came from? Most members are fairly proficient with literacy and comprehension, so I'm sorry I didn't feel the need to spell that out for the other .48% of the collective member populace. Similarly, whenever I sell baseball cards on eBay, I don't emphasize that the players depicted on those cards actually play baseball. Common sense and the like. Something about the "BASEBALL CARDS" heading perhaps?
Here are a few strikingly similar analogues to emphasize the true wonder of names, headings and titles.
•From where does the Alaskan Husky originate?
•Which galactic star causes a sunburn?
•What makes ice water cold?
•For what weather conditions was a raincoat designed?
•For which food item was pancake syrup originally created?
•When was the War of 1812?
Viva La Android said:
Attitude is a good thing. It encourages people to read plain print, comprehend basic grammatical structure, etc As far as source, I share all of my sources. Check any of my dozens of device threads. I always specify the origin, build type, etc. As far as how I obtain factory images, that isn't the least bit relevant to the threads and, quite frankly -- and perhaps a bit attitude coated --it's not any of your business. Indeed, OTA packages and factory firmware images are not the same. You are correct, good sir. Sort of makes my point. That's why one is called OTA while the other is called factory firmware.
By the way, Onn factory firmware is all over the internet in various repos and sources. It isn't elusive by any means.
But yes, if it's called "FACTORY FIRMWARE," guess where it came from? Most members are fairly proficient with literacy and comprehension, so I'm sorry I didn't feel the need to spell that out for the other .48% of the collective member populace. Similarly, whenever I sell baseball cards on eBay, I don't emphasize that the players depicted on those cards actually play baseball. Common sense and the like. Something about the "BASEBALL CARDS" heading perhaps?
Here are a few strikingly similar analogues to emphasize the true wonder of names, headings and titles.
•From where does the Alaskan Husky originate?
•Which galactic star causes a sunburn?
•What makes ice water cold?
•For what weather conditions was a raincoat designed?
•For which food item was pancake syrup originally created?
•When was the War of 1812?
Click to expand...
Click to collapse
I don't know what your problem is other than trying to be a smart a s s lacking any people skills. Why you can't provide a link is beyond me. I have installed board software and factory firmware on many devices and I have not seen factory firmware with so few files before. Provide link to official Onn firmware and stop being an a s s .
tek3195 said:
I don't know what your problem is other than trying to be a smart a s s lacking any people skills. Why you can't provide a link is beyond me. I have installed board software and factory firmware on many devices and I have not seen factory firmware with so few files before. Provide link to official Onn firmware and stop being an a s s .
Click to expand...
Click to collapse
Or, my personal favorite:
What mobile operating system platform has its basis on the Android Open Source Project? Has to be iOS; what do you think? Oh come on, I'm picking on you. Don't take it to heart.
So few files? Allwinner firmware, for instance, is released as a single image -- one .img file. With MediaTek based devices, there is no set amount of individual partition images required to constitute a complete firmware package. This is entirely up to the device manufacturer. Some device makers include all key partitions as well as all sensitive partitions -- essentially, a full partition index for the device. Manufacturers like Hyundai and Motorola are known for releasing robust firmware packages that include the full partition index of images. Other device makers like RCA -- and Onn -- release only the bare minimum of images needed to restore the device to its stock factory state. For this Surf 7 model, Onn has released images for /preloader, /lk1, /lk2, /trustzone1, /trustzone2, /dtbo, /recovery, /boot, /system, /vendor, /userdata, /logo, and /cache. Those images not included in the package are classified either as INVISIBLE or REGIONALBIN; as such, these are simply not needed for restoration purposes and, thus, this is undoubtedly why they were not included in the factory package.
Keep in mind that many images included in typical factory firmware archives are.simply not necessary for firmware restoration; indeed some files are used more for development purposes.
My advice to you, if you don't trust the integrity or legitimacy of a firmware package -- including this one -- don't use it. Get a firmware package elsewhere. I don't post links to channels. Do your own legwork and procure your own contacts with support departments at various manufacturers.
Viva La Android said:
Or, my personal favorite:
What mobile operating system platform has its basis on the Android Open Source Project? Has to be iOS; what do you think? Oh come on, I'm picking on you. Don't take it to heart.
So few files? Allwinner firmware, for instance, is released as a single image -- one .img file. With MediaTek based devices, there is no set amount of individual partition images required to constitute a complete firmware package. This is entirely up to the device manufacturer. Some device makers include all key partitions as well as all sensitive partitions -- essentially, a full partition index for the device. Manufacturers like Hyundai and Motorola are known for releasing robust firmware packages that include the full partition index of images. Other device makers like RCA -- and Onn -- release only the bare minimum of images needed to restore the device to its stock factory state. For this Surf 7 model, Onn has released images for /preloader, /lk1, /lk2, /trustzone1, /trustzone2, /dtbo, /recovery, /boot, /system, /vendor, /userdata, /logo, and /cache. Those images not included in the package are classified either as INVISIBLE or REGIONALBIN; as such, these are simply not needed for restoration purposes and, thus, this is undoubtedly why they were not included in the factory package.
Keep in mind that many images included in typical factory firmware archives are.simply not necessary for firmware restoration; indeed some files are used more for development purposes.
My advice to you, if you don't trust the integrity or legitimacy of a firmware package -- including this one -- don't use it. Get a firmware package elsewhere. I don't post links to channels. Do your own legwork and procure your own contacts with support departments at various manufacturers.
Click to expand...
Click to collapse
You are right, I guess in my mind I was seeing board software from Huawei. I wasn't thinking about Amazon .bin file or Huawei update.app either. As for legwork it's been a while since I looked hard for Onn firmware. When I first posted how to root the 8" model I was sending email to the company that manufactured the tablet for Onn and searching board serial numbers looking for it. Wow, that's been about 3 years ago now, time flies and things change. That is why I was curious as to where it came from with hopes of finding 8" and 10" firmware. I only had the 7" long enough to root it, post how-to and return it. The other thing I quit searching for was info on MTK's ultraflash, back then it was non-existent. I appreciate the decent reply, thank you.
tek3195 said:
You are right, I guess in my mind I was seeing board software from Huawei. I wasn't thinking about Amazon .bin file or Huawei update.app either. As for legwork it's been a while since I looked hard for Onn firmware. When I first posted how to root the 8" model I was sending email to the company that manufactured the tablet for Onn and searching board serial numbers looking for it. Wow, that's been about 3 years ago now, time flies and things change. That is why I was curious as to where it came from with hopes of finding 8" and 10" firmware. I only had the 7" long enough to root it, post how-to and return it. The other thing I quit searching for was info on MTK's ultraflash, back then it was non-existent. I appreciate the decent reply, thank you.
Click to expand...
Click to collapse
No problem friend. Perhaps I came across as being abrasive on my replies to your inquiry. I'm sorry if that's the case. Questions like yours are welcome and the ensuing discussion can be informative to other members.
I will give you a good tip on procuring factory firmware: send a professionally worded email to the support department of the device manufacturer. Let them know you need the firmware as a means to restore your own device, as well as for potential custom development projects here at XDA. Most manufacturers know that XDA is the largest custom Android dev community on the planet. As such, they realize that XDA is a great platform for giving exposure to particular devices, which increases overall sales. Anyway, word your email to infer this scenario. Once you get a firmware package for a particular device, make efforts to thank and give credit to the support representative who helped you. Email the representative's supervisor to give positive feedback on the person. Oftentimes, that individual will then freely assist you with future firmware requests, requests for kernel source code, etc. You will progressively gain some valuable contacts among various manufacturers for obtaining factory images.
Viva La Android said:
Onn's software support server
Click to expand...
Click to collapse
Viva La Android said:
Onn Surf 7 (1st Gen)
Model No. 100005206
7" WiFi Android Tablet
View attachment 5803029
Stock Firmware Restoration
And Upgrading Guide
OVERVIEW:
The 1st Gen Onn Surf 7 is a 7" budget tablet manufactured by the Walmart owned electronics brand Onn (styled onn.). It ships with the MediaTek MT8167B chipset, which integrates an energy efficient quad-core Cortex-A35 CPU clocking at 1.3 GHz max, the Imagination PowerVR Rogue GE8300 GPU, paired with 1 GB RAM. The CPU cores are built on the 28 nm process standard. The tablet ships with Android 9 Pie (Go Edition), compiled using the armv7l (32-bit) architecture. The 7" IPS display has a resolution of 1024 x 600 @ 160 dpi (mdpi), and a 17:10 aspect ratio. This device has 16 GB internal storage (12.2 GB useable). The /userdata partition employs the f2fs file system standard, which allows for faster transfer speeds than the traditional ext4 standard. There is also a micro SD card slot for up to 1 TB additional external storage space. The Li-Ion 2100 mAh battery provides around four (4) hours of power at heavy usage, and up to seven (7) hours of juice with light to moderate usage. The main camera shoots images up to 5 MP, while the front selfie cam shoots at 2 MP.
This guide outlines detailed instructions on restoring and/or upgrading the 1st Gen Onn Surf 7 (Model No. 100005206) tablet's stock firmware. This procedure can be used to fix a tablet which is bricked, stuck in a boot loop or is otherwise unable to boot into the Android OS. This guide can likewise be used by device owners who are experiencing issues attributed to firmware corruption, those who simply wish to revert to a full stock and unmodified Android OS, or those who wish to upgrade from an older firmware build. This process will remove any system level mods, root binaries, custom kernels, recoveries, etc., as well as lock the bootloader if it is in an unlocked state.
FIRMWARE INFO:
• OS/Version: Android 9 (Go Edition)
• Build No. PPR1.180610.011
• Build Date: September 19, 2020
• Security Patch Level: August 5, 2019
• Build Type: User
• Build Tag: release-keys
• Kernel version: Linux 4.4.146
• Custom Build: alps.mp.p0.mp6-V1.134
• API Level: 28
• Partition Scheme: GPT Legacy
PREREQUISITES:
A PC or laptop running on Windows 7/8.1/10/11;
The SP Flash Tool firmware flashing software (link provided below);
A factory firmware package for the Onn Surf 7 tablet (link provided below);
The vCom MediaTek USB drivers installed on your Windows computer (link provided below);
The factory supplied or a quality equivalent micro USB to USB-A data syncing cable.
MEDIATEK vCOM USB DRIVERS:
The most common obstacle many members encounter when using the SP Flash Tool is related to device recognition. The SP Flash Tool software flashes firmware directly to the NAND/eMMC whilst the mobile device is in BROM flash mode. In other words, the flash tool is interacting directly with the MediaTek chipset during the flashing process. The user merely needs to connect the powered off mobile device to the PC or laptop using an adequate USB data syncing cable. SP Flash Tool, in turn, will initiate BROM flash mode on the mobile device and commence with the firmware restoration process. In order for your device to be properly recognized in this regard, it is crucial that the MediaTek vCom USB drivers are properly installed and configured on your Windows computer. While I will not be outlining step-by-step instructions here on installing these drivers, I have provided a link in the downloads section below for a comprehensive guide on properly installing and configuring the vCom USB drivers on your Windows machine. Once you have completed this crucial task, you may proceed with this guide. Be sure and thank the OP of that guide, @skeleton1911, if you use his work.
DISCLAIMER
This guide involves flashing the eMMC internal storage device of your tablet with a factory firmware package, thus fully restoring your tablet to its stock factory condition. The procedure outlined below is inherently risky to the overall integrity and operability of your tablet. Failure to follow the instructions properly can, for instance, render your device completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. I have fully tested this procedure on my own device. Follow the instructions carefully, employ patience, and things should go smoothly. I am not responsible if you brick or otherwise damage your tablet. Moreover, it should be emphasized that this guide is for Model 100005206 (1st Gen) only. The factory firmware package for this model is not compatible with newer generation models of the Onn Surf 7 tablet. View attachment 5741703
INSTRUCTIONS
This section presumes that you have properly installed & configured the latest MediaTek vCom USB drivers on your Windows PC or laptop. Again, I have linked a guide for installing these drivers in the downloads section below. Your bootloader does not need to be in an unlocked state. However, this procedure will relock your bootloader if it is presently in an unlocked state.
WARNING: This procedure will erase all saved user data from your device. Before proceeding, make a backup of any files, media or data that you wish to preserve.
Download the Onn Surf 7 factory firmware package from the link below and extract the contents of the archive to a folder on your computer desktop, or to a folder in another convenient directory;
Download SP Flash Tool v5.1924 from the link below and extract the archive to your desktop, or to another easily accessible directory;
Ensure that your tablet is powered off and is not connected to your PC or laptop;. Likewise, ensure that there are no other mobile devices or USB storage devices connected to your computer;
Open the SP Flash Tool folder that you extracted in Step 2. Click on flash_tool.exe, then right click and choose to Run as Administrator;
Ensure that the pull-down menu, located near the mid-left region of the interface, is set to Download only. Next, click on the Choose folder icon, located to the right of the Scatter-loading file heading.
A file explorer will be launched. Navigate to the saved location of the firmware you extracted in the first step. In the firmware directory, select MT8167_Android_scatter.txt, and then click Open;
The SP Flash Tool will now load the factory firmware package. A violet-colored progress bar near the bottom of the interface will reflect the completion status.
Once the firmware has been loaded, connect the USB-A end of the data syncing cable to your PC or laptop. Click the Download box located near the upper-left region of the interface;
Now, connect the micro USB end of the data sync cable to your tablet. If the vCom drivers are properly installed and configured on your PC or laptop, SP Flash Tool will recognize your device and initiate firmware installation via BROM flash mode. A yellow progress bar located near the bottom of the interface will reflect the percentage of completion. Once completed, you will receive a notification that the procedure was successful.
Disconnect your tablet and use the power key to boot the device. Your Onn Surf 7 should be fully restored to it's stock factory state and running on the most recent firmware build available.
DOWNLOADS:
SP Flash Tool v5.1924
Factory Firmware for Onn Surf 7
vCOM Drivers Installation Guide
THANKS & MENTIONS:
I would like to take a moment to thank @skeleton1911 for his comprehensive tutorial on properly installing MediaTek vCom USB drivers on Windows 10 & 11. I would ask any members who use that tutorial to give the OP thanks.
Click to expand...
Click to collapse
What mediatek does the ONN 7 Gen 3 ships with
Jfuchs2007 said:
What mediatek does the ONN 7 Gen 3 ships with
Click to expand...
Click to collapse
The Gen 3 appears to have the MediaTek Helio A22 (mt6761v), accordubg to FCC cert records. But don't quote me on that. The exact specs for the Gen 3 are a bit obscure for some reason.
Viva La Android said:
Onn Surf 7 (1st Gen)
Model No. 100005206
7" WiFi Android Tablet
View attachment 5907727
Unbricking & Factory
Firmware Restoration Guide
OVERVIEW:
The 1st Gen Onn Surf 7 is a 7" budget Android tablet manufactured by the Walmart owned electronics brand Onn (styled onn.). It ships with the MediaTek MT8167B chipset, which integrates an energy efficient quad-core Cortex-A35 CPU clocking at 1.3 GHz max, the Imagination PowerVR Rogue GE8300 GPU, paired with 1 GB RAM. The CPU cores are built on the 28 nm process standard. The tablet ships with Android 9 Pie (Go Edition), compiled using the armv7l (32-bit) architecture. The 7" IPS display has a resolution of 1024 x 600 @ 160 dpi (mdpi), and a 17:10 aspect ratio. This device has 16 GB internal storage (12.2 GB useable). The /userdata partition employs the f2fs file system standard, which allows for faster transfer speeds than the traditional ext4 standard. There is also a micro SD card slot for up to 1 TB additional external storage space. The Li-Ion 2100 mAh battery provides around four (4) hours of power at heavy usage, and up to seven (7) hours of juice with light to moderate usage. The main camera shoots images up to 5 MP, while the front selfie cam shoots at 2 MP.
This guide outlines detailed instructions on restoring and/or upgrading the 1st Gen Onn Surf 7 (Model No. 100005206) tablet's stock firmware. This procedure can be used to fix a tablet which is bricked, stuck in a boot loop or is otherwise unable to boot into the Android OS. This guide can likewise be used by device owners who are experiencing issues attributed to firmware corruption, those who simply wish to revert to a full stock and unmodified Android OS, or those who wish to upgrade from an older firmware build. This process will remove any system level mods, root binaries, custom kernels, recoveries, etc., reverting the Android OS and corresponding firmware to an unmodified stock state.
FIRMWARE INFO:
• OS/Version: Android 9 (Go Edition)
• Build No. PPR1.180610.011
• Build Date: September 19, 2020
• Security Patch Level: August 5, 2019
• Build Type: User
• Build Tag: release-keys
• Kernel version: Linux 4.4.146
• Custom Build: alps.mp.p0.mp6-V1.134
• API Level: 28
• Partition Scheme: GPT Legacy
PREREQUISITES:
A PC or laptop running on Windows 7/8.1/10/11;
The SP Flash Tool firmware flashing software (link provided below);
A factory firmware package for the Onn Surf 7 tablet (link provided below);
The vCom MediaTek USB drivers installed on your Windows computer (link provided below);
The factory supplied or a quality equivalent micro USB to USB-A data syncing cable.
MEDIATEK vCOM USB DRIVERS:
The most common obstacle many members encounter when using the SP Flash Tool is related to device recognition. The SP Flash Tool software flashes firmware directly to the NAND/eMMC whilst the mobile device is in BROM flash mode. In other words, the flash tool is interacting directly with the MediaTek chipset during the flashing process. The user merely needs to connect the powered off mobile device to the PC or laptop using an adequate USB data syncing cable. SP Flash Tool, in turn, will initiate BROM flash mode on the mobile device and commence with the firmware restoration process. In order for your device to be properly recognized in this regard, it is crucial that the MediaTek vCom USB drivers are properly installed and configured on your Windows computer. While I will not be outlining step-by-step instructions here on installing these drivers, I have provided a link in the downloads section below for a comprehensive guide on properly installing and configuring the vCom USB drivers on your Windows machine. Once you have completed this crucial task, you may proceed with this guide. Be sure and thank the OP of that guide, @skeleton1911, if you use his work.
DISCLAIMER
This guide involves flashing the eMMC internal storage device of your tablet with a factory firmware package, thus fully restoring your tablet to its stock factory condition. The procedure outlined below is inherently risky to the overall integrity and operability of your tablet. Failure to follow the instructions properly can, for instance, render your device completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. I have fully tested this procedure on my own device. Follow the instructions carefully, employ patience, and things should go smoothly. I am not responsible if you brick or otherwise damage your tablet. Moreover, it should be emphasized that this guide is for Model 100005206 (1st Gen) only. The factory firmware package for this model is not compatible with newer generation models of the Onn Surf 7 tablet. View attachment 5907731
INSTRUCTIONS
This section presumes that you have properly installed & configured the latest MediaTek vCom USB drivers on your Windows PC or laptop. Again, I have linked a guide for installing these drivers in the downloads section below. Your bootloader does not need to be in an unlocked state. However, this procedure may relock your bootloader if it is presently in an unlocked state.
WARNING: This procedure will erase all saved user data from your device. Before proceeding, make a backup of any files, media or data that you wish to preserve.
Download the Onn Surf 7 factory firmware package from the link below and extract the contents of the archive to a folder on your computer desktop, or to a folder in another convenient directory;
Download SP Flash Tool v5.1924 from the link below and extract the archive to your desktop, or to another easily accessible directory;
Ensure that your tablet is powered off and is not connected to your PC or laptop;. Likewise, ensure that there are no other mobile devices or USB storage devices connected to your computer;
Open the SP Flash Tool folder that you extracted in Step 2. Click on flash_tool.exe, then right click and choose to Run as Administrator;
Ensure that the pull-down menu, located near the mid-left region of the interface, is set to Download only. Next, click on the Choose folder icon, located to the right of the Scatter-loading file heading.
A file explorer will be launched. Navigate to the saved location of the firmware you extracted in the first step. In the firmware directory, select MT8167_Android_scatter.txt, and then click Open;
The SP Flash Tool will now load the factory firmware package. A violet-colored progress bar near the bottom of the interface will reflect the completion status.
Once the firmware has been loaded, connect the USB-A end of the data syncing cable to your PC or laptop. Click the Download box located near the upper-left region of the interface;
Now, connect the micro USB end of the data sync cable to your tablet. If the vCom drivers are properly installed and configured on your PC or laptop, SP Flash Tool will recognize your device and initiate firmware installation via BROM flash mode. A yellow progress bar located near the bottom of the interface will reflect the percentage of completion. Once completed, you will receive a notification that the procedure was successful.
Disconnect your tablet and use the power key to boot the device. Your Onn Surf 7 should be fully restored to it's stock factory state and running on the most recent firmware build available.
DOWNLOADS:
SP Flash Tool v5.1924
Factory Firmware for Onn Surf 7
vCOM Drivers Installation Guide
THANKS & MENTIONS:
I would like to take a moment to thank @skeleton1911 for his comprehensive tutorial on properly installing MediaTek vCom USB drivers on Windows 10 & 11. I would ask any members who use that tutorial to give the OP thanks.
Click to expand...
Click to collapse
Hello. I'm not a pro, but I decided to make a tablet firmware (due to the fact that there is not enough memory), I seem to do everything as described here .. but nothing comes out. Please tell me what I'm doing wrong?
Kavsokalivit45 said:
Hello. I'm not a pro, but I decided to make a tablet firmware (due to the fact that there is not enough memory), I seem to do everything as described here .. but nothing comes out. Please tell me what I'm doing wrong?
Click to expand...
Click to collapse
I'll research the exact nature of the error you're getting. When you say you made a tablet firmware, what images did you create? I am assuming system.img, & boot.img. is this correct?
You can install firmware images using fastboot mode as well, alleviating any need for SP Flash Tool.
Viva La Android said:
Я изучу точную природу ошибки, которую вы получаете. Когда вы говорите, что делали прошивку для планшета, какие образы вы создавали? Я предполагаю, что system.img и boot.img. это верно?
Вы также можете установить образ прошивки, используя режим быстрой загрузки, что избавит вас от необходимости использовать SP Flash Tool.
Click to expand...
Click to collapse
Привет! Я использовал прошивку здесь, заводскую. Перед этим установил все необходимые программы и драйвера. Возможно, причина проблемы в том, что я удалил не ту программу, которая написана в описании установки Драйверов. Там написано, что после установки драйверов нужно удалить ''MTK USB Port''. Но к сожалению не могу понять какой удалить. Высылаю скрин, посмотрите пожалуйста, не подскажете какой удалить? Признаюсь, я не очень разбираюсь в этом деле, я даже не "любитель".. Думал, что смогу сделать все по описанию. А прошить решил потому, что памяти под видео, музыку нет вообще, хотя написано, что минимум 12 гигов из 16 должно быть свободно, а у меня только около 1 гига.
Viva La Android said:
Я изучу точную природу ошибки, которую вы получаете. Когда вы говорите, что делали прошивку для планшета, какие образы вы создавали? Я предполагаю, что system.img и boot.img. это верно?
Вы также можете установить образ прошивки, используя режим быстрой загрузки, что избавит вас от необходимости использовать SP Flash Tool.
Click to expand...
Click to collapse
Извините, не подскажете, как прошить в режиме Fastboot?
Kavsokalivit45 said:
Извините, не подскажете, как прошить в режиме Fastboot?
Click to expand...
Click to collapse
Please post using English. Your previous two posts were composed -- I'm presuming in your native language. I will try to use a translation tool and decipher your posts. The mods here on XDA wil delete any posts or replies which are not in English.
@Kavsokalivit45, I translated your question. Okay, fastboot mode can be used to flash a firmware image file (.img, .fex, .bin, .mbn, etc.) to a specific partition on your mobile device (/boot, recovery, /vendor, /system, /secro, etc.). The following fastboot command reflects that the boot partition is being flashed by a boot.img file.
Code:
fastboot flash boot boot.img
Note that all flashing commands will begin with the word fastboot, followed by the word flash. The next value is represented by the mounting name of the partition to be flashed...in the above example the partition is boot. Lastly, the image filename to be flashed to the partition...in my example, boot.img.
So, if you wanted to flash the /system partition of the Surf 7 tablet, the location of the Android OS itself, you wouid execute:
Code:
fastboot flash system system.img
(This command presumes that the system image has a filename of system.img.)
Fastboot commands can also be used to wipe or format partitions, resize dynamic partitions, set flag values to certain props, unlock & relock your bootloader, along with dozens of other tasks.
While I don't have time to get in depth on this topic, below is a link to a detailed outline on over 2 dozen different fastboot commands and how to use them . https://technastic.com/fastboot-commands-list/
Viva La Android said:
@Kavsokalivit45, I translated your question. Okay, fastboot mode can be used to flash a firmware image file (.img, .fex, .bin, .mbn, etc.) to a specific partition on your mobile device (/boot, recovery, /vendor, /system, /secro, etc.). The following fastboot command reflects that the boot partition is being flashed by a boot.img file.
Code:
fastboot flash boot boot.img
Note that all flashing commands will begin with the word fastboot, followed by the word flash. The next value is represented by the mounting name of the partition to be flashed...in the above example the partition is boot. Lastly, the image filename to be flashed to the partition...in my example, boot.img.
So, if you wanted to flash the /system partition of the Surf 7 tablet, the location of the Android OS itself, you wouid execute:
Code:
fastboot flash system system.img
(This command presumes that the system image has a filename of system.img.)
Fastboot commands can also be used to wipe or format partitions, resize dynamic partitions, set flag values to certain props, unlock & relock your bootloader, along with dozens of other tasks.
While I don't have time to get in depth on this topic, below is a link to a detailed outline on over 2 dozen different fastboot commands and how to use them . https://technastic.com/fastboot-commands-list/
Click to expand...
Click to collapse
Hello. thanks for the explanation! very grateful to you!
Hot Pepper™ Mobile
Chilaca 4G-LTE Smartphone
T-Mobile® Certified
Model No. HPP-L60A
{
"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"
}
General Info &
Discussion Thread
OVERVIEW:
The Chilaca is a T-Mobile certified 4G-LTE smartphone, manufactured by Hot Pepper Mobile for eligible recipients of the federal Lifeline program and the Affordable Connectivity Program (ACP) -- government sponsored initiatives which assist low-income individuals and households with mobile phone service and mobile devices.
For an entry-level device, the Chilaca is a surprisingly capable smartphone. The MediaTek Helio A22 chipset platform utilizes CorePilot technology, which provides power-aware scheduling, CPU thermal management and persistent UX monitoring. These attributes work in harmony to assign the appropriate workload to CPU cores at a calculated and specific frequency and voltage, balancing the needed performance load demand with the optimal power efficiency. This landmark feature shines bright on the Chilaca, giving the user palpably smooth performance, the ability to maintain heavy workloads, all while maintaining impressive battery life in between charges. Moreover, the Chilaca's certification with T-Mobile provides remarkable network connectivity, excellent upload/download speeds, and extended range LTE coverage by way of Band 12 & 71 support.
HARDWARE SPECS:
Chipset: MediaTek Helio A22 (MT6761V/CAB)
CPU: Quad-core ARM Cortex-A53
CPU Max Clock: 2.0 GHz
Architecture: armv7l (32-bit)
CPU Process: 16 nm
GPU: IMG PowerVR Rogue GE8300
GPU Max Clock: 660 MHz
Display: 6.51" 1600 x 720 HD
Screen Density: 280 dpi (hdpi)
Internal Storage: 32GB eMMC (23.9 GB useable)
LTE Modem: Cat 7 DL; Cat 13 UL
LTE Bands: 2, 4, 5, 12, 25, 26, 41,66, 71
Bluetooth: v5.0, LE
WLAN Support: 802.11a/b/g/n/ac (2.4 & 5 GHz)
Battery: Li-Ion 3200 mAh
RAM: 2.0 GB (+ 1.386 GB zRAM)
Cameras: 5 MP Main; 2 MP Front
Ports: Type-C USB | 3.5mm Headphone Jack
FIRMWARE INFO:
OS/Version: Android 12 (Go Edition)
Firmware Build: HPP-L60A-3.0.18
Build ID: 12/SP1A.210812.016
Kernel Version: Linux v4.19.191
Radio: MOLY.LR12A.R3.MP.V208.3.P5
Security Patch Level: September 5, 2022
API Level: 31
Partition Scheme: Dynamic (Non A/B)
Project Treble: Supported
DEVELOPMENT STATUS:
Hot Pepper Mobile CEO Shawn Sun has selected me as a tester for the Chilaca 4G-LTE smartphone. Accordingly, the Chilaca has not yet been released within the mainstream US smartphone market. . This thread will serve as a general info & discussion forum for the Chilaca as more handsets become available via their release and distribution in the Lifeline program throughout the US.
I have obtained the factory firmware for the Chilaca, but have not yet experimented with bootloader unlocking or rooting the phone. I will keep this thread updated with any news in this regard. Should any members need the stock firmware, just leave a comment with the request.
UPDATE: February 17, 2023:
A recent OTA firmware rollout updates the current build to vHPP-L60A-3.0.19 with the December 05, 2022 security patch level.
I have also discovered that, per contractual terms between T-Mobile and the manufacturer, the bootloader on the Chilaca is not supported for unlocking. However, it appears that the Chilaca can be exploited using the MTK Client utility. Once I confirm bootloader unlocking I plan on writing a full tutorial with the step-by-step instructions and the required files for the task. It does appear that the Chilaca has been distributed throughout several US states via the federal Lifeline and ACP initiatives, making the device prominent on the mainstream market. I would ask that any Chilaca device owners leave a comment below.
UPDATE: March 23, 2023:
Another recent OTA security update has bumped the firmware build to HPP-L60A_3.0.20 with the February 1, 2023 security patch level.
In order to exploit the bootloader using MTK Client, you must be running the HPP-L60A_3.0.18 firmware build, or an earlier build. More recent builds have blocked user-initiated access to BROM mode which is essential to proper device recognition while using MTK Client. Fortunately, device owners may downgrade via the firmware package provided below in conjunction with the SP Flash Tool.
UPDATE: April 15, 2023:
An OTA update dated April 12, 2023, has bumped the firmware build to HPP-L60A_3.0.21, with a security patch level of March 5, 2023. This update included some bug fixes on premature kernel panic triggering and some baseband radio issues involving extended range LTE Band 71.
USEFUL LINKS:
• Factory Firmware HPP-L60A_3.0.18
• Chilaca Factory Firmware Restoration Guide
• SP Flash Tool v5.1924 (32 & 64-bit)
• Chilaca FCC Test Report
• Chilaca HPP-L60A User Manual (PDF)
• MTK Client Setup & Usage Guide **
Credit goes to @Sidharth09 for his guide on setting up and using MTK Flash Tool. Please consider hitting the thanks button on his thread.
Where can I find the decryption key?
MrAx714 said:
Where can I find the decryption key?
Click to expand...
Click to collapse
The download link is fixed.
Hi, guys.
New sign up but get info from y'all pros for long time.
My question about this phone:
Does anyone know if there is a source for a replacement screen for these anywhere yet? Have searched far and wide and no joy... they are very delicate at best.
Thanks and if this is posted in the wrong place just trash the post.
TIA
Peace
b4byl0n said:
Hi, guys.
New sign up but get info from y'all pros for long time.
My question about this phone:
Does anyone know if there is a source for a replacement screen for these anywhere yet? Have searched far and wide and no joy... they are very delicate at best.
Thanks and if this is posted in the wrong place just trash the post.
TIA
Peace
Click to expand...
Click to collapse
Splendid question. I'll see what I can find out on replacement parts.
My preliminary search for the availability of screen replacements and other parts for the Chilaca has been unfruitful. However, I will reach out to the CEO of Hot Pepper Mobile with this inquiry. I'll post back as soon as I know anything.
have you tried mtkclient with this?
luridphantom said:
have you tried mtkclient with this?
Click to expand...
Click to collapse
Indeed. Works on the older HPP-L60A-3. 0.18 firmware build. On newer builds BROM mode has been disabled. But on a positive note you can downgrade to 3.0.18 from a newer build using the firmware from my restoration guide.
wonder how i can be a tester to get my hands on one...
first feedback is to leave a BROM backdoor so we can always mtkclient unlock that baby
luridphantom said:
wonder how i can be a tester to get my hands on one...
first feedback is to leave a BROM backdoor so we can always mtkclient unlock that baby
Click to expand...
Click to collapse
The Chilaca has already completed all testing phases and has received Google Play Certification and T-Mobile certification. It is now being distributed via Lifeline and ACP channels throughout the US.
On unlocking the bootloader, all you need to do is flash my 3.0.18 firmware package and use MTK Client to exploit the bootloader. Once unlocked, you can install OTA updates as long as you are not yet rooted. Once updated to the latest 3.0.20 build, use MTK Client once again to dump your /boot partition in .img format. Use Magisk 26.1 to patch that boot.img, then use fastboot mode to flash the patched image to achieve root.
I have requested the latest full firmware build (3.0.20) for this phone. I should have it this week.
Hi ,. I recently brought a HPPL 69A , Pretty good device honestly but I want to do more with it ,So I looking into Rooting it , Is this could be possible ?
Could I root it without a PC
daremoNo said:
Could I root it without a PC
Click to expand...
Click to collapse
The HPP-L60A cannot be rooted without a PC. In fact, rooting it with a PC is a tedious and daunting task to put it mildly The bootloader must first be exploited using MTK Client. Afterwards, Magisk can be used to achieve systemless root. Also, in order to exploit the bootloader, you must be running the HPP-L60A-3.0.18 firmware build. The newer builds have blocked access to BROM mode. You can downgrade using SP Flash Tool to flash the firmware provided above.
So I just got one from the Lifeline program and I like it so far. I need to downgrade to the firmware ref. in the post above so I am attempting that right now. I am running win 11 and am having slight trouble turning off the driver verification for a 64bit os. I was trying to do it from the command line but ran into issues. edit: I turned off the driver enforcement (or at least I thought I was) in the local group policy editor, but I am still not able to install the mtk inf file. I get the error of " the digital inf doesn't contain any driver information. "
Any help would be great please.
ffreylu00x7 said:
So I just got one from the Lifeline program and I like it so far. I need to downgrade to the firmware ref. in the post above so I am attempting that right now. I am running win 11 and am having slight trouble turning off the driver verification for a 64bit os. I was trying to do it from the command line but ran into issues. edit: I turned off the driver enforcement (or at least I thought I was) in the local group policy editor, but I am still not able to install the mtk inf file. I get the error of " the digital inf doesn't contain any driver information. "
Any help would be great please.
Click to expand...
Click to collapse
Use this guide. Works on Win 10 & 11. https://windowsreport.com/driver-signature-enforcement-windows-10/
So I am thinking its file and not me messing up the driver enforcement. Has anyone vetted the link and what's provided in the link as to it being the proper thing to download or can you suggest a place to find a better firmware? I am trying to downgrade then hopefully achieve root access after that. I'll keep an updated post as I figure more out
ffreylu00x7 said:
So I am thinking its file and not me messing up the driver enforcement. Has anyone vetted the link and what's provided in the link as to it being the proper thing to download or can you suggest a place to find a better firmware? I am trying to downgrade then hopefully achieve root access after that. I'll keep an updated post as I figure more out
Click to expand...
Click to collapse
The firmware provided is directly from the servers of the manufacturer. It is official digitally signed firmware. It was provided to me by Hot Pepper Mobile months before the phone was released to the public. I beta tested this phone for the manufacturer. I've also installed this firmware with SP Flash Tool, via the debug and standard installations. There are no issues with the firmware archive.
If you want to efficiency disable driver signature enforcement, follow the guide I linked. Otherwise , you will likely have issues with installing the unsigned vCom drivers which will, in turn, complicate proper device recognition.
If you are having issues with device recognition with SP Flash Tool, here is a great step-by-step guide on configuring the MediaTek vCOM drivers on your PC or laptop. https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
So I don't know I it's my os on my computer or why I'm not getting the same options as y'all have instructed but I can't seem to figure out how to install these drivers. I disabled the driver verification enforcement and then went to device manager and this is where things were different. I'm not seeing the COM & PORTS...I installed the drivers from what was provided and followed the instructions. So after there is a new category called "SAMSUNG Android Phone" and I obviously don't have a Samsung so I'm not sure why that happened.
Afq
ffreylu00x7 said:
So I don't know I it's my os on my computer or why I'm not getting the same options as y'all have instructed but I can't seem to figure out how to install these drivers. I disabled the driver verification enforcement and then went to device manager and this is where things were different. I'm not seeing the COM & PORTS...I installed the drivers from what was provided and followed the instructions. So after there is a new category called "SAMSUNG Android Phone" and I obviously don't have a Samsung so I'm not sure why that happened.
Click to expand...
Click to collapse
Did you install the vCOM preloader drivers from the link I posted?
I have this phone. Someone from assurance wireless came knocking on my door and I didn't like truconnect anymore.
Anyway I searched and found your post. Bingo! Currently rooted.
Mine came with .18 on it and I had almost updated. I got mtk client working (used python mtk_gui) and backed up all partitions except the user data. Enabled dev mode. OEM unlocking. Went to the flash tab and did unlock bootloader. Installed magisk 26.1 on phone, adb pushed boot.bin to boot.img, patched file, adb pulled it, back into preloader, wrote the boot partition, don't know if it was necessary since I did a factory reset from the recovery menu, but I used mtk reset. I noticed that every time you use the cli mtk file you have to re enter preloader. Anyway, I did that, set it up, working great.
Now I want to remove the assurance wireless (T-Mobile lifeline mvno) subsidy lock, can mtkclient do that by erasing partitions like I've seen for some other phones? It's not a big deal right now and eventually it'll pass the auto unlock.
This is my first MediaTek root that worked. I have a Lenovo tab m8 tablet I tried it with before and didn't work but I didn't put much time into it. Was a few years back. Also I have a cloud stratus c7 which is also a mt6761 but the app I tried didn't work. But that was an on phone app. I'll have to try mtkclient with it.
Couple of questions. I used mtkgui and generated keys. No idea why or what I might use it for but I like to click things does it serve a purpose with this phone?
When I first ran the magisk patch install, after installing magisk 26.1 on the chilaca unrooted, there was a checkbox option for something about vbmeta in the boot image? I had checked it the first time but didn't use that image. But it doesn't show up anymore, so.. should I have used that?
Lastly, is there a way around the bootup having to press power to boot the phone or it'll shut off? Untrusted device message.
I've done plenty of rooting and jailbreaking and hardware hacking tinkering and such, but I owned a couple Samsung Galaxy s5s, then s7 edge, s8, then went to pixels. Got a pixel 3xl and 6 pro and Google makes everything super easy. I know that on the pixel you get a warning message that goes away after a few seconds (or you can press power to pause/unpause the warning) when bootloader is unlocked. I haven't tried it yet myself but I'm also aware of the ability to sign a rooted boot image (pixels are a/b devices if that matters) and relock the phone with it. Would that work on the chilaca you think? I can give it a shot.
I'm about to do the update to .20 right now. I restored the image through magisk manager so it'll patch the it's fine, just gotta reboot. Bootloader will remain unlocked you said? I'll find out
I'm gonna look into finding a kernel source for the mt6761 and see if I can't get a functional source tree up. Then it'd be nice to patch in sdk 32 (a13) pixel experience source tree will be useful for patch pulling guidance. Also I'm curious if twrp can be built, I started to read up on it and saw something about MediaTek and Qualcomm handling things very different, so we'll see.
Anyway thanks for the thread!!
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
{
"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"
}
Rooting Guide
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. XDA hosts a plethora of how-to guides on standard bootloader unlocking. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. As OTA updates are rolled out for this device, I will try to keep this guide updated with a patched boot image that corresponds with the latest firmware build.
Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries with it the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder. Note: the filename for the patched boot image is patched_boot.img. The flashing commands assume that you leave the filename unchanged;
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.
That's it. You're now rooted via the Magisk v26.1 systemless root solution.
IMPORTANT NOTE:
In the unfortunate event that you get stuck in a boot loop or brick your device using this guide, my guide on unbricking this smartphone will get you back up and running fairly quickly. This guide can be used to restore both soft bricked and hard bricked devices. You can then return here and give rooting another go.
Moxee MH-T6000 Unbricking GuideDOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to KonnectONE support specialist Faith Flores for releasing to me the factory firmware for this device.
Viva La Android said:
Assurance Wireless
Moxee MH-T6000 4G-LTE
View attachment 5893661
Rooting Guide
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder;
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.
That's it. You're now rooted via the Magisk v26.1 systemless root solution.
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to the KonnectONE support team for releasing to me the factory firmware for this device.
Click to expand...
Click to collapse
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
scottfan81 said:
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
Click to expand...
Click to collapse
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Thank you so much! I have 3 of these devices and been waiting lol. I see the stock kernel has hot-plug . What's some good tuning profiles? I tried to debloat permanently with LP but it didn't work. I think it's read-only so I flashed the magisk overlay for rw and going to play. We definitely need TWRP! I see a port may be in the works. Awesome. Thanks again
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Argonon said:
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Click to expand...
Click to collapse
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Argonon said:
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Click to expand...
Click to collapse
BLU won't unlock your bootloader. It is locked per contractual agreement with the branded carrier of the phone. However, if it's MediaTek, you may be able to use MTK Client to exploit the bootloader into an unlocked state.
Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
I have 3 of these devices. I surly can test TWRP port if needed
Argonon said:
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
I have 3 of these devices. I surly can test TWRP port if needed
Click to expand...
Click to collapse
Sure. I don't mind sharing my super.img. I'll need to upload it and then I'll message you a link. It's pretty much exactly 2.5 GB in file size, so I'll first compress it to a zip before uploading.
The edited one. Just clarifying so appreciated
Argonon said:
The edited one. Just clarifying so appreciated
Click to expand...
Click to collapse
I don't yet have all my mods made to the /super partition in that regard. Having encountered some force close issues with certain apps, I debloated from scratch and and have now begun my kernel tweaks and edits to the.varuous .prop files. So when finished, I'll share both my boot.img and super.img.
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Argonon said:
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Click to expand...
Click to collapse
MH-T6000 super.img unmodified
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Viva La Android said:
MH-T6000 super.img unmodified
Click to expand...
Click to collapse
Thank you!
Argonon said:
Thank you!
Click to expand...
Click to collapse
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore functionality.
Argonon said:
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Click to expand...
Click to collapse
Check out CRB Android Kitchen here on XDA. Great for unpacking / repacking partition images, including super.img.
Viva La Android said:
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore
Click to expand...
Click to collapse
Have you had anymore luck with this
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
{
"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"
}
Unbricking & Factory
Firmware Restoration Guide
OVERVIEW:
This guide outlines detailed instructions on restoring the KonnectONE Moxee MH-T6000 smartphone to its stock factory state by flashing firmware via the Qualcomm Flash Image Loader (QFIL) software for Windows. The firmware provided is official and signed by the manufacturer. This procedure can be used to restore either a soft or hard bricked device. In addition, this guide would benefit device owners who are rooted or running a custom OS who wish to revert to an unmodified stock state. This firmware will remove any root binaries, custom recoveries, custom kernels, system-level mods, and will restore your smartphone with the unmodified stock Android OS.
DISCLAIMER:
Due to the invasive nature of this procedure, there is an inherent risk that you could damage or otherwise render your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone, thus absolving me of any civil liability in the event things go bad. The steps in this guide have been thoroughly tested. Follow the instructions carefully, pay attention to detail, and things should go smoothly. Nevertheless, you have been cautioned. In the event you are attempting to recover from a hard brick, your device is already unresponsive and inoperable. Thus, the risk involved in such a scenario is virtually inconsequential.
PREREQUISITES:
First and foremost, you will need a PC or laptop running Windows 7/8.1/10/11; the Qualcomm USB device drivers (link provided below); the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable; the Qualcomm Flash Image Loader (QFIL) v2.0.0.0 software (link provided below); and a factory firmware package for the Assurance Wireless KonnectONE Moxee MH-T6000 smartphone (link provided below). This procedure can be carried out regardless of the locked/unlocked state of your bootloader. Moreover, if your bootloader is in an unlocked state, it will remain in an unlocked state once the factory firmware is installed. Likewise, if your bootloader is locked, flashing the factory firmware will not alter its locked state.
FIRMWARE INFO:
OS/Version: Android 11 (Go Edition)
Build No. MH-T6000V1.0.0B010
Build Date: February 20, 2023
Build Type: User
API Level: 30
Security Patch: March 5, 2023
Radio Version:
MPSS.JO.3.4-00044-SDM439_GENNS_PACK-1
Kernel Version: 4.19.157-perf
Partition Scheme: Dynamic (Non-A/B)
Project Treble: Supported
Arch: armv7l (32-bit)
Java VM: ART 2.1.0
Widevine Version: 16.0.0
Widevine Security Level: L3
LTE Band Support: 2/4/5/12/25/26/41
LTE HPUE Bands: 66/71
QUALCOMM FLASH IMAGE LOADER:
For those members unfamiliar, the Qualcomm Flash Image Loader, or QFIL, is a portable software application used for flashing factory firmware to devices powered by Qualcomm chipsets. QFIL is a proprietary flashing protocol, developed by Qualcomm Technologies, Inc., and is also an inbuilt application to the Qualcomm Program Support Tool (QPST). The flashing protocol utilizes Qualcomm's proprietary Emergency Download Mode (EDL), one of the only solutions capable of fully restoring a completely hard bricked mobile device. This flashing method can restore a device in which the partition table has been corrupted or is missing entirely. It is also worth noting that QFIL is integrated with a QCN (Qualcomm Calibration Network) backup and restore feature. The QCN is a binary file which encompasses all calibration data for the various hardware components and sensors within the device. It also stores the baseband radio and network configuration settings, including unique identifiers such as your IMEI/MEID numbers. This valuable feature can be used to restore these settings and values if they become corrupted or lost due to a system-level issue or a botched user-end system modification.
For purposes of simplicity and efficiency, and because this procedure does not require the entire QPST software suite (which includes service programming tools, port configuration monitor, baseband radio diagnostic tools, and QFIL), we will be using the portable standalone version of the QFIL software application.
INSTRUCTIONS:
Download the Qualcomm USB drivers installer from the below link and save it to a convenient location on your PC or laptop. Double click on the .exe installer and follow the prompts for installation. On the Setup Type window, select the first option for WWAN-DHCP then select Next. Now accept the terms of the license agreement and compete the installation. Once completed, reboot your computer;
Download QFIL v2.0.0.0 and extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop;
Download the Moxee MH-T6000 firmware from the below link and extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop;
Double click QFIL.exe inside the QFIL folder (referenced in Step 2) to open the flashing utility. In the upper-left area of the QFIL interface, select the Flat Build option. Next click the Build tab, which will open the Windows File Explorer. Navigate to the extracted firmware folder you created in Step 3. Select the firmware file named prog_emmc_firehose_8917_ddr.mbn, then click Open. Next, click the Load XML... tab which will once again launch Windows File Explorer. Select the file named rawprogram_unsparse.xml, then click Open. On the next screen select patch.0.xml and select Open once more. The firmware package is now loaded and ready to flash;
Now you must initiate Emergency Download Mode (EDL) on your phone. EDL mode is a Qualcomm proprietary firmware flashing & diagnostic protocol To do this, first ensure your device is powered off (unless, of course, your device is hard bricked, in which case it will be completely unresponsive and, for all intents and purposes, is already in a powered off state). Connect one end of your data syncing cable to your PC or laptop, but not yet to your phone. On your smartphone, hold Volume Up and Volume Down simultaneously while connecting the Type-C end of the data syncing cable to your phone. If your phone is being properly recognized, you will see Qualcomm HS USB QLOADER 9008 at the top of the QFIL interface, followed by your active port number. If you do not see this indicator on the QFIL interface, try using another data syncing cable, change USB ports, and/or reinstall the Qualcomm USB device drivers by repeating Step 1;
Once a proper connection is verified, click on the blue Download tab to commence the flashing process. A progress bar on the interface will indicate the status of the flashing process. This can take a few minutes, so just remain patient until the Status window indicates flashing success;
Now simply power up your device. It may be necessary to briefly remove and reinsert the battery to exit EDL mode. That's it. Your device should now be reverted to its factory stock state.
DOWNLOADS:
• Qualcomm USB Drivers Installer
• QFIL v2.0.0.0
• MH-T6000V1.0.0B010 Firmware
• OTA MH-T6000V1.0.OB011
THANKS & MENTIONS:
Thanks to @omb714.1980 for donating the device that made this guide possible. Thanks also to KonnectONE Support representative, Faith Flores, for providing me with the factory signed firmware for this phone.
I ended up removing various system apks by using some ro2rw magisk module etc but upon rebooting it kept going to fastboot. I flashed stock super img with fastboot then reflashed patched boot img and restored firmware that way. Lol I'm trying to recreate what I did idk maybe I needed to disable dfe. I had other magisk modules installed like an overlay to make ro rw partition for read only devices etc so idk yet
I need to try disable avb dm verity. Can someone upload the file I need to fastboot flash disable verity etc please? I successfully edited a super.img and just deleted various apps like outlook, fb installer, my account etc but left the folders etc. I used that ro2rw magisk. Pretty cool but after flashing the edited super.img it boots to fastboot mode. I'd like to try disabling verity.
Argonon said:
I need to try disable avb dm verity. Can someone upload the file I need to fastboot flash disable verity etc please? I successfully edited a super.img and just deleted various apps like outlook, fb installer, my account etc but left the folders etc. I used that ro2rw magisk. Pretty cool but after flashing the edited super.img it boots to fastboot mode. I'd like to try disabling verity.
Click to expand...
Click to collapse
You need vbmeta.img. You'll find it in the firmware package. To flash vbmeta.img and disable verity/AVB, use this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can copy and paste this command to make it easier. All the hyphens are a bit tricky.
Thanks. Now just boots to black screen. Lol. I'll keep playing
Argonon said:
Thanks. Now just boots to black screen. Lol. I'll keep playing
Click to expand...
Click to collapse
I finally got super.img rw and was able to debloat directly from the booted device! I used a magisk module called RO2RW test version. It uses android terminal like termux to pull the super.img then extract it. Once Product, System etc are extracted you use the mount script that makes it able to edit the imgs from MT file manager. Then terminal prompt recompiles it along with a new boot.img. its hard to explain as im not a pro lol. Here's the xda link where I got the ro2rw magisk module. https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
Argonon said:
I finally got super.img rw and was able to debloat directly from the booted device! I used a magisk module called RO2RW test version. It uses android terminal like termux to pull the super.img then extract it. Once Product, System etc are extracted you use the mount script that makes it able to edit the imgs from MT file manager. Then terminal prompt recompiles it along with a new boot.img. its hard to explain as im not a pro lol. Here's the xda link where I got the ro2rw magisk module. https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
Click to expand...
Click to collapse
Nice work. I have the CRB Kitcen for Windows which performs similar operations to super.img. My only dilemma has been a lack of free time. I'll check out the method you linked. I'm not familiar with that Magisk module and I will definitely check it out. Again, nice work. I admire your persistence and determination.
Latest OTA update package
MH-T6000V1.0.0B011
Viva La Android said:
Latest OTA update package
MH-T6000V1.0.0B011
Click to expand...
Click to collapse
Does this change the Security Patch? What have you noticed different?
Argonon said:
Does this change the Security Patch? What have you noticed different?
Click to expand...
Click to collapse
It bumps the security patch level and fixes a couple of bugs in the cellular radio firmware resulting in dropped calls during node switching.
To install it, the simplest way is to revert to an unmodified stock state by flashing the factory firmware in my restoration guide. Once restored, you can install the update.zip via stock recovery mode.
Awesome. Oh btw firmware is now available for the mtk blu view 3 android 11 now!!
Argonon said:
Awesome. Oh btw firmware is now available for the mtk blu view 3 android 11 now!!
Click to expand...
Click to collapse
This is excellent news.
I need to unlock sim for this phone . what is the unlock method pleassss?
Mohammed Alqadri said:
I need to unlock sim for this phone . what is the unlock method pleassss?
Click to expand...
Click to collapse
I unlocked mine simply by flashing the factory firmware via QFIL, using the exact steps outlined in this guide. After initial setup following firmware restoration, the preinstalled network unlock app indicated that my device was permanently unlocked for use with other carriers.
I'm not exactly sure as to the reason why this worked, nor have I researched the possible mechanics behind the occurrence.
Viva La Android said:
I unlocked mine simply by flashing the factory firmware via QFIL, using the exact steps outlined in this guide. After initial setup following firmware restoration, the preibstakked network unlock app indicated that my device was permanently unlocked for use with other carriers.
I'm not exactly sure as to the reason why this worked, nor have I researched the possible mechanics behind the occurrence.
Click to expand...
Click to collapse
When flashing the firmware, is it necessary to have the lock status of the bootloader unlocked or not ?
Mohammed Alqadri said:
When flashing the firmware, is it necessary to have the lock status of the bootloader unlocked or not ?
Click to expand...
Click to collapse
The state of the bootloader has no relevance to firmware restoration. The firmware will be installed in exactly the same manner regardless of whether the device is bootloader locked or unlocked.
For any members interested, my modified stock ROM for this device is complete. The full installation guide can be found here https://forum.xda-developers.com/t/...e-moxee-m2160-mh-t6000-4g-lte.4596393//unread
Viva La Android said:
For any members interested, my modified stock ROM for this device is complete. The full installation guide can be found here https://forum.xda-developers.com/t/...e-moxee-m2160-mh-t6000-4g-lte.4596393//unread
Click to expand...
Click to collapse
I have a question, why when I insert the sim card into the phone, it appears that there is no service, since the service is available on any other device. will the modified ROM solve the problem or the official ROM? please answer......
Mohammed Alqadri said:
I have a question, why when I insert the sim card into the phone, it appears that there is no service, since the service is available on any other device. will the modified ROM solve the problem or the official ROM? please answer......
Click to expand...
Click to collapse
This ROM does not have any effect on the network locked or unlocked state of the device. You may need to configure your network settings or APN configuration for the carrier of the SIM card. But, out of curiosity, what carrier is linked to your SIM card, and has your Moxee phone been network unlocked? By default, the Moxee m2160 is locked to Assurance Wireless and, as such, will only work on their network.
I
Viva La Android said:
This ROM does not have any effect on the network locked or unlocked state of the device. You may need to configure your network settings or APN configuration for the carrier of the SIM card. But, out of curiosity, what carrier is linked to your SIM card, and has your Moxee phone been network unlocked? By default, the Moxee m2160 is locked to Assurance Wireless and, as such, will only work on their network.
Click to expand...
Click to collapse
I use the carrier of GSM. the coverage towers do not appear on the phone. there is no service that has nothing to do with settings or APN