Related
help, xposed not working
Hi.
i cant download the Xposed framework.
i have slimsaber running on a OnePlus One.
i can't share a logcat, because when i reboot after flashing the zip, i get a popup: unfortunately, com.google.android is stopped.....
what can i do?
my phone is not even rebooting normally (i get infinity number of pop-ups)!!
and my adb drivers are all fine, when i restore from backup via TWRP, everything is fine and the adb is working...
PLEASE HELP I NEED XPOSED SO BAD.
@rovo89 maybe u can help!
If you can't live without xposed then change roms. Other than that your post makes no sense.
its alpha, he said flash if you want to risk bootloops..
hopefully you used recovery to backup your rom & data, because you're most likely going to have to flash your rom again.
rhystagram said:
its alpha, he said flash if you want to risk bootloops..
hopefully you used recovery to backup your rom & data, because you're most likely going to have to flash your rom again.
Click to expand...
Click to collapse
i did a backup.
everything is fine now, but i want xposed.
the .jar file is a must?
because i didnt install it.
maybe it's the reason that its not working?
what am i doing wrong?
19dolev said:
what am i doing wrong?
Click to expand...
Click to collapse
probably nothing, it isnt working on my lg g3 either, others reported its working for them on the same device, so i'm in the same boat as you... BUT i understand it's the first release for lollipop, its expected to have issues & i'm patient enough to wait for more advanced releases before i start asking why it isnt working for me.
at this point of time, you're spamming.
.jar for is for module developers.
btw, some modules work for some roms but not for others, so it may be your rom, might be my problem too, but ee have to wait for a better than alpha release.
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.
Hello everyone
Some might know me from the V30... Also got my hands on a V40 now (which I will also give my best to develop for).
I'm currently searching for people who are capable AND willing to test different things.
With that I mean:
- You know how to take logs (logcat, dmesg)
- You know how to recover from a soft brick (either how to get into TWRP for example, or in really bad cases fastboot or flashing a kdz)
- You know how to follow orders
I currently have a (somewhat decendly) working TWRP build (cant decrypt stock encryption atm).
GSIs are a complicated thing, because of not only vbmeta but also because of our 8.1 vendor (Pie GSIs work, if you remove some sepolicies from their system, Oreo GSIs dont have that issue)
What I would need more people to test for:
- stock decryption
- trying out different ways when something (doesnt) boot (e.g. need to flash magisk for xy to not crash to fastboot)
and so on
After everything is somewhat stable (I had to reflash a kdz today, as somehow nothing, no twrp in either slot, or restored stock rom didnt wanna render anything anymore, even though usb/adb worked just fine)
Also working on LOS for this device btw (but thats far more work in progress)
If you wanna be part of this upbringing, reply here, and I'll message you via PM the details.
PS: Having Telegram would be very beneficial.
I volunteer for this. Happy to see you step up for our forgotten device.
How did you reflash the KDZ?
I`m also interested in testing.
onslaught86 said:
How did you reflash the KDZ?
Click to expand...
Click to collapse
In my case i used LG Bridge, at first it complained that MTP wasnt running, but after clicking a few times ok it was fine with that lol
but i read in another thread that a lgup_cmd is able to flash kdzs to the v40
I think I can participate in the test, I have a V405US ROOT phone。
Please forgive me for my bad English. :）
In +1
Hi, how you rooted LG V40?
Any movement on this?
Evilmonstertruck said:
Any movement on this?
Click to expand...
Click to collapse
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
SGCMarkus said:
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
Click to expand...
Click to collapse
Any update is a good update. I appreciate all the work your doing. I know it's not easy. Thanks again
I can test out twrp and or ROM! Best regards.
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Edit : Anyone has an idea to fix this? NO PHONE / NO ESL on QPST
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Edit: If you are hard bricked and can not enter EDL, you will need to buy the EDL cable from Amazon they are cheap, like $5 or if the phone is seen from ADB you can get to EDL ( 9008) with this command : adb reboot edl
tsongming said:
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Click to expand...
Click to collapse
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
The War Profiteer said:
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
Click to expand...
Click to collapse
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
@The War Profiteer
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Just choose the reboot to EDL option
tsongming said:
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Click to expand...
Click to collapse
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
The War Profiteer said:
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
Click to expand...
Click to collapse
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
tsongming said:
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
Click to expand...
Click to collapse
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone ?
The War Profiteer said:
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone
Click to expand...
Click to collapse
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
tsongming said:
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
Click to expand...
Click to collapse
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
The War Profiteer said:
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
Click to expand...
Click to collapse
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
tsongming said:
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
Click to expand...
Click to collapse
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
The War Profiteer said:
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
Click to expand...
Click to collapse
Anytime brother, you have definitely helped me before as well
A heads up: It works on stock miui while not working on pixel experience. Please write on this thread if anyone gets it working on any other custom roms.
Edit: Apparently custom roms don't have the required tools to use the software, only stock roms will let you to modify your efs.
tsongming said:
Anytime brother, you have definitely helped me before as well
Click to expand...
Click to collapse
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
The War Profiteer said:
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
Click to expand...
Click to collapse
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
tsongming said:
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
Click to expand...
Click to collapse
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
The War Profiteer said:
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
Click to expand...
Click to collapse
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
tsongming said:
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
Click to expand...
Click to collapse
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
The War Profiteer said:
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
Click to expand...
Click to collapse
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
phonexpert_alex said:
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
Click to expand...
Click to collapse
Thank you for additional info, surely will help a lot to my search. I'm using PE CAF too (sadly, CAF will be cancelled).
First of all, I thought PE wasn't compatible with WFC, but your statement has confirmed that it's working, so the problem is on my side.
The problems I'm guessing that could be about ROMs and/or kernels are:
1- They may be unable to recognize/read/process a modified EFS and they may be reading only modem. I've merged the proprietary files for enabling VoWiFi, which were officially extracted from a SDM845 device that is officially supported by carrier, to the EFS using QPST. It was supposed to work on MIUI, and it did when I tested it. I created a backup of EFS and did a clean install of PE CAF, restored EFS from the backup and it didn't work. I also tested the backup with a clean MIUI setup and it did work, so I don't think there is an issue about the backup or restoration process since I used the same TWRP version.
2- Diagnostics port will be enabled with "# setprop sys.usb.config diag,adb" command, but since the kernel or the ROM doesn't have the interface to establish the communication between the host and the device, I was unable to check or edit the EFS partition if everything is OK.
I'm here to look for suggestions at the moment. Modifying modem image may be dangerous since it can be signed by the manufacturers in order to prevent any modification, which can lead to an unrecoverable bricks, and I don't know what to modify and how to do it.
Thanks, again. Pardon me if I did any grammar mistakes which will lead to misunderstandings or will make the post completely unintelligible.
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
kawala8888 said:
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
Click to expand...
Click to collapse
Same as on Android 12. That was the one with the issue decrypting in custom recovery.
Can't you just fix boot.img with Magisk and then fastboot flash it?
hyperboarean said:
Can't you just fix boot.img with Magisk and then fastboot flash it?
Click to expand...
Click to collapse
Yep.
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Clawsman said:
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Click to expand...
Click to collapse
Wait the days until you are unlocked, in case something borks during that procedure.
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Clawsman said:
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Click to expand...
Click to collapse
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
hyperboarean said:
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
Click to expand...
Click to collapse
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Clawsman said:
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Click to expand...
Click to collapse
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
hyperboarean said:
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
Click to expand...
Click to collapse
well, it seems "not worth it". until an official TWRP is released.
And if i decide flash boot.img/Magisk or TWRP, mtk will restore my device back to its locked/stocked state?