How To Guide [WIN/MAC/LINUX][GUIDE] Moto G Stylus 5G Firmware Flashing / Restoration Guide

How To Guide [WIN/MAC/LINUX][GUIDE] Moto G Stylus 5G Firmware Flashing / Restoration Guide - Moto G Stylus 5G

Part 1
Telegram: Contact @motogstylus5gdev
t.me
Join my Telegram!
Device Profile:
GitHub - ArtiicPanda/MotoGStylus5G
Contribute to ArtiicPanda/MotoGStylus5G development by creating an account on GitHub.
github.com
Code:
Disclaimer: Following these instructions -MAY- void the warranty (if you haven't already) and I am not responsible for anything that happens to your phone. Do it at your own risk.
I am writing this because on my first day of owning the device, I somehow ran into an error stating "No valid operating system could be found."
If you can get into fastboot mode, this guide is for you. If not, PM me and we'll work through that together so I can write up a guide for that as well.
Spoiler: What I saw
{
"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"
}
ALL VARIANTS:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
ATT:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Boost:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Cricket:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
RETUS:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
TMO:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Tracfone:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

Part 2
Windows Method
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
To interface with the bootloader, download Android SDK Platform Tools from here. To access the bootloader, shut down your device. Hold Vol - & Power until the bootloader screen shows. From here, you can use fastboot to flash your device.
GitHub - ArtiicPanda/FlashFile2Bat
Contribute to ArtiicPanda/FlashFile2Bat development by creating an account on GitHub.
github.com
Download FlashFile2Bat converter from here. Place 'flashfile.xml' from firmware package into the directory with convertor.bat and run 'converter.bat'. This will output a file 'flashfile.bat' which can be used to re-install the firmware.
Copy the firmware files into the Platform Tools folder and run 'flashfile.bat'!

Part 3
MacOS Method
As a prerequisite please make sure you have the XCode Command Line utilities installed. If not, run this command:
Code:
$ xcode-select --install
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
To interface with the bootloader, download Android SDK Platform Tools from here.
To access the bootloader, shut down your device. Hold Vol - & Power until the bootloader screen shows.
Code:
$ cp ~/Downloads/platform-tools/fastboot /usr/local/bin/
From here, you can use fastboot to flash your device.
GitHub - dlenski/motoflash2sh: Convert Motorola flashfile.xml to fastboot shell script
Convert Motorola flashfile.xml to fastboot shell script - GitHub - dlenski/motoflash2sh: Convert Motorola flashfile.xml to fastboot shell script
github.com
Install motoflash2sh from here to convert the flashfile.xml to a bash script using this command:
Code:
$ pip3 install https://github.com/dlenski/motoflash2sh/archive/master.zip
Unpack zip file containing Motorola system image
Run motoflash2sh to convert the flashfile.xml to flashfile.sh
Inspect and/or run the flashfile.sh to execute the equivalent fastboot commands.
Code:
$ unzip XT2131-1_DENVER_TMO_11_RRE31.Q3-60-47_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip -d /tmp/unpacked
$ motoflash2sh /tmp/unpacked/flashfile.xml
Wrote shell script with 26 fastboot steps to /tmp/unpacked/flashfile.sh

Part 4
Linux Live CD Method
I have created a custom Live CD with all the tools needed to maintain and compile software/firmware for Android devices. This is what I use to compile my kernels, boot images, and restore my devices using fastboot. It is also pre-configured with the necessary tools to compile AOSP and many other ROMs. A complete list of ALL software packages and changes from the Lubuntu base is available in the repo.
GitHub - ArtiicPanda/APbuntu
Contribute to ArtiicPanda/APbuntu development by creating an account on GitHub.
github.com
Unpack zip file containing Motorola system image
Run motoflash2sh to convert the flashfile.xml to flashfile.sh
Inspect and/or run the flashfile.sh to execute the equivalent fastboot commands.
Code:
$ unzip XT2131-1_DENVER_TMO_11_RRE31.Q3-60-47_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip -d /tmp/unpacked
$ motoflash2sh /tmp/unpacked/flashfile.xml
Wrote shell script with 26 fastboot steps to /tmp/unpacked/flashfile.sh

If you have any issues, post below or send me a PM. Thanks for reading my guide!

Dumb question: Is RETUS the same as North American Retail?

No dumb questions here! RETUS would be the North American retail yes. RETAIL would be the global retail version they'd sell everywhere else. Pretty standard for Motorola.

My bad miss read what you are doing here.

ArtiicPanda said:
No dumb questions here! RETUS would be the North American retail yes. RETAIL would be the global retail version they'd sell everywhere else. Pretty standard for Motorola.
Click to expand...
Click to collapse
Awesome. Thank you. I purchased 2 of these so I can start dev'ing/bricking one of them. lol
I'll be using Debian as my dev platform. Not a big windoze or Ubuntu fan. Can't wait to get started.

electrofryed said:
Awesome. Thank you. I purchased 2 of these so I can start dev'ing/bricking one of them. lol
I'll be using Debian as my dev platform. Not a big windoze or Ubuntu fan. Can't wait to get started.
Click to expand...
Click to collapse
I've bricked twice today and it won't be my last. As long as we have stock firmwares and blankflash we're pretty much good to test any and everything. Are you working on anything interesting? I'd love to test and help out

ArtiicPanda said:
I've bricked twice today and it won't be my last. As long as we have stock firmwares and blankflash we're pretty much good to test any and everything. Are you working on anything interesting? I'd love to test and help out
Click to expand...
Click to collapse
I'm having a bit of trouble installing the motoflash2sh. Looks like I just need to change the install path for Debian. Once I get that going, I'm going to start on a port on CarbonRom. Hopefully I'll have it ready once the TWRP gets a little further along. If it goes well, I'll try Resurrection after that. RR is a really difficult port. That's why it's last on the list. lol

electrofryed said:
I'm having a bit of trouble installing the motoflash2sh. Looks like I just need to change the install path for Debian. Once I get that going, I'm going to start on a port on CarbonRom. Hopefully I'll have it ready once the TWRP gets a little further along. If it goes well, I'll try Resurrection after that. RR is a really difficult port. That's why it's last on the list. lol
Click to expand...
Click to collapse
I’ve started working on TWRP as well since I saw the links were down. I got it booting this morning but it needs a little more work
GitHub - ArtiicPanda/twrp_denver
Contribute to ArtiicPanda/twrp_denver development by creating an account on GitHub.
GitHub.com
I have a basic tree that compiles and boots the recovery, could be a good starting point for a rom device tree

Also this phone can be unbricked with the moto smart assistant from support.motorola.com, windows only but it will grab the latest firmware from moto instead of a third party that may not have the latest firmware yet

I've never built TWRP (or anything else) from source, is yours much different from Electimons TWRP? His bricks if you switch slots, but the backup to SD works.

I have problems with the drivers on my PC, i install Moto USB drivers v6.4. And it's not been recognized by moto composite ADB in my device manager, also in fastboot neither, i get fastboot Denver s with yellow mark

Smil3yWulf said:
I have problems with the drivers on my PC, i install Moto USB drivers v6.4. And it's not been recognized by moto composite ADB in my device manager, also in fastboot neither, i get fastboot Denver s with yellow mark
Click to expand...
Click to collapse
Moto g stylus 5G kind of going through the same stuff that sounds like. Although I'm finally making some progress I think I'm more or less making progress by accident by bumbling my way through teaching myself all this LOL

get the error no valid operating system. But my bootloader is locked and I can't reunlock it because I can't select oem unlocking in developer options due to no operating system. And I've tried flashing the last use firmware on it and i don't have permission. I've tried many different stock roms including the latest, I've tried the rescue software and it fails every time it gets to flashing the partition. Any suggestions?

Ajpia666 said:
get the error no valid operating system. But my bootloader is locked and I can't reunlock it because I can't select oem unlocking in developer options due to no operating system. And I've tried flashing the last use firmware on it and i don't have permission. I've tried many different stock roms including the latest, I've tried the rescue software and it fails every time it gets to flashing the partition. Any suggestions?
Click to expand...
Click to collapse
Did you relock it or did it lock itself?

sd_shadow said:
Did you relock it or did it lock itself?
Click to expand...
Click to collapse
As embarrassing as it is I gotta be honest I relocked it after seeing no valid operating system thinking it might reset it and reinstall firmware. Obviously I was incorrect

Ajpia666 said:
As embarrassing as it is I gotta be honest I relocked it after seeing no valid operating system thinking it might reset it and reinstall firmware. Obviously I was incorrect
Click to expand...
Click to collapse
No, now it's in a bad state.
What does getvar all say? remove imei before posting.
Code:
fastboot getvar all

Related

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!

Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)

Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.

[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.

Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760

Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!

Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc

Getting an error
FAILED(remote: oem unlock is not allowed)

Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.

I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?

paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...

added to index

Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.

Yes it's normal

Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk

You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.

Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?

Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.

Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks

Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.

OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers

You can lock and unlock your bootloader as much as your heart desires without consequence

skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...

I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?

owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.

Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6a Support Thread.

{
"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"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.

chopt51 said:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
Click to expand...
Click to collapse
If you don't choose wipe data, or force in flash options, then you should keep your data.

I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.

USB debugging turned on?

tlxxxsracer said:
Yet cmd shows an adb connection.
Click to expand...
Click to collapse
Explain what you mean by that?

badabing2003 said:
Explain what you mean by that?
Click to expand...
Click to collapse
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized

tlxxxsracer said:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
Click to expand...
Click to collapse
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.
There is no reason for it not to be detected if you're command detects it.

New Release:
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.

Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?

jpdurand31 said:
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
Click to expand...
Click to collapse
If you can post support.zip file from help menu I can take a look.

If you want more info, i'm 100% available!

jpdurand31 said:
If you want more info, i'm 100% available!
Click to expand...
Click to collapse
Hmmm ...
I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?
I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good
I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)
You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)
On next attempt (one hour later) your device was in bootloader mode.
Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.
You cannot create a patch file in fastboot mode, it needs to be in adb mode.
And please please don't dare to lock your bootloader, I see you attempted and then cancelled,
Code:
2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!
NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!
Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.
2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...
If you lock your bootloader before fixing your device, you will be locked out forever (bricked)
So at this point what are your choice and how can you fix this?
1- get the latest Android Platform Tools
2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.
Select the firmware, process it, this will show the boot.img file
Select the boot.img file and choose keep data and hit Flash.
Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.
Alternately, what happens if you select in PixelFlasher to reboot the device into System.
Does it reboot? and if it does, does it end up in adb mode of fastboot mode?
One other option you have is to flash OTA in sideload mode.
Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.
PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.
Good luck

Thanks for your response and the detailed process.
I was fooled by the version of the package that was in 33...
By upgrading the Android Platform Tools to the latest version, I could update to Android 13.
Thanks a lot for the help and the reactivity!

New Release:
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.

3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.

JudasD said:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
Click to expand...
Click to collapse
Thanks for reporting and sorry for your troubles.
Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.
Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?
It should capture the error PixelFlasher 3.7.0 encountered.

Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.

JudasD said:
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
Click to expand...
Click to collapse
No need for apology, happy to hear that the issue now resolved.

Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):
Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)
Everything seemed to work fine, though.

[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

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

[GUIDE] KonnectONE Moxee m2160 (MH-T6000) 4G-LTE | Unbricking & Factory Firmware Restoration 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"
}
Unbricking & Factory
Firmware Restoration Guide
OVERVIEW:
This guide outlines detailed instructions on restoring the KonnectONE Moxee MH-T6000 smartphone to its stock factory state by flashing firmware via the Qualcomm Flash Image Loader (QFIL) software for Windows. The firmware provided is official and signed by the manufacturer. This procedure can be used to restore either a soft or hard bricked device. In addition, this guide would benefit device owners who are rooted or running a custom OS who wish to revert to an unmodified stock state. This firmware will remove any root binaries, custom recoveries, custom kernels, system-level mods, and will restore your smartphone with the unmodified stock Android OS.
DISCLAIMER:
Due to the invasive nature of this procedure, there is an inherent risk that you could damage or otherwise render your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone, thus absolving me of any civil liability in the event things go bad. The steps in this guide have been thoroughly tested. Follow the instructions carefully, pay attention to detail, and things should go smoothly. Nevertheless, you have been cautioned. In the event you are attempting to recover from a hard brick, your device is already unresponsive and inoperable. Thus, the risk involved in such a scenario is virtually inconsequential.
PREREQUISITES:
First and foremost, you will need a PC or laptop running Windows 7/8.1/10/11; the Qualcomm USB device drivers (link provided below); the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable; the Qualcomm Flash Image Loader (QFIL) v2.0.0.0 software (link provided below); and a factory firmware package for the Assurance Wireless KonnectONE Moxee MH-T6000 smartphone (link provided below). This procedure can be carried out regardless of the locked/unlocked state of your bootloader. Moreover, if your bootloader is in an unlocked state, it will remain in an unlocked state once the factory firmware is installed. Likewise, if your bootloader is locked, flashing the factory firmware will not alter its locked state.
FIRMWARE INFO:
OS/Version: Android 11 (Go Edition)
Build No. MH-T6000V1.0.0B010
Build Date: February 20, 2023
Build Type: User
API Level: 30
Security Patch: March 5, 2023
Radio Version:
MPSS.JO.3.4-00044-SDM439_GENNS_PACK-1
Kernel Version: 4.19.157-perf
Partition Scheme: Dynamic (Non-A/B)
Project Treble: Supported
Arch: armv7l (32-bit)
Java VM: ART 2.1.0
Widevine Version: 16.0.0
Widevine Security Level: L3
LTE Band Support: 2/4/5/12/25/26/41
LTE HPUE Bands: 66/71
QUALCOMM FLASH IMAGE LOADER:
For those members unfamiliar, the Qualcomm Flash Image Loader, or QFIL, is a portable software application used for flashing factory firmware to devices powered by Qualcomm chipsets. QFIL is a proprietary flashing protocol, developed by Qualcomm Technologies, Inc., and is also an inbuilt application to the Qualcomm Program Support Tool (QPST). The flashing protocol utilizes Qualcomm's proprietary Emergency Download Mode (EDL), one of the only solutions capable of fully restoring a completely hard bricked mobile device. This flashing method can restore a device in which the partition table has been corrupted or is missing entirely. It is also worth noting that QFIL is integrated with a QCN (Qualcomm Calibration Network) backup and restore feature. The QCN is a binary file which encompasses all calibration data for the various hardware components and sensors within the device. It also stores the baseband radio and network configuration settings, including unique identifiers such as your IMEI/MEID numbers. This valuable feature can be used to restore these settings and values if they become corrupted or lost due to a system-level issue or a botched user-end system modification.
For purposes of simplicity and efficiency, and because this procedure does not require the entire QPST software suite (which includes service programming tools, port configuration monitor, baseband radio diagnostic tools, and QFIL), we will be using the portable standalone version of the QFIL software application.
INSTRUCTIONS:
Download the Qualcomm USB drivers installer from the below link and save it to a convenient location on your PC or laptop. Double click on the .exe installer and follow the prompts for installation. On the Setup Type window, select the first option for WWAN-DHCP then select Next. Now accept the terms of the license agreement and compete the installation. Once completed, reboot your computer;
Download QFIL v2.0.0.0 and extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop;
Download the Moxee MH-T6000 firmware from the below link and extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop;
Double click QFIL.exe inside the QFIL folder (referenced in Step 2) to open the flashing utility. In the upper-left area of the QFIL interface, select the Flat Build option. Next click the Build tab, which will open the Windows File Explorer. Navigate to the extracted firmware folder you created in Step 3. Select the firmware file named prog_emmc_firehose_8917_ddr.mbn, then click Open. Next, click the Load XML... tab which will once again launch Windows File Explorer. Select the file named rawprogram_unsparse.xml, then click Open. On the next screen select patch.0.xml and select Open once more. The firmware package is now loaded and ready to flash;
Now you must initiate Emergency Download Mode (EDL) on your phone. EDL mode is a Qualcomm proprietary firmware flashing & diagnostic protocol To do this, first ensure your device is powered off (unless, of course, your device is hard bricked, in which case it will be completely unresponsive and, for all intents and purposes, is already in a powered off state). Connect one end of your data syncing cable to your PC or laptop, but not yet to your phone. On your smartphone, hold Volume Up and Volume Down simultaneously while connecting the Type-C end of the data syncing cable to your phone. If your phone is being properly recognized, you will see Qualcomm HS USB QLOADER 9008 at the top of the QFIL interface, followed by your active port number. If you do not see this indicator on the QFIL interface, try using another data syncing cable, change USB ports, and/or reinstall the Qualcomm USB device drivers by repeating Step 1;
Once a proper connection is verified, click on the blue Download tab to commence the flashing process. A progress bar on the interface will indicate the status of the flashing process. This can take a few minutes, so just remain patient until the Status window indicates flashing success;
Now simply power up your device. It may be necessary to briefly remove and reinsert the battery to exit EDL mode. That's it. Your device should now be reverted to its factory stock state.
DOWNLOADS:
• Qualcomm USB Drivers Installer
• QFIL v2.0.0.0
• MH-T6000V1.0.0B010 Firmware
• OTA MH-T6000V1.0.OB011
THANKS & MENTIONS:
Thanks to @omb714.1980 for donating the device that made this guide possible. Thanks also to KonnectONE Support representative, Faith Flores, for providing me with the factory signed firmware for this phone.

I ended up removing various system apks by using some ro2rw magisk module etc but upon rebooting it kept going to fastboot. I flashed stock super img with fastboot then reflashed patched boot img and restored firmware that way. Lol I'm trying to recreate what I did idk maybe I needed to disable dfe. I had other magisk modules installed like an overlay to make ro rw partition for read only devices etc so idk yet

I need to try disable avb dm verity. Can someone upload the file I need to fastboot flash disable verity etc please? I successfully edited a super.img and just deleted various apps like outlook, fb installer, my account etc but left the folders etc. I used that ro2rw magisk. Pretty cool but after flashing the edited super.img it boots to fastboot mode. I'd like to try disabling verity.

Argonon said:
I need to try disable avb dm verity. Can someone upload the file I need to fastboot flash disable verity etc please? I successfully edited a super.img and just deleted various apps like outlook, fb installer, my account etc but left the folders etc. I used that ro2rw magisk. Pretty cool but after flashing the edited super.img it boots to fastboot mode. I'd like to try disabling verity.
Click to expand...
Click to collapse
You need vbmeta.img. You'll find it in the firmware package. To flash vbmeta.img and disable verity/AVB, use this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can copy and paste this command to make it easier. All the hyphens are a bit tricky.

Thanks. Now just boots to black screen. Lol. I'll keep playing

Argonon said:
Thanks. Now just boots to black screen. Lol. I'll keep playing
Click to expand...
Click to collapse
I finally got super.img rw and was able to debloat directly from the booted device! I used a magisk module called RO2RW test version. It uses android terminal like termux to pull the super.img then extract it. Once Product, System etc are extracted you use the mount script that makes it able to edit the imgs from MT file manager. Then terminal prompt recompiles it along with a new boot.img. its hard to explain as im not a pro lol. Here's the xda link where I got the ro2rw magisk module. https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/

Argonon said:
I finally got super.img rw and was able to debloat directly from the booted device! I used a magisk module called RO2RW test version. It uses android terminal like termux to pull the super.img then extract it. Once Product, System etc are extracted you use the mount script that makes it able to edit the imgs from MT file manager. Then terminal prompt recompiles it along with a new boot.img. its hard to explain as im not a pro lol. Here's the xda link where I got the ro2rw magisk module. https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
Click to expand...
Click to collapse
Nice work. I have the CRB Kitcen for Windows which performs similar operations to super.img. My only dilemma has been a lack of free time. I'll check out the method you linked. I'm not familiar with that Magisk module and I will definitely check it out. Again, nice work. I admire your persistence and determination.

Latest OTA update package
MH-T6000V1.0.0B011

Viva La Android said:
Latest OTA update package
MH-T6000V1.0.0B011
Click to expand...
Click to collapse
Does this change the Security Patch? What have you noticed different?

Argonon said:
Does this change the Security Patch? What have you noticed different?
Click to expand...
Click to collapse
It bumps the security patch level and fixes a couple of bugs in the cellular radio firmware resulting in dropped calls during node switching.
To install it, the simplest way is to revert to an unmodified stock state by flashing the factory firmware in my restoration guide. Once restored, you can install the update.zip via stock recovery mode.

Awesome. Oh btw firmware is now available for the mtk blu view 3 android 11 now!!

Argonon said:
Awesome. Oh btw firmware is now available for the mtk blu view 3 android 11 now!!
Click to expand...
Click to collapse
This is excellent news.

I need to unlock sim for this phone . what is the unlock method pleassss?

Mohammed Alqadri said:
I need to unlock sim for this phone . what is the unlock method pleassss?
Click to expand...
Click to collapse
I unlocked mine simply by flashing the factory firmware via QFIL, using the exact steps outlined in this guide. After initial setup following firmware restoration, the preinstalled network unlock app indicated that my device was permanently unlocked for use with other carriers.
I'm not exactly sure as to the reason why this worked, nor have I researched the possible mechanics behind the occurrence.

Viva La Android said:
I unlocked mine simply by flashing the factory firmware via QFIL, using the exact steps outlined in this guide. After initial setup following firmware restoration, the preibstakked network unlock app indicated that my device was permanently unlocked for use with other carriers.
I'm not exactly sure as to the reason why this worked, nor have I researched the possible mechanics behind the occurrence.
Click to expand...
Click to collapse
When flashing the firmware, is it necessary to have the lock status of the bootloader unlocked or not ?

Mohammed Alqadri said:
When flashing the firmware, is it necessary to have the lock status of the bootloader unlocked or not ?
Click to expand...
Click to collapse
The state of the bootloader has no relevance to firmware restoration. The firmware will be installed in exactly the same manner regardless of whether the device is bootloader locked or unlocked.

For any members interested, my modified stock ROM for this device is complete. The full installation guide can be found here https://forum.xda-developers.com/t/...e-moxee-m2160-mh-t6000-4g-lte.4596393//unread

Viva La Android said:
For any members interested, my modified stock ROM for this device is complete. The full installation guide can be found here https://forum.xda-developers.com/t/...e-moxee-m2160-mh-t6000-4g-lte.4596393//unread
Click to expand...
Click to collapse
I have a question, why when I insert the sim card into the phone, it appears that there is no service, since the service is available on any other device. will the modified ROM solve the problem or the official ROM? please answer......

Mohammed Alqadri said:
I have a question, why when I insert the sim card into the phone, it appears that there is no service, since the service is available on any other device. will the modified ROM solve the problem or the official ROM? please answer......
Click to expand...
Click to collapse
This ROM does not have any effect on the network locked or unlocked state of the device. You may need to configure your network settings or APN configuration for the carrier of the SIM card. But, out of curiosity, what carrier is linked to your SIM card, and has your Moxee phone been network unlocked? By default, the Moxee m2160 is locked to Assurance Wireless and, as such, will only work on their network.

I
Viva La Android said:
This ROM does not have any effect on the network locked or unlocked state of the device. You may need to configure your network settings or APN configuration for the carrier of the SIM card. But, out of curiosity, what carrier is linked to your SIM card, and has your Moxee phone been network unlocked? By default, the Moxee m2160 is locked to Assurance Wireless and, as such, will only work on their network.
Click to expand...
Click to collapse
I use the carrier of GSM. the coverage towers do not appear on the phone. there is no service that has nothing to do with settings or APN

Database Info

welcome