Hi,everyone!!
So I am a first timer in such stuff,Anyways,i was looking to flash lineage os 13 rom and hence tried to install TWRP v3.0.2.Since there isn't a dedicated thread or such,I had to try generic MT6582 TWRP.
So i had rooted using kingoroot and flashed a twrp from droidadda using flashr.I had a gray screen with little flickering when i restarted and after that the screen was inverted.Touch left and right side on screen is pressed and vice versa.Same with up and down.Currently on TWRP 3.0.2 with lineage os 13.Been using Vysor to navigate the device.Can navigate device and use root explorer and such
Any help will be appreciated.
ar7711 said:
Hi,everyone!!
So I am a first timer in such stuff,Anyways,i was looking to flash lineage os 13 rom and hence tried to install TWRP v3.0.2.Since there isn't a dedicated thread or such,I had to try generic MT6582 TWRP.
So i had rooted using kingoroot and flashed a twrp from droidadda using flashr.I had a gray screen with little flickering when i restarted and after that the screen was inverted.Touch left and right side on screen is pressed and vice versa.Same with up and down.Currently on TWRP 3.0.2 with lineage os 13.Been using Vysor to navigate the device but since the wifi set up part came im stuck on that front too as the inverted nature is confusing
Any help will be appreciated.
Click to expand...
Click to collapse
Anyone knows a solution?I tried to find the script.bin file however i still cant find it and im stuck.
bump need help urgent
your touch is not inverted, your screen is inverted!
if the screen is inverted only on the OS (Lineage):
* enter recovery -> adb reboot recovery
* mount system -> adb shell twrp mount system
* remount system as rw -> adb shell mount -o rw,remount /system
* pull /system/build.prop -> adb pull /system/build.prop
* search for ro.sf.hwrotation
* change the value by 180 (eg. 0 to 180; 90 to 270, 180 to 0, 270 to 90)
* save and push it back to /system/build.prop -> adb pull build.prop /system/build.prop
* make sure the permissions are right (0644) -> adb shell chmod 0644 /system/build.prop
* reboot -> adb reboot
if the screen is also inverted on the recovery mode, you have to search for the build.prop of the recovery and edit that in a similar fashion
brunolalb said:
your touch is not inverted, your screen is inverted!
if the screen is inverted only on the OS (Lineage):
* enter recovery -> adb reboot recovery
* mount system -> adb shell twrp mount system
* remount system as rw -> adb shell mount -o rw,remount /system
* pull /system/build.prop -> adb pull /system/build.prop
* search for ro.sf.hwrotation
* change the value by 180 (eg. 0 to 180; 90 to 270, 180 to 0, 270 to 90)
* save and push it back to /system/build.prop -> adb pull build.prop /system/build.prop
* make sure the permissions are right (0644) -> adb shell chmod 0644 /system/build.prop
* reboot -> adb reboot
if the screen is also inverted on the recovery mode, you have to search for the build.prop of the recovery and edit that in a similar fashion
Click to expand...
Click to collapse
Doing that (ro.sf.hwrotation 180) only makes my screen upside down, as i said the screen orientation is fine however the touch is reversed.
Related
I recently acquired an htc flyer. I also own a galaxy tab 7. I noticed that everything on the flyer's screen seems smaller than that on the galaxy tab, suggesting it has a lower default lcd density than the tab which has 240 as default. I ask because on the tab, adjusting to a lower lcd density often causes some apps from the market to become incompatible with the device. doe this mean that the flyer will sometimes encounter this due to its default lcd density?
Flyer LCD density should be 160
!!!ATTENTION!!! -Do this only if u got Problems and know what your are doing by ur own risk- !!!ATTENTION!!!
Hi,
maybe it helps u if u got some issues.
1.Boot into Android
2.Open CMD with Administrator rights
3.cd in to folder where ur adb - fastboot (Android sdk) files
4.Start following comands in cmd:
$ adb pull /system/build.prop
Open the file with Notepad++ (Windows users). Find the line starting with ro.sf.lcd_density and change the whole line to:
ro.sf.lcd_density=160 (if its not DEFAULT 160) <----Then save&exit file
$ adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
$ adb push build.prop system/
$ adb shell mount -o remount,ro /dev/block/mmcblk1p2 /system
5.Reboot ur device
Gratz your DONE!
Now u got Default DPI 160 for your Flyer.
Had Problems with changing DPI to 120 on Flyer and this helps me to get back in to normality
Cheers
So I'm an idiot. Anyway, I recently installed cyanogenmod with CWM recovery (on a Nexus 7) and decided to try one of the largest grids for the lock screen security. Needless to say it was soon forgotten. I've tried the gmail reset but it says the details are incorrect even though I can sign in with them on my PC. My guess is that it can't connect to gmail for authentication due to the firewall I'm using.
Edit: Solution
Factory reset from CWM, that's it.
RoberGalarga said:
Factory reset from CWM, that's it.
Click to expand...
Click to collapse
Not the solution I was aiming for.
Fortunately I found http://forum.xda-developers.com/showthread.php?t=1800799
However this does not work for cyanogenmod as they use an additional system. I had no knowledge of this beforehand but a comment on the above post led me to believe something was different. I decided to pull /data/system folder so I could investigate further. I found cm_gesture.key which after looking it up, I found out it's cyanogenmods additional key file.
I decided to remove this file using the same method as the above post and it worked perfectly. After a reboot the pattern screen is still there but any input is correct.
Mini Cyanogenmod 10.1.2 pattern unlocking guide:
If ADB won't work from android reboot into CWM recovery (other custom recoveries may work). Open a CMD (ADB will need to be installed and setup).
Enter the each of the following:
Code:
adb shell rm /data/system/gesture.key
Code:
adb shell rm /data/system/cm_gesture.key
Code:
adb reboot
It should reboot into android and now any pattern will be correct. You should now go into settings and reconfigure your lock screen.
This works if you only have/delete /gesture.key
works on 4.4.2
Trying to make this work on CWM 13. It doesnt, any tips? forgot my 6x6 lockscreen which is also invisible...
Revome the unlock pattern! [CM13.0 tested]
Cryorus said:
Trying to make this work on CWM 13. It doesnt, any tips? forgot my 6x6 lockscreen which is also invisible...
Click to expand...
Click to collapse
FINALLY I HAVE A SOLUTION!
Version 1 (Custom Recovery):
------------
Get the updated version of TWRP (twrp.me). Flash it via Odin or whatever you use and boot into it (Vol Up + Home + Power).
1) go to Advanced > File Manager
2) then go to '/data/system'
3) press on 'gatekeeper.password.key' > Delete > Swipe to Confirm
4) repeat 3) with 'gatekeeper.pattern.key'
5) Reboot & be happy!
Version 2 (Android Debugging Bridge - adb):
-------------------------------------------------------
Just follow these steps:
1) make sure your device shows up here:
Code:
adb devices
2) restart adb as root:
Code:
adb root
3) start the device-shell:
Code:
adb shell
4) make sure to have su access:
Code:
su
5) go to the 'system' directory in the 'data' folder:
Code:
cd /data/system
6) remove the pattern:
Code:
rm gatekeeper.password.key
7) remove the password sequence:
Code:
rm gatekeeper.pattern.key
8) exit the shell:
Code:
exit
9) reboot to be happy again:
Code:
adb reboot
That's it! Hope I was able to help you!
~ Kerskes ~
Awesome. Thanks for sharing your research.
Kerskes said:
FINALLY I HAVE A SOLUTION!
Version 1 (Custom Recovery):
------------
Get the updated version of TWRP (twrp.me). Flash it via Odin or whatever you use and boot into it (Vol Up + Home + Power).
1) go to Advanced > File Manager
2) then go to '/data/system'
3) press on 'gatekeeper.password.key' > Delete > Swipe to Confirm
4) repeat 3) with 'gatekeeper.pattern.key'
5) Reboot & be happy!
Version 2 (Android Debugging Bridge - adb):
-------------------------------------------------------
Just follow these steps:
1) make sure your device shows up here:
Code:
adb devices
2) restart adb as root:
Code:
adb root
3) start the device-shell:
Code:
adb shell
4) make sure to have su access:
Code:
su
5) go to the 'system' directory in the 'data' folder:
Code:
cd /data/system
6) remove the pattern:
Code:
rm gatekeeper.password.key
7) remove the password sequence:
Code:
rm gatekeeper.pattern.key
8) exit the shell:
Code:
exit
9) reboot to be happy again:
Code:
adb reboot
That's it! Hope I was able to help you!
~ Kerskes ~
Click to expand...
Click to collapse
Thanks a ton man !
Acrylate said:
Not the solution I was aiming for.
Fortunately I found http://forum.xda-developers.com/showthread.php?t=1800799
However this does not work for cyanogenmod as they use an additional system. I had no knowledge of this beforehand but a comment on the above post led me to believe something was different. I decided to pull /data/system folder so I could investigate further. I found cm_gesture.key which after looking it up, I found out it's cyanogenmods additional key file.
I decided to remove this file using the same method as the above post and it worked perfectly. After a reboot the pattern screen is still there but any input is correct.
Mini Cyanogenmod 10.1.2 pattern unlocking guide:
If ADB won't work from android reboot into CWM recovery (other custom recoveries may work). Open a CMD (ADB will need to be installed and setup).
Enter the each of the following:
Code:
adb shell rm /data/system/gesture.key
Code:
adb shell rm /data/system/cm_gesture.key
Code:
adb reboot
It should reboot into android and now any pattern will be correct. You should now go into settings and reconfigure your lock screen.
Click to expand...
Click to collapse
Thanks man i was wondering and worried that i would have to reset my phone again .
wajeehuzkhan said:
Thanks man i was wondering and worried that i would have to reset my phone again .
Click to expand...
Click to collapse
Too late for me, already reseted my phone
I'm on lineage
After a softbrick I deleted these two files.
not I can pass the lockscreen again! nice!
now I can't set a new lockpattern...
How can I fix this?
sejmand said:
I'm on lineage
After a softbrick I deleted these two files.
not I can pass the lockscreen again! nice!
now I can't set a new lockpattern...
How can I fix this?
Click to expand...
Click to collapse
Did you manage to find any solution? I'm on LG G5 and get an FC when I try to open Lock screen settings.
Hassaan Masroor said:
Did you manage to find any solution? I'm on LG G5 and get an FC when I try to open Lock screen settings.
Click to expand...
Click to collapse
Finally, I did a hardreset with wipe data partition. After that I use a pin and never had the problem again...
(Do not remove files, rename them... Remember to see beforehand "ls -l" - access permissions and owners.)
With Lineage OS 14.1-20170607-nightly I succeded with as root:
Code:
mv /data/system/locksettings.db /data/system/locksettings.db_disabled
+ two subsequent reboots.
Settings are available and functional after it.
P.S.
The following was done before the trick above, but I'm not sure final permissions should be exactly as below (I did certain moves before it, but finished with the following):
Code:
# chown system.system /data/system/gatekeeper.pa*
# chmod 660 /data/system/gatekeeper.pa*
# ls -l /data/system/gatekeeper.pa*
-rw-rw---- 1 system system 0 2017-06-13 20:40 /data/system/gatekeeper.password.key
-rw-rw---- 1 system system 58 2017-06-13 20:40 /data/system/gatekeeper.pattern.key
Removing-renaming of the files will remove the pattern and fully unlock screen... and will break Settings app functionality (not able to set up new lock of any type). If files are back with these permissions - the pattern is back.
The following is definitely so, sure:
Code:
# ls -lh /data/system/locksettings.db
-rw-rw---- 1 system system 20K 2017-06-13 12:26 /data/system/locksettings.db
P.S.S. Ideas have been found here - https://forum.xda-developers.com/showthread.php?t=1800799&page=15
Hi Kerskes,
Thanks for the solution. It does work also on my hlte phone with Linage 14.1.
But I am seeing only one problem which is addressed by others as well.
That is Settings crashes everytime I want to set new security setting for lockscreen.
Do you have any proposals or solutions?
Also I would request Admin to set this as unsolved or open detach to new thread for the above issue.
Kerskes said:
FINALLY I HAVE A SOLUTION!
~ Kerskes ~
Click to expand...
Click to collapse
---------- Post added at 08:50 AM ---------- Previous post was at 08:32 AM ----------
Thanks Anker,
Your solution did wonderfully worked on Linage 14.1 over HLTE Phone.
I restarted after renaming locksettings.db using SolidExplorer (With Root). Then I needed one restart and Settings did responded properly for Lock Screen Pattern setting. I also observed that the gatekeeper.pa* files which I had deleted were also created again but they has only 600 file permissions. Soon I modified the file properties in SolidExplorer with proper 660 file permissions. Once again thanks a lot.
I apologize for my stupid previous post which I posted without seeing your solution.
B Anker said:
(Do not remove files, rename them... Remember to see beforehand "ls -l" - access permissions and owners.)
Click to expand...
Click to collapse
Dropped my phone this morning (~80cm) & screen cracked; now I've got no response from touchscreen at all.
LG Optimus G
CWM 6.0.4.7
Cyanogenmod 11
all data backed up
I can access ADB shell when it's in recovery mode but once booted up it just connects as MTP device and ADB doesn't see it (nor does fastboot). I've tried an OTG cable with mouse, no luck there. I have a bluetooth mouse but no way to pair it!
Do I just have the wrong driver in windows? Device manager says "LGE Android MTP Device" because I had (at some point earlier) installed the LG usb drivers and recovery tool.
You don't have debugging on is my best guess, but if you're just trying to pull some files you can do this through recovery. Or is there another reason you want adb on while in os?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You don't have debugging on is my best guess, but if you're just trying to pull some files you can do this through recovery. Or is there another reason you want adb on while in os?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct, I don't believe it was enabled in android os. I was hoping to use Screencast or ADB or something to control my phone until I get a chance to order a new screen
you can try this
boot to recovery
use adb to pull build.prop
Code:
adb pull /system/build.prop /location/on/pc
add these lines (or change accordingly if present)
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
now push it back
Code:
adb push location/on/pc/build.prop /system/build.prop
and fix permissions in recovery or
Code:
adb shell
su
chmod 644 build.prop
or try just editing it in a shell like
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
then reboot
either method i would suggest doing a backup in recovery first, just in case, but should be fine
best of luck!
Thank you! I will try when I get home
demkantor said:
you can try this
boot to recovery
use adb to pull build.prop
Code:
adb pull /system/build.prop /location/on/pc
add these lines (or change accordingly if present)
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
now push it back
Code:
adb push location/on/pc/build.prop /system/build.prop
and fix permissions in recovery or
Code:
adb shell
su
chmod 644 build.prop
or try just editing it in a shell like
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
then reboot
either method i would suggest doing a backup in recovery first, just in case, but should be fine
best of luck!
Click to expand...
Click to collapse
Here's what I got:
Code:
G:\android sdk\sdk\platform-tools>adb devices
List of devices attached
01a9a0f610c750f6 recovery
G:\android sdk\sdk\platform-tools>adb root
adbd is already running as root
G:\android sdk\sdk\platform-tools>adb pull /system/build.prop C:\testing\
remote object '/system/build.prop' does not exist
G:\android sdk\sdk\platform-tools>
so then I tried:
Code:
G:\android sdk\sdk\platform-tools>adb shell
~ # ls
ls
boot external_sd property_contexts storage
cache file_contexts recovery sys
charger fstab.geehrc res system
data init root tmp
datadata init.rc sbin ueventd.geehrc.rc
default.prop initlogo.rle888 sd-ext ueventd.rc
dev internal_sd sdcard
emmc mnt seapp_contexts
etc proc sepolicy
~ # cd system
/system # /system # ls -R -l
ls -R -l
.:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
./bin:
Then I found default.prop in ./ (http://pastebin.com/RFyhMJe9) and added the first two lines you suggested (it already had usb.config=mtp,adb) but rebooted and no USB debugging. Booted back into recovery and the lines I added were gone.
You may need to mount /system r/w first as its protected its possible that it won't allow you to pull it otherwise... Can't recall
Default.prop I believe will often do this upon reboot as its part of the ramdisk. To fully edit this try looking at this
http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
But really you just need to look for the build.prop
Just follow the part where I said edit in shell from above, this should work
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You may need to mount /system r/w first as its protected its possible that it won't allow you to pull it otherwise... Can't recall
Default.prop I believe will often do this upon reboot as its part of the ramdisk. To fully edit this try looking at this
http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
But really you just need to look for the build.prop
Just follow the part where I said edit in shell from above, this should work
Click to expand...
Click to collapse
I'll try that. Is there a find command I could use to find build.prop? I'm out of ways to look for build.prop, as I couldn't find it in /system or /sys.
It should be in /system , never seen it elsewhere. Maybe grab the build.prop from the ROM you are running (like direct from a download of the ROM, just unzip) edit this and push it in place, then fix permissions
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You may need to mount /system
Click to expand...
Click to collapse
Bingo! looked in CWM recovery settings and found "Mount /system"
Once I did this, I could see all the files in /system, including build.prop. I updated build.prop and checked file persmissions (they were already correct, wierd). Rebooted, now ADB can see it:
Code:
>adb devices
List of devices attached
01a9a0f610c750f6 unauthorized
and when I try to run screencast (https://code.google.com/p/androidscreencast/) I get a bunch of java errors, including this:
Code:
java.io.IOException: device (01a9a0f610c750f6) request rejected: device unauthorized. Please check the confirmation dialog on your device.
If I try to send a keyevent, I get a similar message:
>adb shell input keyevent 3
Code:
error: device unauthorized. Please check the confirmation dialog on your device.
Realized this meant my PC wasn't authorized, so I followed these instructions: http://stackoverflow.com/questions/...ithout-previous-usb-pairing/15747430#15747430
and now I'm authorized!
Glad it worked out for you! Check out droid explorer and android commander, both should work well for you and have some more advanced options besides just screen cast
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks again, demkantor! I'll give those a try, since screencast only displays on my PC, none of the controls seem to work, and running commands like below are pretty slow:
Code:
adb shell input swipe 390 1100 650 1100 [I] (unlock swipe)[/I]
adb shell input keyevent 3 [I](home button)[/I]
[CODE]
EDIT:
Tried those but they both seem depricated and old. I got AirDroid which isn't exactly remote control but allows reading/writing of texts among other things, and works whenever you get on wifi.
I am trying to do the same thing but I do not know how to append the line I got from my PC. As well on my LG e970 which has not been ever authorized I keep getting the error that there is no directory for /data/misc/adb/adb_keys and I have CWM too in which I have also mounted the data partition. Please help!
I have installed stang5litre rom some time ago via flashfire since I am on of1. Recently I wanted to make a build prop edit to add apn settings and the damn buildprop app cleared the build prop leaving it empty, which I did not realize. I then rebooted and now you can guess I cant reboot. I have looked into a flashable zip with the build prop included but it has not worked. I get package footer is wrong and signature it wrong despite me signing the flashable zip. So what can I do?
I have full ADB access and can push sideload updates my issue is the footer and signature issue. Is there a way to sideload the buildprop without getting these errors? Can I flash the org verizon buildprop from there rom to make this boot? Any ideas?
I believe I have an almost solution, see below.. The problem is my device is unauthorized when I try to do adb devices. This is while allowing the device to boot in without the screen coming on. I can not see the dialog to allow me to confirm adb access. Is there another way?
Here are the steps to restore the build.prop settings.
1. Download android developer kit.
2. Connect tablet to (in my case I used a Mac) computer via USB Cable.
3. Boot tablet to "blank" screen.
4. Open Terminal and enter the following commands.
* cd /path/to/adb
* ./adb root #runs adb as root.
* ./adb devices #lists all connected devices, confirm your device is listed. If it is not, try disconnecting and reconnecting the USB Cable.
* ./adb shell #allows you to run a remote shell interactively.
* su #enters su.
* mount -o remount rw /system #mounts /system as rw.
* cd /system #puts you in the system directory of your device.
* ls -all #lists all the files in your devices /system directory. Look for a backup file of build.prop. If one exists, look at it's contents with less.
* less build.prop.bak #shows the contents of your backup build.prop file (the name of this file may very).
5. If you have a backup of your build.prop (and its' contents are correct), you can restore it using the following commands. If you do not have a backup, you will have to edit the file using vi (see step 6).
* mv build.prop build.prop.bad #renames build.prop.
* mv build.prop.bak build.prop #restores your backup of build.prop (replace build.prop.bak with your backup file name. If there is a space in the name, type \ before the space and hit tab. It should auto complete).
* exit #until you are back to your computers adb directory.
6. If you don't have a backup of your build.prop file, you will have to edit it with vi.
* vi build.prop #edits the file using vi (you will have to google how to edit this file with vi if you don't know how; I'm not doing a tutorial on vi ).
* exit #until you are back to your computers adb directory.
7. Reboot your device! You should be back in business!!!
8. Enjoy!
I'm screwed arnt I? I tried just about everything I could find for days since I posted this. Without USB debugging enabled I can not recover my data. Not with ADB, not with Kies, not with odin, NOTHING. My phone is rooted but that does not seem to matter now. I tried every recovery app out there including dr.fone and nothing can get it back. I guess I just have to reflash to stock and loose it all uh?
=== Moto G Power (2020) XT2041-4-SS FIRMWARE: Android 10 "SOFIA_RETAIL_QPMS30.80-109-5" ===
1)
systemrw_1.32 (./makesysrw.sh size=50) => error code 73 (either way auto or manual)
2)
sysrw_repair_v1.32 (USB stick Ubuntu Mate 21.4) => Successfully created patched super image at /media/ubuntu-mate/Drive-C/sysrw_repair/img/super_fixed.bin
3)
"fastboot flash super super_fixed.bin" (in FASTBOOTD) => was sent 8 sparses SUPER out of 8, no errors
4)
restarted phone => OK
5)
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor
6)
weird things started appear...
build.prop 0 Kb and copying saved earlier file build.prop to /system does not help it stays empty... I could change permissions in properties but it didn't help build.prop empty and nothing I could do... I repeated system rw remount but now I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...
7)
flashed super image again in FASTBOOTD => same results: build.prop empty and nothing you can do with it
8)
flashed super image again now just in BOOTLOADER but weirdly in bootloader there were only 6 sparses SUPER out of 6 (in FASTBOOTD there were 8 sparses out of 8) => same results: build.prop empty and nothing you can do with it
9)
flashed and restored my FIRMWARE: SOFIA_RETAIL_QPMS30.80-109-5 (without erasing: boot, recovery, metadata and user data partitions) phone is fine but ROOT the same RO
-----------------------------------------
P.S. I was afraid to flash SUPER to slots A and B like:
fastboot flash super_a super_fixed.bin
fastboot flash super_b super_fixed.bin
and I didn't do it even though I remember some guy mentioned that it helped with two slots...
I didn't take a chance... I just got my phone back after being dead bricked from Motorola service... in the bricked phone i had perfect touch screen in TWRP (3.5.0_10) damn! in the phone of the same model they send me back TWRP touch screen does not work... (looks like the different drivers are set for the touch screen)
I've run into the same issue with the Self-Erasing Build.prop. Did you ever find a work-around? Maybe patching the build.prop on pc in SUPER and reflashing the Patched.Super.img would work?