Galaxy Watch on LineageOS - Galaxy S 5 Q&A, Help & Troubleshooting

Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
You can now "download" and "upload" build.props. Between adb pull and adb push, you need to edit the downloaded build.prop like I wrote above.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
EDIT: on lineageos 18 you need to edit two more files:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Restart into system after this.
The 3(5) build.prop edit will do the work and Galaxy Wearables will start and you can connect your watch.
Important info again after every OTA or manual LineageOS update, you need to edit build.props to continue using your watch (watch won't connect after OS update at all, without build.prop edits)

liquidraver said:
Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
You can now "download" and "upload" build.props. Between adb pull and adb push, you need to edit the downloaded build.prop like I wrote above.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
EDIT: on lineageos 18 you need to edit two more files:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Restart into system after this.
The 3(5) build.prop edit will do the work and Galaxy Wearables will start and you can connect your watch.
Important info again after every OTA or manual LineageOS update, you need to edit build.props to continue using your watch (watch won't connect after OS update at all, without build.prop edits)
Click to expand...
Click to collapse
Fantastic. I just installed LineageOS 18.1 on my Tab A6 and I Galaxy Wearable app didn't want to work but thanks to your post I managed to get it fixed. Great work. Thanks

Thx, works perfectly on a Galaxy S5 (klte) with LineageOS/eOS based on Android 11 with Magisk-Root.

liquidraver said:
Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
Sie können jetzt build.props "herunterladen" und "hochladen". Zwischen adb pull und adb push müssen Sie die heruntergeladene build.prop bearbeiten, wie ich oben geschrieben habe.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
BEARBEITEN: Auf Lineageos 18 müssen Sie zwei weitere Dateien bearbeiten:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Starten Sie danach das System neu.
Die Bearbeitung von 3(5) build.prop erledigt die Arbeit und Galaxy Wearables wird gestartet und Sie können Ihre Uhr anschließen.
Nochmals wichtige Informationen: Nach jedem OTA- oder manuellen LineageOS-Update müssen Sie build.props bearbeiten, um Ihre Uhr weiterhin verwenden zu können (die Uhr stellt nach dem Betriebssystem-Update überhaupt keine Verbindung her, ohne build.prop-Bearbeitungen)
Click to expand...
Click to collapse
gilt das auch für 19.1

Bernd1712 said:
gilt das auch für 19.1
Click to expand...
Click to collapse
this also applies to

Hi, everytime when i wanted to push the changed build.prop file to system/vendor/odm/etc adb says :
adb: error: stat failed when trying to push to /system/vendor/odm/etc: Not a directory
But the build.props from the other directories work. Can someone help me? And sorry for my english...
Thanks
Edit: I'm using an S5 klte with official Lineage 18.1

Related

[HOWTO] - Deodex & ZipAlign any ROM - More RAM, More Space, More Speed!

Hi all,
I have managed to deodex and zipalign my rooted I8190XXALL2_I8190OXXALL1 ROM in my smartphone, so thought i would share it here.
Follow all the instructions carefully. I will not be held responsible in any manner if your smartphone doesn’t boot up or gets bricked due to not following the instructions.
Please make sure -
1. Your smartphone is already rooted (flash one of the rooted rom's founded here)
2. Download and install Busybox Installer latest version.
3. Make sure you already have Java SE Development Kit and Android SDK installed on your computer.
Install them to the default choice on the C: drive.
4. You should also have a basic knowledge of ADB.
Required Downloads -
1. xUltimate version 2.4.2 – Link. You may have to Google for the correct version to download. Extract it to C:\xUltimate-v2.4.2.
Instructions –
1. Connect your smartphone to your computer. (Make sure you have selected USB debugging in Settings>Applications>Development)
2. Open a command prompt as administrator. Wait for Window to appear.
3. Change Directory to C:\xUltimate-v2.4.2
4. Launch main.exe.
5. If everything goes well xUltimate should recognize the smartphone and make a connection. You should now see a list of options.
6. Select option (1) pull /system/app. Wait until it completes.
7. Select option (2) pull /system/framework. Wait until it completes.
8. Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder.
If you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” see Note below.]
9. Then select option (4) Deodex /system/framework. Wait until it complete.
10. Now Exit from xUltimate.
11. Disconnect and connect your smartphone. Your PC should open a Window for you to view your files.
12. Go to C:\xUltimate-v2.4.2 folder and copy “done_frame”, and “done_app”, and move them to the root of the internal sdcard. Don’t copy them to your external sdcard
14. Now safely eject your smartphone from the PC.
15. Click on My Computer and find the directory where Android SDK is installed (on my PC it is in C:\Program Files (x86)\Android\android-sdk\. Then go to the ‘platform-tools’ folder in it. Right click on any free space in folder while pressing shift key. Select ‘open command prompt here’.
16. Reconnect the smartphone to your PC in USB debugging mode.
17. Now enter the following commands (if you are using adb shell in su for the first time, keep smartphone screen on).
adb shell (this should recognize your device)
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
18. Your smartphone will reboot and perform an automatic Android update. You have now deodexed/zipaligned the ROM on your smartphone.
NOTE
I only tried this on my I8190 with ROM I8190XXALL2 - I8190XXALL1 BTU Rooted.
At Step 8, (running Option 3), if you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” then xUltimate can’t find the PATH to your ‘java’ command.
To add the location of Java to your PATH do this:
Right-click on ‘My Computer’ (or Computer for Vista) and choose ‘Properties’.
Navigate to the ‘Advanced’ tab (or for Vista/7/8, click 'Advanced System Settings’ on the left, then find the ‘Advanced’ tab)
Click ‘Environment Variables’
Under System Variables, find 'Path' and click Edit...
DO NOT ERASE OR REPLACE THE CONTENTS OF THIS. YOU ARE SIMPLY GOING TO ADD TO IT.
At the very end of the text field, add a semicolon [ ; ] and add the location of java.exe.
On my Windows 64-bit system this is in “c:\program files\java\jdk1.7.0_06\bin” . For others it might be "c:\program files\java\jre7\bin". I seem to have java.exe in both locations but only the first one worked for the batch file in xUltimate.
Then ‘Okay’ that to save the addition and come out of ‘Properties’
Batch files will now be able to find java.exe without you modifying the batch file.
*************************************************************************************
If for some reason you can't deodex and zipalign apps and framework with xUltimate, ive uploaded them for your use:
done_app
done_frame
They were deoxeded and zipaligned from ROM I8190XXALL2 - I8190XXALL1 BTU Rooted
*************************************************************************************
I followed the above and it works. I used Root Explorer to check my smartphone and all the .odex files have gone, i have more memory available, and smartphone seems faster!
infected_
Well you'll get more ram and deode xing opens a whole new of theming possibilities but it won't be as fast as odexed rom even though zipaligned !
nikufellow said:
Well you'll get more ram and deode xing opens a whole new of theming possibilities but it won't be as fast as odexed rom even thigh zipaligned !
Click to expand...
Click to collapse
I get more RAM thats what i like and more space..! i dont care about theming... but i guaranty that the phone seems faster deoxed and zipaligned...
infected_ said:
I get more RAM thats what i like and more space..! i dont care about theming... but i guaranty that the phone seems faster deoxed and zipaligned...
Click to expand...
Click to collapse
I do not doubt you mate i just posted what i knew from my experience ! Stay with deodexed Rom for few more days/weeks and then temporarily try coming back to odexed stock and you'll know the difference
Sent from a hybrid phablet !
i just didn't find a way no recompile system.img in windows.... or else i had made a pretty cool rom and fast whit android kitchen 0.208... :silly:
Don't give up we need Roms
Sent from a hybrid phablet !
i can compile cm or aokp if u want
Yes please.
Sent from my GT-I8190 using xda premium
Shapeshift said:
i can compile cm or aokp if u want
Click to expand...
Click to collapse
can you decompile system.img from this latest 4.1.1 rooted rom I8190XXALL2_I8190OXXALL1_BTU and replace /system/app/* and /system/framework/* with the deodexed and zipaligned apk's:
done_app
done_frame
and then compile into odin flashable *.tar.md5 ?!
infected_ said:
Hi all,
I have managed to deodex and zipalign my rooted I8190XXALL2_I8190OXXALL1 ROM in my smartphone, so thought i would share it here.
Follow all the instructions carefully. I will not be held responsible in any manner if your smartphone doesn’t boot up or gets bricked due to not following the instructions.
Please make sure -
1. Your smartphone is already rooted (flash one of the rooted rom's founded here)
2. Download and install Busybox Installer latest version.
3. Make sure you already have Java SE Development Kit and Android SDK installed on your computer.
Install them to the default choice on the C: drive.
4. You should also have a basic knowledge of ADB.
Required Downloads -
1. xUltimate version 2.4.2 – Link. You may have to Google for the correct version to download. Extract it to C:\xUltimate-v2.4.2.
Instructions –
1. Connect your smartphone to your computer. (Make sure you have selected USB debugging in Settings>Applications>Development)
2. Open a command prompt as administrator. Wait for Window to appear.
3. Change Directory to C:\xUltimate-v2.4.2
4. Launch main.exe.
5. If everything goes well xUltimate should recognize the smartphone and make a connection. You should now see a list of options.
6. Select option (1) pull /system/app. Wait until it completes.
7. Select option (2) pull /system/framework. Wait until it completes.
8. Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder.
If you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” see Note below.]
9. Then select option (4) Deodex /system/framework. Wait until it complete.
10. Now Exit from xUltimate.
11. Disconnect and connect your smartphone. Your PC should open a Window for you to view your files.
12. Go to C:\xUltimate-v2.4.2 folder and copy “done_frame”, and “done_app”, and move them to the root of the internal sdcard. Don’t copy them to your external sdcard
14. Now safely eject your smartphone from the PC.
15. Click on My Computer and find the directory where Android SDK is installed (on my PC it is in C:\Program Files (x86)\Android\android-sdk\. Then go to the ‘platform-tools’ folder in it. Right click on any free space in folder while pressing shift key. Select ‘open command prompt here’.
16. Reconnect the smartphone to your PC in USB debugging mode.
17. Now enter the following commands (if you are using adb shell in su for the first time, keep smartphone screen on).
adb shell (this should recognize your device)
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
18. Your smartphone will reboot and perform an automatic Android update. You have now deodexed/zipaligned the ROM on your smartphone.
NOTE
I only tried this on my I8190 with ROM I8190XXALL2 - I8190XXALL1 BTU Rooted.
At Step 8, (running Option 3), if you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” then xUltimate can’t find the PATH to your ‘java’ command.
To add the location of Java to your PATH do this:
Right-click on ‘My Computer’ (or Computer for Vista) and choose ‘Properties’.
Navigate to the ‘Advanced’ tab (or for Vista/7/8, click 'Advanced System Settings’ on the left, then find the ‘Advanced’ tab)
Click ‘Environment Variables’
Under System Variables, find 'Path' and click Edit...
DO NOT ERASE OR REPLACE THE CONTENTS OF THIS. YOU ARE SIMPLY GOING TO ADD TO IT.
At the very end of the text field, add a semicolon [ ; ] and add the location of java.exe.
On my Windows 64-bit system this is in “c:\program files\java\jdk1.7.0_06\bin” . For others it might be "c:\program files\java\jre7\bin". I seem to have java.exe in both locations but only the first one worked for the batch file in xUltimate.
Then ‘Okay’ that to save the addition and come out of ‘Properties’
Batch files will now be able to find java.exe without you modifying the batch file.
*************************************************************************************
If for some reason you can't deodex and zipalign apps and framework with xUltimate, ive uploaded them for your use:
done_app
done_frame
They were deoxeded and zipaligned from ROM I8190XXALL2 - I8190XXALL1 BTU Rooted
*************************************************************************************
I followed the above and it works. I used Root Explorer to check my smartphone and all the .odex files have gone, i have more memory available, and smartphone seems faster!
infected_
Click to expand...
Click to collapse
Make it for pll or rename the thread "INFO OR HOWTO"
Great info thx m8
Sent from my GT-I8190 using XDA Premium App
The done_app link is broken..
JoFury said:
The done_app link is broken..
Click to expand...
Click to collapse
just tried it now... its working.
https://dl.dropbox.com/u/17735355/done_app.rar
https://dl.dropbox.com/u/17735355/done_frame.rar
Is this SIII Mini specific or Any phone and any rom?? THAN-Q.
NHS2008 said:
Is this SIII Mini specific or Any phone and any rom?? THAN-Q.
Click to expand...
Click to collapse
any device running on an odexed Rom
why fix it if it ain't broken ?
nikufellow said:
any device running on an odexed Rom
why fix it if it ain't broken ?
Click to expand...
Click to collapse
Thank you for the answer...
Sent from infected_ s3 mini i8190
nikufellow said:
any device running on an odexed Rom
why fix it if it ain't broken ?
Click to expand...
Click to collapse
Even the L version?
i have a 4.1.2 Faria ROM in my S3 galaxy mini. I can do this?
generalriden said:
i have a 4.1.2 Faria ROM in my S3 galaxy mini. I can do this?
Click to expand...
Click to collapse
I don't advise you... faria's rom is already zipaligned.
infected_ said:
I don't advise you... faria's rom is already zipaligned.
Click to expand...
Click to collapse
I have problem from
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Click to expand...
Click to collapse
and after searche on Google find another thread like this and i see diferant methode can you pleas see and explain i try with this http://forum.xda-developers.com/showthread.php?t=1688211 method this night and feed if worked but if you see we have diferant commande now i know need to change
from
#mount -o remount,rw /dev/block/mmcblk0p9 /system
to
#mount -o remount,rw /dev/block/mmcblk0p22 /system
i try and feed if worked later
thank for tut
hi, need some help. when i try to deodex, i got error "Error occured while loading boot class path files. Aborting. bla bla bla"
please help me

Kindle Fire 7.2.8 (old Hardware Release)

Dear all, just for Info: The RootQemu 1.0 was not working for my Device; Error: permission denied to the /data/local.prop.
So I tried the Standard Method 1 with Root_with_Restore_by_Bin4ry_v33
But I think this was a bit tricky; at first u should test the adb Connection first with adb shell and after this close the Server. Than start the script in the same CMD shell. Ignore the error:
I had the error: C:\Users\username\Documents\ROOTEN\Kindle\Root_with_Restore_by_Bin4ry_v33\ric konnte nicht gefunden werden
After the successfull run, the superuser app was not in my 'carousel' and not listed in Apps on my device. But I found it with search in Apps und also the Root Switch in Es File Explorer was working perfectly. Thanks for the Tools.

ROM for Moto x style Brasil edition dual sim

i am having Moto X style Brazil edition dual sim Retla 6.0
i have tried many Nougat​ Roms Like AICP ., RR , but none of them detected my Sim Card
plz any one help me and tell me about which Rom i Could flash on This varient
i Shall be very thankful .
I have the same problem @malkuu, have you fixed your phone?
richardtrle said:
I have the same problem @malkuu, have you fixed your phone?
Click to expand...
Click to collapse
Yes i have fixed that
richardtrle said:
I have the same problem @malkuu, have you fixed your phone?
Click to expand...
Click to collapse
Follow this
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
malkuu said:
Follow this
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
Click to expand...
Click to collapse
i did that but it didn't work for me
custom roms like AICP and lineage can't rocognize my simcards
what should i do then?
ehsan_991 said:
i did that but it didn't work for me
custom roms like AICP and lineage can't rocognize my simcards
what should i do then?
Click to expand...
Click to collapse
bro i am also using AICP rom u must edit build.prop correctly like when u add lines under radio section dont forget to add a blank space between radio section and the next section

build.prop please upload

HI , im new here but i know a long time ago about this community, anyway, someone can help me uploading a build.prop of the moto g5 plus, i modify it and well... :/ i try to fix it whit a adb on the command promp but my phone still stuck on the boot, and i sorry about this topic maybe can help on the future
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
willclein said:
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
Click to expand...
Click to collapse
Thanks in advance for the reply, i can solve the problem flashing the firmware beacuse i have some troubles on the console using adb, but this happening beacuse i dont give it the correctly permisons, but i want share the way to fix that problem as well, therefore i bring the solution on the command prompt on windows, the solution is very simply but helpfull
step by step, there are been taked on the siteweb TAS beacuse i'm a new user and i cant post url's of the other sites
///
Setup ADB and Fastboot on your PC.
Boot your Android device into TWRP recovery.
Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
Connect your device to the PC with an authentic USB cable.
Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
└ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
Download and install Notepad++ software on your PC.
Open the build.prop file on your PC using the Notepad++ program.
Edit the build.prop file as per your requirement and save it on the PC after making the changes.
Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
thanks and i hope this can help someone else
The number one issue I see with people modifying build.prop (myself included) is forgetting to fix the permissions once you are done. My preferred method for editing it is using BuildProp Editor. It makes editing easy as well as makes setting the permissions extremely easy without having to use ADB. Best part is you can do this on the fly instead of having to use your PC.

My Moto X Style is not recognizing any SIM after installing Nougat

Hello there guys, I have a brazilian Moto X XT1572, I had to reset the android to apply OTA update, because the ota required the android build version MPHS24.49-18-8, I think that I installed the european version, because the SIM card was not being recognized after I reseted the phone, I thought that maybe once on nougat and flashing the modem images from LAT release would fix this, however no help. Can someone help me?
Flash full stock 6.x LAT. @richardtrle
Have u tried any custom rom like AICP , RR i also have RETLA brazil edition these roms doesn't recognizes my sim cards
tagsexx said:
Flash full stock 6.x LAT. @richardtrle
Click to expand...
Click to collapse
@dzidexxI, I have flashed XT1572_CLARK_RETLA_DS_6.0_MPHS24.49-18-16_cid12 firmware, however when I apply OTA the symptoms reappear, no sim, I am thinking about downgrading til 7.0 firmware is released
Try this... it worked for me
richardtrle said:
@dzidexxI, I have flashed XT1572_CLARK_RETLA_DS_6.0_MPHS24.49-18-16_cid12 firmware, however when I apply OTA the symptoms reappear, no sim, I am thinking about downgrading til 7.0 firmware is released
Click to expand...
Click to collapse
Hi, I'm using crDroid 3.6 (latest) and whenever I update the ROM, I got the same issue that none of my two sims are recognized. I follow the steps below on every update:
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
@muneeb_baig I tried doing exactly what u said, no avail
Thanks though
richardtrle said:
@muneeb_baig I tried doing exactly what u said, no avail
Thanks though
Click to expand...
Click to collapse
See if this helps:
https://forum.xda-developers.com/showpost.php?p=71248170&postcount=22
muneeb_baig said:
Hi, I'm using crDroid 3.6 (latest) and whenever I update the ROM, I got the same issue that none of my two sims are recognized. I follow the steps below on every update:
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
Click to expand...
Click to collapse
Do you have RETLA Dual Sim or other variant ?
RETASIA_DS
malkuu said:
Do you have RETLA Dual Sim or other variant ?
Click to expand...
Click to collapse
Always started with RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7, but upgraded to CrDroid 3.4 to now 3.6.
muneeb_baig said:
Always started with RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7, but upgraded to CrDroid 3.4 to now 3.6.
Click to expand...
Click to collapse
Okay
​
muneeb_baig said:
Hi, I'm using crDroid 3.6 (latest) and whenever I update the ROM, I got the same issue that none of my two sims are recognized. I follow the steps below on every update:
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
Click to expand...
Click to collapse
oooooo my f**kin goodness thanks u made my day now I am able to use any custom rom on my moto x style RETLA dual sim Brazilian edition without a problem sim working like charm bro :laugh:
malkuu said:
​oooooo my f**kin goodness thanks u made my day now I am able to use any custom rom on my moto x style RETLA dual sim Brazilian edition without a problem sim working like charm bro :laugh:
Click to expand...
Click to collapse
Nice to hear that it helped
muneeb_baig said:
Nice to hear that it helped
Click to expand...
Click to collapse
Worked like a magic :fingers-crossed:
malkuu said:
​ now I am able to use any custom rom on my moto x style
Click to expand...
Click to collapse
So which ROM you are now on? Brazilian Nougat, Official or Custom?
muneeb_baig said:
So which ROM you are now on? Brazilian Nougat, Official or Custom?
Click to expand...
Click to collapse
Custom rom AICP NIGHTLY
muneeb_baig said:
Hi, I'm using crDroid 3.6 (latest) and whenever I update the ROM, I got the same issue that none of my two sims are recognized. I follow the steps below on every update:
NOTE: This assumes that you have already setup ADB and Fastboot on your PC.
1- Boot your Android device into TWRP recovery.
2- Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
3- Connect your device to the PC with an authentic USB cable.
4- Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
+ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
5. Open the build.prop file on your PC using the Notepad++ program.
6. Edit the build.prop file and add following lines to the Radio Section (or anywhere for that matter) and save it on the PC after making the changes.
This is the MAIN STEP TO FIXED FOR GET DUAL SIM
ro.fsg-id=emea_dsds
persist.radio.multisim.config=dsds
ro.telephony.ril.config=simactivation
7. Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
8. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
9. Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
That’s it.
Click to expand...
Click to collapse
Hi.
I have flashed my moto x style mt1572 single sim using this guide:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
and this stock rom:
XT1572_CLARK_RETLA_DS_7.0_NPHS25.200-15-8_cid12_subsidy-DEFAULT_CFC.xml.zip
after flashing complete i get no sim slot detected. i was installed for dual sim device. then i installed the correct one:
XT1572_CLARK_RETLA_7.0_NPH25.200-15_cid12_subsidy-DEFAULT_CFC.xml.zip
i dont know what is the correct model for my device, but since there is just 2 stock firmware with android 7.0 and i was have this version in my OTA update, so i think this is the correct ROM.
but after installing this one, i got same problem. my baseband not found and IMEI is unknown.
i tried any solution except this. if i want to use this solution how should i edit my build.prop for single sim device?
sorry for my english.
thanks.
yasser93 said:
thanks.
Click to expand...
Click to collapse
Possible answer for you given here, in the thread you created. Please refrain from cross posting.

Categories

Resources