Related
Hi,
Short story, I bought another Mi4C. It's new, not a refurb one, though "new" here has a chinese label which state that the production date around 2016-10.
First thing, apparently the battery was emptied, so it drained very quickly. Second, it came with a non official MIUI rom (marshmallow 8.0.4.0.0), but fortunately for me, the bootloader is already unlocked. I played a bit a little, all sensors were working fine along with all other feature (cameras, digitizer, etc), so I quickly grabbed latest lollipop TWRP, and flash latest nightly AICP, and also 8.5.1.0 firmware.
Everything was working well until I installed a compass app, it's not working. Strange, so I looked up CPU-Z and find out that magnetic sensors doesn't appear.
Now, I've read this might be caused by malfunction/broken persist.img, so quickly grab latest official fastboot MIUI chinese stable (8.5.1.0), extracted the persist.img, but I was worried how small it is. And if I view it under a hex viewer, most of it's file are filled with 0x00 value, is it a correct persist.img?
Before I do anything stupid flashing that suspicious persist.img with fastboot, I need a confirmation whether anyone here ever came across the same problem? I've seen other thread regarding missing sensors too and that thread also suggests to flash the persist.img... But the file quite the same, ~5mb with most of its entry filled with 0x00.
Any helpful feedback is welcomed.
PS: I saved an old mi-globe ROM 8.1.3.0 (lollipop) stable, clean flash to that, and called the MIUI diag (*#*#6484*#*#), this time when I tried the magnetic, the app always crashes.
Anyway, so I had /persist partition backed up using Wanam Partition backup, but before I proceeded to flash the persist.img from mi4c official china stable fastboot, I checked using DiskInfo (and compared it to my old mi4c). I found that /persist at my new mi4c didn't show mounted (it's mounted at the old one). I fired up some sensor test app, but it was never mounted, strange. I've attached both screenshots.
I tried to mount it manually from terminal, but it always ends up with invalid argument error or I/O error (see attachment). I need to know whether this might caused that problem. If anyone could shed some light, I'd really appreciate it.
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/
I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!
For everyone, make sure you download AONLY images, not AB !
_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.
Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.
@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help
Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.
Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?
so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping
Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,. https://androidfilehost.com/?fid=11410963190603878004 This method preserves IMEI and Baseband.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
##
I find the earliest of these metro pcs firms have a working vendor image.
https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/
I got bluetooth working today, and lots of clues where I found the fix...
####Bluetooth
Now that I can set it up from a clean install, here's the basics for Bluetooth...
You'll need files from the stock system image. You can use a backup to get these or also use simg2img with dd and 7zip, I'll make a zip installer when I have more time.
1. Copy the following files, from stock image directory "/system/etc/" to the "/vendor/etc/" directory on device
mixer_paths* (14 files)
audio_* (5 files)
media_profiles* (3 files)
Edit the file /system/etc/ld.config.26.txt
add this text to the very end of line 61 :/system/${LIB}/vnd-sp/hw
You're done! If you did everything as described, and it doesn't work, check the permissions of the files you add to vendor partition with other xml files in same directory. I did mine on the device while running, it worked in place, without rebooting device. The GSI system is new to me, however the "Same Proccess HAL(hardware abstraction layer)" voodoo can likely be configured correctly to fix screen and port other GSIs' to our device.
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
edit: 9/21 6pm
I think it's because mine is TMO variant.
Mattswad said:
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
Click to expand...
Click to collapse
Trying based on this now. I'll update you.. been trying for TOO LONG lol it's almost the same time you posted 2 days ago!
---------- Post added at 04:12 AM ---------- Previous post was at 03:45 AM ----------
I've been up all night trying to get either one to work.. I think I came close but I am stuck at a looping blank screen.
If you could step through a bit more for us? I'd REALLY love to have lineageOS on it.
mrbox23 said:
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
Click to expand...
Click to collapse
I have the Metro PCS version
Moto e5 Play XT1921-3
Mattswad said:
I have the Metro PCS version
Moto e5 Play XT1921-3
Click to expand...
Click to collapse
Ahh That is excellent news. I am about to take a focus supplement, and dive into trying again I'll let you know. I found a few more of MrBox23's posts and I think I MAYBE onto something.... wish me loads of luck. If it works for me I THINK it should work for you, but you might need to start with a diff image than me, or use a different boot and vendor img than I will.. not sure if I can help you find those files or not..
I'll be back later to update what I find.
Sorry I haven't been on for awhile. I'll go ahead and post my working vendor and boot images. On Google drive for download. Doing this will trash your speaker if you play music very loud at all, expect that. I do not understand how to fix it. Other than that it's a daily driver. I have been asked about encryption this and that.. You have to modify fstab.qcom within vendor partition. Also the TWRP for this device will format your data partition as ext4 while the ramdisk and init stack are configured for f2fs(if you try and boot with ext4 data, you get corrupted/encrypted data message). You have to change data partition back to f2fs in TWRP every time you format that partition. Or you could modify the TWRP image like I did to fix it permanent.
Files will be uploaded soon, make sure you understand what's involved before getting into this. I'll answer questions best I can, but this is for those who are dediced and willing to get down on some bootloops to figure it out, especially if you're not used to this sort of thing. Some magisk modules will cause bootloops, do those one at a time and gapps separately. I seriously recommend taking apart the firmware from OP and focus on getting to the aosp boot animation, THEN take care of verity/root and fstab. You're formatting data partition anyway you might as well successfuly backport the graphics first.
Vendor image TWRP backup, put this on its own with boot image. I keep it as vendor_fixed for easy reference. The fstab is already patched if you use mine.
Boot image TWRP backup, it is patched with magisk (19.4 likely) install magisk on your own anyhow. KEEP YOUR ORIGINAL VENDOR/BOOT PARTITIONS! There's stuff in there that you might want later on. Like the /vendor/etc/wifi folder for example or the pieces from the original ramdisk.
Vendor and boot with md5 sums to verify integrity.
https://drive.google.com/folderview?id=1-2KO_iRFTjLv6pyx-7Qmhi8kWZBpVIWD
Wipe everything, including internal storage(after backing up a working system).
Format data partition back to f2fs in advanced wipe options.
Get LineageOS 15.1 beta or RR you can find these here on XDA.
Flash Lineage zip its the old style zip install that copies idividual files, not an image, the boot image it installs needs to be replaced per instructions that follow.
Or flash RR system image from official repository link is found here on XDA.
If you flash a system image with TWRP you'll need to reboot back into recovery right after and resize the system partition in advanced wipe options or your system partion will be incorrect size afterwards, if flashing system with fastboot(recommended) then skip the resize instruction.
After you have a system installed, restore the vendor and boot images from the link. A good approach would be to backup your existing boot/vendor as a pair, then replace originals with downloaded images.
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me. I dealt with the fstab and boot verity patching AFTER I first saw the default Android boot animation. Once you see that plain white "android" with the slow moving left to right animation, your in. From what I can tell our device needs the older kernel within the boot image and the libs/binaries from the vendor image to get the screen working correctly. Your trading your working speaker, for a working screen. I have attempted to find exactly what it is that's different between the two, but it's over my head. Overall it's relatively stable, go easy with magisk modules, some of them will cause kernel panic(bootloop) use a recovery based magisk tool to disable offending module if this happens. Sometimes the device will not boot normally, usually this means the cache was erased(its okay) for whatever reason and I wait it out, otherwise I restore the vendor_fixd backup I made. I have not had gone back to stock ROM, however I have had to flash the vendor partition to get it booting, usualy happens if i flash a module or when updates break substratum theme.
Good luck!
Oh email me for quick response, within reason.
mrbox24 at gmail
Bonus screenshot and the TWRP 3.1.1 I modified with correct data format. If you have an sdcard with second partition it will show up as "linux" named after the chroot partition from mine.
Screenshot shows LSM kernel found here, yes it works.
mrbox23 said:
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me.
.
Click to expand...
Click to collapse
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
aka.bugle said:
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
Click to expand...
Click to collapse
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
mrbox23 said:
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
Click to expand...
Click to collapse
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
aka.bugle said:
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
Click to expand...
Click to collapse
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
I make custom scripts and have a custom build.prop, for example this.....
resetprop 'media.camera.ts.monotonic' 0
resetprop 'persist.camera.HAL3.enabled' 1
resetprop 'audio.deep_buffer.media' true
Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh
echo battery-charging > /sys/class/leds/charging/trigger
Which turns on the light, otherwise never used, in front of phone when charging.
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss with that issue.
I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.
Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.
Anyway, new mpcs files up soon.....
mrbox23 said:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
###bugle added### my Att is an xt1921-2, can't even unlock the bootloader... But 30 bucks isn't bad for a new screen and a new speaker. ###
Another thing of note is how i spoof the mac adress for wifi, this(and other things) .
Anyway, new mpcs files up soon.....
Click to expand...
Click to collapse
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
aka.bugle said:
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
Click to expand...
Click to collapse
My first "Android" phone was the HTC HD2 wich was actually a Windows phone that can boot linux from the sdcard. I came across it while learning how to get linux booting on laptops. I was fascinated with booting a mini linux on a portable device. I learned about Android and linux in that way, at the same time. Kernel, ramdisk, java machine, broadband cellular modem, and wifi radio in my pocket. I abandoned windows entirely, to this day lol
Right you are! @mrbox23 ... I've got camera on RRemix on the metro 1921-3!
I'm gonna put the lineage/no camera issue on the back burner for when I try to use your older boot/vendor img trick (boot Lineage 15.1) on the unlocked 1921-5.
(I only have a 1Mb/s dsl connection here, takes about 4-5 hours for a 1 gig file to dl)
So, for the Metro 1921-3, I can't find libeffects.so or even the soundfx folder to copy into. (studder fix)
Your script 2 files for media/camera and charge led, other than making them executable (0755? 0700?) will they be called (without any other mod) being in /data/adb/service.d ?
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
Click to expand...
Click to collapse
I pulled one out of my Att phone that is a james xt1921-2 but has a locked bootloader, all stock ... I used #getprop ro.build.fingerprint.. not sure if i should use this, or wait to see your build.prop...
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
Click to expand...
Click to collapse
All the best to you and yours in 2020. Meeeerrrry eXksMix, hic up'
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
mrbox23 said:
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
Click to expand...
Click to collapse
mediafix line 2... set or resetprop?
1 resetprop 'media.camera.ts.monotonic' 0
2 setprop 'persist.camera.HAL3.enabled' 1
what are these last lines in mediafix for?
16 resetprop net.dns1 1.1.1.1
17 resetprop net.dns2 1.0.0.1
and i'm guessing the deb.sh is for your wifi repeater? swap space in oem?
how is mpcs.prop called? where is its proper folder?
can you host a copy of libeffects.so ?
@mrbox23 Bluetooth working! check.
aka.bugle said:
@mrbox23 Bluetooth working! check.
Click to expand...
Click to collapse
something I just noticed here recently is that's all the audio output now. I can't test cellular calls, Hangouts only works when i restore that vendor path Back to where it was. My camera broke again to. I want to reach out to phh here or github.
Well that's a big bug, sorry. I've reverted the metro 1921-3 to stock for now, but on the positive side, I tried using your older boot/vendor imgs trick on the 1921-5 (Sprint)... and success! it boots Lineage 15.1 and bluetooth works, I haven't tried using the GSM Att Sim yet and still no camera, (I haven't tried your other camera recommendations yet.) One step closer for the 1921-5.
I have now test all. I have the Persist image over the, Orange Fox recovery and also with code over the TWRP recovery. I also test flash over fastboot and edl mode. (for edl mode my account don't have the premission to flash.....)
Only the gyro and accelerated was fixed by flash the persist image over the recovery.
So i have a broken promoxity and Brigthness Sensor.
Is there a way that ones can give me a Orange Fox backup of his Persist image?
My device ist the 3/32 Gigabyte Version when it is important.
Thanks for help :fingers-crossed:
No Man can help me?
Why don't you try testing if your proximity sensor is working or not with cpuz
I have tested and they don't work. On CPUZ not listed.
hmm even if it's broken it should still show in Cpuz.
Maybe try testing with other ROM
You have the same device? When yes can you backup for me the persist image? I have flash more than one time the original rom over miui flash tool
I have attached the backup. One more thing when I checked your attached image, I see that your accelerometer is of other name (or brand) and mine is BMI... Something. I request you to make backup of your current persist and I also want to say maybe your phone might not boot (maybe, I hope not). It's risky but give it a try. Good Luck!
A big thanks for it. The sensor will work after your backup. But than the other sensor goes down. Gyroskope and Accelerometer :silly:
Witch Version of redmi note 6 pro you have? My is 3/32 Gigabyte Version.
After flash the latest persist image from us all other works and promoxity goes down and light :silly:
I will test for flash the persist over twrp with the flash code after your backup. Hope this work or i must search for a user like you with right Version.
For now very big thanks now i know it is not damaged and i can awake the sensors.
My new list after your backup flash
Here is a list of my Sensor. When anyone have the same is it possible to give me a backup of his persist image over Orange Fox recovery?
Promoxity Sensor:
stk3x1x alsprx
Sensortek
Brightness:
stk3x1x alsprx
Sensortek
Gyroscope:
ICM20607
IvenSense
Magnetometer:
AK09918
AKM
Accelerometer:
ICM20607
IvenSense
Mine is 4/64 version but I think it should have been compatible with yours. Maybe different revision or something
---------- Post added at 08:34 AM ---------- Previous post was at 07:48 AM ----------
Anyways bro
It seems that flash tool ignors flashing persist so
Try this method take your persist.img if you have from fastboot ROM file and do as below:
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
That i have test. Simg2img don't work. Direkt over "dd if=" flash works also like Flash over Orange Fox. But the same result that the both sensor not work.
A big thanks for your answer and help.
Do tell us if you find any solution. It will help us all
I will make it. The easy way when other with same sensor give me a backup like you.
Hey bro I found this video on YouTube I recommend you to watch this
Thanks. This solution i have also tried no work for me.
I have now fix the issue
I have make a guide to fix it :
https://forum.xda-developers.com/redmi-note-6-pro/how-to/guide-repair-persist-image-sensor-crash-t4082147
HumanBoy23 said:
I have attached the backup. One more thing when I checked your attached image, I see that your accelerometer is of other name (or brand) and mine is BMI... Something. I request you to make backup of your current persist and I also want to say maybe your phone might not boot (maybe, I hope not). It's risky but give it a try. Good Luck!
Click to expand...
Click to collapse
Hi Bro i would like to talk about this personally, i have used your backup file for recovery some curropted file in my device actually it did worked well, but there is a problem which is solved by you only.
pls help me in this......!
vamsimec14 said:
Hi Bro i would like to talk about this personally, i have used your backup file for recovery some curropted file in my device actually it did worked well, but there is a problem which is solved by you only.
pls help me in this......!
Click to expand...
Click to collapse
What you want to do?
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Healthcare App works, too - without any issue. Thanks again! If I ever get TWRP installed on this device but that's another story...
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Thank @backroot,
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Great it works for you 2. Concerning saving I noticed I had the same issue. I almost never take pictures myself is why I haven't noticed myself. I got this resolved by installing myflir.apk again, without removing myflir app, from the following location:
/system/app/myflir
or
/system/priv-app/myflir
Hope this works 4u2.
Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?
backtoroot said:
Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?
Click to expand...
Click to collapse
I've noticed that too and have been searching how to resolve this but haven't been able to find a solution. I know it works on the original rom from Blackview.
How to install twrp?
1x23 said:
How to install twrp?
Click to expand...
Click to collapse
i got TWRP to install by treating the phone as if it had ramdisk.
fastboot devices
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
Hey, I'm running an eBay business, had a request to work on the BV9900Pro. I have ported a twrp build from the BV9900, but cannot test because I am not currently in possession of the device. Could you maybe test it for me?
1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
If you are trying to flash a GSI, you don't need it. You can do fastboot flash system GSI.img in the bootloader and it will flash. I have booted CAOS and LineageOS. Make sure you download the ab versions because the a only versions do not work for some reason. You could possibly do adb sideload in twrp afterwards for root.
[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Good afternoon and what a good afternoon that is.
I have accidentality formatted and downloaded stock ROM by SF Format tool on my BV9800pro phone. I was looking for ways to fix it, even instaled a custom rom.
I'm quoting this user because his file saved me. "MM-Myflir.zip" - so to anyone please make a copy and don't let it get lost.
Now I have again a working phone with thermal cam, that isn't crushing when taking a picture or anything.
Did any of You did it on a stock ROM after crushing it? I don't have much time to explain how I did it (and it took many approaches to do so). So I'll write what I did. I don't know it was the right way to approach it but it works and it's all that matters.
Thanks again
I'm a bit sad. That TWRP on my BV9800pro works only before booting for the first time to the system. I can't decrypt it even if I know the pin that I used.
So I made the stupid mistake of formatting and flashing stock ROM on my phone. Who knew, before having this problem that it will mess up my thermal camera.
Anyway what I did was, unlocking bootloader. Installed TWRP.IMG.
Before first boot to system I went to recovery mode. On my SD card I had my copy of MM-Myflir.zip, and it was decompressed to a folder in Windows.
All I did was transfer files from "lib64", "bin" and "app" folders to those on /system/app/Myflir /system/bin and /system/lib64.
I did not coppy those .sh files.
Now I didn't change any chmod on files, I also didn't use any "getenforce" on those files to make them enforced or permissive.
So here what happened. I didn't check if those files got replaced or not, but the one thing I wanted to replace was the Myflir.apk. I have forgotten to name it properly so it was like in the zip folder Myflir.apk and not Myflir-2.3.8.... (can't remember it whole, because I'm writing this on a bus).
After reboot there was no Myflir apk. That was the moment I understood my mistake. Installed es manager. Went to /system/app/bin directory and installed the app (no root). The app came up on desktop of phone, now it can be uninstalled. But the most important thing is that it WORKS!!!
I wonder if the only step that I could have made was add an app in the same location and to the above, or copying those files was necessary.
Maybe I'll check it out. But I think I'll leve it like this since all works.
Please report on your successes. I would like to know what it took for You.
I did test the phone. On newest stock rom. All above for me is not needed. I don't need to copy all those files. Only thing to copy is the Myflir.app.
But my phone is not formatted again. I lef the recovery partition for TWRP.
Again after booting first time and going trough all those windows. I didn't have my stock Myflir apk installed. So I installed after going to /system/app/Myflir-bv2.3.8...
That did the trick.
I won't go trough format restoring the Tee and google services by sw write tool again just to check if we all could do what I wrote in all my posts....
I hope it is a solution for all people that would like to stay by the stock rom.