Related
Dear open developers community I managet to fully root BlueBerry NetCat M-12 Tablet PC (a.k.a rebranded Cube H30GT) using "remount" exploit, here is my contribute:
{
"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"
}
REQUIREMENTS:
* Android SDK with ADB (guess you have this, if not, main files are included in permaroot.zip attached below)
* RockChip RK3066 USB Driver (see attachments below)
* Root/UnRoot script (thanks to Bin4ry from this thread, see attachments below)
* Micro USB Cable to connect Tablet and Windows Desktop PC (Linux is unsupported for now due to manufacturer limited driver distribution)
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You will spot that i dont recommend making any nand backups in this howto - is because I am not aware of any working method for backup M-12. I onlu can imagine dumping whole partition images to your EXTERNAL_SD and flashing back through bootloader but I did not tested that for now.
#GET ROOT
STEP-BY-STEP HOWTO
1. On your tablet PC go Settings -> Developer Options -> Turn on USB Debugging
2. Now You need to manage your Android Debug Bridge recognize your Tablet PC. You can check if it already works by typing this command in command prompt (in ADB folder, or wherever if you extracted adb into windows/system32)
Code:
adb devices
It should give you list of attached devices (something like this: 0123456789ABCDEF device) you should recognize your device if is connected. From my experiences it wont work the way manufacturer described, therefore you need to install patched RK3066 SoC driver you downloaded (this post below). To do so you must right click on My Computer -> Manage -> Device Manager, find your Unknown Device and install driver manually by selecting search folder manually, where you extracted RK3066_ADB_PATCHED.rar content respectively to your OS version (use correct 32-bit or 64-bit driver). Reboot your PC, go to device manager to check if Android Debug Bridge is there:
And You can repeat "adb devices" once again in adb to verify:
3. Now is time to obtain temporary root. To do so, simply navigate command prompt to wherever You extracted adb.exe and type following command:
Code:
adb remount
It uses common JB exploit, which exists in BlueBerry NetCat M-12, alowing you to get temporary root access via ADB shell until next reboot. You can stop at this point and push any system file You want (ie /system/etc/hosts) and set permissions. But if you want permanently rooted device, you need to push SuperSU.apk, su, busybox,... manually via adb before next reboot. Lucky for you, there is a script (permaroot.zip thanks to Bin4ry) which can do it all automatic with just few clicks. Download it from attachment below, extract somewhere on your hard drive run permaroot.bat and have fun.
Comming soon...
++ Flashing through Bootloader (via RockChip Batch Tools) HowTo ++
++ Illustrated Hardware disassembly guide ++
++ There is one custom ROM ported for another device and tested by me, which works in M-12 like a charm. It is purified JB ROM, rooted and without bloatware. I will post it ASAP ++
++ If i be able to obtain original Blueberry firmware dump, i will make CWM Touch based recovery image. Any interested owner of original BlueBerry NetCat should supply me with F/W dump, so if you are one, PM me please ++
++ If I be able to make Cube CWM Touch recovery work I will share (I managed to extract and install it from supersport900 ROM but it wont mount partitions for some reason) ++
BlueBerry NetCat M-12 Disassembly Guide
+++ BlueBerry NetCat M-12 HardWare Assembly +++
Tools needed:
1 x 1mm Torx Screwdriver (pictured below)
2 x sharp plastic departer for simultaneous two-side gently disassembling plastic parts (any Credit Card or guitar pick will do)
Step-by-Step Guide for servicing (H/W repairs, forced bootloader, etc) your BlueBerry NetCat M-12:
* Torx screws are located along port side, noted the difference on Torx and Cross screw types between some devices - Picture 5
* Some BlueBerry NetCats M-12 dont have left speaker - Pictures 20, 25 and 26
* BlueBerry NetCat M-12 has different stamp (OEM Logo) on backside - Picture 14
** Note LED and short circuit testpoint locations for forced bootloader mode which will be described later in more details - Pictures 25-32
Picture 1:
Picture 2:
Picture 3:
Picture 4:
Picture 5:
Picture 6:
Picture 7:
Picture 8:
Picture 9:
Picture 10:
Picture 11:
Picture 12:
Picture 13:
Picture 14:
Picture 15:
Picture 16:
Picture 17:
Picture 18:
Picture 19:
Picture 20:
Picture 21:
Picture 22:
Picture 23:
Picture 24:
Picture 25:
Picture 26:
Picture 27:
Picture 28:
Picture 29:
Picture 30:
Picture 31:
Picture 32:
Picture 33:
There is a PDF with all images in attached archive.
+++ClockWorkMod based recovery image for BlueBerry NetCat M-12+++
CWM Touch 6.0.2.7 (Thanks to Typhoon.X)
CWM Touch is Direct-Touch-Input CWM Recovery image: you can use touch gestures to navigate through menus, but I still prefer old-fashioned way of navigating through menus by using Volume +/- for <UP> and <DOWN>, and Power button as <CONFIRM> which is also available on our devices.
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You are welcome to make backup(s) before make any change to your device; You can export partition(s) dump or make nandroid backup via CWM based recovery image if you have it allrady installed.
Install:
1. Make sure you have installed RK3066 drivers;
2. Download ClockWorkMod.zip, extract, run RKAndroidTool.exe.
3. Reboot your BlueBerry NetCat M-12 in Flash Mode (turn on device by holding Volume- and Power Button or push "Reboot to Flash Mode" button in RKTool)
4. Push "Flash ROM" button like on image below (all settings are stored in config.cfg so You dont need to change anything):
After procedure is finished (cca 15 seconds), device will be automatically rebooted into CWM Recovery, so it's highly recommended making first nandroid backup.
Usage:
If your device is rooted, you can reboot your device into CWM recovery by typing following commands in terminal emulator:
Code:
su
reboot recovery
Or by using any 3rd party rebooting widget/app, which allows rebooting into recovery.
However, if your device is not-rooted, you can reboot into CWM recovery by typing following commands which exploit temporary root access via Android Debug Bridge (adb.exe on your PC, drivers must be installed):
Code:
adb.exe reboot recovery
or
Code:
adb remount
adb shell
su
reboot recovery
Download CWM Touch based recovery image from Google Drive: ClockWorkMod or attachment below.
Be aware that bootsplash will be changed as you need to replace misc.img, so dont panic if you see Cube logo instead of NetCat.
Hey, CyberianIce, thank you for your contribution for this device, since it's really hard to find anything verified out there, and xda is alwas the safest choice.
I wanted to ask you if you could share the info, or link maybe, to that ported ROM you tested on Blueberry, since I don't wont to brick my device by trying an untested ROM.
Thanks in advance!
I can re-upload from my HDD because I forgot original URL, when I got day off my work.
/CyberianIce via TapaTalk HD
That would be amazing, thank you! And if you could write something about the ROM (when you have free time, of course) just so that I know what I'm installing..
Hi, i wonder how to make a hard reset on this devices, i have tried the normal way, volume(-)(+) + power but nothing is working. Can someone help me? Thanks!!
Hi, CyberianIce, I was wondering if you'll have time soon to upload the ROM, if it's not too much trouble. Thank you!
So far I found this Firmware image working best on NetCat M-12: http://www.rockchipfirmware.com/sites/default/files/cube_u30gt-h_V1.11_TNT_R1.zip
For Flashing use this tool: http://www.rockchipfirmware.com/sites/default/files/RKBatchTool1.5en.zip
(Credits: http://www.rockchipfirmware.com/)
It is great because you can flash it vie Rockchip Batch Tool which means its very useful for debricking. It is 4.1.1 from Cube U30GT-H with all this tweaks:
Brief Description:
-Rooted
-Based on stock rom (2012.12.28)
-App partition is Larger
-Build.prop mod based on SGS II SGH-i777 for improved market
-Added Permission Files for improved market
-Removed Chinese Apps
-framework.jar mod for better gameloft compatibility (Asphalt 7 should now work)
-Added SuperSu, gallery with picasa support, ESfile Explorer, english dictionary fix
-Simplified and pretty boot animation
-Changed Annoying Keyboard Key-press sounds... now they are less annoying (based off Cyanogen sounds)
-Default Background should be changed
-Changed "browser" start page to our Google paid search. Use it (free to use for you) to search the web and you will be helping to support us as we release more free firmware. Can easily change this if you want.
Click to expand...
Click to collapse
Afterwards one can flash CWM based recovery image following tutorial from this post
[ROM][RK3066][U30GT-H]BlueBerry NetCat M12
Based on latest original Cube U30GT-H ROM debranded from BlueBerry NetCat M12
Tested on many CUBE U30GT-H devices
Debloated
Removed China
Custom tuned Kernel for optimum performance and stability (up to 15k points in AnTuTu Benchmark)
Increased /data partition size to 2GB instead of 1GB (reduced internal sdcard partition to 12.5GB instead of 13.5GB)
NetCat BootSplash
Custom android bootanimation.zip
Fully working CWM Recovery 6.0.2.7
HOWTO:
1. Shut down your tablet and start it by holding down Volume + button and insert USB Cable with PC. RK Device will apear, if you have no drivers you can find them in archive.
2. Navigate to RKDevelopTool_v1.35 folder and run RKAndroidTool.exe
3. Click Erase IDB and wait for finish
4. Click Run and wait for finish
5. After procedure is complete, if your tablet don't start automatically in CWM, remove USB and shut down tablet by holding POWER button for 8 seconds (you will hear silent *click* sound from tablet as signal it's off). Now download CWM Base from this XDA post put tablet in download mode (VOL+ and USB CABLE) and flash this recovery (run RKAndroidTool.exe, push Flash ROM button). It is very same recovery from this ROM, but after this flashing is finished, tablet will boot into CWM automatically on it's own.
6. Now install ZIP files from after_install folder via CWM recovery. Format NAND is required if you first time using 2GB Data mod, and int2ext is required for some devices which reported switch between internal and external SD card. You must use an external SD Card for flashing ZIPs and search for files in both internal and external sd card in CWM as you still dont know how CMW see your SD card.
7. Reboot System. All done!
DOWNLOAD
Note: If you are used increase /data to 2GB MOD before, you can just install this firmware via RKAndroidTool. If your /data partition was 1GB before, you may need to install patches from folder after_install via CWM recovery.
TOPELOTEK METEOR T07D
7" ANDROID TABLET
Product: astar_733Q1
Board Platform: Allwinner-A33
CPU: Quad-Core Cortex-A7 (ARMv7l)
CPU Clock: 200 MHz - 1.2 GHz
[Overclock Up To 1.51 GHz]
GPU: Mali-400MP2
RAM: 1 GB
Bluetooth: 4.0
Internal Storage: 8 GB (eMMC)
External Storage: microSD Slot (Up to 128GB)
USB OTG Support
OEM Unlocked
Display: 7" IPS
Screen Resolution: 800 x 1280
Screen Density: 190 DPI (mdpi)
Battery: 2850 mAh Li-Ion
Cameras: 2.0 MP Main; 0.3 MP Front
OVERVIEW:
The Topelotek Meteor (T07D) is a very affordable, very basic, low-spec 7" Android tablet. As reflected by the above hardware specs, this tablet is by no means spectacular with regard to performance potential. Nonetheless, for the pricetag (typically about $25 or less), the Meteor T07D is not a bad deal. Like many Chinese tablets of its kind, stock firmware can be very difficult -- if not impossible -- to locate. However, this device does ship with a couple of extraordinary features: an unlocked bootloader and insecure boot image support (ro.secure=0) out of the box. As such, rooting and customizing this tablet are fairly simple tasks, as is pulling firmware images from the device's partitions. This firmware package is constructed from unmodified stock partition images (/system, /boot, /bootloader, /recovery), which can be installed using a few rudimentary fastboot commands, and can be beneficial in restoring a device that is soft bricked, stuck in a bootloop, etc. Installing this firmware package per the instructions below will restore your Topelotek Meteor to a stock factory state.
FIRMWARE BUILD INFO:
Android Version: 6.0.1 Marshmallow
Build ID: MOB30R
Firmware Version: v6.0rc3
Build No.: A33-1+8-0312+2145-1280x800-6.0-733Q1-8703-180601
Kernel Version: 3.4.39
Build Date: May 30, 2018
Security Patch Level: April 1, 2018
Insecure Boot Image (ro.secure=0)
DISCLAIMER: By proceeding further, your warranty can be rendered null & void. (However, because the device ships OEM unlocked, out of the box, your warranty may or may not be affected. You will need to make this determination on your own.) As with any other system-level procedure, installing this firmware invokes the possibility that your device could be damaged or rendered completely inoperable. While I have thoroughly tested this firmware on my own device, I will not be held liable for anything that goes wrong during your installation of this firmware. By proceeding, you are taking sole responsibility for the integrity and operability of your device.
PREREQUISITES:
For this installation, you will need a PC or Mac with the latest Android platform tools or the latest Minimal ADB & Fastboot utilities installed. Visit this thread for download links and instructions: https://forum.xda-developers.com/showthread.php?t=2317790 Please give @shimp208 a tap on the THANKS button if you use his work. This is a link to the July, 2019 Minimal ADB & Fastboot thread by @K3V1991. https://forum.xda-developers.com/an...g/tool-mini-adb-fastboot-2019-06-30-t3944288. Again, please give thanks if you use the developer's work.
Also, you will need to install the correct ADB and USB device drivers for this tablet.. A simple Google search for "Allwinner-A33 ADB & USB drivers" will provide links to these files, as well as guidance for proper installation of the drivers. As mentioned supra, this tablet ships with an unlocked bootloader. Nevertheless, you will need to go to SETTINGS>ABOUT TABLET and tap Build Number 7 or 8 times until Developer Options are enabled. Then, you will need to check the box called OEM Unlocking. Once this is done, your device bootloader is unlocked for all intents and purposes.
INSTRUCTIONS:
1. Download the firmware package from the below link and extract the contents of the archive to your ADB & Fastboot directory on your PC;
2. Boot your device into fastboot mode. One way to do this is by connecting your device to your PC with a quality micro USB to USB syncing/charging cable. Boot your device up, ensure USB Debugging is enabled, and open a command prompt on your PC in the path of your ADB/Fastboot directory. Execute this command:
adb devices
If properly connected, the command window will return with an alphanumeric string that represents your device serial number. If you do not see confirmation of a proper connection, check your driver installations, your sync cable, and/or try another USB port.
(In the event your device will not boot into the Android OS (soft brick, boot loop, etc.), you can boot directly into recovery mode/fastboot mode by using hardware key combinations. However, I am not familiar with the hardware key method, so you will need to research the proper procedure.);
3. Once properly connected, execute the following command:
adb reboot bootloader
Your tablet will now boot into fastboot mode. Your device screen will simply display the white Topelotek logo lettering amidst a pale blue screen. Open a command window once again in your ADB/Fastboot directory;
4. Execute this command:
fastboot devices
Once again, if properly connected, the word "fastboot," or your device serial number will be displayed in the command window;
5. Once fastboot communication has been established, execute the following command set:
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
(Please note that system.img is a large file. Fastboot will automatically parse this image into a series of sparsechunks and systematically flash them to your device. This process can take up to 5 or more minutes, so just be patient. To avoid any possible issues, it is imperative to be using a current version of either the Android platform tools or the Minimal ADB and Fastboot utilities.)
Upon reboot, your device should be restored to a factory stock state and be running on the latest available firmware version.
DOWNLOAD LINK:
Firmware v6.0rc3: https://drive.google.com/file/d/1-0UciSFgTwqN-n_TyL255oZcOVZMqjso/view?usp=drivesdk
QLink Scepter 8 TabletBy Hot Pepper Mobile
{
"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 Guide
For Gen 1 & Gen 2 Models
TABLET MODELS & VARIANTS:
For those members familiar with the firmware restoration thread, there are a total of four model variants of the QLink Scepter 8 tablet: two variants of the Gen 1 model, and two variants of the latest Gen 2 model. Determining which Scepter 8 you have is a very simple two-part check. First, if you don't already know your Android OS version, go to device Settings> About tablet, and locate your Android version. If you are running Android 11 (Go Edition), you have the original Gen 1 model. If you are running Android 12 (Go Edition), your tablet is the latest Gen 2 model. Secondly, you will need to locate the device S/N in order to determine your tablet variant. Your S/N is printed on the manufacturer's label affixed to the exterior of the tablet's rear housing. From the Android OS, you can also locate your S/N by opening device Settings>About tablet>Model. Regardless of whether you have the Gen 1 or the Gen 2, the first two letters of your S/N will be either CF or MD. This is the codification of your tablet variant. To alleviate some of the legwork of rooting, and to keep this thread simple to follow, I have provided boot images pre-patched for Magisk v25.2 systemless root support. I have categorized the download links for each of the boot images in accordance with the respective model and S/N variant. To avoid potential bugs, instabilities, boot loops and the like, it is crucial that you download the boot image that corresponds with your model & variant. OVERVIEW:
This guide outlines step-by-step instructions for unlocking the bootloader and rooting all variants of the Gen 1 & Gen 2 QLink Scepter 8 tablet. This guide also includes a detailed section on properly installing the ADB, fastboot, & USB device drivers on your Windows PC or laptop, as well as steps to troubleshoot & manually update these drivers in the event the tablet is not being recognized while in fastboot mode.
DISCLAIMER:
Unlocking your bootloader and rooting your device are both procedures that carry inherent risks. Because these procedures involve modifying the device from it's stock factory configuration, it is possible to corrupt, damage, or even render your tablet completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your device, therefore absolving me of any liability in the event something goes south. I have, however, tested these guides and feel confident that things will go smoothly as long as you follow the instructions carefully. Moreover, I encourage all members to read the instructions fully before starting the steps, in order to first gain a fundamental understanding of the concepts and methods involved.
PLEASE PLAY NICE & FOLLOW XDA RULES:
This thread was created with the intent of being a noob-friendly forum. This simply means that new and inexperienced members are fully welcome here, and will be provided with extra guidance and assistance if needed. Please keep in mind that XDA is a global community of developers, enthusiasts and device users. As such, and although English is the only permitted language in the forums & threads, not all members speak English as their first language, and often rely on text translation tools when asking questions & posting. Accordingly, it is very common for words to be misconstrued, meanings to be misinterpreted, and the context as a whole lost in translation. I ask members to be patient, compassionate and respectful to others on this thread. Those members with the knowledge to do so are urged and asked to help newer members, and recall back when you were new here and others helped you.
Please help me with keeping this thread on point by ensuring that all subject matter herein be kept relevant to the topics of rooting and OEM unlocking the QLink Scepter 8. Any posts about other devices or subject matter run afoul of XDA rules and are subject to removal by moderators -- and potential sanctions imposed upon the offending member. Moreover, an on-topic thread keeps things organized and easier to follow. Thank you for your consideration.
PREREQUISITES:
To unlock the bootloader and root the QLink Scepter 8 tablet, you will need a laptop or PC running on Windows 7/8.1/10/11. (A Mac or Linux machine can also be used. For purposes of this guide, however, I am focusing on a Windows setup.) You will also need the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Last but not least, you will need to install compatible USB device drivers for ADB & Fastboot on your PC/laptop. I have included the 15-Second ADB Driver Installer below, under the DOWNLOADS section. This Installer will configure ADB & Fastboot system-wide, and installs the universal Google USB device drivers. I would encourage members to first read the instructions in their entirety prior to actually starting the guide.
•INSTALLING USB DEVICE DRIVERS•
This section is included to install and configure ADB, Fastboot and the proper USB device drivers on your Windows computer. This section can also be used to troubleshoot and fix issues involving your tablet not being recognized by Windows while connected in fastboot mode. If you have already installed the ADB & Fastboot tools (& the proper USB device drivers), and you are not experiencing fastboot recognition issues, you may skip this section and proceed to the bootloader unlocking section.
Many members have reported issues with device recognition while in fastboot mode. I have also noticed a persistence problem with Windows drivers on this tablet. I can manually update the driver using Windows Device Manager, enabling fastboot recognition; yet, once the tablet is disconnected from my PC the updated driver does not always persist, requiring a manual driver update each time fastboot mode is needed. Follow these steps to enable fastboot recognition of your device.
• 1. If you have not yet done so, install the 15-Second ADB Installer from the link below on your Windows PC or laptop. Open the utility and follow the prompts to install the ADB & Fastboot drivers. Next, opt to install ADB system-wide. Lastly, you will be prompted to install the Google USB device drivers. Select Y and install them. You should see an interface informing you that the drivers were successfully installed. NOTE: If you get a warning notification that the drivers are unsigned, select the option to install anyway;
• 2. With your tablet powered off, hold the Power and Volume Down buttons simultaneously until the QLink logo appears, at which time you release the Power button but continue holding Volume Down. When a green Android graphic appears on your display, you are in fastboot mode;
• 3. Connect your tablet to your Windows machine using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable;
• 4. Open a command window in the path of your ADB/Fastboot directory. Execute this command:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string which is synonymous with your tablet serial number. If this occurs, you are finished with this section and may proceed to the instructions for unlocking the bootloader/rooting. If the command window displays Waiting on Any Device, or if your serial number is not displayed, continue with the following steps;
• 5. Keeping your device connected to your Windows PC/laptop, right click your Windows Start icon and select Device Manager. Locate your tablet in the menu. It will likely be located under either the Portable Devices or Android Device heading;
• 6. Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your tablet in the Device Manager menu, the driver selection menu can vary. If you see an option for Android Device, select that option and then select Android Composite ADB Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
• 7. Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. If you are still experiencing fastboot recognition issues, try using another data sync cable, change USB ports on your computer, and/or reinstall the drivers using the 15-Second ADB Installer.
I. UNLOCKING THE BOOTLOADER:
If you plan on rooting your tablet, this step is mandatory. If your bootloader is already unlocked and you only wish to root your device, skip down to the rooting instructions in the next section below.
WARNING: Unlocking your bootloader forces the device into a factory data reset, which will effectively wipe all saved user data from the device. Make a backup at this point if there are files and media on your tablet that you wish to keep.
INSTRUCTIONS:
1. Enable Developer Options on your tablet by going to device Settings>About tablet and tap Build number approximately seven times. Android will notify you that Developer Options are enabled; this menu will appear under device Settings>System>Advanced.
2. Enable USB Debugging and OEM Unlocking in the Developer Options menu. NOTE: Users have reported the OEM Unlocking option being greyed-out unless you are signed in to your Google account.
3. Now to boot into fastboot mode, and this particular step is extremely important. Android 10 introduced a new fastboot mode for dynamic partitions, known as FASTBOOTD, which is relocated from the bootloader to userspace. This particular fastboot mode supports resizeable partitions within the dynamic scheme, and enables the user to create, resize and delete various logical partitions. However, FASTBOOTD mode cannot be utilized to unlock the bootloader, and will not recognize the unlock command. As such, the user must rely upon legacy fastboot mode in order to unlock the bootloader. From stock recovery mode, you may simply choose the option to reboot to bootloader. DO NOT CHOOSE THE OPTION TO ENTER FASTBOOT, as this option will boot to FASTBOOTD. From the Android OS, you can boot into legacy fastboot mode by executing:
Code:
adb reboot bootloader
Once you see a green Android graphic appear in the center of your display, you are in the correct fastboot mode.
4. Connect your tablet to your PC/laptop using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Next, open a command window in the path of your ADB/Fastboot directory. Check your connection by executing this command:
Code:
fastboot devices
If you are properly connected, the command window will return an alphanumeric string synonymous with your device's serial number. If you do not see this, there is a problem with communications between your tablet and PC/laptop. To troubleshoot the issue, switch to another USB port, try another data sync cable, and/or reinstall the ADB/Fastboot drivers on your PC or laptop. Also, see my instructions above on installing USB device drivers on your Windows computer;
5. Once a proper connection has been verified, execute this command:
Code:
fastboot oem unlock
Once you see the Okay notification in the command window, your bootloader is now unlocked. Execute this command:
Code:
fastboot reboot
Your tablet will now initiate a factory data reset and then reboot into the initial setup for the Android OS.
II. ROOTING THE QLINK SCEPTER 8
Now that the bootloader has been unlocked, rooting this tablet is very straightforward. Again, I have provided pre-rooted boot image files in the DOWNLOADS section for all four models & variants.
INSTRUCTIONS:
A. Gen 1 QLink Scepter 8Android 11 (Go Edition)
NOTE: If your tablet is running Android 12 Go Edition, you're in the wrong place. Skip down to the next section.
1. Download the Gen 1 patched boot image that matches your S/N variant using the links below, and save the file on your PC/laptop in the ADB/Fastboot directory. Note that the file is named patched_boot.img. The flashing command below assumes that you leave this file name unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute these commands:
Code:
fastboot flash boot patched_boot.img
fastboot reboot
NOTE: Your active boot slot should be boot_a. Regardless, the above command flashes your active slot by default, without having to specify slot _a or _b.
Upon reboot, your tablet will be rooted with the latest Magisk systemless root strategy. If you do not see the Magisk app or the placeholder stub in your app drawer, go ahead and download the latest version from the link below and install the APK on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to complete setting up the root environment.
B. Gen 2 QLink Scepter 8Android 12 (Go Edition)
NOTE: If your tablet is running Android 11 Go Edition, you're in the wrong place. Go back to the previous section. .
1.Download the Gen 2 patched boot image that matches your S/N variant and the empty vbmeta.img using the links below, and save the files on your PC/laptop in the ADB/Fastboot directory. Note that the boot image file is named patched_boot.img, and the vbmeta image is named vbmeta.img. The flashing commands below assume that you leave these file names unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now, continuing in fastboot mode, you will need to disable dm-verity/Android Verified Boot (AVB) by flashing an empty vbmeta.img via executing the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Next, execute this command to reboot your device:
Code:
fastboot reboot
Upon reboot, your tablet should now be rooted with the Magisk systemless root strategy. If you do not see the Magisk app or the stub placeholder in your app drawer, go ahead and download the latest version from the link below and install it on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to update Magisk and/or complete setting up the root environment.
IMPORTANT NOTE:
In the unfortunate event you have a mishap with rooting your tablet and get stuck in a boot loop, or if your tablet will not otherwise boot into the Android OS, have no worries. My tutorial on firmware restoration for the QLink Scepter 8 will revert your device back to its original stock factory state. You can then return here and give it another try.
QLink Scepter 8 Firmware Restoration Guide
DOWNLOADS:
• 15-Second ADB Installer
• Gen 1 (CF) Patched Boot Image
• Gen 1 (MD) Patched Boot Image
• Gen 2 (CF) Patched Boot Image
• Gen 2 (MD) Patched Boot Image
• Empty vbmeta.img
• Official Magisk Releases / GitHub Repo
THANKS & MENTIONS:
Thanks goes out to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing stock firmware images for this device.
Also, I wish to recognize and thank @13lack13ox for being a huge help to thread members at times when I was not able.
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
64Star said:
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
Click to expand...
Click to collapse
Sounds like you have a common driver issue. Do this: with your device connected to your PC in fastboot mode, right click your Windows start button and open Device Manager. What is your tablet showing up as? We will need to update your driver. I can walk you through it. Did you install the Google driver from the 15-Second ADB Installer? I am nearly finished writing a guide on properly installing the device drivers. I will link it here when posted. It will give you a detailed step-by,-step outline. I don't think it's an issue with the firmware builds. Fastboot detection issues are common with this tablet due to some type of instability with driver persistence. For example, I often need to update my driver every time I use fastboot mode because, for some odd reason, the updated driver doesn't persist once the tablet is disconnected from the PC and then reconnected.
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
luridphantom said:
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
Click to expand...
Click to collapse
The Scepter 8 does not ship with adb root shell (adbd) enabled. In fact, the bootloader was not even intended to be unlocked. The unlock command is disabled in standard fastboot mode. Luckily, the Scepter 8 is integrated with a second fallback fastboot mode, which we were able to use to to the oem unlock.
Many AllWinner tablets and other Chinese devices do, as you pointed out on your Hot Pepper device. When the Scepter 8 was first released I was able to pull a boot image using a Phoenix Suite tool that had been reverse engineered and modded. As luck would have it, I got rid of the tablet and lost my files along with access to the Phoenix Suite tool. So I've been weeks quarreling with Hot Pepper Mobile to provide firmware and the kernel source code. To their credit, the Hot Pepper CEO and support team were very helpful once they understood what I needed. Hot Pepper's software developers are in China, so a language translation issue hindered my request for some time.
Anyway thank you for your kind words and it is a pleasure making your acquaintance.
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Viva La Android said:
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Click to expand...
Click to collapse
It does, I've unlocked the bootloader and now i'm gonna go root it. Thanks for your help!
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
64Star said:
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
Click to expand...
Click to collapse
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
LOL really turning a profit!
13lack13ox said:
LOL really turning a profit!
Click to expand...
Click to collapse
Haha. No doubt
Sorry about the delay on TWRP guys. My mounting issues are actually encryption issues. TWRP isn't decrypting the /userdata or /vendor partitions with the default key. I'm going to chat with one of my friends over at TeamWin and see if I can get a little guidance.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
64Star said:
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
Click to expand...
Click to collapse
Not really. I was only providing you info as to where they were available. I found one for $19 which is more than I really wanted to give.
As it stands now,.all the lag is gone in mine. I debloated everything that wasn't essential for normal operations. Then I edited the system/build.prop to increase responsiveness and I limited background apps & processes. Finally, I installed a kernel tuner and set the LMK to very aggressive, tweaked the I/o scheduler parameters, and increased entropy from the available pool. And set SELinux to permissive mode. I'm using Nova Launcher Premium with the launcher locked into memory. Believe it or not, the tablet is now very responsive considering the specs. I'm looking into overclocking the CPU a bit, but 1.46 GHz seems to suffice once RAM is optimized. It's a difference in night and day. It's good for a project tablet but that's about it.
There's another government tablet floating around called the Maxwest Nitro 7Q. 4G/LTE supported with a lot better specs. I think I have one located to buy for cheap.
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
13lack13ox said:
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
Click to expand...
Click to collapse
Absolutely. I'll list those for you here in just a little bit. I have a pure stock ROM built with a TWRP installer, but my TWRP has run into a snag. I've reached out to TeamWin for guidance on that.
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
13lack13ox said:
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
Click to expand...
Click to collapse
You seem to know your way around the Android OS pretty well. I'm a developer in training myself. Learning every day. Yeah AOSP 6, I still love working with the Marshmallow builds.
Ok first things first. I notice a huge performance boost from some kernel level mods. Here is a link to Kernel Toolkit. Install both APKs. https://mega.nz/folder/QYwA0QTA#O_Zg3h_iVkHOdeyU_yOmLw
First go to the CPU heading and change the scaling governor to Ondemand. Under CPU Governor Params, tap on Performance Profile and select Maximum Performance (you may personally want to scale back to Aggressive or Balanced, depending on your need for battery life). Now, close Kernel Toolkit and restart the app. Next go to the I/O heading. Choose kyber as the I/o scheduler and set the read ahead buffer to 512 KB. Go down to ZRAM and increase to the maximum of 1000 MB. Set Swappiness to 100. Go over to the Profiles heading, create a profile will all settings and give it a name recommended from the list. When complete, tap on the profile, select save settings and then apply settings.
Now go to the menu button in the upper left of the app. Go down and enable Apply Settings on Boot. Select All and set a 5 second delay.
Next, download a build.prop editor from Play Store. There are tons of free ones and any will suffice. Make a backup of your system/build.prop before you tweak anything. Open the editor and grant root permission.
For build.prop edits, locking your launcher into memory helps a lot with responsiveness. Add this line to system/build.prop
ro.HOME_APP_ADJ=1
This basically prevents the launcher from being killed by Android's native LMK.
To increase touch responsiveness, add these lines as well.
debug.performance.tuning=1
video.accelerate.hw=1
Disable the boot animation for faster boot time.
debug.sf.nobootanimation=1
Reboot to enable the tweaks.
Give these a try and let me know your feedback. I'm working on a few more mods to optimize this tablet and I'll keep you posted on those as well.
Thx great changes so far. Yeah more "snappyness" for sure. I'll have to play around and open up as much as i can swap around.
I can't change I/O scheduler though, I get a contact developer message.
13lack13ox said:
Thx great changes so far.
Click to expand...
Click to collapse
Yw. Do you notice a decent improvement?
Hot Pepper™ Serrano
AKA: QLink Serrano 3
Model No. HPP-L55B
By Hot Pepper Mobile
{
"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"
}
Factory Firmware Restoration
And Upgrading Guide
OVERVIEW
The Hot Pepper™ Serrano is a GSM unlocked 4G-LTE smartphone manufactured by Hot Pepper Mobile. A popular carrier variant of this device is the QLink Serrano 3, a model manufactured specifically for eligible recipients of the Affordable Connectivity Program (ACP). The ACP is a US government sponsored initiative that assists low-income households with wireless internet service.
This firmware package is specific to the QLink Serrano 3 carrier variant of the HPP-L55B, and includes QLink carrier apps and services. However, notwithstanding the minimal bloatware, this firmware should work on any unlocked or carrier-branded variant of this smartphone. I am presently working on removing all bloatware and carrier-ware from this firmware package. Once I have finished that task, I will provide a clean build that can be flashed via FastbootD mode.
DEVICE SPECS
Model No. HPP-L55B
Board Platform: MediaTek MT6739
CPU: Quad-core ARM Cortex-A53
CPU Architecture: 64-bit
Instruction Set: ARMv8-A
Process: 28 nanometers
CPU Max Clock: 1.5 GHz
GPU: Imagination PowerVR Rogue GE8100
GPU Max Clock: 570 MHz
Display: 5.5" FWVGA+ 960 x 480
Aspect Ratio: 18:9
RAM: 2 GB LPDDR3 (1 GB variant available)
Internal Storage: 16 GB eMMC 5.1
WLAN: 802.11a/b/g/n/ac
WiFi Bands: 2.4 GHz & 5 GHz
Bluetooth: v4.2
LTE Modem: MediaTek MT6177M
LTE Bands: 2, 4, 5, 12, 13, 25, 26, 41, 66 & 71
HD Voice: Supported
VoLTE: Supported
HPUE LTE: Supported via Band 41
Camera: 8 MP main / 5 MP front
Battery: 2,200 mAh Li-Ion
FIRMWARE INFO
OS/Version: Android 10
Build No. HPP-L55B-J-9.0.0
Build ID: 10/QP1A.190711.020
Kernel Version: v4.14.141
Radio: MOLY.LR12A.R3.MP.V140.8.P8
Build Date: September 27, 2022
Patch Level: September 5, 2022
Partition Scheme: Dynamic (non-A/B)
Build Type: user
Build Status: Signed / Official
DISCLAIMER
This guide involves flashing the eMMC internal storage device of your smartphone with a factory firmware package, thus fully restoring your device to its stock factory condition. The procedure outlined below is inherently risky to the overall integrity and operability of your mobile device. 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 phone. 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 Serrano. Moreover, it should be emphasized that this guide is for model HPP-L55B only.
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 HPP-L55B (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 DEVICE DRIVERS
We will be using SP Flash Tool v5.1924 to install this firmware package. One of the biggest obstacles encountered by device owners using SP Flash Tool is device recognition. The SP Flash Tool software installs firmware to a USB connected device by flashing the eMMC/NAND while the device is in BROM flash mode. This Boot ROM (BROM) state is a MediaTek proprietary firmware flashing protocol that utilizes hardware embedded bootloader code. In order for the SP Flash Tool to properly communicate with your MediaTek device, it is imperative that you have the latest MediaTek vCom drivers properly installed and configured on you Windows PC or laptop. While this guide will not include a dissertation on setting up these vCom drivers, I have included a link in the downloads section below to a comprehensive step-by-step guide on the procedure. Hence, if your Windows PC or laptop is not presently configured with installation of the latest vCom drivers, take this time to visit the guide linked below, and return to the instructions below once you have completed that task.
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 should not relock your bootloader if it is presently in an unlocked state.
WARNING: This process 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 HPP-L55B 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 smartphone 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 MT6739_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 phone. 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 Serrano and use the power key to boot the device. Your phone should now be restored to its unmodified factory state.
DOWNLOADS
• Firmware Build HPP-L55B-J-9.0.0
• SP Flash Tool v5.1924
• MediaTek vCom Drivers Installation Guide
• Hot Pepper Serrano User Manual (PDF)
THANKS & MENTIONS
A heartfelt thanks to Mr. Jorge Chavez, Technical Support Specialist at Hot Pepper™ Mobile for providing the factory signed firmware for this device. Thanks also to @skeleton1911 for his comprehensive guide on Installing vCom drivers on Windows.
Thank you so much, I have been searching for 2mos since mine soft bricked with an ota
@Viva La Android why is the firmware encrypted? i didnt see where the password is
Pls delete this
WillisD said:
@Viva La Android why is the firmware encrypted? i didnt see where the password is
Click to expand...
Click to collapse
I'm waiting on the okay from Hot Pepper™ to release this firmware package to the public. I should get the go ahead any time.
Firmware is live @WillisD
I just want to thank y'all for letting me be able to resurrect this phone, first ota and got a dm-verity error and became a paper wieght. Fully fixed and booted right up. Thanks so much!!!
@WillisD that's the stuff I love to hear. Glad it recovered your device. So no issues with the instructions?
Viva La Android said:
@WillisD that's the stuff I love to hear. Glad it recovered your device. So no issues with the instructions?
Click to expand...
Click to collapse
Not at all, but I'm far from a rookie, but they are good, was actually something different for me. Never messed with mediatek like that before. However, it said it relocks bootloader, it however left mine unlocked. So I don't know if I'm the only one, or known issue, or if for once in lucky? Lmfao
WillisD said:
Not at all, but I'm far from a rookie, but they are good, was actually something different for me. Never messed with mediatek like that before. However, it said it relocks bootloader, it however left mine unlocked. So I don't know if I'm the only one, or known issue, or if for once in lucky? Lmfao
Click to expand...
Click to collapse
What method did you use to unlock your bootloader initially? Just the standard fastboot command line?
By the way this is a phone i am presently beta testing for Hot Pepper Mobile. Very nice device and T-Mobile certified. I highly recommend this phone once it is released for the public market.
[INFO][INDEX] Hot Pepper™ Chilaca (HPP-L60A) 4G-LTE Smartphone | General Info & Discussion Thread
Hot Pepper™ Mobile Chilaca 4G-LTE Smartphone T-Mobile® Certified Model No. HPP-L60A General Info & Discussion Thread OVERVIEW: The Chilaca is a T-Mobile certified 4G-LTE smartphone, manufactured by Hot Pepper Mobile for eligible recipients of...
forum.xda-developers.com
Also, if you wouldn't mind, can you confirm that this firmware is based on Android 10 (Go Edition) please. And please post a screenshot of your kernel version, baseband version, etc., for my reference. I don't actually have a Serrano, but I would like to add the firmware specifics to this guide. In fact, if you could post the info provided by running
Code:
fastboot getvar all
It wouid be extremely helpful. Thank you
Stock Firmware HPP-L55B-J-9.0.0
Click to expand...
Click to collapse
Hello ! Sorry, where can I found the download link or someone can reupload this stock firmware please ?
Thank you very much.
odilonser said:
Hello ! Sorry, where can I found the download link or someone can reupload this stock firmware please ?
Thank you very much.
Click to expand...
Click to collapse
Greetings @odilonser. Technically speaking, this factory firmware mage for the Serrano is a leaked resource. Because I maintain an amicable relationship with Hot Pepper Mobile, I need to first ascertain that the company's upper echelon is okay with me hosting this particular firmware package before reposting the link.
@Viva La Android what is the decryption key? if you cant do that can you upload the boot image by itself please?
VenomousSteam81 said:
@Viva La Android what is the decryption key? if you cant do that can you upload the boot image by itself please?
Click to expand...
Click to collapse
Sure. What all do you need? Just the stock boot image? As it stands, sharing the entire factory signed package cam delve off into ethical and even civil questions. However I have no problem sharing some individual images.
Viva La Android said:
Sure. What all do you need? Just the stock boot image? As it stands, sharing the entire factory signed package cam delve off into ethical and even civil questions. However I have no problem sharing some individual images.
Click to expand...
Click to collapse
Yes, just the boot image.
VenomousSteam81 said:
Yes, just the boot image.
Click to expand...
Click to collapse
This folder includes both boot images: boot.img & boot-debug.img; it also contains vbmeta.img, the scatter file for the firmware, recovery.img, ramdisk.img & preloader.img
72.86 MB folder on MEGA
7 files
mega.nz
If you're using the boot image to patch for Magisk systemless root, you'll likely need to disable AVB/dm-verity using vbmrta.img.with the corresponding fastboot command.
To clarify, these images
were pulled from the HPP-L55B-J-9.0.0 build.
Ok, thank you! I don't like mega, but as long as i can root my phone, it should work. Ah, its another service I'm thinking of. I take that back lol
Cool. Yeah Mega is fully.safe: encrypted file.srorage and end-to-end encryption file transfers.
Code:
fastboot flash boot patched_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
@VenomousSteam81 ... Does the stock boot image have a dedicated ramdisk? Does the Magisk app indicate yes or no next to ramdisk? Nevermind on thatI just decompiled the boot image and saw tharthere is a boot-ramdisk.
Android 11 (Go Edition)
Modified Stock ROM
{
"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"
}
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
OVERVIEW:
This is a heavily modified build of the stock Android 11 (Go Edition) ROM which comes preinstalled on the KonnectONE Moxee m2160 smartphone. Please note that, while flashing this ROM will not network unlock your device, the ROM does include added support for most GSM based providers on devices which have previously been network unlocked.
In a nutshell, this modified build focuses on the removal of bloatware and a slimmed-down, more responsive stock OS experience. In addition, once installed, the ROM supports full R/W mounting of all logical partitions encompassed within /super. (The unmodified stock ROM, notwithstanding Magisk systemless root, restricts proper R)W mounting of these partitions due to the stringent codebase changes which implemented the dynamic partition scheme back with the release of Android 10.) This ROM also disables force encryption to /userdata (DFE), disables AVB/dm-verity, and includes several mods for improved performance and responsiveness. While certainly nothing special in terms of custom development for the Moxee m2160, this ROM should provide users with a sufficient daily driver ROM with an optimized stock feel.
FEATURES & BUILD INFO:
• Based on firmware build MH-T6000V1.0.0B010
• Kernel version: 4.19.157-perf
• Security patch level: March 5, 2023
• GMS version: 11_202111.go
• VNDK version: 30
• Quick boot sequence
• Systemless root via Magisk v26.1
• Enabled Power Stamina mode for better battery life
• /system mounts R/W
• /system_ext mounts R/W
• /product mounts R/W
• /vendor mounts R/W
• Force encryption of /userdata disabled (DFE)
• OTA notifications & persists disables
• AVB/dm-verity disabled
• Stock launcher locked in memory
• Zipaligned /system/app & /system/priv-app
•Zipaligned /system_ext/app & /system_ext/priv-app
• Zipaligned /product/app & /product/priv-app
• Custom TCP congestion algorithm presets
• Heavily debloated w/minimal Google framework
• Kernel level performance optimizations
• Google Pixel 2 dark bootanimation
• Optimized RAM management
• Schedutil tuned CPU governor parameters
• Enabled fast charging (1100 mAh stable)
• GSM support for network unlocked devices
PREREQUISITES:
An unlocked bootloader
A PC or laptop running on Windows 7, 8.1, 10 or 11
Smartphone must be running Firmware Build No. MH-T6000V1.0.0B010
The SDK Platform Tools on your Windows computer (link provided below)
Installation of the proper ADB & Fastboot device drivers on your Windows computer
The factory supplied, or a quality sufficient, USB-A to USB-C syncing/charging cable
A reliable internet connection for downloading the required files
NOTE: We will not be using a custom recovery for installation of this ROM, but rather the dynamic user space implementation of fastboot mode, formally called FastbootD. This fastboot protocol was first introduced with the release of Android 10, and is primarily utilized for the management of dynamic partitions (devices with a /super partition).
DISCLAIMER:
This guide involves the invasive procedure of flashing the partitions of your device, thus modifying the configuration of the device from its factory stock state. This is always inherently risky to the integrity and operability of your mobile device. By proceeding further, you are assuming sole responsibility for the functionality and physical wellbeing of your mobile phone, thus absolving me of any liability in the event things go badly. This ROM has, however, been tested thoroughly on my own device with no negative issues. Moreover, in the unfortunate event your device becomes bricked or otherwise inoperable by way of a botched adherence to this guide, my firmware restoration guide for this device can restore both soft and hard bricked phones. Moxee m2160 Unbricking Guide
INSTRUCTIONS:
WARNING:
These instructions include steps for initiating a factory data reset, a procedure which will effectively erase all saved user data, app data, app preferences, photos, videos, music, documents and other media files from your smartphone. Make a backup at this point of all data, files and media that you wish to preserve.
Download the SDK Platform Tools from the link below and extract the contents of the archive to an empty folder on the desktop of your Windows computer
Download the ROM from the link below and extract the contents of the archive to your platform tools directory created in the previous step
Because this ROM has been modified to disable DFE force encryption, it is first necessary to format the /userdata partition. With your phone in a powered off state, press the Volume Up & Power keys simultaneously until the Moxee logo appears on your display, at which time you should release the Power key, but continue holding Volume Up until an Android logo and a corresponding No Command notification appears on your phone display. Now quickly press and hold Power, tap Volume Down and then Volume Up to enter stock recovery mode.
Use the Volume Down key to navigate to the Wipe data/factory reset option, then press Power to select. Confirm this selection on the next screen to initiate the factory data reset.
Once the factory reset is complete, navigate to the option to Enter Fastboot, then press Power to select. Your phone should now boot to FastbootD mode.
In the platform tools folder created in the first step, click on cmd-here.exe, then right click and opt to run it as an administrator. A command window will be launched. Now connect your Moxee m2160 to your Windows computer using a sufficient USB-A to USB-C data syncing/charging cable.
In order to verify proper fastboot communication between your phone and PC, execute the following command:
Code:
fastboot devices
If properly connected, the command window will yield an alphanumeric value consistent with your mobile phone serial number.
Execute the following commands once a proper fastboot connection has been verified. Note, the user may copy these commands and paste the full text to the fastboot command window for systematic execution:
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.patched.img
fastboot flash vbmeta_system vbmeta_system.patched.img
fastboot flash vbmetabak vbmetabak.patched.img
fastboot flash vbmeta_systembak vbmeta_systembak.patched.img
fastboot erase super
fastboot flash super super_rw.img
fastboot erase metadata
fastboot erase cache
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
** Please note that the super_rw.img file is large in size. Fastboot may initially give a header magic notification error. However, the super_rw.img will then be allocated into a number of smaller sparsechunk files, which will subsequently be flashed to your device one at a time, until complete. Just remain patient during this process. This can take five minutes or more, but the process will not require any user action.
Upon first reboot following installation, and after completing initial device setup, open your app drawer and search for the Magisk app or its stub placeholder. Open Magisk, grant any requested permissions, and follow any prompts by Magisk to update the version or complete setting up the root environment. If you do not see the Magisk app or stub, download the Magisk v26.1 APK from the link provided below and install the app on your phone. Be sure to then open Magisk and follow all prompts.
DOWNLOADS:
• SDK Platform Tools r34.0.3
• Modified Stock ROM Package
• Official Magisk Releases / GitHub Repo
BUGS:
Please report any bugs or instabilities you may encounter using this modified stock ROM. Those who know how to submit an official bug report are urged to do so. Otherwise, please give a concise and detailed description of the issue, including photos or screenshots if possible. I will work diligently to patch any reported bugs or instabilities.Moxee m2160 Firmware Restoration & Unbricking Guide
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
scottfan81 said:
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
Click to expand...
Click to collapse
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Update: I have disabled system updates and OTA notifications. Proved trickier than I thought, since system updates on Android Go Edition are governed by Google Play Services. I had to decompile the Google Services apk, manually disable the individual system update service and listeners, then recompile and reinstall the Google Services core app. I am presently uploading the new super_rw.img.
One thing that should work for you in the meantime, while I get these new files uploaded, is to perform another factory data reset. During initial boot and setup, opt to complete setup offline, without connecting to WiFi or a mobile data network. Accordingly, your device will not be able to check for pending system updates and you should, therefore, be able to complete setup.
Viva La Android said:
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Click to expand...
Click to collapse
That would be awesome. I really appreciate your help.
scottfan81 said:
That would be awesome. I really appreciate your help.
Click to expand...
Click to collapse
The files should be finished uploading within the next 15 minutes or so. I will then update the download link and will inform you here when that's done.
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Viva La Android said:
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Click to expand...
Click to collapse
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
scottfan81 said:
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
Click to expand...
Click to collapse
Do a factory reset beforehand. Then flash the super_rw.img
@Viva La Android
I haven't had any luck since my last post. Before I posted about the verification issue I had when setting up my phone I made sure I double checked that I did not have the option to skip the update as you suggested. That was not an option for some reason and that is when I came here. I have followed your steps with the new super.rw.img you updated but I am worse off than I was before. Now I cannot do anything as the phone is not recognizing any network or available WiFi connections. I have tried a factory reset and started over from your first step with no success. I should also include that since flashing the updated super.rw.img file, when the phone first boots the screen quickly flashes black and blue for about 10 seconds before finally starting the set up process then I get 2 error messages. The first being "system UI isn't responding" and second "Android setup keeps stopping" After all of that the setup starts and that's as far as I can go because I can't connect to anything. Trying to give you as many details I can think of. Before the screen flashing when powering on the phone, the boot animation just function properly. Only between the boot animation and setup process do I experience the rapid black and blue screen for roughly 10-15 seconds. I am including some screenshots of the error messages and setup screens showing no connections available. I almost forgot. I also tried manually adding my network and scan qr code with no success.
Unfortunately I have physically damaged my device beyond any hope of restoring it, so I won't be able to support this device any longer -- until & unless I can get a replacement display. But before my device went kaplut, I did test this ROM and had no issues. I wish I could be more help.
I would recommend performing all steps over again from the top -- formatting /userdata before doing anything. Have you tried by completing all the steps over?