Database Info

Elephone P6000 Pro MTK6753 Information Thread: Root, Recovery, ROMS and more

General information - P6000 Pro 2gb / 3gb
This is a great mid range phone, and packs the performance of larger devices such as the P8000 into a smaller profile. Ideal if you want a responsive device, but don't want the phablet bulge in your trousers.
Important:
This thread is for the P6000 Pro - not the P6000. That's a separate (older) model.
{
"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"
}
Specification:
Dimensions: 144.5 * 71.6 * 8.9mm
Weight: 165g (with battery)
CPU: MediaTek MTK6753
GPU: ARM MALI-T720
RAM: 2GB / 3GB versions
Storage: 16GB ROM
Display: LG, 5.0" 1280*720 pixels
Battery: 2700 mAh
OS: Android 5.1 stock
Camera: Samsung rear-13MP, front-2.0MP
SIM card: Dual Micro SIM card,dual standby
Wi-Fi: 802.11n wireless
USB: 2.0 Micro USB
Bluetooth: 4.0
Positioning: GPS, A-GPS
Launch date: July 2015
Official Website:
http://www.elephone.hk/P6000-Pro-3gb.html
http://www.elephone.hk/P6000-Pro-2gb.html
http://bbs.elephone.hk/forum.php?gid=283#.VghRY_lVhBc (forum)
Reviews:
1. http://bbs.elephone.hk/thread-7585-1-1.html#.Viae_fmrS70 [Credit: @megthebest]
2. [Credit: @megthebest]
3.
4.
Hardware teardown:
http://www.gizmochina.com/2015/07/30/teardown-of-elephone-p6000-pro-3gb-version/

Root Information
Rooting is the process of allowing users of smartphones, tablets and other devices running the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems.
The P6000 Pro's stock firmware is rooted as shipped, and does not require any hacks to activate it. Just install Chainfire's SuperSU from the Google Play store:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en_GB

Custom Recovery Information
Philz 6 recovery:
- This version includes modified kernel with working Touch screen. SD Card also supported:
http://forum.xda-developers.com/showpost.php?p=64038183&postcount=52 Credit: @lion567
- No touch:
http://4pda.ru/forum/index.php?showtopic=686517&st=100#entry43546180 (Release thread)
https://yadi.sk/d/HZfsB0nZjbkhJ (Download link)
CWM Custom Recovery:
- No touch or SD card support
CWM can apply software changes to the device. Unlike the stock recovery, CWM is able to entirely replace the device's primary Android operating system ("flashing a new ROM").
An unofficial version of ClockwordMod (CWM) Custom Recovery has been released by for the P6000 Pro:
http://www.needrom.com/download/cwm-carliv-6-from-hypoturtle/
Credit: @HypoTurtle, @yuweng and @carliv
Installation:
1. Install SuperSU from Google Play store
2. Install Flashify from Google Play store
3. Flash the downloaded file (CWM-P6000Pro-recovery.img) with Flashify app (Grant root rights with SuperSU when requested)
Accessing Recovery once installed:
Method 1:
1. Turn your phone off
2. Push and hold Vol Up and Power buttons together until a menu appears. It takes about 3 seconds. You should have the following options:
[Recovery mode]
[Fastboot mode]
[Normal mode]
Use the Vol Up button to scroll through the menu options, and press Vol Down to select.
Method 2:
Choose the option 'Reboot to recovery' from within Flashify

Android Development
ROM Reading / Writing with SP Flash Tool:
Smartphone Flash Tool (SP Flash Tool) is a Windows application for reading and writing to MediaTek SOC powered devices.
To read or write to a specific device, you need a 'scatter file' for the correct type of CPU. The scatter file defines the memory ranges within the chip. P6000 Pro uses the MediaTek MT6753 SOC:
http://androidurdu.net/mediatek-scatter-files-download/
Instructions to read back from SP Flashtool:
1. Load the Scatter file (download from above)
2. Select the 'Readback' tab, press 'Add' to add a range
3. Double click on the row that appears in the table. Type a filename to save this memory range to (Eg. recovery.img if you're reading the recovery memory area)
4. Enter the start address and length of the section you are reading back - copy them from the scatter file.
3. Push 'Read Back' button
4. Remove the battery from the phone
5. Connect the phone to USB. No need to power it on. It will connect and commence reading. The recovery memory range took about 3 seconds to read back.
6. It will say 'Readback OK' and you will now have a img file from that memory range.
Available ROMs:
Stock Android 5.1 20150910:
http://bbs.elephone.hk/thread-7986-1-1.html#.VghUSflVhBc
https://mega.nz/#!ghgSHQCL!xxvBWtgCQsaXe2I7yOBxIl5w5SV2hpfFRtefAEmWxPU
Stock Android 5.1 20151031:
http://bbs.elephone.hk/thread-9362-1-1.html#.Vl9bd_nhC70
https://mega.nz/#!M5YFWRiC!pYiql0Q556CmFyB0t8XRUxgTxMe-LW1pfSfuqUxEYvY
FlyME 4.5.3a:
http://bbs.elephone.hk/thread-7380-1-1.html#.VghUevlVhBc
https://mega.nz/#!z8NRAKyS!BkQQc44aTciy9vuT-d4-kWnyr8pnHkI595U7nEfXMGU (26.08.2015)
DCU v12.1 (AOSP):
http://bbs.elephone.hk/thread-8759-1-1.html
http://4pda.ru/forum/index.php?showtopic=686517
https://yadi.sk/d/637BNhDQjdwtr (09.10.2015)
https://yadi.sk/d/ylE2JKN5jroQN (20.10.2015)
Eragon 5.1 Lollipop (AOSP):
http://forum.xda-developers.com/android/development/rom-18-11-eragon-v1-0-p6000-pro-android-t3251881 (Credit: @skeleton1911)
IUNI OS Android 5.1.1:
http://4pda.ru/forum/lofiversion/index.php?t686517-320.html (release thread)
https://yadi.sk/d/UGEdEkb2jutMp (22.10.2015)
Upcoming ROMS:
Elephone have announced Android 6.0 Marshmallow will be released for the P6000 Pro:
http://www.elephone.hk/readnews/8160.html
Custom Kernel:
[Kernel][1.5 Ghz] visi0nary's kernel for P6000 Pro credit: @BlueFlame4
Stagefright Patch:
The stock ROM is vulnerable to Stagefright CVE-2015-6602 and CVE-2015-3864. A patch is available:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219 Credit: @superdragonpt
Note: Modification to the loader script or manual installation via ADB required, due to the P6000 Pro using different partition names. A modified version by @ahorntaler is available on needrom but may not be the latest version.
Source Code:
Elephone have released via Github the source code for the P8000, which shares the same CPU (MTK6753) and GPU (ARM MALI-T720) as the Elephone P6000 Pro:
https://github.com/elephone-dev/P8000-Kernel
Discussion: http://forum.xda-developers.com/ele...el-elephone-p8000-kernel-source-code-t3163314
Compiled P8000 kernel: http://forum.xda-developers.com/elephone-p8000/orig-development/kernel-visi0narys-kernel-t3226081 Credit: @BlueFlame4

Other Guides
Engineering Mode:
Use the secret menu carefully.. if you don't know what you are doing... don't do it!!
On the stock 5.1 ROM, you can access P6000 Pro Engineering mode with the following code entered on the dialer: *#*#3646633#*#*
Note: This is the same as P6000.
If you are not running the stock 5.1 ROM, you can download MTK Engineering Mode from the Google Play store.
It has the available menus:
Telephony
Connectivity
Hardware Testing
Location
Log and Debugging
Others
Manual IMEI Programming:
If you experience "can't detect SIM cards" or "can't make a phone call" error messages, you should check your IMEI code hasn't been accidentally overwritten. If your IMEI codes are not valid as can happen after flashing an image, please go through the following tutorial to reprogram your original IMEI. Your original IMEI numbers are printed on the label under the battery.
1. Enter Engineering Mode (as above)
2. Click on "CONNECTIVITY"
3. Click on "CDS INFORMATION"
4. click on "RADIO INFORMATION"
5. then to "PHONE 1" for the 1st IMEI, and write in:
AT +EGMR=1,7,"00000000000" (Replace the "zeros" with your own IMEI No.)
6. Press 'SEND AT COMMAND'
7. "PHONE 2" for the 2nd IMEI and write in:
AT +EGMR=1,10,"0000000000" (Replace the "zeros" with your own IMEI No.)
8. Press 'SEND AT COMMAND'
IMPORTANT: All typing on keyboard
Demo:
Other IMEI tools:
MTKdroid Tools 2.5.3d does not support MTK6753.
Chamelephon does not support MTK6753 (Appears to work, but corrupts the IMEI)

Reserved for future use
Reserved for future use
To be updated

Can you add how save and restore imei ?

Krystyna said:
Can you add how save and restore imei ?
Click to expand...
Click to collapse
Good idea.
Do you have P6000 Pro? I think MTKdroid Tools would work, but I didn't try it. (see here: http://androidxda.com/backup-and-restore-imei-nvram)
Do you have any confirmation or alternative method?

blahmartinblah said:
Good idea.
Do you have P6000 Pro? I think MTKdroid Tools would work, but I didn't try it. (see here: http://androidxda.com/backup-and-restore-imei-nvram)
Do you have any confirmation or alternative method?
Click to expand...
Click to collapse
I tried MTKdroid Tools 2.5.3.d tonight on my P6000 Pro. It doesn't support NVRAM download/restore from MTK6753.
So I think manual programming of the IMEI through the Engineering Mode is the only option at present. I have confirmed it is working fine.
The IMEI are printed under the battery, so no real need to "back up".

Updated with links to DCU v12.1 ROM.

blahmartinblah said:
Stagefright Patch:
http://www.needrom.com/download/stagefright-patch-p6000-pro-2/ (for Stock ROM Android 5.1 20150910. Credit: @superdragonpt and @ahorntaler)
Click to expand...
Click to collapse
Who tha hell is ahorntaler?
The patch was compiled by me ...
And why are you linking to that stupid website?
Stagefright patch for some Mediatek devices is here at xda:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219

superdragonpt said:
Who tha hell is ahorntaler?
The patch was compiled by me ...
And why are you linking to that stupid website?
Stagefright patch for some Mediatek devices is here at xda:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219
Click to expand...
Click to collapse
Thanks for stopping by, and for your original work on the Stagefright patches.
I guess with a little reading, you could see that @ahorntaler is someone who modified your works to suit the Elephone P6000 Pro, and gave you credit. Out of the box, the patch doesn't work. (See post 63163952) I also prefer hosting files on xda to needrom, but mirroring the authors work would have been equally bad IMO. We all appreciate your work You seem disgruntled, which I didn't intend to cause. Can I amend the post in some way that remains useful to P6000 Pro owners, but still makes you happy?

blahmartinblah said:
Thanks for stopping by, and for your original work on the Stagefright patches.
I guess with a little reading, you could see that @ahorntaler is someone who modified your works to suit the Elephone P6000 Pro, and gave you credit. Out of the box, the patch doesn't work. (See post 63163952) I also prefer hosting files on xda to needrom, but mirroring the authors work would have been equally bad IMO. We all appreciate your work You seem disgruntled, which I didn't intend to cause. Can I amend the post in some way that remains useful to P6000 Pro owners, but still makes you happy?
Click to expand...
Click to collapse
Modified what?
It's very well explained, the partition stuff in my thread ...
Quote from my op:
For other devices that don't use the mmcblk0p17 as /system partition:
The flash may fail, if that's your case, simply extract all the files, and push via adb to your device.
Click to expand...
Click to collapse
I need to update the stagefright thread with a new build btw... there's new stagefright bugs around (they are fixed on our Lp build, i need to update the thread for other devices ...)
ps: No im not pissed, i just didn't know who that guy is/was
Ps2: Nothing against you, i just really hate needrom these days,,, all the KANGers are posting "their work" there.
cheers

superdragonpt said:
Modified what?
Did he compiled the libs by any chance?
Click to expand...
Click to collapse
No lib changes judging by the file time stamps. I believe the modifications are to the updater-script, to include the correct paths.
Flashing this modified update is a lot more convenient for newbies like me
He also retains your credits in the updater script.
In the future, I agree it's better to link to your thread like you suggest, and I'll include instructions on how to modify the updater-script. That way we P6000 Pro users can benefit from future updates to the patch you release.

superdragonpt said:
Modified what?
Did he compiled the libs by any chance?
It's very well explained, the partition stuff in my thread ...
Quote from my op:
I need to update the stagefright thread with a new build btw... there's new stagefright bugs around (they are fixed on our Lp build, i need to update the thread for other devices ...)
ps: No im not pissed, i just didn't know who that guy is/was
cheers
Click to expand...
Click to collapse
Hi superdragonpt,
I'm very sorry that You are disappointed. I don't want any credit for the patch. I only modified installation script to make it useable for P6000 Pro users and I wrote that the patch is not my work, but Yours. So why are You pissed? I'm only a simple user who wanted to share the benefit of Your work with others. I don't (want to) earn any Money with programming. Next time I ask You. The question is: why didn't you modify installation script? Credit would have been Yours. I wanted to be You only help.

ahorntaler said:
Hi superdragonpt,
I'm very sorry that You are disappointed. I don't want any credit for the patch. I only modified installation script to make it useable for P6000 Pro users and I wrote that the patch is not my work, but Yours. So why are You pissed? I'm only a simple user who wanted to share the benefit of Your work with others. I don't (want to) earn any Money with programming. Next time I ask You. The question is: why didn't you modify installation script? Credit would have been Yours. I wanted to be You only help.
Click to expand...
Click to collapse
It's nothing against you...
i thought it was some "random guy" from needrom ...
(im a bit pissed with needrom in general...)
PS: Tell me something guys, your latest official rom is Lollipop v 5.0 or 5.1 ?
PS2: Re-Download the latest stagefright app from Zimpherium to check what are new bugs...
I need to release a new build for other MTK phones (yours included)
Cheers

superdragonpt said:
PS: Tell me something guys, your latest official rom is Lollipop v 5.0 or 5.1 ?
Click to expand...
Click to collapse
:good:
P6000 Pro stock ROM is Lollipop 5.1.

What ROM ?!!
i Have just bought a P6000 pro , the battery lasts about 7 hours what rom should i flash to improve battery life?
Thanks in advance.

blahmartinblah said:
:good:
P6000 Pro stock ROM is Lollipop 5.1.
Click to expand...
Click to collapse
Can you give me the build ID?
(check under build.prop), i may need to make some small corrections for the stagefright, depending on the android build
cheers

superdragonpt said:
Can you give me the build ID?
(check under build.prop), i may need to make some small corrections for the stagefright, depending on the android build
Click to expand...
Click to collapse
From build.prop on the Elephone P6000 Pro 20150821 stock ROM:
Code:
ro.build.id=LMY47D
ro.build.display.id=ALPS.L1.MP3.V2_NB6753.65U.L1_P22
ro.build.version.incremental=1440142279
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1

[GUIDE][TWRP][ROOT] Oukitel C4 TWRP (by Jemmini) & (systemless) Root

DISCLAIMER: all operations descripted here should be done *only* by trained & expert guys... as every "hacking" operations, they involve the risk of soft/hard bricking your device making it unusable temporary or permanently. I will not be responsable in any way for it. So, pay attention and, if not sure, simply don't do it.
WARNING #1: this is a fast guide describing needed steps and providing needed files only for expert guys. It is *not*suitable* for newbies who need detailed instructions on how to install drivers, programs, flash partitions, etc...
WARNING #2: on this phone there are (strangely...) close ties between boot.img and recovery.img content. This involves that changing contents of recovery.img can produce bootloop and changing contents of boot.img can prevent to access recovery too, creating a soft brick condition. I don't know exactly why, BUT you are warned.
WARNING #3: the procedure and files provided are *only* for ROM1 firmware version 14 of 13 Aug 2016. It is indicated as OUKITEL_C4_V14.0_20160813 in "About phone" and as t637d-oq-s08-fdd3m-hd-64g8g-sd internally. If you are on a differently indicated version and/or release date, *don't*even*think* about trying to apply the provided files: bootloops and (at least) soft bricks are easy coming, expecially because of warning #2...
WARNING #4: all provided files are in .zip format only due to forum rules and limitations. They *all* need to be *unpacked* before use them.
CREDITS: this TWRP recovery has been compiled by Jemmini on 4PDA forum. Since of the Russian only language of that forum and the very hard way to subscribe on it for not Russians (needed to download files too...), I'm reporting it here with more explanations and my hints & experiences too...
Said that... Let's start! :highfive:
IF (and *only* if...) your firmware version is reported as OUKITEL_C4_V14.0_20160813 in your phone, these are the steps to follow:
- unlock your bootloader (no special code needed, just enable the apposite option slider in Developers section of Settings and unlock it by the standard fastboot command in fastload mode... you need adb, fastboot and adb/fastboot drivers installed in your pc obviously )
Please remember that, as ever, unlocking your bootloader will factory reset your phone (and void your warranty...), so take it in proper account....
- using SP Flash Tool (recent versions since of the new MT6737 used in C4... tested one is the v.5.1644, just Google for it) just flash the provided twrp-c4.img (by Jemmini on 4PDA) selecting "Download only" on top, using the provided scatter file and selecting only the recovery row (browsing to twrp-c4.img file). Then press Download button and connect your phone in OFF status. If all was OK and you have MTK drivers properly installed (Google for them... search for MT6737 drivers. To test them just try to connect your phone to PC as storage to check if it is properly seen...), you should see a green checking sign "v" on top of SP Flash tool.
If nothing happens, try to reinstall drivers and/or doublecheck your phone is in OFF status when connected.
- don't try to boot to system now. It simply doesn't anyway.
For some unknown reason connected to warning #2, flashing twrp introduces a bootloop (soft brick...) on this phone.
Nothing to be worried of anyway: systemless rooting will fix it!
To root simply flash by TWRP (yes, you need to enable /system modification on first twrp boot...) SuperSU v.2.78 "standard" version in zip format (just Google for it...).
For standard is intended the released one, not SRx or "forced to system" one... (tested version is SuperSU-v2.78-201609011115.zip) .
Just remember that, since of unability to boot system before flashing SuperSU, its zip have to be already on your device before flashing TWRP. Otherwise you can use a microSD card to flash from it...
If you do all fine you now have your rooted & TWRP 3.0.2-x provided Oukitel C4!!! :highfive:
If you are in a bootloop condition you aren't able to fix, just turn off your phone and, ever using SP Flash Tool in the same way, simply reflashing stock boot.img and recovery.img (both provided as zipped-to-to-be-unzipped attachment for... emergency reasons ).
After, if you want, you can install Xposed (in system mode) or busybox by app (it will be automatically installed in systemless mode since of supersu installation method...).
Don't even try to install Magisk v.9 instead: it will not work and will produce a soft brick (with no recovery access too...) that will requires a boot.img and recovery.img reflashing to be solved (with all this procedure to be redone one more time...).
This said... if you have questions... I'm here to answer them. Otherwise... have a nice time with your TWRP provided and systemless Rooted Oukitel C4!!! :fingers-crossed:

Reserved. :silly:

Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways

[email protected] said:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
Click to expand...
Click to collapse
Added in OP. Don't expect to find more anyway...

I can confirm that this TWRP build also works fine with the newest OUKITEL_C4_V17.0_20161124 Firmware. Important: before flashing TWRP disable your boot lock code, otherwise you will softbrick your device.
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
EDIT:
I successfully installed XPOSED on my C4! This rocks the **** out of an 50 EUR budget phone!

Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards

salvarez01 said:
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
Click to expand...
Click to collapse
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.

[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
Hello thank you I have flashed 64 bits Rom and updated to V17, now all OK with TWRP and SuperSU.
Seam 64 bits version more slow than R06, but OK.
Thanks.

Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk

[email protected] said:
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
Click to expand...
Click to collapse
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
I managed to create an account on 4pda.ru and downloaded twrp for all firmware versions!
Files are attached!
Use twrp_recovery_C4_V.zip if your phone uses the OUKITEL_C4_VXX.X_XXXXXXXX firmware (Tested with OUKITEL_C4_V17.0_20161124)
Use twrp_recovery_R0x.zip if your phone uses the R0X_XXXXXX firmware. (Tested with R06_102033)

Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.

pop003 said:
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
Click to expand...
Click to collapse
Which rom do you have on your device?

Now I have R06_102033 on my C4

pop003 said:
Now I have R06_102033 on my C4
Click to expand...
Click to collapse
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10

[email protected] said:
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
(do not forget to give it a like)
Click to expand...
Click to collapse
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.

pop003 said:
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
Click to expand...
Click to collapse
Glad to hear it worked!

salvarez01 said:
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can configure SIP by using an App called Activity Launcher.
Download and Install Activity Launcher
Start Activity Launcher
Choose 'All Activities'
Search for 'Phone'
Open 'Phone'
Search and Click 'Sip Settings', 'com.android.phone.services.telephony.sip.SipSettings'
{
"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"
}

Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk

salvarez01 said:
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
After you added an Sip account you can choose you default dailing method as follows: Dailer -> Settings -> Accounts -> Dail With
You also see your SIP account as "additional SIM Card" when Opening the dailer!

Thank you!

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

[GUIDE][FIRMWARE] Hot Pepper™ Serrano 3 (HPP-L55B) Factory Firmware Restoration & Upgrading Guide

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.

[GUIDE] Assurance Wireless KonnectONE Moxee m2160 (MH-T6000) Rooting Guide

Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting Guide​
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. XDA hosts a plethora of how-to guides on standard bootloader unlocking. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. As OTA updates are rolled out for this device, I will try to keep this guide updated with a patched boot image that corresponds with the latest firmware build.
Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries with it the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:​
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;​
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);​
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder. Note: the filename for the patched boot image is patched_boot.img. The flashing commands assume that you leave the filename unchanged;​
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;​
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;​
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;​
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.​
That's it. You're now rooted via the Magisk v26.1 systemless root solution.​
IMPORTANT NOTE:
In the unfortunate event that you get stuck in a boot loop or brick your device using this guide, my guide on unbricking this smartphone will get you back up and running fairly quickly. This guide can be used to restore both soft bricked and hard bricked devices. You can then return here and give rooting another go.
Moxee MH-T6000 Unbricking Guide​DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to KonnectONE support specialist Faith Flores for releasing to me the factory firmware for this device.​

Viva La Android said:
Assurance Wireless
Moxee MH-T6000 4G-LTE
View attachment 5893661
Rooting Guide​
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:​
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;​
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);​
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder;​
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;​
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;​
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;​
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.​
That's it. You're now rooted via the Magisk v26.1 systemless root solution.​
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to the KonnectONE support team for releasing to me the factory firmware for this device.​
Click to expand...
Click to collapse
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!

scottfan81 said:
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
Click to expand...
Click to collapse
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.

Thank you so much! I have 3 of these devices and been waiting lol. I see the stock kernel has hot-plug . What's some good tuning profiles? I tried to debloat permanently with LP but it didn't work. I think it's read-only so I flashed the magisk overlay for rw and going to play. We definitely need TWRP! I see a port may be in the works. Awesome. Thanks again

Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos

Argonon said:
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Click to expand...
Click to collapse
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.

Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them

Argonon said:
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Click to expand...
Click to collapse
BLU won't unlock your bootloader. It is locked per contractual agreement with the branded carrier of the phone. However, if it's MediaTek, you may be able to use MTK Client to exploit the bootloader into an unlocked state.

Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work

Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
I have 3 of these devices. I surly can test TWRP port if needed

Argonon said:
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
I have 3 of these devices. I surly can test TWRP port if needed
Click to expand...
Click to collapse
Sure. I don't mind sharing my super.img. I'll need to upload it and then I'll message you a link. It's pretty much exactly 2.5 GB in file size, so I'll first compress it to a zip before uploading.

The edited one. Just clarifying so appreciated

Argonon said:
The edited one. Just clarifying so appreciated
Click to expand...
Click to collapse
I don't yet have all my mods made to the /super partition in that regard. Having encountered some force close issues with certain apps, I debloated from scratch and and have now begun my kernel tweaks and edits to the.varuous .prop files. So when finished, I'll share both my boot.img and super.img.

Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.

Argonon said:
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Click to expand...
Click to collapse
MH-T6000 super.img unmodified

I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module

Viva La Android said:
MH-T6000 super.img unmodified
Click to expand...
Click to collapse
Thank you!

Argonon said:
Thank you!
Click to expand...
Click to collapse
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore functionality.

Argonon said:
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Click to expand...
Click to collapse
Check out CRB Android Kitchen here on XDA. Great for unpacking / repacking partition images, including super.img.

Viva La Android said:
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore
Click to expand...
Click to collapse
Have you had anymore luck with this