Related
Solved. Thanks!
Anyone wanna help? -.-
xGary said:
So I did some modding (unfortunately) to the framework-res.apk file and it worked the first time and a few other times but then I changed something and now when I turn on the phone it freezes at the "Sony Ericsson" screen before the logo. What do I do?
I tried pushing the backup framework file but it says "failed to copy framework-res.apk to /sdcard/framework-res.apk: Permission denied
however, when I use adb devices, it does show my device as being attached.
So what can I do now?
Edit
I was also able to pull files...
Also tried manually putting the framework-res.apk in the sdcard and then using adb to copy it to the framework folder. Doesnt work. Saids that the directory cannot be open for read. I guess the device cant read the SD card until it boots up
Also, if you are replying, please stay on the thread. I will probably comment back ASAP
Click to expand...
Click to collapse
Hey... are you sure that you've got your phone rooted? I mean sure pulling files work irrespective if you are rooted or not, but in order to replace files under the /system filesystem you've gotta have root and remount it as read/write.
Happen to me too, for the exact same reason. I had to reformat the phone... I simply re-rooted the damn phone.
cp /system/bin/sh /system/bin/rootsh
chmod 6755 /system/bin/rootsh
Try using this script before trying to push your framework back on
Well it was rooted and I already flashed it and re rooted it. However, I have three questions
1) Should I update from the v24 to 26?
2) I have a x10a, after running step 3 my phone still says its an x10i with baseband version of 1.1.28
3) And those apps that were supposed to be installed in step 2 didnt go so well. I could install them manually with ADB right?
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
It is present on my phone.
Do you need me to upload it for you?
Yes please! That might fix my problem! For some reason I dont have it and I think that is why my phone is seen by my computer but is always offline. Hopefully this will work!
Sent from my MB860 using Tapatalk
Anyone that has the adbd service in /sbin/adbd, could you please upload it here for me. I would really appreciate it!
Sent from my MB860 using Tapatalk
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Thanks a lot, I will let you know how it goes. Hopefully it works.
Sent from my MB860 using Tapatalk
clubtech said:
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Click to expand...
Click to collapse
Holy crap, it worked!!! My device is not offline any more and adb is working!! For four days now I have been trying to figure this out. Thank you for the file!!
One weird thing though, after a reboot the file is gone and I have to copy it over to /sbin again to get it working. Now I need to figure out why it gets removed on a reboot. Anyone have any ideas?
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
It gets removed because the ramdisk extracts it to that directory on boot
designgears said:
It gets removed because the ramdisk extracts it to that directory on boot
Click to expand...
Click to collapse
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
airbillion said:
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
Click to expand...
Click to collapse
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
Yes a bunch: acpi_available, alsactl, apm_available, badblocks, blkid, blockdev.....vol_id. There are about 40 files, but the adbd seems to disappear after a reboot and my early usb enumeration does not work. I think it is because it adbd gets removed on a reboot. Is there a way to keep it in there after a reboot that you know of or to get usb early enumeration working?
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
NguyenHuu said:
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
Click to expand...
Click to collapse
Thanks, i will look into this.
What about adding it in then changing permissions on it to disable the system from deleting it?
Sent from my SAMSUNG-SGH-I897 using XDA App
Changing your adbd permissions back to stock may help, as the file in the .zip won't have the proper permissions. Do this:
Code:
chmod 0750 /sbin/adbd
The one in the zip will be 0777, which gives everyone read and write access, which isn't set normally.
Atrix ADB offline issue
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
I have the same problem! Any solutions found?
How do it get this onto a phone that is not rooted, so that I can root it?
Thanks.
Atrix Rooted Deodexed ADB Offine Issue
When I received my Atrix I used the program superoneclick to root the atrix and then Fully Deodexed, i enabled the sideloading of apps with the same program.
I then went to my external sd card where I had saved the apk's for titanium backup and adfree and installed them without any issues.Over the next few days I used my phone without any problems at all.I had some apk's on my computer that i wanted to push to my atrix so i tried to connect via adb and my phone was seen as offline no matter what computer, usb port or cable I used.I then thought that a hard reset might solve the issue so I went to the recovery menu and performed a system restore.This did not fix the problem.For days I tried to figure out how to fix it, until I realized that the adbd service in /sbins was missing so i got a copy and placed it in /sbins and adb worked again. However, after a reboot the adbd file is removed from /sbin and to get adb working again I have to place my copy of the adbd service back into the folder.The problem now though is that early usb enumeration in the recovery does not enable adb, the phone just boots normally after about 5 seconds.Thank you for your help and interest in my problem.Mroadster
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
I really wish I could tell you how I did it, but I was going through this very same issue with loss of ADB after doing the SuperOneClick with a subsequent reset. After resetting the device I was not able to obtain ADB.
I got to a point where I decided I was going to just get rid of root and try to remove Superuser however every time I ran the script to remove it, it was still there. The script was running but no connection to ADB resulted in no execution.
I reset the device a couple more times and uninstalled all Motorola drivers from my computer. When I went through the initial setup and driver install again, it installed all the drivers like normal including the ADB communication. I confirmed ADB via "adb devices" and I everything seemed good to go.
I then used DG's aRoot to root once again without any issues at all. Every time I attempt to use ADB, it now connects flawlessly.
I have this problem as well and it is driving me insane as I bit off more than I could chew just trying to root my phone... Hopefully we can figure something out in the future.
the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.
adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).
try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...
dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?
I could not find any resource here, to provide a step-by-step guide for going from ATT 4.5.91 rooted, with Unlocked Bootloader to the latest 4.5.141 without bricking. I put this together myself and tested it on my own Atrix. Use at your own risk!
It's kind of a technical guide, but you really get to learn about your phone doing it this way. I did assume you know some basics about Android and Atrix that you could learn from Swiftks great guide: http://forum.xda-developers.com/showthread.php?t=1154600
Thanks to all of the resources here on XDA, that I used to pull this info together.
REQUIREMENTS:
- ATT Atrix 4.5.91 with Unlocked Bootloader
- Custom Recovery (Romracers or Rom Manager)
PRE STEPS:
- Take a full Nandroid Backup with CWM
- Backup your apps with TiBu
- Backup Call and SMS Logs with My Backup Root
Files Needed:
- 4.5.141 Full SBF - http://atrix.tk/4.5.141/ or http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
- preinstall.img - for root - http://forum.xda-developers.com/showpost.php?p=15023022&postcount=2
- adb and moto-fdastboot - get anywhere
- Portable SBF Tool - http://forum.xda-developers.com/showthread.php?t=1059643
- .37P Radio zip (N_01.77.37P_usa_att_12dec2011.zip) - http://forum.xda-developers.com/showthread.php?t=1339047 or http://forum.xda-developers.com/showpost.php?p=22399253&postcount=171
- Nebtop for Webtop over HDMI - http://forum.xda-developers.com/showthread.php? t=1404625
Steps:
- Open full 4.5.141 SBF with Portable SBF Tool, to extract the smg files. Move the SMG folder, before closing the tool.
- Power off phone
- Power on while holding down the vol button
- Scroll to Fastboot with the vol down, vol up to select fastboot
- Connect to PC
- Cleanup:
moto-fastboot erase system
moto-fastboot erase boot
moto-fastboot erase webtop
- Flash new boot, system, webtop, preinstall
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
moto-fastboot flash preinstall preinstall.img
- Wipe and reboot
moto-fastboot -w
moto-fastboot reboot
- Turn on USB Debugging
- Root
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH
pm install /preinstall/Superuser.apk
*Make sure to accept the Superuser prompt on the phone when using it the first time.
- sqlite
cp /preinstall/sqlite3 /system/bin/sqlite3
chmod 6755 /system/bin/sqlite3
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
- Radio
adb push N_01.77.37P_usa_att_12dec2011.zip /mnt/sdcard/
reboot into recovery and apply from sdcard
wipe cache
wipe dalvik cache
reboot
- Recover apps with TiBu
- Restore Call log and SMS data with My Backup Root
- Remove Annoying SDCARD Mount sounds
adb shell
su
setprop persist.service.mount.playsnd 0
- Install the Nebtop Apk for Webtop over HDMI
**Another method to try, using CWM: http://forum.xda-developers.com/showpost.php?p=22997305&postcount=22
Will this work?
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
I had a Froyo phone, that I unlocked, rooted, and then installed a custom ROM.
I unlocked and rooted my phone with this link. And I am running Alien ROM #4 de-blurred. I never realized that doing that keep you from getting the OTA announcements till this big ball of snot dropped (4.5.141)
I'm also downloading NottachTrix 1.2.1. I thought if I change my ROMS with one that has the new updates, I would be ok, but again, nervous as hell about this.
As long as you are unlocked, you can simply download the 2.3.6 SBF and use sbf_flash -x to turn it into .IMG files. Then you can rename and flash the files with moto-fastboot and reboot into 2.3.6.
* CG59.img -> boot.img code:moto-fastboot flash boot boot.img
* CG60.img -> system.img code:moto-fastboot flash system system.img
* CG61.img -> webtop.img code:moto-fastboot flash webtop webtop.img
Make sure to wipe and reboot as said by OP and you will be fine after this. I have tried this on my unlocked Atrix and it works fine. Root however you want after and all is well.
fastboot method?that's safe,i tried many times.
zoness said:
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
Click to expand...
Click to collapse
I'm happy to report that everything went perfectly for me!!! I'm so happy this worked. Thank you!
Getting the SBF tool was a little annoying having to sign up for another site where the OP found this app he doesn't own, so I made a mirror:
http://www.mediafire.com/?wo8g5hgeo9jtedq
Thanks a bunch Uncle!
Jason_Thames said:
As long as you are unlocked, you can simply download the 2.3.6 SBF and use sbf_flash -x to turn it into .IMG files. Then you can rename and flash the files with moto-fastboot and reboot into 2.3.6.
* CG59.img -> boot.img code:moto-fastboot flash boot boot.img
* CG60.img -> system.img code:moto-fastboot flash system system.img
* CG61.img -> webtop.img code:moto-fastboot flash webtop webtop.img
Make sure to wipe and reboot as said by OP and you will be fine after this. I have tried this on my unlocked Atrix and it works fine. Root however you want after and all is well.
Click to expand...
Click to collapse
Hi,
Where can I find sbf_flash -x? can I just rename it? or where exactly do I run this? under adb, rsd lite? any help appreciated thanks?
And also I was confused...how to the sqlite3 in the procedures? is that another program I need to have?..
---------- Post added at 04:44 AM ---------- Previous post was at 04:14 AM ----------
I have trouble following these steps:
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
with cg60 and cg61
image is too big, use 0x10000000 bytes chunks FAILED <remote: <00000006>>
so what does this mean?
I definitely tested this on my ATT atrix without any issues. Spent a few hours putting this together mostly for myself, but thought i would share it.
zoness said:
you posted this a few days ago, but with all the bricking issues you have no posts saying, hey this works. Not trying to dismiss you here, but I'm very nervous about doing this update. I can' afford to brick my phone, but i really need the new updates 'cause ATT is messing with the towers in this area.
I had a Froyo phone, that I unlocked, rooted, and then installed a custom ROM.
I unlocked and rooted my phone with this link. And I am running Alien ROM #4 de-blurred. I never realized that doing that keep you from getting the OTA announcements till this big ball of snot dropped (4.5.141)
I'm also downloading NottachTrix 1.2.1. I thought if I change my ROMS with one that has the new updates, I would be ok, but again, nervous as hell about this.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
The filesize issue probably means that you were using the wrong fastboot. You need moto-fastboot, since it was specifically modified to allow for larger file sizes. Dont use the regular fastboot. As far as sqlite3, it is part of the preinstall and you will need it for some of the last steps, but you can skip those if you dont care for them.
vastelectron said:
Hi,
Where can I find sbf_flash -x? can I just rename it? or where exactly do I run this? under adb, rsd lite? any help appreciated thanks?
And also I was confused...how to the sqlite3 in the procedures? is that another program I need to have?..
---------- Post added at 04:44 AM ---------- Previous post was at 04:14 AM ----------
I have trouble following these steps:
moto-fastboot flash boot CG59_0x00000130.smg
moto-fastboot flash system CG60_0x00000140.smg
moto-fastboot flash webtop CG61_0x00000150.smg
dunno what i'm doing wrong..
after I extracted to folder.. my files don't have the same names as above.. it's only cg59.smg, cg60.smg, ect.. so I flash these but with cg60.smg it won't flash saying the size is too big? I tried putting 0x00000140 before and after but doesn't work..
Could you help be how to do it properly? I used MotoAndroidDepacker to extract.. am I not extracting properly? I did the split to folder or is there something else? and there's no difference if I move the extracted folder before or after the program is closed.? the contents are the same
wait i noticed i used the wrong program...
-so do I run adb shell on the phone or on the computer?
thanks
-yeah still getting errors..
with cg60 and cg61 now..
image is too big, use 0x10000000 bytes chunks FAILED <remote: <00000006>>
so what does this mean?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Thank you
Thank you I got it to work but i'm not so clear about these 2 parts:
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
so what are the command lines? you do this still in command prompt correct?
so example after I enter "sqlite3 /data/data/com.google.android.gsf/databases/gservices.db"
how do you select (((select * from main where name='gtalk_vc_wifi_only')) ? I don't see how I can do a select and the * means what? does it mean not a command line?
Sorry a video tutorial would help.. please clarify if you can thanks a lot.
I noticed under the files needed section the first mirror link to the sbf not only does it show the update sbf file but it also shows in the dir the individual parts (img.gz's) are those the extracted smg files from the sbf? they have the same date, and roughly time on them.
You do both of these from the command line using adb. Just copy paste each line individually and that should do it. The star in the beginning of the line indicates the output i would expect you to see and not commands you have to run.
vastelectron said:
Thank you I got it to work but i'm not so clear about these 2 parts:
- Google Video over 3g
adb shell
su
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|true
update main set value='false' where name='gtalk_vc_wifi_only';
select * from main where name='gtalk_vc_wifi_only';
*gtalk_vc_wifi_only|false
.exit
- Tether hack
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value='disabled' WHERE name='entitlement_check';"
sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db
select * from settings WHERE name='entitlement_check';
*118|entitlement_check|disabled
.exit
so what are the command lines? you do this still in command prompt correct?
so example after I enter "sqlite3 /data/data/com.google.android.gsf/databases/gservices.db"
how do you select (((select * from main where name='gtalk_vc_wifi_only')) ? I don't see how I can do a select and the * means what? does it mean not a command line?
Sorry a video tutorial would help.. please clarify if you can thanks a lot.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
They are maybe the same files, but i didn't want to risk it, and just extracted them myself.
eclypse3demons said:
I noticed under the files needed section the first mirror link to the sbf not only does it show the update sbf file but it also shows in the dir the individual parts (img.gz's) are those the extracted smg files from the sbf? they have the same date, and roughly time on them.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
I wanted to Reply to this thread saying i was running Nottatrix ROM the new one with 4.1.141. My phoen would not run CM9 so i decided to do an sbf flash. IT failed leaving me at rebooting loop. i then followed this thread got the scf extracted the files from it flashed manually with and installed with fastboot and now its working even though it says things do not flash properly its working and i am so thankful for this thread. I still get a warranty replacement but i got it working.
moneyman1978 said:
I wanted to Reply to this thread saying i was running Nottatrix ROM the new one with 4.1.141. My phoen would not run CM9 so i decided to do an sbf flash. IT failed leaving me at rebooting loop. i then followed this thread got the scf extracted the files from it flashed manually with and installed with fastboot and now its working even though it says things do not flash properly its working and i am so thankful for this thread. I still get a warranty replacement but i got it working.
Click to expand...
Click to collapse
I am glad it worked for you! I just think that doing it this way, you learn about your phone to prepare you for flashing other ROMS and recovering from various situations.
running into a problem here. I can't find the file called N_01.77.37P_usa_att_12dec2011.zip inside that directory. there is one in there called N_01.77.36P_usa_att_.zip but not .37P
that__guy said:
running into a problem here. I can't find the file called N_01.77.37P_usa_att_12dec2011.zip inside that directory. there is one in there called N_01.77.36P_usa_att_.zip but not .37P
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showpost.php?p=22399253&postcount=171
thanks! one more thing, what exactly is being modified regarding tethering with the code in the instructions?
that__guy said:
thanks! one more thing, what exactly is being modified regarding tethering with the code in the instructions?
Click to expand...
Click to collapse
A setting that forces the phone to do some type of a check on whether you have the tether plan or not with ATT is disabled. By not doing the check the hot spot functionality will work, but ATT might still be able to track your data usage and give you a warning. Use at own risk.
Hi, N00b question
I have an ATT 4.5.91 Rooted Atrix but I don't know if it is unlocked or not... how can I find out that? in order to know the best way for me to update to .141?
I tried to unlock the bootloader using fastboot: "fastboot oem unlock" but I got an error that says that it is not implemented...
Can anyone help me to figure out which could be the best way to apply the .141 update?
Thanks
EDIT: Never mind that, I figured out what the problem was and it was unrelated. I just happened that something updated at the same time I ran the code and I thought it was the code that did it. (uninstalled updates to google search to fix) Sorry.
ok, so I have the update installed and am rooted. But now anytime I try to search in the application tray I get a message box saying that "process com.motorola.home has stopped unexpectedly". It didn't do that before I ran the root part of the code so I suspect it is because of that. This is what I ran and got back from the cmd prompt
C:\fastboot>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
[email protected]:/# PATH=/system/bin:$PATH
PATH=/system/bin:$PATH
[email protected]:/# pm install /preinstall/Superuser.apk
pm install /preinstall/Superuser.apk
pkg: /preinstall/Superuser.apk
Success
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.