Related
I've been looking around for this answer and probably missed it somewhere I'm sure. Can we fix permissions somehow on this phone? I've tried through terminal. Tried using cwr through imnuts otb kernel but cwr freezes. It gives the memory choices in cwr. I've tried everyone and cwr just freezes. Can somebody help me out here? I think a fix permissions might help the occasional acore force close I'm getting. Thanks.
Sent from my SCH-I510 using Tapatalk
Sorry but what do you mean fix permission? I'd like to help but I don't really know what you mean.
I want to run the fix permissions script which can usually be done through ClockworkMod or through Terminal Emulator. Running this script usually fixed most force close issues. I don't know how to run it with the ClockworkMod recovery I have installed. It appears broken. Is there an alternative method or am I doing something wrong?
Sent from my SCH-I510 using Tapatalk
I'm not sure thats a fix anymore like it was with the Fassy, it would be working in CWM otherwise and on top of that I've never seen it suggested in any rom threads... I could be wrong though
blazing through on my VZ Droid Charge 4G
anoninja118 said:
I'm not sure thats a fix anymore like it was with the Fassy, it would be working in CWM otherwise and on top of that I've never seen it suggested in any rom threads... I could be wrong though
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
Interesting. I'm curious to see what others say too.
Sent from my SCH-I510 using Tapatalk
SOTK said:
Interesting. I'm curious to see what others say too.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
I looked in GummyCharge and the debloated/deodexed EE4 ROMs and neither contain the fix permissions or battery stats script which would be necessary to perform either action in terminal emulator. So that option is out. Don't know if the script has to be present in the ROM in order for it to work in CWM or if it is included in CWM.
So yeah, any time I install an app from the market or the Amazon store, Sense force closes. I'm rooted using stock ROM. Known issue, or more importantly, advice?
Sent from my myTouch_4G_Slide using XDA Premium App
Did you try fixing permissions inside rom manager? That normally fixes root related fc issues.
Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App
You're rooted and you don't have ROM Manager?
rorytmeadows said:
Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
You are kidding right? Please say this is a joke?
AndroidBotx said:
You are kidding right? Please say this is a joke?
Click to expand...
Click to collapse
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)
Blue6IX said:
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)
Click to expand...
Click to collapse
Press "flash recovery" and grant Superuser permissions. Not that hard.
Delivered via candygram for Mr. Mongo.
Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App
rorytmeadows said:
Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
ROM Manager also allows you to flash ClockworkMod recovery and fixes your apps permissions. Once we get AOSP on this phone, you'll see what's really available.
blackknightavalon said:
fixes your apps permissions
Click to expand...
Click to collapse
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.
AndroidBotx said:
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.
Click to expand...
Click to collapse
Not only that - but i've noticed on the stock ROM every time I plug my phone into a computer without rebooting first it locks up and restarts - I have yet to have this happen on my ROM or any of the others I used before that.
Once you root the stock ROM, it just doesn't seem to work as well, and I had the restart issue before root was available for us with this device. At first I thought it was my computer doing it, but now with an older desktop in service it happens on that too, and other random computers I plug into that my friends own too...I dunno.
There is a lot to be said for running a custom ROM instead of the stock one, beyond all the little fixes and enhancements they bring.
...but, that's why we all work together here to constantly bring better software with more support for these devices all over XDA.
rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
When is the last time you cleared cache and dalvik-cache? That might help with some of your issues.
I wrote a flashable-zip package that will do just that if you don't want to do it manually, it does a wipe (not format) so is compatible with all 3 clockworkmod recoveries we have available, since 4.0.0.8 and 4.0.0.9 don't implement the format command correctly.
Blue6IX said:
Third one is: Blue6IX_C01_Wipe.zip
MD5: a8c57de781b2abfca2dfcdcae57d439c
This one will wipe the /cache partition and also wipe dalvik-cache. Use this one if you are having problems with specific apps, especially when changing to a different version of an already installed app.
Click to expand...
Click to collapse
Either manually doing it or flashing my script might help with your issues, or might have no effect.
The next time you boot after doing so the machine will have to rebuild both cache and dalvik-cache, so it will take a little longer to boot that first time and after it's done and has sat for 5 minutes or so you should reboot the machine again before using it, just to get everything worked out right.
Hope it helps!
OK, I installed Cheesecake after seeing all the signatures asking if I had "checked Cheesecake today?" I had been checking on a regular basis, finding nothing. I came to the realization that I would have no idea what to do with whatever I found anyways, so I decided to remove it. I was unable to find any definitive answers on the forum after several days, so I simply uninstalled it. When I check for updates I get a message saying that it is not available without a Motorola Service Account, then I get this:
Update Failed
In order to complete setup, you need a data connection.
You have the following choices:
Click to expand...
Click to collapse
Which is followed by 3 choices. It fails when either trying to use the current connection, or when trying to setup a wifi connection, even though I am already connected to the wifi. The third option is to just skip the setup. When I try to skip, it tries to sync my AT&T address book. It will not check for any actual updates. I know that this can happen with Cheesecake installed, but I have now removed it.
I know that there is an update for ICS coming to the Atrix 2, and I would like to be able to get it when the time comes, but until I can get this cleared up, I will not be able to get it. I already tried clearing the cache through Clockwork Mod, as well as doing a "Wipe data/factory reset" using Clockwork Mod. I am using the Stock Rom that came with the phone. What I would like to ask, is how to completely remove this, and return it to normal? As you can probably tell, I am still a noob to this, so if I left any information out that would help, please ask.
Already a thread about Cheesecake: http://forum.xda-developers.com/showthread.php?t=1801855 Motorola account error
Please, as always, search before making new thread posts…
Sent from my Atari Falcon030
Thank you, I missed that one, guess I was using the wrong search terms...
Chr0nos77 said:
Thank you, I missed that one, guess I was using the wrong search terms...
Click to expand...
Click to collapse
No problem. You should be okay just to remove the Cheesecake .apk from your phone and reboot. I think that'll take care of deleting everything, and revert back to the 'normal' OTA server service built-in to the phone. Can anyone else confirm?
Sent from my Atari Falcon030
Had the same problem once, and i had to reinstall cheesecake, switch to production and then uninstall cheesecake to get it working.
Sent from my MB865 using xda premium
Apex_Strider said:
No problem. You should be okay just to remove the Cheesecake .apk from your phone and reboot. I think that'll take care of deleting everything, and revert back to the 'normal' OTA server service built-in to the phone. Can anyone else confirm?
Sent from my Atari Falcon030
Click to expand...
Click to collapse
Not quite, it actually edits a defaults.xml somewhere in .... wait. I'll find it and edit this post.. you would need to change that to match stock (I think I posted the exact file and edits somewhere on here), or you might get by by changing to the Production server in cheesecake one last time, then uninstalling.. edit#1: yes, what Fall of said..
Edit#2: it's the defaults.xml in /system/etc/motorola/com.motorola.blur.service.blur folder...
Sent from my phone's mind
Thanks for the help. I reinstalled cheesecake, and set it back to the production server, now it is working normally again.
Sent from my MB865 using xda app-developers app
Glad you got it worked out!
Alright, I'm hoping I can get some quick useful feedback on this. I'm currently on AOKP Official Milestone 6, and every time I reboot it reverts me settings I had on August 28th. I've been going thru this all day long, Google searching, scanning forums for our device and the T989.
I've attempted Odin flashes 13 times today to go back to Stock Gb and Stock Ics, the flashes show successful, yet AOKP boots right back up. Recovery does nothing to wipe, currently on Clockworkmod Touch Recovery.
Formatting all caches and partitions, Dalvik wipes all 5x each do nothing, even flashing something after this does nothing. I can't even reset AOKP, it takes me right back to the same condition from August 28th, same theme, apps, etc, all there. I've even formatted both emmc and sdcard, nothing. Whatever I do gets overwritten to the previous condition.
Can someone please help me out with this. I'm not even sure what to classify an issue like this as.
Sent from my SGH-I727 using xda premium
you are not the only one who had this issue, its a failure to write to the nand, for the lack of a better word, i have some links in my ref sticky, 1st link in my sig, under the info section on other users who had this problem, one thing i don't think they tried is using adb to push files
edit: damn i forgot to add those posts to my sticky, i/ll search for them and post them up
EDIT: here is one , couldnt find the other one http://forum.xda-developers.com/showthread.php?t=1751338
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
KillaT21 said:
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
vincom said:
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I don't think it applies 100% to me. I can write to system, it just gets ignored lol. I read that Mightyoj had the exact issue and adb did nothing for him. I'm within my 30 days, I may need to either find another way to hard brick it or call at&t like he did.
Regardless, thanks for your help Vincom.
Sent from my SGH-I727 using xda premium
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I remember this issue. The guy who's post you linked to did try adb to no luck. The only thing I can think to try through adb is changing the permissions of emmc? Some one with more knowledge then me might chime in but I'd say
Code:
adb shell
chmod 666 /emmc
That should give read/write to emmc if it will stick. Again you might want to get confirmation on this before attempting it as it is my best guess for your issue. If it's a bad nand you may just be SOL.
Illnevertell said:
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There's a thought...hmm
Sent from my SGH-I727 using xda premium
All right, after a few weeks of headache, I thought I'd update this thread as to whats going on.
Sent my phone off to Samsung twice for a fix. Twice due to the support rep not having any clue what the issues were that I was describing to her the first time over, so they sent it back in the same condition as when I sent it to them. Their solution: Applied stock SW.
They didnt even attempt to turn it on to see if the issue was resolved. So fast forward to 3 days after receiving it back and I called Samsung back and carefully worded my problem again and pointed out that I sent it to them before and no solution was found.
So I sent it back off, and 3 days later they called me asking me what exactly was wrong with my phone and I mentioned that it was some issue with the internal memory upon boot that locked everything into a specific setting from August 28th, and that it must be hardware related. She said she would inform the technicians.
So finally, I got my service ticket and the solution they reached was:
Replaced PBA, which is the Print Board Assembly. Looked around on Xda and for the definition and found that a few Samsung devices that were having similar issues as myself and a few others were remedied by replacing it. Currently waiting on them to reship it to me.
So, the "moral" of the story is, if you are within your Manufacturers warranty with Samsung, give Support a call and try as best as you can to explain your problem to them, but dont let them know you're rooted. They are not "supposed" to troubleshoot/fix your issue when rooted. But when they get hands on, they know that the average person that roots would have likely reversed any software issues/damage aside from a brick.
Hopefully this tidbit of information can help future Androidians with Samsung Devices on whats going on and expedite their efforts for a solution. Thanks again to all that were involved
Sent from my SGH-I997 using xda premium
Just wondering if anyone has tried to FXZ back after accepting the Update?
Sent from my XT1080 using Tapatalk
Brenardo said:
Just wondering if anyone has tried to FXZ back after accepting the Update?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Had to do this, but it wasn't intentional. I had to take out specific lines in the XML file to get it to work. The first few lines caused errors so I had to delete them and start at factory.img command to get it to work. I have the edited file if you'd like me to post it. I was messing around with my dev edition and something went wrong and likely I figured out how to restore to stock with the edited file.
What are the odds it will work with a consumer edition?
Sent from my XT1080 using Tapatalk
Brenardo said:
What are the odds it will work with a consumer edition?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
My guess is it should work. The xml file is the stock img, recovery, data, boot, etc for both the dev and consumer editions. I must say that what I did wasn't intentional and wasn't something I wanted to happen. If you are on the update and want to go back to 12.7.7 you could try this, but if something would happen to go wrong you could potentially brick your phone. It seems unlikely though as I thought I bricked mine and editing the file did indeed return me to 12.7.7 and I flashed the update zip from stock recovery as I had before.
Well I would like to see the edited file if you dont mind
Sent from my XT1080 using Tapatalk
Brenardo said:
Well I would like to see the edited file if you dont mind
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
View attachment 2375754
I deleted everything down to the boot.img. The prior commands come up with an error that I believe is some sort of security or files out of place that doesn't allow you to drop down to a lower firmware. If you are going to try this my suggesting would be to try the full xml and see if you get errors. If you do then try the way I did.
I'll be curious to see how it works for you. This could come in handy to people if they accidentally cause a boot loop. Once the files for 12.15.15 are released they won't have to do this.
theycallmerayj said:
I'll be curious to see how it works for you. This could come in handy to people if they accidentally cause a boot loop. Once the files for 12.15.15 are released they won't have to do this.
Click to expand...
Click to collapse
I can confirm it doesn't work if the update actually completes. Once the system partition is updated, there's no going back.
Sent from my SCH-I605 using Tapatalk
I had the update completed and working and I went back to 12 7.7
Sent from my XT1080 using Tapatalk
theycallmerayj said:
I had the update completed and working and I went back to 12 7.7
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Please enlighten us on how you did it.
bigv5150 said:
Please enlighten us on how you did it.
Click to expand...
Click to collapse
This is what I'm talking about further up in the thread. I was messing around and honestly can't remember what I specifically did but basically I updated to 12.15.15, bricked my phone into a boot loop, and assumed I couldn't do anything until they release the xml file for the update. I tried to 12.7.7 xml file and at first it didn't work. The first few commands give you an error basically saying some sort of security or files won't allow you to drop down to the old firmware. Unfortunately I don't know the exact wording of it. But I edited the xml file to only run the commands from boot.img down which I posted in this thread. Now I do have a dev maxx. I mean I could try it again, but I'd rather not as I have my phone all set up after having to restore to stock.
---------- Post added at 09:48 PM ---------- Previous post was at 09:40 PM ----------
Sorry I can't give more specific details, as I said I didn't intend to do all this so it wasn't something I thought I'd need to remember. I don't post much on here to begin with but I thought what happened to me and how I fixed it could potentially help someone else.
theycallmerayj said:
This is what I'm talking about further up in the thread. I was messing around and honestly can't remember what I specifically did but basically I updated to 12.15.15, bricked my phone into a boot loop, and assumed I couldn't do anything until they release the xml file for the update. I tried to 12.7.7 xml file and at first it didn't work. The first few commands give you an error basically saying some sort of security or files won't allow you to drop down to the old firmware. Unfortunately I don't know the exact wording of it. But I edited the xml file to only run the commands from boot.img down which I posted in this thread. Now I do have a dev maxx. I mean I could try it again, but I'd rather not as I have my phone all set up after having to restore to stock.
---------- Post added at 09:48 PM ---------- Previous post was at 09:40 PM ----------
Sorry I can't give more specific details, as I said I didn't intend to do all this so it wasn't something I thought I'd need to remember. I don't post much on here to begin with but I thought what happened to me and how I fixed it could potentially help someone else.
Click to expand...
Click to collapse
That's cool I wouldn't expect you to try again I think you having a dev phone is what allowed you to do it anyway. I tried to fastboot the system image and it wouldnt take.
bigv5150 said:
That's cool I wouldn't expect you to try again I think you having a dev phone is what allowed you to do it anyway. I tried to fastboot the system image and it wouldnt take.
Click to expand...
Click to collapse
Okay, I thought maybe that had something to do with it. I wouldn't suggest trying it to people anyway cause I was really worried I did brick my phone.
theycallmerayj said:
Okay, I thought maybe that had something to do with it. I wouldn't suggest trying it to people anyway cause I was really worried I did brick my phone.
Click to expand...
Click to collapse
Were you actually running 12.15.15 for a period of time, or did the bootloop occur during the update?
If you were actually running it, then my only conclusion is that the dev edition ignores the partition version check.
I don't recommend anyone on a consumer version try this.
Sent from my SCH-I605 using Tapatalk
I was actually on the update running it.
Sent from my XT1080 using Tapatalk
theycallmerayj said:
I was actually on the update running it.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Must be a dev edition thing then. Mine fails on system version checks for boot, recovery, and system. 2 of those 3 are apparently important.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Must be a dev edition thing then. Mine fails on system version checks for boot, recovery, and system. 2 of those 3 are apparently important.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Yeah it must be. Once they release the xml for 12.15.15 I might be willing to try this again to record the errors to see why I was able to do it. I don't want to do it now because I don't want to take the risk that it won't work.