Related
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2
Hello, guys. I have the newer line of the 16GB nexus 7's(C90K, iirc), which I just got the other day. Bootloader is unlocked, TWRP is recovery, device is rooted. I checked the md5 of the Bugless Beast flash and all matched up. Yet, every time I flashed it resulted in a bootloop that wouldn't fix itself. I thought maybe I was doing something wrong so I looked at how others were doing it: everything was just right. I factory reset and wiped system for good measure, wiped caches, and installed the ROM.
To make sure that I really wasn't doing anything wrong, I took Paranoid Android and flashed it. It was running in like two minutes. I tried the latest and the second latest of BB releases, so I don't think it's his release but something on my device? I'd appreciate some assistance, guys.
I don't mean to double post, but any ideas?
How long did you let it try booting? I noticed my newer nexus 7 takes longer to flash and first boots seem to be a lot longer as well.
Sent from my SGH-T999 using xda app-developers app
Warrior1975 said:
How long did you let it try booting? I noticed my newer nexus 7 takes longer to flash and first boots seem to be a lot longer as well.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It was a bootloop rather than actually getting anywhere/loading anything. I let it bootloop for 30 minutes a couple times just to see, though.
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
MERKJONES said:
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
Click to expand...
Click to collapse
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
simms22 said:
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
Click to expand...
Click to collapse
I tried clearing the data from the phone app. I can reboot and clear dalvik again. I also flashed http://forum.xda-developers.com/showthread.php?t=2127498 and it's still acting up.
are you using any mods or themes?
simms22 said:
are you using any mods or themes?
Click to expand...
Click to collapse
Nope.
MERKJONES said:
Nope.
Click to expand...
Click to collapse
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
simms22 said:
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
Click to expand...
Click to collapse
I did a clean install and manually installed all of my apps again. I managed to fix it by dirty flashing the 4.2 version of AOKP. However; my phone still has that random reboot issue. The thing that's odd is, when it comes back online it loses it's settings. So I'll have to setup Google Wallet and Google Voice again. My keyboard goes back to the default AOSP one.
I think I might just RMA this phone and start over. I do love it, and the negatives don't outweigh the positives.
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
molesarecoming said:
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
Click to expand...
Click to collapse
Um... I had the problem on stock 4.2 as well, factory from Google themselves. It rebooted at random for no reason. I have wiped everything... multiple times. It's still doing it.
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
MERKJONES said:
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
Click to expand...
Click to collapse
i just used the stock 4.2.1 ROM and kernel. I am using the backup I made for my phone when i first rooted my phone. I don't a copy of the that. try using WUG rooting kit. u should be able to load it in that way. good luck. i missing flashing custom ROM, but I need my phone call to work. and by the way my last custom ROM was AOKP.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can always follow efrants guide to go fully back to stock.
Sent from my Nexus 4 using xda premium
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
tokuzumi said:
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No. And even on stock 4.2 I'm now having the sound disappearing problem. Where it'll just stop for no reason.
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
MERKJONES said:
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
Click to expand...
Click to collapse
Everything is good now. Just flash new AOPK mr1 build 3 with newly doiwnload gapp. So far so good. Make sure you download the gapp from 12/12/2012
Sent from my Nexus 7 using xda app-developers app
Hello!
I had my S4 rooted and nandroid back up. I was trying to install this link:
http://forum.xda-developers.com/showthread.php?t=2316308
I installed it and gapp installed too and rebooted. I got this message appears
"System software not authorized by AT&T has been found on your phone"
upper corner in orange says "kernel Failed"
That means I did something wrong?
I read about odin. Does Stock rom get you back to fully stock?
Thanks
Did you run loki doki? see.your on at&t..locked bootloader and i dont think that rom is autolokied. Boot back into recovery flash ld.and see if it boots.
Yes odin will put your phone back to.stock,been there done that lol.
sent from my CleanRom 1.5 i337m
force70 said:
Did you run loki doki? see.your on at&t..locked bootloader and i dont think that rom is autolokied. Boot back into recovery flash ld.and see if it boots.
Yes odin will put your phone back to.stock,been there done that lol.
sent from my CleanRom 1.5 i337m
Click to expand...
Click to collapse
Ok, I been reading some threads about recovery, I didn't relieze, i was away from s3 so long. I just restored from backup data and it boots into this stuck Samsung screen with custom unlocked logo. Bootloop?
Havent seen that particular screen but yeah sounds like your bootlooped. If.you can three finger back into recovery and have a nandroid i would full wipe then Restore your back up (even though people.say restoring wipes anyway..id wipe.if u.are using twrp do not format data!).if.your still looped you may have to try and odin back to stock.firmware can be found on sammobile.com had to do this the other night due to a bad nandroid..lots of fun lol.
sent from my CleanRom 1.5 i337m
force70 said:
Havent seen that particular screen but yeah sounds like your bootlooped. If.you can three finger back into recovery and have a nandroid i would full wipe then Restore your back up (even though people.say restoring wipes anyway..id wipe.if u.are using twrp do not format data!).if.your still looped you may have to try and odin back to stock.firmware can be found on sammobile.com had to do this the other night due to a bad nandroid..lots of fun lol.
sent from my CleanRom 1.5 i337m
Click to expand...
Click to collapse
Thank you!:victory:
My heart dropped like fainting ghost after I see the at&t software showed up. I wiped factory reset and goes past the samsung with unlocked logo into at&t boot up like new phone. It took 5 mins to get into welcome screen. All is working.
Now, I begun to wondering why my logo says it bootloader unlocked and I download correct at&t rom is in? I use this causal download from this link:
http://forum.xda-developers.com/showthread.php?t=2297900
I am trying to understand and pick my first rom. Was thinking downloading pure google rom. Had to read again
That mod.will loki your kernel,prolly why it says unlocked. I.have the.canadian. version..unlocked already thank.god lol.
A.simple wipe can work wonders..if you can get into.recovery and have something.to.flash most times your gona be okay.
Glad your back in.business!
sent from my CleanRom 1.5 i337m
Flash another kernel made for your device, or go thru the ODIN thing, your choice. this is for anyone who have that triangle.
Yes, I read some thread and the roms need kernel, without kernel installed which was has leaded me into that warning att screen. I tried again with roms above link with ktoon kernel and made it through. I was probably be dumb. Pardon me, lots to relearn here.
I own iPhone 4s but I went back to android.
Sent from my SM-T310 using xda app-developers app
You should be able to get rid of that boot screen with the lock on it by using triangle away. http://forum.xda-developers.com/showthread.php?t=1494114
Does anyone know what that com2s and the one below it is? And anyway to delete them?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Does anyone know what that com2s and the one below it is? And anyway to delete them?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
delete em (un-install), junk, are you getting spam and such? Did you install those? Do you have any protection on your device? Just curious.
Thank you
TheAxman said:
delete em (un-install), junk, are you getting spam and such? Did you install those? Do you have any protection on your device? Just curious.
Thank you
Click to expand...
Click to collapse
I can't find them to uninstall them just to force stop and unable them. Not getting any spam but I have used 4shared and and downloaded some stuff that didn't work and just download to my storage. No protection for my device. Any suggestions? I haven't had an android since the mytouch on T-Mobile years ago and I'm still new to this.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
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...