Related
How can you tell if the update to the rom was sucessful? Is there a different vesion number in the phone? Thanks
It looks different? The internal and external sd cards are switched? Myverizon app is gone? If it said in recovery that the installation is successful, it worked. If it produced an error it didn't. These are all good ways
Sent from my DROID X2 using XDA App
only reason im asking is I installed .02 with no problems, but was having the rebooting when charging issue. i installed the .02-.03 patch, it said it installed sucsesfully but i was still having the same issue. I'm on .04 now and i am liking it, but i hear a new patch will be released today and wanted to make sure it was actually updated.
Alright well as long as there was no error during the flash its all set. It shouldn't matter if he releases a full rom and not a patch. A full rom can be flashed over anything with the same base, the patches need to be flashed over the correct version.
Sent from my DROID X2 using XDA App
I had flashed .4 directly over .3 with a couple of wipes in-between and had no issues with the transition. however the rom was a bit slower than .3 imho. i am def going to try to flash to his next version when it comes available since he has mentioned it being a big step forward.
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
botzen67 said:
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
Click to expand...
Click to collapse
If you have Titaniumbackup Pro then just freeze the update/updater apk. If not, I would suggest getting it, it is well worth the cost.
Great suggestion. I have TiBu Pro and have frozen the two Update apps I found in the list along with "VZW Package Installer 1.0" and "Field Test 2.1-update1" and "Field Trial 2.2.1", having done the last three just now. It did try to do yet another update a few hours ago, so we'll have to see if the last three do the trick.
Anybody got any other suggestions for Apps I should freeze to prevent OTA updates?
Update: None of the items I've frozen seems to have made a difference. Still looking for other ideas.
I'm thinking it was DM.apk or something similiar that controlled ota updates. I don't have a stock rom running atm so i can't be sure. When you find the correct one you won't be able to get to the update phone screen from settings any longer. Wish i could be more help but i just can't remember.
Sent from my HTC ThunderBolt using Tapatalk
I was having that same problem and I just broke down and applied the update. I used clockwork rom manager and a rooted/deodexed update file that I found on the forums (linked from androidpolice, i think). Flashed the update, without wiping the current setup, then flashed the radio from the bootloader. Worked like a charm. I've got the update, it's not searching for more, and it reinstalled all the bloatware that I deleted instead of freezing when I got the phone. I went back through and freezed all the bloat junk, and my TB is running better than ever. Oh, and I'm just running a rooted stock rom.
I too suffered the same problem. I just ended up installing a custom rom to get rid of it for good. Best decision I ever made, I really like the Synergy build.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.
I have had many phones and never had as much trouble than this phone is giving me. Every rom that does work when I flash them don't have any wifi or service. Even when I install gapps it is like it skips the setup and goes straight to the home screen.
I just came from a bionic and didn't think it would be much of a change to make this phone run like my bionic did. I have tried recreating rom slots with fresh installs and wipes on several roms, most of them cm10 based and even liquid smooth wont even install which is the rom I love the most. I have looked for several fixes but nothing seems to be working.
Is there something I am missing? Do you have to unlock the bootloader on this thing or something? Any help would be appreciated.
Rmbloungeact said:
I have had many phones and never had as much trouble than this phone is giving me. Every rom that does work when I flash them don't have any wifi or service. Even when I install gapps it is like it skips the setup and goes straight to the home screen.
I just came from a bionic and didn't think it would be much of a change to make this phone run like my bionic did. I have tried recreating rom slots with fresh installs and wipes on several roms, most of them cm10 based and even liquid smooth wont even install which is the rom I love the most. I have looked for several fixes but nothing seems to be working.
Is there something I am missing? Do you have to unlock the bootloader on this thing or something? Any help would be appreciated.
Click to expand...
Click to collapse
Wifi usually fixes itself after reboot, but for no-service I dont know.. Are you flashing correct version for your Razr (xt910/xt912), or flashing GSM patch if you have xt912 on GSM network?
Not to be redundant, but how ARE you flashing the ROMs? I've never had issues with connections (so long as I am using the applicable google apps, I have had to revert to a release or two earlier for proper operation in the past). I wouldn't recommend flashing ROMs via RSDlite, if that's the route you're taking. BMM and Safestrap (The latter can be achieved with Matt's Utility, it's what I use) are better options. Using a different partition on the internal storage, and retaining Stock rom. I never had any issues with Avatar (CM10.1 based). I'm about to try out AOKP. Good luck.
LuckiestNut419 said:
Not to be redundant, but how ARE you flashing the ROMs? I've never had issues with connections (so long as I am using the applicable google apps, I have had to revert to a release or two earlier for proper operation in the past). I wouldn't recommend flashing ROMs via RSDlite, if that's the route you're taking. BMM and Safestrap (The latter can be achieved with Matt's Utility, it's what I use) are better options. Using a different partition on the internal storage, and retaining Stock rom. I never had any issues with Avatar (CM10.1 based). I'm about to try out AOKP. Good luck.
Click to expand...
Click to collapse
Well I have been using safestrap since I used it on my Bionic and I am already familiar with it. The one that is bugging me the most is not being able to flash LiquidSmooth 2.9. (I am on SS 3.53 btw) Also I am using the XT912 and already researched the difference between 910 ROMS before flashing.
When I try to install it the error comes up saying:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: no file_contexts
set_perm: some changes found
E: error executing updater binary in zip '/sdcard-ext/Liquid-JB-v2.9-OFFICIAL-spyder.zip
Error flashing zip
I just wonder, if that thing is saying that the zip is meant to be an update for an existing version of LiquidSmooth. But on goo.im there is only 2.7, 2.8 and 2.9.
I've never seen that error (but I've been wanting to try LiquidSmooth, maybe I can duplicate the problem). I know with AOKP, I have to install on romslot2. For whatever reason. Have you tried any other slots besides 1?
EDIT
http://forum.xda-developers.com/showthread.php?t=2222535
The installation instruction for LiquidSmooth 2.9 say to install on RomSlot3, and only RomSlot3. I'll give it a whirl on 1 and see if the error is duplicated, but it shouldn't effect the install, regardless of the slot #.
http://goo.im/devs/liquidsmooth/spyder/Liquid-JB-v2.9-OFFICIAL-spyder.zip
This is the mirror I used to get the ROM.
Installed on Slot 1 without errors. Flashed gapps, wiped cache, restarted- wouldn't boot.
Wiped and deleted Slot 1
Installed on Slot 3 without errors. Flashed gapps, wiped cache, restarted- Success!
I never could duplicate the error you had, using the JB Liquid Smooth I got from goo.im
Also, for what it's worth, in the "Issues" category on the LS link from above, it said there was an autofix that would correct the wifi connectivity problem. Mine would never fully turn on wifi on first boot. Rebooted, worked perfectly. And the CM style setup went off without a hitch.
I also used goo.im to get mine. I tried all three versions of it but no success; all three got the same error code. I am wondering if the version of safestrap I am using is causing the error.
Rmbloungeact said:
I also used goo.im to get mine. I tried all three versions of it but no success; all three got the same error code. I am wondering if the version of safestrap I am using is causing the error.
Click to expand...
Click to collapse
Just threw out the version 3.5x of SS I was using. Going to try 3.11 and see how it goes. Man, I hope this works, I just came back from using an iPhone for the last two months after letting my brother have my Bionic because they couldn't flash the iPhone on his service provider. I guess if it doesn't work I will be happy having android back nonetheless. Just want something other than motoblur.
Rmbloungeact said:
Just threw out the version 3.5x of SS I was using. Going to try 3.11 and see how it goes. Man, I hope this works, I just came back from using an iPhone for the last two months after letting my brother have my Bionic because they couldn't flash the iPhone on his service provider. I guess if it doesn't work I will be happy having android back nonetheless. Just want something other than motoblur.
Click to expand...
Click to collapse
So I scrapped 3.5x for 3.11 and the install went perfectly normal. Accidentally installed the wrong gapps package and had a force close assault from hell. Redid it with the right gapps and everything is up and running now. I am so glad to have it running and ready to set up now. Thanks for your help guys!