I have tried many ROM/Kernal Combinations and none of them seem to support OTG. Am I doing something wrong?
OTG working in stock rom, have you tried?
matt040 said:
OTG working in stock rom, have you tried?
Click to expand...
Click to collapse
Yes OTG Works stock but not on any custom ROM
No. You aren't doing anything wrong. It's a known issue; enforcing selinux.
"usb_otg" folder is missing in root directory.
Yesterday I added the folder manually and went to recovery. OTG worked there, but the phone never booted up. Had to clean flash.
---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------
Mr.Ak said:
No. You aren't doing anything wrong. It's a known issue; enforcing selinux.
Click to expand...
Click to collapse
My phone is currently on Permissive SeLinux. Are you saying that setting it to Enforcing would solve the problem??
Update: changing SeLinux status doesn't help.
Rr gsi, aex pie gsi otg working.
Disclaimer - I am not responsible with anything that goes wrong while doing this procedure.
I am on stock and after flashing xposed my USB-otg stopped working.
So here is what i did-
Go to system/etc/permissions and find this file- "handheld_core_hardware.xml"
Add this line -
<permissions> <feature name="android.hardware.usb.host"/> </permissions>
Save the file and reboot.
It might work, though I haven't tried this method in any custom ROM.
Take a backup of that .xml file before editing just in case...
The method recommended on stack exchange didn't work atleast for oreo.
Not working, no otg
It's not an selinux problem. Im on enforcing and otg working fine. Maybe something has to do with the order of flashing.
1)rom
2)magisk
3)gapps
4)kernel
5)other mods
No working otg in pixal experience and rr roms
There are no otg support
---------- Post added at 05:33 PM ---------- Previous post was at 05:31 PM ----------
Yes there is no otg support on pixal experience and rr roms
farhanshaikh671 said:
It's not an selinux problem. Im on enforcing and otg working fine. Maybe something has to do with the order of flashing.
1)rom
2)magisk
3)gapps
4)kernel
5)other mods
Click to expand...
Click to collapse
I only flashed rom and gapps with havoc, no magisk or kernel but still no otg, do we need to flash magisk too?
Related
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
i am on zui 2.3.045
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
i am on zui 2.3.045 tell me full installation process if possible
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Can i flash in fastboot or install Lineage os recovery?
Mikuzukz1 said:
Can i flash in fastboot or install Lineage os recovery?
Click to expand...
Click to collapse
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
+∆bhijith said:
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
Click to expand...
Click to collapse
it's showing error that way
Mikuzukz1 said:
it's showing error that way
Click to expand...
Click to collapse
Even now? Even after rebooting to recovery via ADB?
+∆bhijith said:
Even now? Even after rebooting to recovery via ADB?
Click to expand...
Click to collapse
I don't know how to boot via adb ijust wiped all partitions in twrp
got it working finally....installed it over cm13.0 and done
Mikuzukz1 said:
got it working finally....installed it over cm13.0 and done
Click to expand...
Click to collapse
Wonderful ! Good to go for any 7.x.x rom now...
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Because i faced same problems before and searched in XDA and that is the solution available right now.
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
I think file is not completely downloaded...
Once same happened when I checked I chose wrong file wwhich was half downloaded.. Check it
i'm facing the same problem. i don't know how to use adb boot.
isn't there any other way.
also i checked the file was completely downloaded
and i'm on zui 2.5
I also have problem when flash nuclearom from cm13. I have some zuk devices but got problem with 2
First, it has bootloop
I have to flash China ROM then it works
I can flash CM 13
But up to 14 or 7.x will have bootloop again
Pls help
Basically i rooted systemlesly and changed my emojis to the IOS ones with an app on the playstore. Then i reset my phone because of reasons. Now i want to remove my root and get magisk and xposed. To do this i need to remove my SU root and flash magisk, however magisk will only flash with an unmodified system.
This is where my problem occurs. When i reset my phone my original emojis were removed, leaving me with the IOS emojis. I made no backup of my original emojis. When i click restore emojis on the app no emojis change, and when i install the nougat emojis from the app my system is still considered "modified"
Therefore, im asking if anyone has a boot.img of my Moto x style, as i think flashing that would fix it. I also think that if anyone has the original NotoColorEmoji.ttf file, i can replace it with mine and it could fix it aswell. If anyone has any of these 2 files it would be much appreciated ??
Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX
dzidexx said:
Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX
Click to expand...
Click to collapse
Trying to restore boot from SuperSU resulted in it saying uninstallation failed. I also tried looking through the general section and none that ive found have a boot.img file i can just flash.
Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX
dzidexx said:
Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX
Click to expand...
Click to collapse
Funny indeed ? That image doesn't have a -3 at the end, and mine does, so idk if it will work and i wanna be sure
For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.
dzidexx said:
For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.
Click to expand...
Click to collapse
Ive already uninstalled supersu, i just said no when it asked to restore ti stock boot because when i chose yes it said failed. The only backups i have are of marshmallow 18-8 and nougat, but with the changed emojis (pretty stupid on my part)
I also have no idea what u mean by boot(kernel)
Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.
dzidexx said:
Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.
Click to expand...
Click to collapse
Lol its fine. Well eventually i managed to install magisk. I downloaded the boot/sys backup from https://forum.xda-developers.com/mo...gust-2017-security-patch-nph25-t3673373/page3 and restored it via twrp, then flashed magisk and it worked
https://dl.twrp.me/s2/
allrockedout said:
https://dl.twrp.me/s2/twrp-3.2.0-0-s2.img.html
Click to expand...
Click to collapse
What are the changes, oh wait, can read here https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html :
What's new in 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Click to expand...
Click to collapse
Anyone tried yet?
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
mdio said:
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
Click to expand...
Click to collapse
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
I'm on le s3 working fine
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
is only for snapdragon or mediatek also?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
Did not try 3.2.1.0 yet, but 3.2.0.0 is running ok.
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
That is nice... but is there any Android 8 rom for S2 already???
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
EDIT: 3.2.1.0 Ok and running.
dziubson said:
is only for snapdragon or mediatek also?
Click to expand...
Click to collapse
This ist only for Snapdradon (the X52x Models)
---------- Post added at 06:16 AM ---------- Previous post was at 06:13 AM ----------
I installed it via TWRP app (RR-OS 5.8.5) on my X527 and it works very good
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Andy_04 said:
This ist only for Snapdradon (the X52x Models)
Click to expand...
Click to collapse
Sukkel21 said:
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Click to expand...
Click to collapse
If you can write, I assume you can read, can't you?
It doesn’t work on eui 5.9.028s I tried flashing no Luck, I tried booting without flashing didn’t work either. And when I try to boot into it it changes my oem unlocking from true to false so I don’t know how to install it.
Hi friends just now got xposed latest updated version for EMUI 8.0 and working fine. Yahooooo thanks @rovo89
link?
https://androidfilehost.com/?fid=746163614322267211
hey can u help me in installing twrp, I am getting the error again and again " failed remote partition length get the error "
frendzarena said:
hey can u help me in installing twrp, I am getting the error again and again " failed remote partition length get the error "
Click to expand...
Click to collapse
You are flashing/installing twrp in the wrong partition. Huawei changed name of the default recovery partition. Do some research bcz I forgot the new name for cmd command to flash.. (I think it's recovery_ramdisk.img or something similar instead of recovery.img)
---------- Post added at 11:44 AM ---------- Previous post was at 11:38 AM ----------
naveen00781 said:
Hi friends just now got xposed latest updated version for EMUI 8.0 and working fine. Yahooooo thanks @rovo89
Click to expand...
Click to collapse
I'm very curious.. Magisk was working but without any module support due to oem kernel restrictions. Can you tell how Xposed is faring with regard to this? Do modules work properly or do you get any bootloop?
puneetbhagat said:
You are flashing/installing twrp in the wrong partition. Huawei changed name of the default recovery partition. Do some research bcz I forgot the new name for cmd command to flash.. (I think it's recovery_ramdisk.img or something similar instead of recovery.img)
---------- Post added at 11:44 AM ---------- Previous post was at 11:38 AM ----------
I'm very curious.. Magisk was working but without any module support due to oem kernel restrictions. Can you tell how Xposed is faring with regard to this? Do modules work properly or do you get any bootloop?
Click to expand...
Click to collapse
Come to Telegram
https://t.me/joinchat/G2i160nl5GwMECHUc2ZeyQ
Hello, I have been trying to fix this oddly specific issue with my Moto G7 running LineageOS. I can make and receive calls fine, but I have issues receiving texts. I can send them, but replies are delayed from a few minutes to an hour or two. I am unsure of why this has happened, but I remember trying to install LineageOS for Micro G and noticing this after. However, I didn't happen to be texting much before this, so it may not be relevant.
Anyways, I went to Verizon twice and they confirmed there was no issue with the sim card. However, when they tried replacing it, the system didn't recognize it at all and it couldn't even make a phone call.
I am honestly stuck and I do not know where to go from here. I've tried finding stock firmware but the issue persists after flashing what I THINK is the correct firmware and reinstalling. I really don't want to have to pay for a new phone (one that would likely be way more expensive than this one), so please give me anything I could work with.
Go back to stock 10, make calls and texts (including MMS), and then twrp, los17.1, gapps, root and start over
What's your phone model?
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
Xt1962-1 from Amazon is mine
---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------
https://mirrors.lolinet.com/firmware/moto/river/official/
---------- Post added at 11:49 AM ---------- Previous post was at 11:41 AM ----------
May have to erase modem partitions and then reinstall stock 10 using "adb shell" command while in fastboot mode:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I have the same model, I'll try your solution now.
HueyT said:
Go back to stock 10, make calls and texts (including MMS), and then twrp, los17.1, gapps, root and start over
Click to expand...
Click to collapse
After installing the firmware, my device does not boot and stays on the unlocked bootloader warning. I can easily reinstall LineageOS, but my issue still persists.
CheeseESimp said:
After installing the firmware, my device does not boot and stays on the unlocked bootloader warning. I can easily reinstall LineageOS, but my issue still persists.
Click to expand...
Click to collapse
Do you mean that stock 10 won't boot? Any errors while installing stock 10? Which batch file did u use to automate all the fastboot commands?
Fastboot batch file
Unzip for bat file, put file in adb folder which should have all the files of stock ROM zip file that's been unzipped, and run it at dos prompt
https://forum.xda-developers.com/moto-g7/how-to/to-stock-relock-boot-loader-google-fi-t3966959
Is a guide to flashing stock rom (your rom will be different but the steps are similar except Q rom has 10 sparsechunks while PIE rom only has 9)
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Is a guide to flashing via LMSA
HueyT said:
https://forum.xda-developers.com/moto-g7/how-to/to-stock-relock-boot-loader-google-fi-t3966959
Is a guide to flashing stock rom (your rom will be different but the steps are similar except Q rom has 10 sparsechunks while PIE rom only has 9)
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Is a guide to flashing via LMSA
Click to expand...
Click to collapse
Okay I went back to stock and found that the issue was not present. I shall report this to the LineageOS devs or something. Is there anything else this could possibly be?
Once VZW drops CDMA and adopts GSM, this prob will be gone (1/2021)