Database Users

[Resolved] dx moto logo boot error

hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt

You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App

You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk

google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition

Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk

well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that

Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App

mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk

well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.

if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App

Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App

If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App

thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.

i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.

mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.

i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?

It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App

oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol

Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!

yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.

EA28 OTA

I just activated my girlfriend's phone and immediately it prompted for update, so I did. To my surprise it was not DL09, but instead EA28. So after some google searches I found this:
http://phandroid.com/2011/02/03/samsung-fascinates-ea28-update-coming-to-fix-emergency-calling-bug/

The site is basically right, they repackaged dl09 with the emergency calling bugfix and pushed it out with a new build number.

just got mine... I'm gonna have a seizure in a public place to test it out.

Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App

Deathbeaver said:
Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It worked for me on DL09 and this isn't that much different so I'd say yes.

Skrazz said:
just got mine... I'm gonna have a seizure in a public place to test it out.
Click to expand...
Click to collapse
Youtube...

The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There is a thread on ODIN. Simple directions, I thought.
Sent from my SCH-I500 using XDA App

So how does one "Make instantaneous emergency calls from a locked device in a time of need"?

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Just as a side note if your having to redo the phone from scratch make sure to put the pit file in the pit on odin otherwise the phone will not activate!
Click to expand...
Click to collapse

One Click root works just fine! Just completed root!

I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.

PantsOnFire said:
I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.
Click to expand...
Click to collapse
When you flash a new ROM it overwrites CWM, so you'll have to re-install it with Odin.

What is pit in general and why it is needed?

CNemo7539 said:
What is pit in general and why it is needed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=771426
may answer some questions
http://forum.xda-developers.com/showthread.php?t=723596
may answer others
the search tool is great. google works too.

Update broke my phone!
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?

Yeah I just went to ask if there is an update and it said yes. Afraid to update because who knows if it'll break root....
Sent from my SCH-I500 using XDA App

Why suggest people to mess with pit in odin? You do NOT need to do this. Geez, people make this mistake enough on their own. Pda, choose file, press start... thats it.
Sent from my stock 2.1 unrooted, fully bloated Fascinate

EA28 broke my phone
knmb323 said:
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?
Click to expand...
Click to collapse
I managed to get my phone to stop rebooting every 3 minutes by ending the InnoPath Active Care process and clearing the cache. But when I woke up this morning, the phone was at the emergency recovery screen. It went into a cycle of rebooting that made it as far as media scanner. I got it to stop rebooting by turning ON wifi (I suppose that's because Active Care needs WiFi off to do an OTA). Does anyone have any suggestions on how to stop this "Feature" that is rebooting my phone?

You tried pulling the battery (soft reset) i presume? After that theres factory rest, then odin back to stock
Sent from my stock 2.1 unrooted, fully bloated Fascinate

[ROM] RUU 2.11.605.2 Newest Leak Rooted Stock & Deoxed & Deoxed/Debloat

Thanks to Android Police leak. The links provided will be for rooted users only.
Flash in Recovery Only!
AS A EXTRA MEASURE, I SUGGEST WIPE CACHE, DALVIK, AND IN CLOCKWORK UNDER "MOUNTS AND STORAGE" FORMAT /SYSTEM. You can keep your data if come from 2.11.605.0
I will be working on rooted only PURE stock, Rooted and Deoxed, and Debloat. So download away well as many times as my free account allows LOL.
None of this is thanks to me other than my time I am sure there is a whole list of people I can thank having to do with programs I have used Android-SDK & Kitchen, SU, and Busybox so I will say Thank you to them but other than that still trying to learn if someone wants to send some data my way, hit up the PM.
All versions have booted up on Android-SDK Emulator and on my phone. I was a little conservitive on the Debloat but it saved over 160MB so if I didnt take enough out for you, sorry.
Android Police Link for non-rooted users
http://www.androidpolice.com/2011/0...build-2-11-605-2-ruu-for-the-htc-thunderbolt/
Rooted Stock
http://www.megaupload.com/?d=V4H10NI7
MD5 - DFA537E258B8D297CB7A834A308689A7
Rooted Deoxed/Debloat
http://www.megaupload.com/?d=MOV2627N
MD5 - BB539379C297A5EACC592D51DD5F01CC
Looking to get a little more away from stock and want a Kernel to under/overclock link provided down below.
Read up on it here. http://forum.xda-developers.com/showthread.php?t=1260185
http://www.megaupload.com/?d=B4XM1ZZF (Kernel)
MD5 - 2530A337B92871E6BC75B1B9D4DE67F1
If anyone wants stock kernel if you don't like kernels you flashed I have a copy in zip I can post if needed.
As always I am not responsible for what happens to your phone please follow the instructions. I did an edit and I posted all the MD5s for these ROMs sorry it did slip my mind

thanks! does this have automatic Voicemail alerts?

I believe I read those are not fixed yet I know they may pop up but mine would only go away after a reboot, but the camera is fixed
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

All Versions are up, MD5 are up, Kernel is up, and I am going to sleep. Let me know if they all work out for you who ever downloads them I did test each one on SDK and my phone I am now back to my Synergy ROM hope you enjoy your GB fix have a great day. Also thank me if you download this so I know my work was worth something

Tried stock rooted and deoxed niether will load even after complete wipe and sd format all i get is htc screen white back ground and thats it ???

Not Booting
Flashed, wiped everything, still stuck on HTC splash screen. Not working

Will look into it once again. All 3 loaded on mine if I run into issue will pull post till fixed. Anyone else having issues who is rooted and has flashed before?
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

ghamden said:
Tried stock rooted and deoxed niether will load even after complete wipe and sd format all i get is htc screen white back ground and thats it ???
Click to expand...
Click to collapse
Wait did you say you formatted your SD card? I said system format.
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

Same for me. White HTC screen. Wiped data, cache, dalvik formated system. Tried system mounted, not mounted.

Will pull till I can explain these issues
Till I get my RUU working for everyone you can download the rooted versions here
http://www.htcthunderbolt4g.com/htc...breadrockv1-0-v1-1-(newest-gingerbread-leak)/
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

Anybody have radio versions for this RUU?

I don't think it has a new radio, just the same one from 2.11
Sent from my ADR6400L using Tapatalk

All files pulled till issues have been resolved.

Cubs2008 said:
Anybody have radio versions for this RUU?
Click to expand...
Click to collapse
It's the same radio as the previous leak. 817 for cdma and 802 for LTE
Sent from my ADR6400L using xda premium

thisismalhotra said:
It's the same radio as the previous leak. 817 for cdma and 802 for LTE
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yes same radios which to me suggest this is as close to OTA w/o the VM fix.
Uploading Stock_rooted now just did the whole thing over.
Deoxed_Debloat will be up in an hour

Thanks guys...I just wanted to check to make sure.

All versions are now redone and live in OP. I did test rooted_stock and worked fine I did not test rooted_deoxed_debloat since i work night shift and need sleep. Please let me know if there are any issues with these two files if you download them either way yes or no. Thx.
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

I'm not sure it is a problrm with the zip. I think it may be a cwm problem. I tried the link you posted for the other site and same white screen. When I try to do more than two maneuvers (for lack of a better term) in cwm I get the android in the box with the arrow. Going to try to find the .zip for cwm and reflash it.

Rooted and DEOX'ed file stuck on white screen

Same issue here, stuck at the white HTC screen
i've tried all of the rooted zips and md5 checked out fine.

[Q] 4.5.621 uprgrade failed

I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack

Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision

rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack

Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk

update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.

From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.

4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe

Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2

missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.

Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error

Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app

palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help

Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time

Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk

deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk

[Q] UI Stops Working EVERY DAY!!!

No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???

System UI errors
alwaysbelieve1 said:
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
Click to expand...
Click to collapse
Did you freeze any of your system apps?

mcapozzi said:
Did you freeze any of your system apps?
Click to expand...
Click to collapse
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com

Launcher
alwaysbelieve1 said:
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Click to expand...
Click to collapse
What launcher are you using?
-Mike

mcapozzi said:
What launcher are you using?
-Mike
Click to expand...
Click to collapse
Nova Prime

alwaysbelieve1 said:
Nova Prime
Click to expand...
Click to collapse
You didn't by chance accidentally freeze the stock launcher?
-Mike

mcapozzi said:
You didn't by chance accidentally freeze the stock launcher?
-Mike
Click to expand...
Click to collapse
No

Here is a thread regarding the issue, but none of the "fixes" worked for me: http://forums.androidcentral.com/sa...0371-unfortunately-system-ui-has-stopped.html
I deleted Facebook so we shall see if that does the trick.

When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app

Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4

ezknives said:
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.

evastonian said:
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes that is exactly what I do every time. Today I started completely fresh and installed everything manually so I can better narrow down any issues.

alwaysbelieve1 said:
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
Click to expand...
Click to collapse
Yea I backup everything on my external hard drive (that after I back anything up I bubble wrap and put in my fire safe< a bit paranoid) every week, so that if anything happens I can just wipe it clean and start fresh (I have never used rsd lite but I'm guessing its somewhat like option one of Matt's utility) that restores your phone to a moto flashed like state... ready to be sold as a certified like new device (as Verizon would call it)...
Sent from my XT907 using xda app-developers app

Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.

RikRong said:
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
Click to expand...
Click to collapse
Don't even know how to do this or what this means exactly...