Database Users

How I upgraded to WW version of Jelly Bean after a booched install stopped it.

Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium

gurningchimp said:
Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
I have the same problem but i can't find the dlpkgfile file. Searched with root explorer in the cache folder and rest of system root but nothing... Also tried temp. unroot with cold boot... :crying:

thanks, the whole morning and afternoon this was driving me crazy... but now its dl again :good:

Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.

Update worked fine for me. I Just wiped my data as well
Sent from my R800i using xda app-developers app

bazzio said:
Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.
Click to expand...
Click to collapse
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:

What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.

Ulric099 said:
What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.
Click to expand...
Click to collapse
Tried this, and it let me download and install the update again, but it failed again

mcall_r said:
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:
Click to expand...
Click to collapse
Im in the same boat as you, I did the same steps but it fails with the red triangle... I even did a factory reset and still doesnt update, could it be becuase of the root?

Have tried everything (dm delete, cm delete, temp unroot, atp tweak uninstall, cold boot, regular boot, etc) after the download failed at 99% and still either can't find or get immediate download failed. No JB love here
Sent from my SGH-I747M using XDA Premium HD app

Could anyone upload EmailWidket.apk from the WW version?
Found one but it says the check sum is not correct when trying to update...

During my update I also got the red triangle, so after a bit of investigation /cache/recovery/last_log pointed me to checksum error of Keyboard.apk. Restored it, fixed CM and DMClient but now it just says no update found. Any other suggestions?

VZW 7.7 Update

I just got the VZW 7.7 update but it was only 29.3 mb, but it was not ICS. Did anyone else get the 29mb update today? :cyclops:

After it downloaded the update and rebooted I got the Android with gear logo then an Android with an exclamation mark in the middle. It then rebooted and came back up. It's no longer offering me the update so I don't know if it was applied correctly or not. The Android with an exclamation mark looked like something I would get if the update had failed. Not sure what it is?

gshaw1967 said:
After it downloaded the update and rebooted I got the Android with gear logo then an Android with an exclamation mark in the middle. It then rebooted and came back up. It's no longer offering me the update so I don't know if it was applied correctly or not. The Android with an exclamation mark looked like something I would get if the update had failed. Not sure what it is?
Click to expand...
Click to collapse
I had the same happen as well as other people on the Verizon forum. 29.3MB update and an android with exclamation mark after install. No changes in the About device screen.

thanks just a little excited!

Try rebooting into the boot loader. Power + down volume. It will boot to Odin and start the real download.
Sent from my Nexus 7 using Tapatalk 2

The update we are looking for is LP10 (ICS 4.0.4).

Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.

dailong said:
Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.
Click to expand...
Click to collapse
Just tried this...no luck. I see the last check date change to 1969, but a recheck just says no updates available.
Did the FH01 29-meg "pre-update" work on yours (without an exclamation mark and actually showing FH01 in About prior to ICS)?
Rodney

rhester72 said:
Just tried this...no luck. I see the last check date change to 1969, but a recheck just says no updates available.
Did the FH01 29-meg "pre-update" work on yours (without an exclamation mark and actually showing FH01 in About prior to ICS)?
Rodney
Click to expand...
Click to collapse
Yes the 29.3 update worked with no exclamation mark. I was stock. Initially I forced quit google services, cleared the cache and restarted the device. That didn't work so I cleared the google services cache first, forced quit then checked for updates. Hit the check now button couple of times and it showed up.

dailong said:
Yes the 29.3 update worked with no exclamation mark. I was stock. Initially I forced quit google services, cleared the cache and restarted the device. That didn't work so I cleared the google services cache first, forced quit then checked for updates. Hit the check now button couple of times and it showed up.
Click to expand...
Click to collapse
I tried Clear Data first, then Force Stop on Google Services, but always get the exclamation mark while trying to apply the 29.3MB update. I guess this is stopping the ICS update from coming through. Anyone have any ideas on how to get around this? I was rooted, but I used the Gingerbreak method to unroot and it seemed to work just fine. I am also on the stock recovery.

Has anyone been able to do it if they had installed CWM Recovery? I got an error that it wasn't signed properly and it asked if I wanted to install anyway, so I did and it failed there too.
---------- Post added at 02:21 PM ---------- Previous post was at 01:44 PM ----------
Do you have to be back to stock recovery for this update to work?

This has turned into a very special event. I've talked to Verizon support a couple times (meaning on hold for hours) and this is what seems to be happening.
There is a problem with the update coming from Samsung. I found a forum entry on Verizon reporting the very same problem with the GT 10.1 update a few months ago. Bottom line this isn't the first time this problem has been seen and it's up to Samsung to fix it.
That said as of a couple hours ago Verizon has no record of the problem. I take it most people in this forum don't report errors to Verizon. It has now been reported and is being escalated. If you have a chance to report the problem to Verizon or Samsung it might help speed up the fix.
During my customer support outing Verizon has been very nice but total useless. They routed me to Samsung level 1 who told me no update was taking place and they contacted Samsung level 2 support for me which hung up the phone on me and on the Verizon rep. It was interesting.
I guess it's time to take a break and let it shake out.

dailong said:
Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.
Click to expand...
Click to collapse
If you have the LP10 update can you post it for everyone else? or is it now gone from your cache folder? What about a Nandroid or have you already started to tinker in the ROM?

Here is the youtube video of ICS on the Verizon Galaxy Tab 7.7
http://www.youtube.com/watch?v=dg9egFXi9FA&feature=plcp

so your update was for FH01 to LP10?

We need to make a thread organizing all this information with updating issues and figure out what people who got the update to work have in common.
Also, someone with the update please post the file from your cache or make a "as stock as possible" nandroid and post that.

"This video does not exist"

fixed

dailong said:
fixed
Click to expand...
Click to collapse
This is getting ridiculous. I also called Verizon, of course tech support is clueless. They didn't even know about any update for our tab since May 2012. Their answer was to Wipe Data/Factory Reset, then try the update..... of course, didn't work. Unrooted, stock recovery... Couldn't be more stock than I am right now. Update will not install. What gives?
Anyone have ANY suggestions on how to kick this thing off? Starting to think I should have stuck with my OG galaxy tab..... Which has Jelly Bean running on it by the way....

dailong said:
Here is the youtube video of ICS on the Verizon Galaxy Tab 7.7
http://www.youtube.com/watch?v=dg9egFXi9FA&feature=plcp
Click to expand...
Click to collapse
Very interesting news. Do you have it rooted yet? Is there any way to root the sucker? Because then it's super easy to grab the rom and make it available for everyone here!

"Unfortunately, System UI has stopped" won't stop popping up. So frustrating.

"Unfortunately, System UI has stopped" won't stop popping up. So frustrating.
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new

Factory reset?

309041291a said:
Factory reset?
Click to expand...
Click to collapse
I guess that's my last resort. Damn
Edit: How would I even factory reset it? I literally can't use the phone. It's bricked. And in the recovery mode menu there is no option to factory reset. (tried pressing power and volume up)

If your phone is still locked, save the data (if needed) via adb and unlock it. But there could be easier way.
Sent from my Nexus 4 using xda premium

go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.

neotekz said:
go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.
Click to expand...
Click to collapse
I've had something similar to this on my G2x at one point; Android keeps popping up with errors and you can't do a single thing but reboot...which ends up erroring the same way when you're back in in an endless loop.
OP, you'll have to wipe and reinstall. If you've rooted it and enabled USB debugging then you're golden. If not, you'll have to go through several hoops to flash a factory image.
This link should help. http://forum.xda-developers.com/showthread.php?t=2016395
Several users have managed to invoke ADB commands.

Launcher
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...

cadiutori said:
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...
Click to expand...
Click to collapse
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4

time and space don't exist
spaceman860 said:
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4
Click to expand...
Click to collapse
maybe useful for someone else

cadiutori said:
maybe useful for someone else
Click to expand...
Click to collapse
Yes. Maybe he didn't restore the default keyboard before removing.

Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA

1droidmod said:
Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA
Click to expand...
Click to collapse
Flash factory image
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
Flash factory image
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
He doesn't have a nexus. He's in the wrong place
From my BLACKED OUT N4

Sorry.. Googled topic, brought me here, did not realize... And i did fastboot the firmware, still systemUI issue but only with PAC-man... Handful of others I tested no issues.. I read on github (after i posted here) is a Know issue for PAC and why!!! Just strange, V05 was released weeks ago, why sooo long for issue to submerge... And no issues with V01-V04
XT912 RaZR SpYdEr CDMA PAC-manVO5

I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.

nubhihi219 said:
I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.
Click to expand...
Click to collapse
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!

hp420 said:
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!
Click to expand...
Click to collapse
you haven't used stock 4.2.2 have you? Its quick settings is so frustrating, it always takes me to Settings to turn on or off Wifi. I want a quick Settings that takes only one click to turn on or off Wifi, so I have to install that mod. Btw, I'm still waiting for the battery to die
_______________________________________
Update: Just to confirm, it works as I expected

hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.

cjleven4 said:
hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.
Click to expand...
Click to collapse
I recently had this issue and determined also that it must be something with my status/notification bar as it seemed to resize the screen to show the bar and then immediately resized it again as it displayed the System UI message. I use both Wanam and XBlast and disabled those as well as all Xposed modules. I also disabled Nova Launcher as default and rebooted. Re-enabled all and rebooted again and problem was resolved. Hopefully this will help others as well.

Same thing happened to my phone - Huawei Ascend y511. System UI has stopped Help!!!!!
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
Hi I have huawei ascend y511 and after disabling google keyboard i turned off phone and put it back on. This happened. Help me please, How do I get it back to normal? If I factory reset, will it work? Or should I let the battery drain out and do something. I can't do anything on my phone now because I can't even press anything because of the really frequent pop out of "system ui has stopped" . Help please.

Rooting my Metro PCS S3 (SGH-T999N)

Is there any way too root this phone?
Sent from my SGH-T999N using xda app-developers app

More info
Sent from my SGH-T999N using xda app-developers app

Root SGH-T999N (metro PCS) to SGHT999NUVUBMK7 after 4.3 update
RawesomeMike said:
More info
Sent from my SGH-T999N using xda app-developers app
Click to expand...
Click to collapse
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.

polkcontracting said:
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.
Click to expand...
Click to collapse
You say you think.....doesn't sound reassuring can you elaborate a bit more? I don't seem to understand what you are getting at if it works or not? I don't know if I should root my phone now or wait for 4.4.......

Have you heard of/tried the Morobo + Shuame method? Worked a treat for my HTC Wildfire, Motorola Defy, and my HP Slate 7.
Seriously worth a shot if you ask me. A link to the XDA thread:
http://forum.xda-developers.com/showthread.php?t=2092349

Know this is old, but if you're still looking for a method, I successfully rooted my T999N yesterday using ChainFire's autoroot for the t-mobile variant (the T999). I'm new so I can't post a link here, but if you google "chainfire autoroot", it'll direct you to his page where you can download the package from the list of supported devices. The package conveniently contains a version of Odin3 that you will use to flash his stuff to your phone.
Remember, the phone must be in samsung's "download mode" to receive the flash. You get this model into the mode by powering it off, then holding the HOME button, the POWER button, and the VOLUME DOWN button all at once. When the warning message comes up, you push VOLUME UP to continue, then the phone will be in download mode. You can then connect the phone to your computer and if you have the drivers installed correctly, Odin will recognize the phone and be able to send the flash. You will then need to go about disabling Samsung's security software, KNOX, before the phone will be fully rooted. There are plenty of guides on how to do that so no worries there.

(XT1575) Moto X Style February Security Update Problem

Hi all
First I'd like to apologise if this thread already exists but so far I cannot find anything (please link me it if it does)(this is my first post as well)
I bought the phone a couple of weeks back. The phone had Android 6.0 marshmallow on it out of the box. The phone has been working perfectly up until today. This Morning i got a notification to say there was a new security update available. I downloaded the update (6mb) and installed it. I went off to work and when i took the phone out of my pocket it was rebooting. I waited for it to boot and after about 20 seconds of using the phone it became unresponsive, i.e. the screen froze, and a couple of seconds later the phone restarted. The phone rebooted constantly throughout the day when I tried to use it. When I got home I searched online for help but didn't find anything, although a factory reset can solve a lot of problems and so that's what I did. I setup the phone as a new phone but after about mins it froze and rebooted again. I have just turned the phone off and I am using a spare atm. I am considering a re flash of the software, however if any of you have had the same problem and have had an easy fix, please let me know. Any help is appreciated
Regards
TechGuy

It is odd that even after a factory reset it did this. Maybe try another factory reset and put your Google account on the phone but not any of the apps from Google restore. This will tell you if an app that you have installed is clashing with the new security patch or if the phones software is the culprit.
Sent from my XT1575 using Tapatalk

TechGuy82 said:
Hi all
First I'd like to apologise if this thread already exists but so far I cannot find anything (please link me it if it does)(this is my first post as well)
I bought the phone a couple of weeks back. The phone had Android 6.0 marshmallow on it out of the box. The phone has been working perfectly up until today. This Morning i got a notification to say there was a new security update available. I downloaded the update (6mb) and installed it. I went off to work and when i took the phone out of my pocket it was rebooting. I waited for it to boot and after about 20 seconds of using the phone it became unresponsive, i.e. the screen froze, and a couple of seconds later the phone restarted. The phone rebooted constantly throughout the day when I tried to use it. When I got home I searched online for help but didn't find anything, although a factory reset can solve a lot of problems and so that's what I did. I setup the phone as a new phone but after about mins it froze and rebooted again. I have just turned the phone off and I am using a spare atm. I am considering a re flash of the software, however if any of you have had the same problem and have had an easy fix, please let me know. Any help is appreciated
Regards
TechGuy
Click to expand...
Click to collapse
@TechGuy82 ... Go to the "General" thread (if you haven't already) the whole matter of installing the update is being thrashed out there.

Yeah check out the thread in general... Also just wanted to confirm that I'm having the exact same problem you are and have tried factory reset with the same results. I'm currently attempting a complete software flash with the CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip using the flash all bat

ahent said:
It is odd that even after a factory reset it did this. Maybe try another factory reset and put your Google account on the phone but not any of the apps from Google restore. This will tell you if an app that you have installed is clashing with the new security patch or if the phones software is the culprit.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
After the factory reset, the phone is rebooting before i can even set it up.

Same issue. I even rerooted and flashed a different rom and it will do it. going to try flashing back to stock before the update and see what happens.

I have the notice for this update - I am not rooted nor have I installed TWRP (I'd like to, eventually)
What I do need to know:
I don't use the phone like most do - services except for buying apps are not necessary. I have downloaded and paid for large data base nature and astronomy apps which a dumb phone won't run. I like speed on the phone so a program opens faster.
Given that - I have disabled 95% of the social type apps on the phone. I've disabled all the extras from Motorola. I don't use, want or need them. What will happen if I apply this update? I
1. Will it refuse to run if something is disabled?
2. Will it override disable and open whatever it thinks it needs?
3. Will it just install where it needs to?
4. Will it bugger the phone?
I just read through what's in Google services and I don't seem to need that. The only thing would be verification of a bought app from Play Store. I disabled Maps, Location, Hangouts, Photos -- There's better paid apps in Play Store and that's why I need to be sure that Play Services doesn't do the checks to see if you bought the app.
I like the feel of this phone, the performance and I love the camera. I just want to use it my way. If I could carry all my reference books with me, I'd use a feature phone. I like to take nature walks and birdwatch.

Guys can anyone help, after full restore on 6.0 I can't normally reboot or turn on my phone .the trouble is when am turn on my phone it loads bootloader instead boots up, and in bootloader when I click "start" it booting up. Reboot do the same thing .
Sent from my XT1575 using Tapatalk

towfurious said:
Guys can anyone help, after full restore on 6.0 I can't normally reboot or turn on my phone .the trouble is when am turn on my phone it loads bootloader instead boots up, and in bootloader when I click "start" it booting up. Reboot do the same thing .
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Clear data and cache in recovery?
(Warning, do you have a backup?)
Enviado desde mi XT1575 mediante Tapatalk

Altomugriento said:
Clear data and cache in recovery?
(Warning, do you have a backup?)
Enviado desde mi XT1575 mediante Tapatalk
Click to expand...
Click to collapse
It happens when I'm flash stock moto x ROM from moto gdrive on stock recovery , and on twrp too, and yes before flashing I had clear all cache and and data in recovery .
Sent from my XT1575 using Tapatalk

towfurious said:
It happens when I'm flash stock moto x ROM from moto gdrive on stock recovery , and on twrp too, and yes before flashing I had clear all cache and and data in recovery .
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I have got answer for my own question.
It happens when before flashing in terminal type "fastboot oem fb_mode_set" , thats kind like bootloader force mode , when you reboot it always boots to fastboot. So after flashing i forgot to type "fastboot oem fb_mode_clear" to exit force mode.
Sorry for too many "reboot" words)

The only way I was able to resolve it was to do a full restore using this factory image. Leave it in fastboot and reflash. I tested before had wiping my sd card, removing my sd, wiping the internal, cache. Figured at that point easier just use a full stock image and see what happens.
Here is the Image : https://docs.google.com/uc?id=0B5AiGacWcBRzMTBlWmppOC1DS3c&export=download

oracleminder said:
The only way I was able to resolve it was to do a full restore using this factory image. Leave it in fastboot and reflash. I tested before had wiping my sd card, removing my sd, wiping the internal, cache. Figured at that point easier just use a full stock image and see what happens.
Here is the Image : https://docs.google.com/uc?id=0B5AiGacWcBRzMTBlWmppOC1DS3c&export=download
Click to expand...
Click to collapse
I will try it, i hate lenovorola right now
Enviado desde mi SM-T320 mediante Tapatalk

towfurious said:
I have got answer for my own question.
It happens when before flashing in terminal type "fastboot oem fb_mode_set" , thats kind like bootloader force mode , when you reboot it always boots to fastboot. So after flashing i forgot to type "fastboot oem fb_mode_clear" to exit force mode.
Sorry for too many "reboot" words)
Click to expand...
Click to collapse
Thank you for this been struggling for hours