Related
Persist Resurrector
Code:
#include<disclaimer.h>
void main()
{
clrscr();
printf("If you are reading this, your warranty is already void.");
printf("/nYou can't blame me for that. It is your own doing");
printf("/nFor using this software, you need to agree following things");
/* */
/*I am not responsible for bricked devices, dead SD cards,*/
/* thermonuclear war, or you getting fired because the alarm app failed. Please*/
/* do some research if you have any concerns about features included in this software*/
/* before using it! YOU are choosing to make these modifications, and if*/
/* you point the finger at me for messing up your device, I will laugh at you.*/
/* */
getch();
}
Hello everyone!
It has been observed that few custom ROMs of Mi A1 change persist partition. This has no observable (yet) effects when using those ROMs. However after flashing stock ROM back, connecting to Wi-Fi becomes impossible. This happens because the ROM changes your Wi-Fi MAC address. The custom ROMs causing this bug do not depend on Vendor MAC, so Wi-Fi works fine with them.
Reconstructing original vendor MAC address is possible, but ONLY if you have persist partition which belongs to YOUR PHONE. This means you HAVE NOT flashed any of the several persist.img files floating around xda.
If you have flashed someone else's persist image -
You CANNOT use this tool since you have destroyed the last chance to repair original Wi-Fi MAC.
You have lost your original Bluetooth MAC and replaced with someone else's.
You have lost calibration data of various sensors (Unconfirmed, but usually sensor calibration data is stored in /persist)
If you connect to the same Wi-Fi with someone else who is using same persist.img or has same MAC address by coincidance. Same for BT.
Wi-Fi where that MAC is banned won't let you join or if you added MAC filter to your own Wi-Fi it won't recognise your phone anymore.
It is illegal.
CosmicDan said:
Yeah that's actually illegal here in Australia too, and they DO crack down on it in many countries (cloned MAC's are a target for anti-terror units, and ISP's *can* see your device MAC's so that thread really should be taken down)
Click to expand...
Click to collapse
This is when this tool comes into picture. A guide is posted in guides section of Mi A1 forum by SevenSlevin. But it involves completely deleting the contents of the file which stores the MAC address. This deletes the faulty MAC addresses causing problems, but does not give you original Vendor MAC address (from Xiaomi) back. I personally didn't like losing the original MAC address which came from factory. I am sure there would be many of you thinking along the similar lines.
So what this tool does is it reconstructs your Wi-Fi MAC addresses using dark hex magic (pun intended) and pushes it back to your device, puts it in appropriate position if you want and voila!
FAQ (Recommended to read)
Add a MAC randomizer for people who already have destroyed their persist.
=> This looks like on the borderline of legality and illegality. I can add this feature in the next release if this is legal. (Please reply in this thread)
Is this tool safe?
=> I have tested it on 3 different Mi A1s and I haven't found any problem yet.
Will this work if I have xyz ROM?
=> I always use and prefer stock Oreo ROM when testing. So you have to find the answer yourself.
But it is best to be on stock ROM because it is the ROM which has the problem you are here to get fixed.
I have got a warning with an error code or FAILSAFE kicked in.
=> Send the error code here.
What is FAILSAFE?
=> Failsafe is a series of measures to avoid potential problems or damage done made by me for another personal project. Only a very small part is implemented here and this is made 60% failsafe which means there are *some* loopholes left due to time constraints and unnecessary redundancy, but you won't find them unless you are doing terminal stupidity.
This is the main reason why I am not releasing the source code. It is still in its infancy and it will be long before it will be mature.
Stick to the instructions and FAILSAFE won't kick in.
This software is NOT working at all.
=> Post here along with the steps you followed.
Awesome! YOU FIXED MY PHONE!
=> I am glad to hear read this. :highfive:
Requirements -
Mi A1 (stock ROM recommended)
Root access
ADB Drivers installed
Microsoft DOT NET Framework (Tested on v4+, but v3.5+ should work)
Your firstborn
{
"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"
}
(JK JK)
Downloads -
Attached to the bottom of this post.
Current version - 1.0.0.0
Date - 22/04/2018
File: Persist Resurrector v1.0.zip
MD5: 82fd5a6dfc28d2388649db4ae72c4538
SHA-512: a9eb3124315cf0cfe0875f1aae61127a4f71441fd294d63e46efa9fe198971e05a54aa2f15e70ebebfa356ae4b660356b24c424cd2008cefb56fed5fe740b81b
Individual file checksums are included in the zip.
No viruses included.
VirusTotal Scan
Only 1 (Dr Web) gives a False Positive.
Click to expand...
Click to collapse
Changelog -
v0.5, 20th April, 2018
Initial Release
Calculations working as intended
Manual file replacement
v0.7.5, 21th April, 2018
Automated file replacement
Changed code to be more effective and cleaned it up
v1.0, 22th April, 2018
xda release
FAILSAFE implemented
Click to expand...
Click to collapse
Instructions -
Download and extract the zip to any directory. (Avoid Program Files or at the root of Windows Installation Drive, UAC becomes a problem)
Run the Persist Resurrector.exe
Connect the phone via USB cable and unlock screen.
Press the buttons in the sequence as labeled on screen.
Give confirmations to ADB and Root as necessary.
Profit!
Developer of this tool, hnkotnis, has no responsiblity if your phone, memory card or you are bricked, bootlooped or damaged in any other way.
You are using this tool on your own and you take whole responsibility of any damage caused.
Feel free to POST this to your website or blog BUT DO NOT MIRROR DOWNLOAD LINKS. SHARE LINK TO THIS PAGE.
So that I can get the exact download count.
YOU CANNOT MODIFY, DISTRIBUTE (Free or paid), CHANGE or REVERSE ENGINEER THIS SOFTWARE.
Click to expand...
Click to collapse
Reserved
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Ay the one that we all needed! Thank you!
Calibration also related to fingerprint sensor?
Nice work
I think a random MAC would be useful, legal issues aside. There are tools out there that anyone can use to freely edit and/or change MAC addresses in many hardware. The tools themselves are not illegal, bit the use of specific MAC's or non-original MAC's in certain situations may be illegal.
It would be good if you could provide an option to enter MAC manually too. The original MAC may be recoverable in some way, possibly by contacting Xiaomi or something. It sadly isn't printed anywhere on the box or anything.
iamshivendu said:
Calibration also related to fingerprint sensor?
Click to expand...
Click to collapse
That's a good point. A corrupt persist may be why some users cannot enrol more than X fingerprints. Not sure though.
Can someone mention which custom ROMs possibly change persist partition?
unos21 said:
Can someone mention which custom ROM possibly change persist partition?
Click to expand...
Click to collapse
All of them do AFAIK. Maybe only all 8.1 firmware.
CosmicDan said:
Nice work
I think a random MAC would be useful, legal issues aside. There are tools out there that anyone can use to freely edit and/or change MAC addresses in many hardware. The tools themselves are not illegal, bit the use of specific MAC's or non-original MAC's in certain situations may be illegal.
It would be good if you could provide an option to enter MAC manually too. The original MAC may be recoverable in some way, possibly by contacting Xiaomi or something. It sadly isn't printed anywhere on the box or anything.
Click to expand...
Click to collapse
I will try to implement both in the next release. Both are easy to add since most of the code remains same. No ETAs but it could be in the next week if possible. But if I cannot do it within next week then the release will be directly after 16th of may.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Am i the only one not having wifi issues after flashing stock rom? I used a lot of custom 8.1 roms and if theres new update in stock rom i flashed back to test it and not having wifi not connecting issues. Hmm ?
t0per666 said:
Am i the only one not having wifi issues after flashing stock rom? I used a lot of custom 8.1 roms and if theres new update in stock rom i flashed back to test it and not having wifi not connecting issues. Hmm ?
Click to expand...
Click to collapse
After flashing custom rom have you tried connecting to 5hz wireless network?
This tool just help me fix my phone , thank you man :v
ShazlieyAzizan said:
This tool just help me fix my phone , thank you man :v
Click to expand...
Click to collapse
and how did you do it? You were in the last rom stock right? I'm going crazy and I can not solve it, thanks.
ruperxl89 said:
and how did you do it? You were in the last rom stock right? I'm going crazy and I can not solve it, thanks.
Click to expand...
Click to collapse
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
ShazlieyAzizan said:
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
Click to expand...
Click to collapse
thank you i will try this now, i tried with last oreo build yesterday and it failed, sorry for my english
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
ShazlieyAzizan said:
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
Click to expand...
Click to collapse
but you have some backup of /persist?
Hi mate, I've lost my persist partition (original), because of that, I've to erase the persist partition and reflash it from the "stock rom image" to stop the continue reboot bug. The IMEIs and S/N work great but the Wi-Fi and Bluetooth Macs are different now from the originals.
I know which were my MACs, is there some method to re-insert them???
Thanks for your time, kind regards.
I totally lost imei , sn , FSN and PSN due wrongly clicked flash_factory.bat , i send back for warranty but they can't fix and refuse to change board ( even i want to pay) .. hope this tools can help me find back my original mac address when i get back my device
ruperxl89 said:
thank you i will try this now, i tried with last oreo build yesterday and it failed, sorry for my english
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
but you have some backup of /persist?
Click to expand...
Click to collapse
yes i do have
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
JoKeRLeE said:
I totally lost imei , sn , FSN and PSN due wrongly clicked flash_factory.bat , i send back for warranty but they can't fix and refuse to change board ( even i want to pay) .. hope this tools can help me find back my original mac address when i get back my device
Click to expand...
Click to collapse
yeah actually they should refuse to check your phone because you the one who mess with the phone . hahah english tak padu type melayu la , imei lost semua tu sebab kacau system dia kan ? kalau betul nak hantar warranty ksi rosak die punya software sampai blank then kata jadi lepas update software , dorang confirm boleh tolong , anyway goodluck
Raskaipika said:
Hi mate, I've lost my persist partition (original), because of that, I've to erase the persist partition and reflash it from the "stock rom image" to stop the continue reboot bug. The IMEIs and S/N work great but the Wi-Fi and Bluetooth Macs are different now from the originals.
I know which were my MACs, is there some method to re-insert them???
Thanks for your time, kind regards.
Click to expand...
Click to collapse
In the v2 there will be a feature to add MAC manually.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
It will possible add too the Bluetooth MAC???
Raskaipika said:
It will possible add too the Bluetooth MAC???
Click to expand...
Click to collapse
It is easily possible to add it. But it will need writing the whole code again. I will be busy with exams so it is on top of my to do list as soon as exams are over.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22
many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj
new update is in the op.
just small changes and updated security patch level.
Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt
Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).
Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...
lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo
slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.
This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated.
I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's open source. Instead, it is signed with one of my own "Google Play certified" keys. Changes are below for anyone that would rather build and sign the application locally.
The caveat to using a different key is that the unofficial version cannot be installed directly over the official and vice versa.
Pull Request
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Original Source
GitHub - HomerSp/AsusVoLTE: Enable VoLTE/VoWiFi on the ROG Phone 2
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
Thanks a lot for your update.
I made some progress.
App is working perfectly, triggered the USB PDC mode as well. (Which I couldn't do earlier).
The older versions we used were not detecting the device.
Got the new QPST from here
The latest driver I could find was from here
Still stuck at exactly here;
{
"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"
}
The guide I follow is the one which worked for me on the ROGII - Which is here. Didnt require any MBN flashing, as I have a global device and just needed to use the existing VoWiFI Profile.
Any ideas on how to resolve the connection issue?
Maybe there are newer drivers?
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
JazonX said:
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
Click to expand...
Click to collapse
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
twistedumbrella said:
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks a lot, Made it through to the EFS Tools guide.
Did the mod to the EFSToolsdllconfig, Matched Ports.
Currently stuck here, Will keep you updated of the progress.
EDIT:
Tested with my ROG II and the command is working, So it's unable to read the ROG 5 for some mysterious reason.
I would test, but VoLTE works out of the box for Tencent / T-Mobile. No use trying to break it, especially if it's meant to survive updates / firmware.
At the point of giving up.
Stuck here;
and also I noticed that the Driver detection page keeps refreshing.
So I assume that neither of the tools we use are compatible with the ROG 5 yet, as they all link and work properly with my ROG II.
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
twistedumbrella said:
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
Click to expand...
Click to collapse
Thanks a lot for the responses;
(And thank you for your patience)
Here are my findings;
* The new EfsTools app is sorta broken, because it doesnt SIM Slot #2 Changes - Someone already reported it.
* Android 11 seems to block the PDC function, hence no ADB command can trigger it. However somehow your version of the AsusVoLTE app on first post here forcefully enters the Phone to PDC mode. This is a win, however the Device Manager keeps refreshing every second - so no connection can be made. I'm using Qualcomm Driver 1.0061 which seems to be the latest. I have used older .37 / .40 drivers as well, nothing changes the "frequent refresh" behavior.
* Not sure how this guy managed to get the ADB command to work on Android 11 in Zenfone, I tested it with both USB ports, multiple cables.. Nothing seems to trigger anything.
The code he suggested is
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
* OnePlus folks have the same issue and they have managed to enable PDC support by taking the phone to Field Test Mode via "ADB reboot FTM" command. This doesnt work for asus. OnePlus Method.
* I tried putting the phone in EDL mode, however this doesn't enable any Diag or PDC port, it seems its only for flashing. So far I have no clue whether any engineering or FTM mode exists on Asus.
* Many forums have *#*# codes - I think I have tried all of them, none of them seems to make any new option appear in sim menus.
So .. still. No VoLTE, and therefore no 5G either.
If you have any ideas / guides I can try .. Much appreciated!
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
twistedumbrella said:
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
Click to expand...
Click to collapse
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Vojtek12 said:
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Click to expand...
Click to collapse
You can enter diag mode using this commands
Inline links are only good when they save space for a reference that most readers may not be interested in reading
jbm76 said:
Install these usb drivers - https://gsmusbdriver.com/category/xiaomi/page/3
These are the commands -
Both of these work.
adb shelll,
su
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
Either setprop command will work.
setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl
In regards to the VOLTE issue still no go on A11 - I have been able to access the EFS partition but the ims_user_agent won't stick even if I write to it with in EFS explorer of EFs tools, it doesn't survive a reboot.
Click to expand...
Click to collapse
JazonX said:
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
View attachment 5393765
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Click to expand...
Click to collapse
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
LinhBT said:
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
Click to expand...
Click to collapse
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
JazonX said:
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
Click to expand...
Click to collapse
My ROG 5S is now in a very weird situation while both SIM is working, baseband is there, but no IMEI ( but still can make and receive phone call, sms....etc ). Also, can't unlock bootloader since it has no IMEI
Dear Viewer,
This will temporary be a medium for all owner of 'Samsung Galaxy A13' to share latest info about the device.
I will try to update as often as I can, but I'm not an active member in the forum.
Please do try you best to look for information needed by scrolling through them.
WARNING
Please do bare in mind that any action took, are solely your responsible.
Anyone either me or anyone shall take any responsibility.
Steps to enable OEM Unlock
Go through your device setup. (if you're starting brand new)
Enable Developer Settings.
Connect to any network & disconnect after time sync.
Manually change your date to at least 2 year later.
Restart your device
Directly navigate to Developer Settings after restart.
Have any of you tested Pixel Experience android 13 installations on this phone? If so, what rom?
[RECOVERY][TWRP][3.6.11][UNOFFICIAL] FOR SAMSUNG [A135F][A13]
UNOFFICIAL TWRP FOR SAMSUNG A135 EXYNOS DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES. We are not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting...
forum.xda-developers.com
Is there a LineageOS install guide somewhere?
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 GuideDOWNLOADS:
• 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