ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD; OTG USB support)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As to the filesystem of this device, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).
Oh hell yea !!!
MotoJunkie01 said:
ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As for the partition index/filesystem, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).
Click to expand...
Click to collapse
OK I don't Have the Device Yet...
BUT I am here and Team_Astr4y4L's Got your back!
Brother If you need anything from us over here you just name it and we're on it !!
Attention XDA Take notice; you have in your presence the Koolest Tower-climbing Rom developer I know !! If it can be done @MotoJunkie01 with the help of his Friends will make it reality !!!
@MotoJunkie01 Brother we will be watching this closely...
you know how we feel Over here about Big-Red ... LOL
Astr4y4L
Team_Astr4y4L
As always, your continued support and assistance are beyond value. By the way, you may know the answer to this. I have a new BLU Studio M4 with a Spreadtrum sp7731 processor. I'm having trouble finding proper USB drivers for my Windows 10 PC. Are you familiar with this chipset?
MotoJunkie01 said:
As always, your continued support and assistance are beyond value. By the way, you may know the answer to this. I have a new BLU Studio M4 with a Spreadtrum sp7731 processor. I'm having trouble finding proper USB drivers for my Windows 10 PC. Are you familiar with this chipset?
Click to expand...
Click to collapse
you can try to follow this Here
https://forum.hovatek.com/thread-827.html
it deals with
[Tutorial] How to manually install Spreadtrum USB drivers on a Windows PC
wow copy past was kinda size-crazy there ...LOL
but it's dated Oct 2013
but again,
it references in first paragraph
Disable driver signature verification enforcement if using a Windows 7, 8, 8.1 or 10 PC (see https://forum.hovatek.com/thread-752.html )
SO maybe this will work for you Bro.
IDK not familiar with the platform personally but I do Know
WINDOWS-BLOW's ..
noticed that it's also used in several of the newer Samsung devices also...
Astr4y4L said:
you can try to follow this Here
https://forum.hovatek.com/thread-827.html
it deals with
[Tutorial] How to manually install Spreadtrum USB drivers on a Windows PC
wow copy past was kinda size-crazy there ...LOL
but it's dated Oct 2013
but again,
it references in first paragraph
Disable driver signature verification enforcement if using a Windows 7, 8, 8.1 or 10 PC (see https://forum.hovatek.com/thread-752.html )
SO maybe this will work for you Bro.
IDK not familiar with the platform personally but I do Know
WINDOWS-BLOW's ..
noticed that it's also used in several of the newer Samsung devices also...
Click to expand...
Click to collapse
Thank you. Yes that did work. Disabling kernel signing was necessary on my Windows 10 (64 bit) setup first.
Well I tried.
Okies so I did actually try to unlock the bootloader. I plugged it in then used the
Code:
adb devices
command, it showed up so then after trying
Code:
adb reboot bootloader
it just booted regularly. So I decided to use
Code:
adb reboot recovery
, it went into recovery mode. But when I tried
Code:
fastboot devices
nothing happened. I then tried to put it in to bootloader mode using the key combo and still
Code:
fastboot devices
did not do anything so this leads me to believe that for some reason the fastboot command doesn't recognise that there is anything attached. Not sure where to go from there, so I am calling it a night for now. I will likely try again sometime tomorrow or the next day as I have them off. Good luck to anyone who tries after this post.
Ubervillin said:
Okies so I did actually try to unlock the bootloader. I plugged it in then used the command, it showed up so then after trying it just booted regularly. So I decided to use , it went into recovery mode. But when I tried nothing happened. I then tried to put it in to bootloader mode using the key combo and still did not do anything so this leads me to believe that for some reason the fastboot command doesn't recognise that there is anything attached. Not sure where to go from there, so I am calling it a night for now. I will likely try again sometime tomorrow or the next day as I have them off. Good luck to anyone who tries after this post.
Click to expand...
Click to collapse
Yeah, just like LG, ZTE oftentimes disables fastboot mode on their devices, making it all the more difficult -- if not nearly impossible -- to unlock the bootloader or achieve systemless root. If I can find stock firmware for the Z839, I will try to reverse engineer the boot chain, and try to find a workaround to get into fastboot.
Hello I have the ZTE Blade Vantage (z839) and when I click activate account on Message+ it says please wait starting service for like a second and goes off. It never activates. Please help
Hey @MotoJunkie01,
Any more news on this device?
Team Astr4y4L's looking at it again.
I'm doing Gofer Work.
@MotoJunkie01
How far is the development going on for this device and also does any know how to root this device?
from what I can tell Root will require some sort of exploit to unlock the bootloader.
it's msm8909 so there may be a firehose file for another zte msm8909 device and that may let us play with QFIL and QXDM.
I am digging everywhere trying to just find a stock firmware file for it. and coming up empty
George_Jetson said:
from what I can tell Root will require some sort of exploit to unlock the bootloader.
it's msm8909 so there may be a firehose file for another zte msm8909 device and that may let us play with QFIL and QXDM.
I am digging everywhere trying to just find a stock firmware file for it. and coming up empty
Click to expand...
Click to collapse
Yeah, due to its locked down bootloader and lack of factory images, development has failed to get off the ground for this device. Shame too, it has great specs for a budget smartphone. I'm pretty sure there are some available firehose files for the Qualcomm chipset. I had the same thoughts. If the stock boot image could be patched for systemless root, there is a chance we could push the patched boot image with QFIL. But where to get stock images is the key.
Hi, ZTE BLADE VANTAGE only comes w/ LTE Mobile Network Settings. I'd like to know if it's going to be posible in the future to change this option to Global Setting (and how?) so it could be use internationally. Thanks..
MotoJunkie01 said:
ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD; OTG USB support)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As to the filesystem of this device, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).
Click to expand...
Click to collapse
Here is the B20 firmware package (Z839V1.0.0B20) it also includes the firehose for this device allowing you to use QPST/MiFlash to restore your device or to flash custom boot.img's among other things.
https://www.androidfilehost.com/?fid=1395089523397895595
Separate download with just the firehose, rawprogram0.xml, patch0.xml
https://www.androidfilehost.com/?fid=1395089523397895596
I have also uploaded a few other tidbits that aren't super useful but maybe will help someone down the line:
Verizon Repair APN tool (Could be useful if you break something)
https://www.androidfilehost.com/?fid=1395089523397895588
ZPST for the ZTE MultiDL Tool (Not useful unless you have the ZTE MultiDL Tool)
FRP/Kill Switch Reset tool (Requires License file so not useful)
https://www.androidfilehost.com/?fid=1395089523397895587
Any updates on this device?
It's been a while since this device has come out, and now we have more available files for it. Is anyone interested in looking into maybe rooting this device?
Would be super awesome if someone could root it!! If I was any better at this I would give it a shot but I am not there yet lol!
When I power on my zte z839 am stuck on bootloop,and even when I plug my charger my phone powers on and sticks on bootloop. I need a solution pals. Moseti(Kenya).
Hey everyone. It seems that there is now a bootloader unlock for this device. Anyone want to look into this?
https://forum.xda-developers.com/android/software/bootloader-unlocking-qualcomm-zte-t4100897
still no easy way to root this device? or any successful way?
Hey everybody! Thanks for your help in advance. I also have the ZTE Z839 and I want to use it with a carrier other than verison when I try to unlock the phone, it asks for a verification code. I got the code from cx service however it said incorrect code. The cx rep. had only 1 code and it didnt work! then he simply said either I can get verison service or the phone is incapable of using on other networks......... Duh why would there be a option in settings to use with different carrier and ask for a code if it is incapable? I tried tech support also to no avil. Ive spent hours on hold with cx and have troubleshot in every way I know how. Can anybody confirm if this is even possible or not and what is the code or should I just give up?
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!!