[Q] Haptic Feedback won't work - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Help!!! I have a VZW note 3, latest ota, rooted with towelroot, and no matter what I try no vibration whatsoever will work. Navigation keys, notifications, nothing will work. I have battery saver off and have already hard reset the phone. Any ideas on what's wrong? Thanks in advance!!!!

Not even a phone call? What about when you set it to vibrate does it buzz in?
Sent from my SM-N900V using XDA Premium 4 mobile app

Absolutely nothing will vibrate no matter what volume mode... any ideas??? P.S. it was working when I first got my hands on the phone then we updated to the kitkat ota and it completely stopped. Even after a hard reset.

It could have been a bad flash. You should try using kies to reflash the official software.
Sent from my SM-N900V using XDA Premium 4 mobile app

I just did. Nothing still. I'm guessing now I have to go rip open my phone and replace the vibration motor?

If your Knox counter isn't tripped I would just warranty a new one...
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 10:40 PM ---------- Previous post was at 10:35 PM ----------
Also check your power savings menu
Sent from my SM-N900V using XDA Premium 4 mobile app

bigbroncomiddlelb said:
Help!!! I have a VZW note 3, latest ota, rooted with towelroot, and no matter what I try no vibration whatsoever will work. Navigation keys, notifications, nothing will work. I have battery saver off and have already hard reset the phone. Any ideas on what's wrong? Thanks in advance!!!!
Click to expand...
Click to collapse
If you deleted Samsung Hub in TiBu, this is your cause

Related

[HELP PLZ!]IM app message push issue

Hello Guys! I need some help plz
I'm from asia and I like to use WeChat to keep in touch with my friends(whether you guys know it or what, this app is popular in mainland of China)
Here comes the problem: new message wont be pushed to my Nexus 4 after I locked my phone for a while.
I'm doing all kinds of tests these days. I finally reflashed the factory image yesterday. After flashing the image I did nothing but install WeChat.
Then I logged in and locked my phone and waited for 15 minutes. No interrupt during this 15 minutes. Then I used my iPhone to send a WeChat message to my nexus 4. NO NOTIFICATION......the notification came out after I turned on the screen and unlock the phone. WTF:crying:
By the way, my nexus 4 connects to my wifi all day long. I've already turned off the wifi optimize and I chose to keep the wifi connection when the screen turns out.
I also noticed that when I locked my phone for a while and turn on the screen, the signal icon is grey. After 1 or 2 seconds it will turn blue. I know the blue color means the phone is connected to Google. So I guess the phone will disconnect wifi after locked for a while? I have no idea about it...
Other IM apps seems having the similar issue... I dont like to miss my friends' message and keep them waiting...
Can you guys help me out? Thanks!!!
Problem with 4.2.1 on Googles part
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 12:59 AM ---------- Previous post was at 12:59 AM ----------
Try using CM10 it stopped the notification lag for me on wifi
Sent from my Nexus 4 using xda app-developers app
It happeb to me before.. I flash cm10.1 to solve this problem. Now, work like charm. Stock android 4.2.1 cuase this problem.
Sent from my Nexus 4 using xda app-developers app
neer2005 said:
Problem with 4.2.1 on Googles part
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 12:59 AM ---------- Previous post was at 12:59 AM ----------
Try using CM10 it stopped the notification lag for me on wifi
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thank you bro! Finally I know what's wrong... Now I have to wait for 4.2.2 OTA
faiz2036 said:
It happeb to me before.. I flash cm10.1 to solve this problem. Now, work like charm. Stock android 4.2.1 cuase this problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I see! It's the problem of stock 4.2.1...
In fact I would like to try CM when the stable rom comes out...
Thank you for the answer!:victory:

help me pls.. sudden wakelock

guys what is this media wakelock? Its draining my battery very badly. I restart my phone countless times, wipe data/cache but the problem still exist. it just happen suddenly only and now no matter what i do it wont go away.
It is DRM Protected Content Storage scanning the storage for DRM content.
Sent from my Nexus 4 using Tapatalk 4 Beta
how do i stop this? this thing happen out of the sudden and now it just wont stop
andyabc said:
It is DRM Protected Content Storage scanning the storage for DRM content.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
how do i stop this? this thing happen out of the sudden and now it just wont stop
annoymous1234 said:
how do i stop this? this thing happen out of the sudden and now it just wont stop
Click to expand...
Click to collapse
when you have a media file thats corrupt, sometimes this happens, it gets "stuck" scanning.
annoymous1234 said:
how do i stop this? this thing happen out of the sudden and now it just wont stop
Click to expand...
Click to collapse
It is actually not using it has much you think it is.
When you place multimedia files onto the storage and will scan for a few minutes.
It will be listed to show what was using up your battery.
If you recharge your Nexus 4 fully without storing any multimedia files and/or rebooting then it should not be on the list after unplugging.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
It is actually not using it has much you think it is.
When you place multimedia files onto the storage and will scan for a few minutes.
It will be listed to show what was using up your battery.
If you recharge your Nexus 4 fully without storing any multimedia files and/or rebooting then it should not be on the list after unplugging.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
but it did. i restarted my phone and charge fully twice and it still appear
Dude I had this problem... And I just flashed another ROM. What kernel are you running. This never happened to me on a stock kernel.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 08:41 PM ---------- Previous post was at 08:41 PM ----------
And its still happening
Sent from my Nexus 4 using xda app-developers app
akaiNe-iSolutions said:
Dude I had this problem... And I just flashed another ROM. What kernel are you running. This never happened to me on a stock kernel.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 08:41 PM ---------- Previous post was at 08:41 PM ----------
And its still happening
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm using CM10.1 rom and kernal. the weird thing is that I've been using the rom for a very long time but now only this thing happen

Nexus 4 doesnt turn on

Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
eksasol said:
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
Click to expand...
Click to collapse
Nope it doesnt turn on at all, also treid volume down and power button, still no succes. But like i said if i put the charger on it and try to power on, the red light goes on. The phone was at 35% when i flashed the twrp update
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just give it a few hours of charge, it will be back.
Mercado_Negro said:
Just give it a few hours of charge, it will be back.
Click to expand...
Click to collapse
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It happens. Battery stats in our device isn't too accurate. I've had that a couple of times. In fact, when my Nexus 7 2012 runs out of battery and I don't charge it for 4 hours or so it always needs half an hour to turn on.
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
frankvcs said:
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
Click to expand...
Click to collapse
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
I had a similar issue, I ran antutu and my phone went into a coma, no button combos were working and when I plugged in my phone I got the flashing red death light. But like PsyOr says just take of the back undo the two little screw's the hold the battery connector on, pop it off the put it back on and you're good. Worked like a charm for me.
Sent From a Slim Sexy Nexy
Actually seems like a hard brick. http://forum.xda-developers.com/showthread.php?t=2347060 try this.
And don't forgot to thank that guy, it's a brilliant post
No, its not a hardbrick, its the red light issues which is well known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
eksasol said:
No, its not a hardbrick, its the red light issues which is if en't it ll known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
Click to expand...
Click to collapse
That doesn't explain why the pc is asking him to use drivers for download mode. If the phone really dint have enough battery shouldn't it have not connected to the pc.
Also the device will be hard bricked even if a wrong kernel/rom is flashed. But it can be unbricked by the above method.
Try the Nexus 4 toolkit. There are options to re-install everything up again. If you are sure that your battery is in good working order, then it might be software related issue. I don't think it's a hardware problem.
soylukral said:
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are in download mode as indicated by your pc detecting the phone as QHUSB_DLOAD this is not the common battery fault.
You will likely get here by the bootloader failing
At this point you are more bricked than a general soft brick. But still not completely hard bricked.
There is a very useful thread in the general section about how to fully flash using download mode.
You can find the info below, note that there are a lot of steps involved so if your not confident. Rma is probably your best bet
http://forum.xda-developers.com/showthread.php?t=2347060
Sent from my Nexus 4 using xda app-developers app
Thanks guys for all of tour help. I wil try everything to bring the phone back. I will report if something happens. Btw what is RMA?
Sent from my Nexus 4 using XDA Premium 4 mobile app
RMA is return merchandize authorization.
sent from xda premium app
eksasol said:
RMA is return merchandize authorization.
sent from xda premium app
Click to expand...
Click to collapse
ok, and that is??
Guys, i did send it back to LG for repair. I want to thank all of you for the help you gave!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Prevention information

My note 3 is giving an annoying message tutled prevention information which warns the following: "an application has been firced to stop for and unauthorized attempt ti access system in your device, then it suggests that i uninstall all the app obtained from an unauthorized route. But all the app i have were downloaded from play store... help this message is annoying. And i cant find the app
Sent from my SAMSUNG-SM-N900A using Tapatalk
lemuel12 said:
My note 3 is giving an annoying message tutled prevention information which warns the following: "an application has been firced to stop for and unauthorized attempt ti access system in your device, then it suggests that i uninstall all the app obtained from an unauthorized route. But all the app i have were downloaded from play store... help this message is annoying. And i cant find the app
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
have you got knox on
Yes but i thought knox worked for stopping issues
Sent from my SAMSUNG-SM-N900A using Tapatalk
lemuel12 said:
Yes but i thought knox worked for stopping issues
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
not always ,i not got knox see if you can stop it and then try
Im pretty sure it will stop the notifications but i dont wanna ignore the issue i wanna know whats creating it or what is trying to access my info
Sent from my SAMSUNG-SM-N900A using Tapatalk
lemuel12 said:
Im pretty sure it will stop the notifications but i dont wanna ignore the issue i wanna know whats creating it or what is trying to access my info
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
have a look at all the apps you downloaded after it started and delete them one by one untill you find it
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
lemuel12 said:
Im pretty sure it will stop the notifications but i dont wanna ignore the issue i wanna know whats creating it or what is trying to access my info
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Take a look at "TrustGo Ad Detector"
https://play.google.com/store/apps/details?id=com.trustgo.addetector
Thata what i feared... i was hoping there was a log from everything that tries to access the system haha
Sent from my SAMSUNG-SM-N900A using Tapatalk
Should be an app on leak identity info right?
Sent from my SAMSUNG-SM-N900A using Tapatalk
lemuel12 said:
Should be an app on leak identity info right?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
maybe
Mine has started doing this too. After a reboot and at random times. Lookout doesn't report any malware and all my apps are from play store. It's annoying more than anything else. It's a useless prompt as it does that say which process was closed.
Sent from my SM-N9005 using Tapatalk
Has anyone deleted Knox to see what happens other than a warranty void? I'm having the same issues when unload any titanium backup apps. It could be just one app I load up and I get this message. But if I get the app from the note 3 itself it doesn't prompt.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Exactly... could u give me a list on ur downloaded apps to compare it to mine and see if we got any in common? Might help
Sent from my SAMSUNG-SM-N900A using Tapatalk
On mine it seems to be connected to the wifi in some way. For I In Bataan be I leave the wifi on when I leave home and when I pull into the driveway the message pops up.
Sent from my SM-N900T using xda app-developers app
---------- Post added at 12:26 AM ---------- Previous post was at 12:20 AM ----------
Damn autocorrect.
That strange sentence was supposed to start: For instance I leave...
I've never even been to Bataan!
Sent from my SM-N900T using xda app-developers app
Maybe when router retrieves the phone info?
Sent from my SAMSUNG-SM-N900A using Tapatalk
lemuel12 said:
Maybe when router retrieves the phone info?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Maybe, I was thinking of something along those lines, but maybe triggered by something the phone does. It happens when I am away from my home router sometimes, possibly driving through the range of another WiFi router, even if I haven't tried to connect.
I'll try to watch for that to happen when I go out today.
Sent from my Nexus 10 using xda app-developers app

New update 5.1.1

Got a new update no idea if it is different yet
Sent from my SM-N910P using XDA Premium HD app
Yoshi1221 said:
Got a new update no idea if it is different yet
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
615 MB.. hopefully its something good.
OS upgrade to 5.1.1, still don't know what the stagefreight security patch is. Looks like they forgot to mention the OS upgrade in the notes
Sent from my SM-N910P using XDA Premium HD app
Yoshi1221 said:
OS upgrade to 5.1.1, still don't know what the stagefreight security patch is. Looks like they forgot to mention the OS upgrade in the notes
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
That was to patch the link sent via messages and when you opened the video it would "harm the system" and if you used hangouts, it would automatically harm it due to hangout opening the video ahead of time for quicker viewing. It was an issue within the core of Android, not the OEM, itself and has been a 'vulnerability' for quite some time but was just exposed not too long ago.
Got the Patch and the 5.1.1 update, good deal.
Please report back the responsiveness and overall feel. I just might make the leap if they got Lolliflop right with this update.
xxSTARBUCKSxx said:
That was to patch the link sent via messages and when you opened the video it would "harm the system" and if you used hangouts, it would automatically harm it due to hangout opening the video ahead of time for quicker viewing. It was an issue within the core of Android, not the OEM, itself and has been a 'vulnerability' for quite some time but was just exposed not too long ago.
Got the Patch and the 5.1.1 update, good deal.
Please report back the responsiveness and overall feel. I just might make the leap if they got Lolliflop right with this update.
Click to expand...
Click to collapse
Well it does seem much more responsive. The optimizing apps process was painfully slow. My GPS puts me in Virginia though and I live in MA. Hopefully after it settles it will update itself.
Edit: GPS is good now.
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Another thing I notice is when you hit the recents button it opens immediately whereas before it would take a couple seconds.
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 10:41 AM ---------- Previous post was at 10:19 AM ----------
Well it does seem that GPS only works on power saving mode. I like to use GPS only mode in location settings so I set it to that and will leave it alone for a while to see what happens. Is this happening to anyone else?
Sent from my SM-N910P using XDA Free mobile app
t4d73 said:
Well it does seem much more responsive. The optimizing apps process was painfully slow. My GPS puts me in Virginia though and I live in MA. Hopefully after it settles it will update itself.
Edit: GPS is good now.
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Another thing I notice is when you hit the recents button it opens immediately whereas before it would take a couple seconds.
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 10:41 AM ---------- Previous post was at 10:19 AM ----------
Well it does seem that GPS only works on power saving mode. I like to use GPS only mode in location settings so I set it to that and will leave it alone for a while to see what happens. Is this happening to anyone else?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
The GPS location error is definitely sprint, had this problem for years where it would put me at Burbank, CA when I live in Las Vegas, NV. However when travelling to a different area of Vegas, that seemed to put me in Las Vegas. Now when at home it puts me at Dana Point, CA. Lol.
I did a test, had at least 20+ apps running, pressed the recent apps key, and it opened immediately. Usually with that heavy activity, I would be waiting anywhere from 15-30 seconds to pop up. One thing I am waiting to see is if it freezes on me. Had a few instances where apps were making the screen not respond. Seems much faster with the update though.
Sent from my SM-N910P using XDA Premium HD app
Yup leaving the house did it. Lol.
Sent from my SM-N910P using XDA Free mobile app
Had some message come up saying device must restart. No idea what that was all about.
Sent from my SM-N910P using XDA Free mobile app
Going to install and try to root. Will post back.
I've been running it for the past few hours. GPS works and the BT audio bug looks to have been fixed. The UI is smooth as glass. Has Sammy/Sprint finally gotten it right?
I tried to root, and phone rebooted but said su binary was missing. Tried routing with su in twrp and bootlooped. Tried reinstalling bof5 and can't go back. Going to install rom through twrp and wait for stock rooted.
Downloading now! In Southern CA.
Android version 5.1.1, Lollipop OS Upgrade
Message Waiting Indicator fix
Security fix (Stagefright)
Misc. bug fixes.
http://www.androidpolice.com/2015/0...ts-android-5-1-1-update-with-stagefright-fix/
So you can flash TWRP via Odin right? I would not care too much about not being to flash back to OF5 since I have a phone that lags severely after a few days of running stock OF5. I would just want the ability to flash CM12.1.
SD card Wiped
Did the 5.1.1 and my SD card was mostly wiped. Pics and music gone. Funny thing is, some things are still there such as carbon backup files. I'm not exactly thrilled.
5.1.1 kills cf-auto root... It did the same with the note edge.. Kernel exploit is the only way to root..
Loving the new updage so far. Not laggy at all. Now for the battery test.
Sent from my SM-N910P using Tapatalk
just my luck i decided to root OF5 last night!
Are my only options to
1) odin stock unrooted of5
2) wait till the new update is available to flash?
if i do option 1 will i lose all my data on the phone? thanks
nsvencer said:
Did the 5.1.1 and my SD card was mostly wiped. Pics and music gone. Funny thing is, some things are still there such as carbon backup files. I'm not exactly thrilled.
Click to expand...
Click to collapse
Did not wipe mine.
itony007 said:
just my luck i decided to root OF5 last night!
Are my only options to
1) odin stock unrooted of5
2) wait till the new update is available to flash?
if i do option 1 will i lose all my data on the phone? thanks
Click to expand...
Click to collapse
I odined stock unrooted OF5 and it's getting the OTA update now. So that works.
Phone feels much snappier. Recent apps menu opens instantly. Camera seems to open a bit faster.
Are we not going to get RAW support like the newer phones are getting? Thats some BS if not.

Resources