Hi all,
I am kind of new to the whole Android scene. I need a little help updating my phone. I recently rooted it on 2.2.19.a955. I uninstalled several stock apps, 3G Wifi Hotspot, the Amazon stuff, and something else. I was able to reinstall everything but the 3G Wifi Hotspot. Can't seem to find an apk or recover it or anything.
When I tried to update, it gives me an error saying that it is unable to update.
I am not sure what it is. I think the missing apps or the root is preventing me from updating.
Please help!
Thanks.
-Kevin
Im having the same issue
I also removed some of the bloat and when my OTA update failed I reinstalled all of it from the system dump found in another thread on this forum (it won't let me post a link). I checked all my permissions and made sure they were 644 but my update is still failing on Mynet.apk. I have checked it; it is there and its permissions are 644. Any ideas? Thanks in advance for any help.
darkonion said:
Hi all,
I am kind of new to the whole Android scene. I need a little help updating my phone. I recently rooted it on 2.2.19.a955. I uninstalled several stock apps, 3G Wifi Hotspot, the Amazon stuff, and something else. I was able to reinstall everything but the 3G Wifi Hotspot. Can't seem to find an apk or recover it or anything.
When I tried to update, it gives me an error saying that it is unable to update.
I am not sure what it is. I think the missing apps or the root is preventing me from updating.
Please help!
Thanks.
-Kevin
Click to expand...
Click to collapse
darkonion said:
Hi all,
I am kind of new to the whole Android scene. I need a little help updating my phone. I recently rooted it on 2.2.19.a955. I uninstalled several stock apps, 3G Wifi Hotspot, the Amazon stuff, and something else. I was able to reinstall everything but the 3G Wifi Hotspot. Can't seem to find an apk or recover it or anything.
When I tried to update, it gives me an error saying that it is unable to update.
I am not sure what it is. I think the missing apps or the root is preventing me from updating.
Please help!
Thanks.
-Kevin
Click to expand...
Click to collapse
You could always just flash back to the stock system with the .sbf released in "The Bomb" you probably used to root. Once you do that youve lost root but back to stock then do the OTA update, re-root, and also have your bloat back... Its a little lengthy but Google and your sd card have most everything backed up for you anyway.
cryptkpr said:
I also removed some of the bloat and when my OTA update failed I reinstalled all of it from the system dump found in another thread on this forum (it won't let me post a link). I checked all my permissions and made sure they were 644 but my update is still failing on Mynet.apk. I have checked it; it is there and its permissions are 644. Any ideas? Thanks in advance for any help.
Click to expand...
Click to collapse
Is system dump the 128MB file off of rapidshare?
RammiKan said:
You could always just flash back to the stock system with the .sbf released in "The Bomb" you probably used to root. Once you do that youve lost root but back to stock then do the OTA update, re-root, and also have your bloat back... Its a little lengthy but Google and your sd card have most everything backed up for you anyway.
Click to expand...
Click to collapse
I have the SBF. I am just not sure how to flash it back onto my phone. I really don't have that much stuff. I've only installed a few programs. Not a big deal.
darkonion said:
Is system dump the 128MB file off of rapidshare
Click to expand...
Click to collapse
Yes that's the one I used to restore my apk's but its still hanging on Mynet.apk
cryptkpr said:
Yes that's the one I used to restore my apk's but its still hanging on Mynet.apk
Click to expand...
Click to collapse
I think that's the one I need to reinstall...
Still having trouble figuring out how to install mynet.apk. I downloaded the file, but I am unsure what to do now.
You have to use adb to install system apps. So, something like:
- put Mynet.apk in your sdk tools folder
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb remount
- adb push Mynet.apk /system/app/Mynet.apk
- adb remount
As a note, I updated to 2.2.20 with root but without removing apps.
If you do use the snf from The Bomb, what is that other file out of curiosity?
Thanks Karnovaran.
Is there anything I need to do with the opek file? I followed your steps generally and I am still not getting anything.
So... I followed your directions. I put Mynet.apk in the folder. Ran ADB, copied the file to the sdcard. Mounted. Ran rageagainstthecage. Copied the Mynet.apk to the apps folder on the system. Same with the odex file, and remounted, and exited, but still nothing...
I was able to flash my phone using the files from the RootzWiki bomb. Flashed it successfully. Now it doesn't have a connection to the Verizon network. No data service. Not sure about phone service though.
darkonion said:
I was able to flash my phone using the files from the RootzWiki bomb. Flashed it successfully. Now it doesn't have a connection to the Verizon network. No data service. Not sure about phone service though.
Click to expand...
Click to collapse
You probably need to dial *22899 from your phone before it will get back on the Verizon network.
Does the ota contain something that is really needed. I am debating if I want to unroot just for the ota. Hopefully some one figure away to give us an update that remains rooted.
pc747 said:
Does the ota contain something that is really needed. I am debating if I want to unroot just for the ota. Hopefully some one figure away to give us an update that remains rooted.
Click to expand...
Click to collapse
my answer is in droidlife
DROID 2 Receiving Minor Update, Now Allows for User Initiation
On 08.21.10, In News, by Kellex
Share3
If you own a Droid 2, you should be receiving a minor update over the next couple of days and in fact, there is a pretty good chance that you have already been prompted to install it. The update, although minor, does fix a couple of things which will enhance your D2 experience…
Improvements:
+ Enabled text and picture message scrolling.
+ Streamlined set up of Visual Voice Mail feature.
+ Improved contact sync with Corporate Exchange categories
and groups.
+ View accurate contact pictures when reviewing Recent Call Log.
On a related note, it looks like Verizon may be allowing user initiated updates for their new Droid family member. If you check out their update installation instructions, there are now 2 types of software loading: user initiated and server initiated. We also just received this shot which shows that manual updates could start as early as last night, and OTA server initiated updates will start on the 24th if users have not already gone through the process…
After the update you will be running version 2.2.20.en.us.
Via: Verizon Wireless
Cheers Mitch and Shawn!
2.2.20 is root-able, so if you really want it you can do the sbf flash and grab the update before rooting. I don't think we'll be seeing any custom updates for the D2. Let's just thank our lucky stars the sbf showed up.
ITGuy11 said:
You probably need to dial *22899 from your phone before it will get back on the Verizon network.
Click to expand...
Click to collapse
Darn, wish I knew that before I factory resetted my phone. Do you know this for a fact?
Yes a factory reset is necessary...I just flashed my phone this morning with the sbf and I connected to verizon network but it would not connect to any data connection 3g or 1x, nothing so a factory reset took place and it works almost better than before for some reason lol..my internet connection seems to be more stable and reception is a little better and I've done* 22899 before I rooted and flashed back and this time around its just working better idk..but back to the topic at hand if u* 22899 it will connect you to verizon network but no 3g or anything
JonandRoid said:
Yes a factory reset is necessary...I just flashed my phone this morning with the sbf and I connected to verizon network but it would not connect to any data connection 3g or 1x, nothing so a factory reset took place and it works almost better than before for some reason lol..my internet connection seems to be more stable and reception is a little better and I've done* 22899 before I rooted and flashed back and this time around its just working better idk..but back to the topic at hand if u* 22899 it will connect you to verizon network but no 3g or anything
Click to expand...
Click to collapse
Did you try *228? Maybe might have been a better way to go. But thank you for trying.
If you can't update or anything flash an sbf. Isn't hard.
If you are rooted and need to sbf, I used the droid bootstrap recovery to wipe my cache and data, then flashed the sbf from the bootloader (turn the phone all the way off, and hold the up arrow as you power on). Made it a lot easier, and fixed all the errors I was having
Sent from my DROID2 using XDA App
Related
I just got my Xoom back from the 4G upgrade yesterday. I decided I would take a shot at rooting and overclocking it for the first time since now I didn't have to worry whether Motorola would care about the voided warranty.
So, I rooted using the universal root kit and everything was working swell. Well, except one problem - I couldn't download anything from the market. Instead of looking more into it, and see if there was a way to fix it, I just decided to unroot.
Surprise, surprise - I went all the way back down to 3.01 without knowing the consequences. Not only did I lose my 4G connectivity, but also 3G. Now, it shows me having full bars, but it's just not connecting. My Wi-Fi works fine.
So, now I've been hunting and trying frantically to get back up to 3.2.2 and get my internet back. I've tried using the stock/rooted version that Solarnz provided, but alas, I still have no connectivity.
I've tried looking around on the forum, and I've tried a couple of methods that still didn't help. Has anyone heard of a sure fire way to correct this problem yet? I think I'm practically screwed, since my 3G won't even work when I'm down on 3.01, so I won't be able to get an upgrade to 3.2.2 later on (if the stock image is released).
Might want to look around some more:
http://forum.xda-developers.com/showthread.php?t=1294821
http://forum.xda-developers.com/showpost.php?p=18243360&postcount=10
http://forum.xda-developers.com/showpost.php?p=18353730&postcount=2
Just a few links to check out.
scsa20 said:
Might want to look around some more:
http://forum.xda-developers.com/showthread.php?t=1294821
http://forum.xda-developers.com/showpost.php?p=18243360&postcount=10
http://forum.xda-developers.com/showpost.php?p=18353730&postcount=2
Just a few links to check out.
Click to expand...
Click to collapse
Well, I tried some of those methods already. I just tried manually updating to HLK75D this morning and I still don't have either 3G or 4G connectivity.
My kernel version still doesn't have the "ltedc" part that it had before I went through all this mess. Every time I go into the mobile network settings, I still don't have the LTE option and "Activate Device" is always available, even after I activate over Wi-Fi.
Ok try this. Its working with any android device. But I never try on honeycomb.
Open Market and download "Astro file manager".
Open astro>preferences>enable browsing download.
Restat u xoom, just for me
Enjoy
Update: ops....u about "market "download problem.....
Did u try do simple cache clean from application> manage aplication?
avetny said:
Ok try this. Its working with any android device. But I never try on honeycomb.
Open Market and download "Astro file manager".
Open astro>preferences>enable browsing download.
Restat u xoom, just for me
Enjoy
Update: ops....u about "market "download problem.....
Did u try do simple cache clean from application> manage aplication?
Click to expand...
Click to collapse
Well, I'm not entirely sure how that would help with my lack of 3G/4G connectivity. If I would have known about that method to fix the market problem prior to flashing back down to 3.01 from 3.2.2, that could have saved me a lot of trouble.
My dad's Nexus S keeps disconnecting from Wind and will NOT automatically reconnect to Wind. I've set it to Automatic. On top of this, *every* time I enable Wifi or Bluetooth on his device, his Wind connection drops and remains dropped until I manually reconnect.
The only way around this issue is if I manually select Wind's network in the settings menu, thereby avoiding 'Select automatically'. The problem here is that when the phone needs a reboot, it doesnt remember the last network and it needs to be manually selected *again*.
I've done a quick search via Google and there are others having the same/similar problem;
http://www.google.ca/support/forum/p/Google+Mobile/thread?tid=34411ac78e8a4ff6&hl=en
Apparently the 2.3.6 update doesn't fix this either. Is there a 2.3.7 release? I'm even thinking of rooting and flashing the phone to use a custom ROM (MIUI, its much cleaner with better shortcuts which my dad would like).
Does anyone know of a solution to this? I'm thinking of going into Wind and having it replaced (its less than a week old). Question is, if he's racked up more than 30 minutes, can he still get a straight exchange for the phone? Would it still be eligible for exchange/replacement if I tried the ICS update to the phone?
Did you guys root the phone? Ans if you did, did you installed custom rom? If so, it just might be the incompatibility with the Nexus S. If you didn't root it, the phone just might be defected. Try updating the os. It always doesn't hurt to update os. If that doesn't work, I guess you should return it and get the new one it somethign :/
Sent from my Nexus S using XDA App
At the minimum, I would try updating to 2.3.6.
Yeah try to update to newer os. And if that doesn't work, I guess you should exchange your phone or something??
Sent from my Nexus S using XDA App
kyokeun1234 said:
Did you guys root the phone? Ans if you did, did you installed custom rom? If so, it just might be the incompatibility with the Nexus S. If you didn't root it, the phone just might be defected. Try updating the os. It always doesn't hurt to update os. If that doesn't work, I guess you should return it and get the new one it somethign :/
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I've updated my original question with more details.
But no, its not a rooted phone. Everything is stock Android 2.3.4. The phone is only about 5 days old, we got it for him on the 27th of December (or 26th, cant remember). I have installed a few applications (cnn news, wp.pl, bbc news, unit converter, etc). I've updated all the applications as well.
How can I obtain 2.3.6 and install it? Is the process difficult and would it render the phone non-returnable to his carrier for fixing/replacing?
If you have stock, the process is easy was snap if there's a avaliable ota update to your phone. Go to setting-about phone-system update (I'm pretty sure) and if there's an update for your phone, you can download and install the new rom from there.
Sent from my Nexus S using XDA App
kyokeun1234 said:
If you have stock, the process is easy was snap if there's a avaliable ota update to your phone. Go to setting-about phone-system update (I'm pretty sure) and if there's an update for your phone, you can download and install the new rom from there.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Will it give me the option to update to Iced Cream Sandwich Android 4.0 as well?
Um probably not. Depends on what model you're using. It probably promt you to update to later version of gingerbread :/
Sent from my Nexus S using XDA App
Hi, I have the exact same problem as the original poster, except worse.
I lose my data connection when I turn on wifi, or after I reboot my phone. And once I lose the connection, I have to power off and take out the battery for it to work again. My phone was already rooted when this problem start about 4 days ago, was using stock rom (2.3.6) I downloaded for my I9020T (don't ask, minor hiccup when I was rooting my phone...)
So far I've tried the following:
1. boot to CWM recovery -> factory reset, wipe cache, unsuccessful
2. *#*#4636#*#*, changed preferred network to WCMDA preferred or only, unsuccessful (I also had issues with sending SMS, so I also updated the SMSC, which is 07916174080001f6 for Mobilicity in Canada). Also selected "Automatic" in "Select radio band".
3. I flashed the OS to cyanogen, still same problem.
4. In mobile settings, tried changing apn, toggle data connection, 2g/3g, "Select automatically", doesn't work.
5. a whole bunch of other voodoo I found on the web, but none worked.
The only thing I haven't tried yet is flashing with a stock sbf, because I can't seem to be able to find one.
The error message I see in *#*#4636#*# -> Phone info is something like DcInactiveConnection...: unknown data error (sorry can't remember the whole thing).
Also tried asking mobilicity to refresh my service, but that also didn't help.
I ran logcat in terminal emulator and searched through the log for "error" or anything suspicious, the only thing I saw were these,
1. Error loading keycharmap file '/system/usr/keychars/herring-keypad.kcm.bin'
2. caused by: java.net.SocketTimeoutException: Connection timed out
I/TelephonyRegistry( 188): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=apnSwitched interfaceName=null networkType=3
I/TelephonyRegistry
3. onErrorResponse: Failed to send 5 events because of [com.android.volley.TimeoutError]
D/Volley
Tried googling all of them but didn't find anything useful.
I've been at this for the past 4 days and still haven't been able to fix this. I tried swapping in another mobilicity sim card and it also had the same behaviour, so it's definitely something with my phone.
Also, after I power down and remove the battery and power it back up again, the connection still doesn't come back automatically, but I have to toggle the airplane mode to get it to connect.
At this point, what else can/should I try? Or should I just ask them to send it for warranty?
Any help/advice will be VERY much appreciated!!!! And apologies for the essay.
Thanks!
NM, I reread your post. I have nothing for you. Sorry.
My Atrix 2 is a 2.3.5 firmware version. ATT 110921_0913
From previous 2 to 3 days my phone is in complete freeze mode...meaning whatever I do to my phone install any app uninstall any app...when I restart the phone it just gets back to the same state....
I have tried factory reset from the settings I didn't worked..... then I tried the hard reset method but that didn't worked too...
After that I tries reloading the stock fxz using the rsd lite but it failed at step 3 saying mbmloader cannot be flashed....
Then I tried the script method...http://forum.xda-developers.com/showthread.php?t=1539167
In that it said that the bootloader is restricted and it cannot write it it wrote the rest of the things but still my phone is in the same state it was with same apps and everything.....
I tried booting into the CWM recovery mode but when I try to run the AtrixBOOtloader.apk it reboots and the restarts normally....
Please I really need som help....
just to let you know I have Go launcher installed I know its absurd to thing that it can be causing the problem...but just in casee....
Please let me know if you need any other information.....
Any help will be greatly appreciated....
Thanks....
More info is always nice:
Are you rooted? Were you running a special ROM? If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started?
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's.
PS: From now on please post things like this in the Q&A forum. We're kinda letting this slide so far since it's still new and not everyone is aware of it.
Fall of Enosis said:
More info is always nice:
Are you rooted? Were you running a special ROM? If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started?
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's.
PS: From now on please post things like this in the Q&A forum. We're kinda letting this slide so far since it's still new and not everyone is aware of it.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Here are the answers:
Are you rooted? Yes!
Were you running a special ROM? No I did nothing that could mess up my rom or anything...
If rooted, did you make any changes to your system? If rooted, do you have a backup made (cause you should)? What did you do (system wise) before this started? No to above all...this started happening 2-3 days ago after some of my apps were updated...and I dont have any backup
And are you SURE you are 2.3.5? Because all A2's are 2.3.5 out of the box but have since been upgraded to 2.3.6, which is the stock norm for A2's........
I am sure that I am at 2.3.5 because I was not able to install the 2.3.6 update I kept on failing on me while installing on halfway.....
Again I have not done anything related to my system that I could cause this...only thing I can think of is because of some rogue app or something!!!!
Ok now that we have the basics down, one other question, what EXACTLY do you mean by "freeze mode"? What exactly is the phone doing that you don't want it to do? Force closing all the time? If so, what apps?
I'm still a little confused as to what EXACTLY the phone is doing.
The more info the better.
I agree with you Fall of Enosis, we need some more exacted information regarding the OP's issue here.
OP: You say you tried a factory reset, but now are concerned that it is a "rogue app", but unless you've re-installed apps you previously had installed, this is not likely.
What is your location, and do you have access to WiFi or network connectivity to enable the update from 2.3.5 to 2.3.6?
Sounds to me as if you have tried to do something that we're not entirely clear of (and perhaps you are not either) and as result you've borked the boot image, but I can't convincingly determine that is the case here. If the phone is still booting into Android, but simply "freezes", then you may have a bad flash of the FXZ.
If you are experiencing "freezing" of the UI or system itself, it could be application-related or a handful of other things.
You really need to be as precise as you possibly can, describing in detail everything you have done, tried, and are experiencing here for us to be of any real help. Otherwise, we're left to 'fishing' for information from you, which wastes everyone's time here.
Fall of Enosis said:
Ok now that we have the basics down, one other question, what EXACTLY do you mean by "freeze mode"? What exactly is the phone doing that you don't want it to do? Force closing all the time? If so, what apps?
I'm still a little confused as to what EXACTLY the phone is doing.
The more info the better.
Click to expand...
Click to collapse
Yes all of my apps are force closing like motorola.service.....facebook rebtel and many others...sometimes one crashes on other restart some other.....
NOTHING IS ACTUALLY FREEZING
By freeze mode I mean like the deep freeze effect on the PC...I cannot uninstall any app or install a new one cannot make any changes ot my system settings or anything......
So sometimes critical processes closes like contacts process and then no contacts are shown.....I am able to use the phone and the apps which are not closing for that time works prefectly fine....
Apex_Strider said:
I agree with you Fall of Enosis, we need some more exacted information regarding the OP's issue here.
OP: You say you tried a factory reset, but now are concerned that it is a "rogue app", but unless you've re-installed apps you previously had installed, this is not likely.
What is your location, and do you have access to WiFi or network connectivity to enable the update from 2.3.5 to 2.3.6?
Sounds to me as if you have tried to do something that we're not entirely clear of (and perhaps you are not either) and as result you've borked the boot image, but I can't convincingly determine that is the case here. If the phone is still booting into Android, but simply "freezes", then you may have a bad flash of the FXZ.
If you are experiencing "freezing" of the UI or system itself, it could be application-related or a handful of other things.
You really need to be as precise as you possibly can, describing in detail everything you have done, tried, and are experiencing here for us to be of any real help. Otherwise, we're left to 'fishing' for information from you, which wastes everyone's time here.
Click to expand...
Click to collapse
I am really sorry for not being much more clearer with my problem.....!!
I am currently in US LA and yes I do have wifi connectivity I have tried update several times but I just fails...I think may be I rooted it incorrectly....
I HAVE NOT TRIED TO DO ANYTHING WITH MY SYSTEM
The phone still boots up normally and works fine I mean nothing is freezing ....by freeze mode I mean the whole of the phone memory is frozen like deep freeze on the PC so I cannot make any changes to the settings or install uninstall any apps....moreover on each restart many of the processes keeps on closing...
So agian I will try to make it as clearer as possible.....I have not tried to install any custom rom or make any os or system related changes to my atrix 2....
What is actually happening is I cannot make any changes to my phone memory....I cannot change any settings or install or uninstall anything since as soon as I restart my phone ANY CHANGES WILL DISAPPEAR and it will be back to the exact same state as it was before.....
Please help I am not able to fix this thing....
Ok, thanks for being clearer. It helps.
I have had something like this happen to me, constant moto apps fc'ing.
For me it was an app causing my headache. However the only way i could take care of it was to restore one of my backups.
I think you possibly have an app causing your headache as well. And i think that somehow (whether you know it or not) you accidentally borked the system UI. So before we go to the extreme of fxz'ing back (since you don't have a backup) what kind of rooted apps are you using?
I know YOU didn't personally change anything but rooted apps will make all sorts of changes that you are unaware of.
What rooted apps are you running and more importantly which apps (rooted or not) were most recently installed before this happened?
Don't fret man, we'll work this out for ya.
Sent from my MB865 using xda premium
Maybe.. the flash memory cannot be written?
Is it possible to post "adb logcat" when your apps are force closing or you are trying to do an install? And if you could make adb work, then grab a shell and paste the o/p of the commands "mount", "df" ... Also you may want to try command like "adb install <package.apk>", and check what's the error code returned.
Fall of Enosis said:
Ok, thanks for being clearer. It helps.
I have had something like this happen to me, constant moto apps fc'ing.
For me it was an app causing my headache. However the only way i could take care of it was to restore one of my backups.
I think you possibly have an app causing your headache as well. And i think that somehow (whether you know it or not) you accidentally borked the system UI. So before we go to the extreme of fxz'ing back (since you don't have a backup) what kind of rooted apps are you using?
I know YOU didn't personally change anything but rooted apps will make all sorts of changes that you are unaware of.
What rooted apps are you running and more importantly which apps (rooted or not) were most recently installed before this happened?
Don't fret man, we'll work this out for ya.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Okay, so I have been playing with the phone form last two days and I have figured out what the problem is...ITS A ROGUE APP...HOW??!!!!
Well, I started my phone in safe mode and I was out of the WIFI reach so no network access then to my surprise everything worked fine like a charm no process was closing and the phone was perfectly fine as it should but as soon as I went into wifi connectivity around 12 of my apps got automatic updates and my phone started f*king again.....
As soon as the updates were installed all my apps started force closing and it was absolutely like a what a virus does on the PC my apps were starting trying to load and then were kill in about 3-4 seconds......
So, it has to be a rogue app nothing else.....I am not sure which app is causing the problem and I don't even remember which app I recently installed but it has to be one of the app which is getting updated...right??
Just for reference these many apps gets the update after which my phone starts messing up....
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
So, now we know what the problem is...what am I supposed to do now...I have tried uninstalling my apps in the safe mode also but as usuale after the restart I gets back to the same exact state it was.....
Any suggestions will be really helpful....
Also what I am wondreing about is if the app has somehow restricted the mbmbootloader writing isn't there any other way we can write it or change the permission...??
Also thanks for staying with me on this till now
PhoenixNghi said:
Maybe.. the flash memory cannot be written?
Click to expand...
Click to collapse
Are you referring to mbmloader.bin???
black_panther10 said:
Okay, so I have been playing with the phone form last two days and I have figured out what the problem is...ITS A ROGUE APP...HOW??!!!!
Well, I started my phone in safe mode and I was out of the WIFI reach so no network access then to my surprise everything worked fine like a charm no process was closing and the phone was perfectly fine as it should but as soon as I went into wifi connectivity around 12 of my apps got automatic updates and my phone started f*king again.....
As soon as the updates were installed all my apps started force closing and it was absolutely like a what a virus does on the PC my apps were starting trying to load and then were kill in about 3-4 seconds......
So, it has to be a rogue app nothing else.....I am not sure which app is causing the problem and I don't even remember which app I recently installed but it has to be one of the app which is getting updated...right??
Just for reference these many apps gets the update after which my phone starts messing up....
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
So, now we know what the problem is...what am I supposed to do now...I have tried uninstalling my apps in the safe mode also but as usuale after the restart I gets back to the same exact state it was.....
Any suggestions will be really helpful....
Also what I am wondreing about is if the app has somehow restricted the mbmbootloader writing isn't there any other way we can write it or change the permission...??
Also thanks for staying with me on this till now
Click to expand...
Click to collapse
Ok, I am going weigh in here now....
All of this has absolutley NOTHING to do with the Bootloader/mbmloader, not sure where that came from.
My advice is disable all the updates in the playstore, or well the auto update feature, then those apps that you mentioned that are getting updated. After you restore the fxz, this time make sure that the auto update is off, and then update each of the noted problem apps ONE AT A TIME, then when the issue starts you know which one is the problem app, most likely the last app installed or updated, and I would not install that one again. Simple solution here.
Yes this will be painful, because you might have to do the fxz more than once, but it is the best way to know you are back to 100% stock again.
kousik said:
Is it possible to post "adb logcat" when your apps are force closing or you are trying to do an install? And if you could make adb work, then grab a shell and paste the o/p of the commands "mount", "df" ... Also you may want to try command like "adb install <package.apk>", and check what's the error code returned.
Click to expand...
Click to collapse
Okay here I was doing adb logcat and when I tried play music it got killed and this was the adb logcat output
09-03 11:56:33.054 1362 1362 D dalvikvm: GC_EXPLICIT freed <1K, 48% free 2839K
/5379K, external 2357K/2773K, paused 52ms
09-03 11:56:35.750 521 538 W ActivityManager: Activity destroy timeout for H
istoryRecord{406001e0 com.google.android.music/com.android.music.activitymanagem
ent.TopLevelActivity}
09-03 11:56:38.070 1414 1414 D dalvikvm: GC_EXPLICIT freed 6K, 47% free 2892K/
5447K, external 2357K/2773K, paused 69ms
09-03 11:56:42.710 521 605 V AlarmManager: sending alarm Alarm{40b32c60 type
2 android}
09-03 11:56:42.726 4335 4471 I Gmail : MainSyncRequestProto: lowestBkwdConvo
Id: 0, highestHandledServerOp: 924491, normalSync: true
Let me know if you can make any sense out of it.....
And I am able to install and uninstall apps it is not like I wont be allowed to install them its like when I restart all the changes that I make are lost system setting any apps the I installed/uninstalled.....??
Is there anything else you want me to do??
jimbridgman said:
Ok, I am going weigh in here now....
All of this has absolutley NOTHING to do with the Bootloader/mbmloader, not sure where that came from.
My advice is disable all the updates in the playstore, or well the auto update feature, then those apps that you mentioned that are getting updated. After you restore the fxz, this time make sure that the auto update is off, and then update each of the noted problem apps ONE AT A TIME, then when the issue starts you know which one is the problem app, most likely the last app installed or updated, and I would not install that one again. Simple solution here.
Yes this will be painful, because you might have to do the fxz more than once, but it is the best way to know you are back to 100% stock again.
Click to expand...
Click to collapse
But, I am not able to an fxz completely thats what I said...when I try to do fxz back to stock while trying with rsd lite it failed at step 3 saying cannot write mbmloader
then I tried the script method and it said that mbmloader is restricted and it cannot write to it and it did rest of e things which were in the script.....so not matter how many times I fxz it when I start my phone it just gets back to where I left it...??
All I want is that I can just flush everything my phone nad get it back to as it was new....no apps nothing...
black_panther10 said:
But, I am not able to an fxz completely thats what I said...when I try to do fxz back to stock while trying with rsd lite it failed at step 3 saying cannot write mbmloader
then I tried the script method and it said that mbmloader is restricted and it cannot write to it and it did rest of e things which were in the script.....so not matter how many times I fxz it when I start my phone it just gets back to where I left it...??
All I want is that I can just flush everything my phone nad get it back to as it was new....no apps nothing...
Click to expand...
Click to collapse
You have a corrupt install, since it did not flash the correct BL, and most likely other files from the fxz. Your issue is that being in that state will make your phone completely unstable as it is. You are most likely partly on 2.3.5 and 2.3.6 at this point.
Did you EVER install the ICS leak?
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US?
If you can answer all of that, I am sure I can get you all fixed with a good fxz.
jimbridgman said:
You have a corrupt install, since it did not flash the correct BL, and most likely other files from the fxz. You issue is that being in that state will make your phone completely unstable as it is. You are most likely partly on 2.3.5 and 2.3.6 at this point.
Did you EVER install the ICS leak?
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US?
If you can answer all of that, I am sure I can get you all fixed with a good fxz.
Click to expand...
Click to collapse
Did you EVER install the ICS leak? No I never tried the ICS leak!!
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US? Yeah I applied the correcty fxz patch.....I am currently on 2.3.5 and I used the 2.3.5 fxz patch only......I purchased my atrix 2 from LA and I am using the phone in LA only
Well to your doubt that I can be partially on 2.3.5 and 2.3.6 .....well that is somehow possible since when the 2.3.6 update came out I tried to install it but it always failed in the halfway...but that never seemed to cause the problem...I tried that a couple of times when the update came out and then I gave up on it ....I thought it may be because I rooted my phone incorrectly.....but still my phone was working perfectly fine after that....
black_panther10 said:
Did you EVER install the ICS leak? No I never tried the ICS leak!!
Did you apply the corerct fxz patch? which version of firmware are you on, and where do you live (what country), and are you using an AT&T phone outside the US? Yeah I applied the correcty fxz patch.....I am currently on 2.3.5 and I used the 2.3.5 fxz patch only......I purchased my atrix 2 from LA and I am using the phone in LA only
Well to your doubt that I can be partially on 2.3.5 and 2.3.6 .....well that is somehow possible since when the 2.3.6 update came out I tried to install it but it always failed in the halfway...but that never seemed to cause the problem...I tried that a couple of times when the update came out and then I gave up on it ....I thought it may be because I rooted my phone incorrectly.....but still my phone was working perfectly fine after that....
Click to expand...
Click to collapse
Ok, now you still did not answer the exact firmware version your on... please do this:
Settings --> About phone, now give me the long string of numbers and letters under the following things:
System Version:
Android Version:
Kernel Version:
Build number:
Once I have all of those, I will know how to patch the fxz for you. If you are truely on 2.3.5 there would be no need at all for any fxz patching by the way, that only applies if the 2.3.6 OTA actually took.
jimbridgman said:
Ok, now you still did not answer the exact firmware version your on... please do this:
Settings --> About phone, now give me the long string of numbers and letters under the following things:
System Version: 55.11.16.MB865.ATT.en.US
Android Version:2.3.5
Kernel Version: 2011-09-21 09:42 off.Bld LUD_EDISON_RLD7_PATCH_27_110921_0913
Build number:5.5.1-175 EDEFW1-16
Once I have all of those, I will know how to patch the fxz for you. If you are truely on 2.3.5 there would be no need at all for any fxz patching by the way, that only applies if the 2.3.6 OTA actually took.
Click to expand...
Click to collapse
I have used the exact same version of fxz as the kernel version.....
black_panther10 said:
Line Runner
Words with friends
Foursquare
Facebook
3D Matrix Vol.2 (its a live wallpaper)
TuneIn Radio
Skype
GO Keyboard
Nexus Pro Live wallpaper
GO Locker
(this only these got updated....it can the live wallpaper app I ma not sure)
Click to expand...
Click to collapse
Once you uninstall these apps, is everything fine? And if so, uninstall them all, and update them ONE at a time to see which one is borking everything.
Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.
Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems
a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....
ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?
a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.
zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.
i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!
My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.
Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues
Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?
Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.
Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.
Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.
I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.
I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.
Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.
aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.