Database Info

[Q] missing: Matricom Iota [tablet android 4.4.2], root /without/ Windows

While there is a less than useful thread for a similar model, Matricom Quantum, there are apparently significant differences to warrant a unique thread if not section.
Matricom shipped tablets with the prior android version, 4.2.2, already root with su and SuperUser.apk installed. Newer batches although not changing the amazon descriptors shipped with "upgraded" android 4.4.2 but no longer root from factory For those [many] users who do not have a windows license [and who are not members of the eye patch crowd] seem to have no root recourse. Those with windows are advised by the manufacturer [through interaction via amazon fba] to install kingo which is the adware flavor of malware.
Please help us root Matricom Iota [without windows]: OSX 10.9.4+ Or Ubuntu 14 LTS
16 gig NAND
1 gig RAM ddr3
Quadcore A31S 1.5+ GHz
PowerVR (not mail400 as indicated elsewhere)
IPS screen 1280x800 (over 4 devices each has had at least one hot-pixel)
twelve dozen dollars USD
10-touch capacitance
6000 maH
The product page is a bit out of sync as it suggests flashing firmware for their xbmc STB. Both their internal support forums- and obscured ticket system were of no help on this topic.
web: matricom.net/gtabiota/
Towel root: fails auto, fails in 56 manual permutations.
There are too many nuanced differences from the reference design to use Onda firmware on matricom. (it does change bootlogo, does add su, busybox and SuperUser.apk but unable to mount /system as RW leaving it seemingly root albeit non-functionally)

Need help with root or custom recovery myPhone L-Line

Hello,
I need help with rooting my new device - myPhone l-line. This is typical Chinese phone rebranded by Polish company myPhone. It runs Android 5.1 on MediaTek MT6735M with 1 gigabyte of RAM and 3000mAh battery. I tried everything: oneclickroot, Kingroot (PC and APK), Kingoroot (PC and APK), framaroot (device not supported), towelroot (not vunerable to exploit), 360root, Baiduroot, rootkhp and many other metods and my device seems to have very good security background (i am simply amazed by the way, because this device is low-budget phone, about 80$ in my country) and there is no custom recovery to download. I have Oneplus 2 (previously Oneplus One and Nexus 5) phone as my second device and i am really into changing ROMs, recoveries, rooting and modding Android, but i don't know how to crack this myPhone. If there is no option to root this device, i will be very grateful if someone can tell me how can i remove bloatware without root, because this fone is full of uneccessary aplications, which occupy memory and slow down the phone. This is the only reason i want to root this smartphone. Please help me with rooting or if someone know how to compile custom recovery for this phone, i will be very grateful if someone could post it here, i will probably know how to change stock recovery in this phone to custom one (this device seems to have unlockable bootloader, thus i think that custom recovery can be sent to phone via fastboot). Thank You very much for any help and please forgive me if i make any mistake in this post, English is not my mother language. Below You can find full specs of this phone:
Processor: MediaTek MT6735M
Screen: 480 x 854 px (4,50")
RAM: 1GB
Internal memory: 8GB + microSD support
Dual SIM
Rear camera/front-facing camera: 5MPix/2MPix
LTE baseband support: 800, 1800, 2100 MHz
OS: Android 5.1 Lollipop
version of the baseband: MOLY.LR9.W1444.MD.LWTG.MP.V8.P28,2016/01/05 20:21
kernel: 3.10.65+ [email protected] #1, Tue Jan 5 20:31:51 CST 2016
complilation: L-Line_PL_V1.0.9
Android security patch: 2015-11-01
EDIT: I already unlocked bootloader, then i get scatter and stock recovery.img. If these files are needed to compile custom recovery or to get root access - feel free to PM me, because i can't post external links, but still i can send You these files via e-mail.
Cheers

UMIDIGI S3 Pro

New UMIDIGI S3 Pro
New thread for the new model UMIDIGI S3 Pro Helio P70 Octa core Mtk 6772
Umidigi S3 PRO MT6772 Octa Core 4G LTE 802.11ac 6GB 128GB Android 9 Smartphone 6,3 inches
{
"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"
}
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

Specification
Basic Information
Brand: UMIDIGI
Language: Multi language
OS: Android 9 Pie
Provide Services: Unlocked
SIM Slot cards: Standby Dual
SIM Card Type: Double Nano SIM
to Sciarba type: 4G Mobile
Hardware
CPU: Helio P70
Cores: 2.1GHz, Octa Core
External Memory: TF card up to 256 GB (not included)
RAM: 6GB of RAM
ROM: 128GB
Network
2G: GSM 1800MHz, GSM 1900MHz, GSM 850MHz, GSM 900MHz
3G: UMTS (WCDMA) / HSPA + / DC-HSDPA: BAND1 / 2/4/5/6/ 8/19
Network Type: FDD-LTE, TDD-LTE , WCDMA
WI-FI: WiFi 2.4G / 5G, 802.11a / b / g / n / ac Wi-Fi
wireless Connectivity: 3G, 4G, Bluetooth, GPS, WiFi, GSM, 2.4GHz / 5GHz WiFi, A-GPS , WiFi Dual Band
4G LTE: B28a / B28b, FDD B1 2100MHz, FDD B13, FDD B17 700MHz, FDD B2 1900MHz, FDD B20 800MHz, FDD B3 1800MHz, FDD B4 1700MHz, FDD B5 850MHz, FDD B7 2600MHz, FDD B8 900MHz, TDD B38 2600MHz, TDD B39 1900MHz, 2300MHz TDD B40, B41 TDD 2500MHz
Screen
The Screen resolution: 2340 x 1080
the Screen Size: 6.3 inches
Screen Type: Capacitive
Camera
Auto Focus: Yes
Retro camera: 48.0MP 12.0MP +
Functions Camera: Beauty face, face recognition
of Camera Type: Cameras Triple
Flashlight: Yes
Camera Front: 20.0MP
Fire Touch: Yes
Video recording: Yes
Multimedia Formats
Live Wallpaper Support: Yes
MS Official format: Excel, PPT, Word
Music Format: MP3, AAC, AMR-NB, AMR-WB, APE, WAV
Picture Format: BMP, GIF, JPEG, JPG, PNG
Video format: MP4, H .264, MPEG4
Other characteristics
Additional Features: Alarm, Browser, Calculator, Calendar, Camera, E-book, fingerprint recognition, fingerprint release, Gravity sensing, Gravity Sensor System, light sensor, Light sensor system, MMS, Notification, proximity Sensor, Sound Recorder, Video Calling
Bluetooth version: Bluetooth V4.2
Google Play Store: yes
I / O Interface: 1 x Nano SIM card slot, 3.5mm audio output port, Microphone, Card Slot Nano SIM / TF Speaker, Type-C
Sensor: Accelerometer, E-Compass, geomagnetic sensor, gravity sensor, gyroscope sensor proximity
Sound Recorder: yes
Battery
Battery capacity (mAh): Built-in 5150mAh
Package Contents
Back: 1
Phone: 1
Charger: 1
SIM Needle: 1
USB cable: 1
Dimensions and weight
Package Size: 18.50 x 18.50 x 4.20 cm / 7.28 x 7.28 x 1.65 inches
Weight Package: 0.5840 kg
Product Size: 15.70 x 7.50 x 0 85 cm / 6.18 x 2.95 x 0.33 inch
Weight of Product: 0.2170 kg​

Recovery modded +
How to receive Right Root in this new Device S3PRO From UMIDIGI Brand
This Thread is not for beginners and all the steps made will be down the warrancy at own risk.
This tutorial will guide you through the process of installing a custom recovery image
on your MediaTek based UMIDIGI smartphone and to receive right root access.
Some possible issues that might need your attention:
Custom recovery images of different Android versions are not always interchangeable. For example, you can't install an Android 5.0 recovery on a 4.4 system and so on. Any exceptions are mentioned in the list of recovery images.
At most of the devices, after flashing the TWRP image, first you have to boot into recovery (TWRP) or the stock recovery will be restored.
At some devices, after flashing TWRP, first you have to root your phone (install SuperSU or Magisk) or it won't be able to boot into the system.
Once you've rooted your device, you won't be able to install OTA updates anymore but the only way to update your phone is flashing with SP Flash Tool. Flashing a stock ROM (with the stock recovery) will make you able to install OTA updates again.
At some devices (or specific ROM versions), when powering on your phone to boot into TWRP (power + vol-up), after about 3 seconds, you have to release the power button (even if your screen is still black) and keep only the vol-up button pressed until the TWRP welcome screen pops up or the recovery will be skipped and your phone will boot into the system.
What you need:
Driver for Preloader USB VCOM mode:
Windows 10 already can automatically install it or you can use this:
MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe
SP Flash Tool application:
SP_Flash_Tool_v5.1904
Adb Command for Windows pc:
Command adb for dos/windows
A custom recovery image that fits your phone
Twrp By material Design test 1:
Scatter + Recovery twrp
Twrp By material Design test 2:
https://www.mediafire.com/file/r486...wrp_323_Mat_Des__UmidigiS3_Pro_test2.rar/file
New Twrp 3.3.1 test 1:
http://www.mediafire.com/file/kajeg9bbcb0kb55/recovery-twrp-3.3.1_Umidigi_S3_Pro_Test1.rar/file
Procedure to how to flash the Recovery into Umidigi S3 Pro
Now is not possible to flash the recovery throught flashtool because there is a bootloader locked so we must go ahead with adb command.
1) download all the previous files;
2) in Android S3 Pro in "Settings System details" enter in about phone ot make visible the developer options click several times on about phone ....
3) in Setting System will be now shown the developer menu' enter and switch to visible OEM unlocking allow the bootloader to be unlocked.
4) in Setting System --> the developer menu' --->debug usb activated and connected the usb cable to the phone and the other side to the pc...
5) Now in windows pc run the commad cmd or open a ms-dos window and enter in the adb2 folder
(adb folder when you extraced the adb command and check with adb command);
Type: adb devices .....if the device is recognized type: adb reboot bootloader
6) SEEMS NOT RUN THIS STEP IN THIS DEVICE
(reboot the phone and with power menu' and volume + in the same time enter in booting menu'.......select fastboot mode.)
7) do not remove the usb cable.....now you entered in Fastboot menu...
write the command fastboot devices...and the phone connected with the usb cable must answer the command that is connected..
8) use the command
fastboot oem unlock
o
Fastboot flashing unlock
and wait checking the device screen.....
9) copy with windows command the recovery twrp.img in the adb folder and renamed it with recovery.img
to flash in the phone use this command : Fastboot flash flash recovery recovery.img
the process will start ...and wait it...
10) make this command to reboot into recovery mode: fastboot reboot.
11) now take the buttons pushed with power menu' + volume + and select recovery mode....
12) in recovery mode will show probably russian language...skip the alert with the arrow back and enter in details menu' on the right top to change the language...
NOW NOT REBOOT INTO ANDROID SYSTEM WITHOUT MAKE THE ROOT STEPS
because the android system protection will flash automatically the recovery original and all of you will lost the recovery twrp flashed before
and all of you will repeit all the preious steps again
How to Root your Umidigi S3 Pro
How to Root:
Enter in the Recovery mode.....
You need to FORMAT the partition given TWICE a simple deletion is not enough it seems in Android 7 and upper.
Follow this procedure in this exact order and should solve most problems.
1. Install TWRP through flashtool or adb command and then directly restore in recovery (twrp) do not enter in android system under penalty of twrp deletion and restoration of the original recovery.
2. Select Wipe / Advanced / select date Yes to confirm. When finished, choose Restart, then always in recovery.
3. Choose Wipe Advanced Format DATA again type Yes to confirm When it ends choose Restart always in recovery.
4. Select Wipe and select cache and Dalvik scroll to confirm When it finishes choose Restart and always in Recovery.
5. Now install Magisk 17.1 use this version tested
Magisk 17.1 (Tested)
you can restart in the android system and you will find magisk installed.
For a full root you have to install from the play store busybox app and install the busybox binaries at least in sbin and bin (system folders) the app will guide you
Busybox see here:
Busybox in the google playstore
I prefer this app to others because of its track automation that doesn't require much experience.
@Everybody
the custom recovery twrp test1 is already in testng phase..................... ​

This could be best in class for the price ($279.99 on sale). What's the developer community like for Umidigi? Is bootloader normally unlockable etc? Very tempting compared to Redmi Note 7 Pro

Just purchased one, well soon see how good.

any word on root?

THANK YOU
Woooo-hooooooo! got me one ordered....
I cannot wait to see That you guys (and ladies) have
in store for this phone. hopefully as many goodies as you have for galaxy s5
-----and,......thank you ALL for all of that, by the way.....you guys are
:good::good: !!!AWESOME!!!:good::good:

Don't get your hopes up... there is no root for the S2 Pro still. I read something about efuse protection but unconfirmed.
Hoping a dev will try to root this S3 Pro
...and that UmiDigi learned from their previous mistakes and deliver a great phone with no camera/battery/charge-port issues, that is really running Pie.
It is a big gamble, but one I was willing to make for $289.
BOUNTY: If a Dev does make a way to root my S3 Pro, I will send them a free S2 (lightly used, doesn't always charge but does sometimes, and always works when plugged in). -lol, if they want it.
(Bounty not valid if it turns out the phone is easily rooted using available tools)

Hi, yes when the device will arrive in my hands i will continue to make a review and i will open a specific detailed thread about how to receive right root and others mods on it!

Can't wait for my Umidigi S3 Pro that is due to arrive in 1-2 weeks.
Generally, do you guys know what is Mediatek devices development like? Any hope for the P70 processor to get some custom ROMs?
Sent from my Lenovo P2a42 using Tapatalk

stazz83 said:
Can't wait for my Umidigi S3 Pro that is due to arrive in 1-2 weeks.
Generally, do you guys know what is Mediatek devices development like? Any hope for the P70 processor to get some custom ROMs?
Click to expand...
Click to collapse
Is too early to speak about the custom rom... This device is not arrived to anyone and no one firmware is pubblished yet!

Yeah, true, but my question is about Mediatek devices development in general. What could we hope for?
Sent from my Lenovo P2a42 using Tapatalk

Project treble
ghost45 said:
Is too early to speak about the custom rom... This device is not arrived to anyone and no one firmware is pubblished yet!
Click to expand...
Click to collapse
Will treble project be possible on this device?

totmakina said:
Will treble project be possible on this device?
Click to expand...
Click to collapse
Probably yes when it will arrive in my hands..

ghost45 said:
Probably yes when it will arrive in my hands..
Click to expand...
Click to collapse
Thanks. The S3 pro will be an excellent mobile. With twrp already impressive !!

I don't know guys... I'm worried about this phone and the camera app. Do you have any informations about slow motion video and night mode photography? For this Sony sensor and this processor should be super easy...
But te umidigi team is really small and I'm worried that they don't know how to use potential of this Sony camera sensor and mediatek processor.
I hope I can install GCAM or openCamera
I see they have huge problem to sent s3 pro to indigogo customers but what about aliexpress customers...? How long we have to wait for it?

The twrp is pubblished in official forum... I will update also this thread.. I need a period of test phase....

Good Notice! TWRP!!
ghost45 said:
The twrp is pubblished in official forum... I will update also this thread.. I need a period of test phase....
Click to expand...
Click to collapse
Hello Ghost! I already saw the publication of your post in the official forum. Now download the twrp and also download the official rom to have it in reserve.
Hopy bought the s3 pro. I just hoped that the official rom would come out to carry a twrp that already had realme u1 if no one did it. But luckily you posted one that will be installed when I get the smartphone. When I arrive, you can count on me for any help. It would be nice to have treble for this team. We trust you !!

Hi
Just received this phone, do you know if xda will open a new dedicated forum?
Thx

cy-rock said:
Hi
Just received this phone, do you know if xda will open a new dedicated forum?
Thx
Click to expand...
Click to collapse
How long did it take to receive it, my friend? I asked for it yesterday and I already want to have it in the. Hands

[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
{
"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!!

root successes ? ALLDOCUBE iPlay 50 or a Blackview Tab15

Curious if anyone has any experience good or bad about rooting these two tablets, if you have I'd love the method!
I haven't seen any methods, conversations, twrp for the iPlay 50 or the Blackview Tab15.
I understand these are not mainstream tablets and won't receive mainstream attention however I can always hope. A tablet like this suits my wanted specs and budget.
thanks

If the Linux kernel of both tablets mentioned is version 5.10 or higher then you can root via KernelSU: KernelSU is working in Linux kernel mode, it has more control over userspace applications. Only App that is granted root permission can access `su`, other apps cannot perceive su. KernelSU supports.
See also here:
KernelSU reborn: Developer ports kernel-assisted root access to GKI compatible devices
A Magisk successor at last?
www.xda-developers.com

Very interesting. I'll research and post an update.
In downloading a terminal emulator and using the command uname -a I've got the following.
ALLDOCUBE iPlay 50​5.4.161​​Blackview Tab15​4.19.191
ah well

I've looked and found a reference to an earlier tablet model an iPlay 40 where they say " you can use magsik app to modify the factory boot.img ,and flash patched boot.img ".
I'll take a look at this.

didn't have much luck. it seems these tablets are locked in not a conventional way. best to leave as is unfortunately.

Up

mountainsnow said:
these tablets are locked in not a conventional way
Click to expand...
Click to collapse
Did you try this method for unlock?
Meberry M7 - Unisoc Tiger T310 - Root, TWRP, +Info, etc.
Little review and tablet issues: This is a 2020 Tablet, that was launched with Android 11, and the last security patch was December 2021. Hardware It packs an UNISOC Tiger T310, basically 1 ARM A75 and 3 A55 4 GB RAM and 64 GB ROM Build...
forum.xda-developers.com
-------------------
Drivers for windows
SP_Drivers_EXE_v2.0.zip
drive.google.com
-----------------------------
Unlocking Unisoc Bootloader on linux​1) fastboot oem get_identifier_token
2) ./signidentifier_unlockbootloader.sh 303132333435363038394142434????6 rsa4096_vbmeta.pem signature.bin
where 303132333435363038394142434????6 is identifier_token , rsa4096_vbmeta.pem is a private key of Unisoc
3) fastboot flashing unlock_bootloader signature.bin

I ended up just returning the tablet and grabbing something else. I no longer have this model to test unforunately.