Related
First of all i used CWM to root my phone flashed via odin. Then i accidently installed chainfire 3d's driver, it wasn't booting and was freezed so i re-installed the firmware. now everything works fine except the LED notifications, only when i restart it, the LED turns blue. doesn't lit up even while charging/missed calls etc. and alarm sound isn't working either (quiet odd), while call and other sound based notifications works perfectly fine!!
I searched and searched, but none has problems similar to me. Please suggest me to try something that'll work besides re-installing the firmware again. not sure if custom kernel will do or not :'(
btw i rooted it again with CWM, hoping i'd work, because it allows custom led lights to work, but it didn't.
Still no reply!
-_- still no reply! :crying:
Try using light manager app found in the play store
Sent from my GT-N7100 using xda app-developers app
did u tried to wipe data ??
yes
wada7o said:
Try using light manager app found in the play store
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
i did try that but the whole led thing isn't working. only lights up while restarting. and for some un known reason the alarm isn't working, it works just there is no sound.
no i didn't...
yahyoh said:
did u tried to wipe data ??
Click to expand...
Click to collapse
i just installed the firmware. and reinstalled all the apps as they were wiped out.
Did you check the led configuration in Settings-Display-Led indicator ?
P_
yep
pakalrtb said:
Did you check the led configuration in Settings-Display-Led indicator ?
P_
Click to expand...
Click to collapse
i did
How did you reinstall firmware? Odin or cwm? Try odin and flash tar firmware. Copy first your data from mobile because this operation will wipe everything
.
poltec said:
How did you reinstall firmware? Odin or cwm? Try odin and flash tar firmware. Copy first your data from mobile because this operation will wipe everything
Click to expand...
Click to collapse
i did try it, tar.md5 right? (1.4 gigs)? i flashed it using odin, then flashed CWM. and then all this is haappening
*#0*# on your key pad and use the diagnostics.
The LED should flash 3 primary colours before ending.
If one of the colours isn't working, then it's a hardware issue.
.
AjunNg said:
*#0*# on your key pad and use the diagnostics.
The LED should flash 3 primary colours before ending.
If one of the colours isn't working, then it's a hardware issue.
Click to expand...
Click to collapse
That was interesting thanks, but no, no hardware problems. any possible way i can fix this without formatting and all? i'd be grateful.
have you tried getting back to stock entirely? i mean even get back to the stock recovery. plus factory reset.
and then if you still need root, you might wanna try the ExynosAbuse option, it's the cleanest.
.
primusmagestri said:
have you tried getting back to stock entirely? i mean even get back to the stock recovery. plus factory reset.
and then if you still need root, you might wanna try the ExynosAbuse option, it's the cleanest.
Click to expand...
Click to collapse
no i haven't, when i installed the clean stock firmware (md5 file), i still had those issues. i shouldn't have installed chainfire 3d, i was too hasty, i didn't read it's official thread, which mentioned it's only for ICS. Thanks, next time i'll use that to root. Also will titanium backup be of any help?
try flash stock by odin, then do a full wipe, if still no led, take to warrenty
OMFG!!!!!!!!!!!!!!
emprize said:
try flash stock by odin, then do a full wipe, if still no led, take to warrenty
Click to expand...
Click to collapse
NOTIFICATIONS/LED AND ALARMS WERE TICKED IN BLOCKING MODE!!!!
DAMN I FEEL SO STUPID :silly:
THANK YOU EVERYONE FOR KEEPING UP WITH ME, SERIOUSLY.
[Solved] Need some help..
I want to get my ATT galaxy s4 back to stock. I searched for a lot online. Basically it needs Odin and a downloaded stock firmware.
My question is does it work even for my phone currently is CWRP recovery and custom rom flashed? Does the Odin flash the stock recovery to the phone?
Thank you so much!
LingBo said:
Need some help..
I want to get my ATT galaxy s4 back to stock. I searched for a lot online. Basically it needs Odin and a downloaded stock firmware.
My question is does it work even for my phone currently is CWRP recovery and custom rom flashed? Does the Odin flash the stock recovery to the phone?
Thank you so much!
Click to expand...
Click to collapse
CWRP recovery? is that new? You have the 2 recoveries mixed, hehe good one though. I like that name. Anywaz...use ODIN, get the stock image and flash.
TheAxman said:
CWRP recovery? is that new? You have the 2 recoveries mixed, hehe good one though. I like that name. Anywaz...use ODIN, get the stock image and flash.
Click to expand...
Click to collapse
TWRP..typo..:laugh:
So it can remove the TWRP and flash stock recovery automatically by ODIN, right?
LingBo said:
TWRP..typo..:laugh:
So it can remove the TWRP and flash stock recovery automatically by ODIN, right?
Click to expand...
Click to collapse
heh we cool, um, it does not remove the recovery, but a hint here, odin back to stock, go into recovery after and factory reset. If you are wanting to remove everything including recovery, there is a thread or 2 with info on that.
Good luck.
TheAxman said:
heh we cool, um, it does not remove the recovery, but a hint here, odin back to stock, go into recovery after and factory reset. If you are wanting to remove everything including recovery, there is a thread or 2 with info on that.
Good luck.
Click to expand...
Click to collapse
Thank you very much! Still have a question..After I go to recovery and factory reset, can I get OTA update?
since the OTA update would check for system integrity like recovery.
LingBo said:
Thank you very much! Still have a question..After I go to recovery and factory reset, can I get OTA update?
since the OTA update would check for system integrity like recovery.
Click to expand...
Click to collapse
I have heard different stories on that, the one that I think is if you are rooted and recovery installed, your status would show custom, so no updates.
Anyone have any input on this?
TheAxman said:
I have heard different stories on that, the one that I think is if you are rooted and recovery installed, your status would show custom, so no updates.
Anyone have any input on this?
Click to expand...
Click to collapse
Asked someone if OTA is available after, he just said "should be" which is risky for me...
The goal is to get everything back to stock and question is can "Odin+stock firmware" achieve... I am so confused..
LingBo said:
Asked someone if OTA is available after, he just said "should be" which is risky for me...
The goal is to get everything back to stock and question is can "Odin+stock firmware" achieve... I am so confused..
Click to expand...
Click to collapse
Yes, ODIN BACK TO STOCK.
TheAxman said:
Yes, ODIN BACK TO STOCK.
Click to expand...
Click to collapse
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
LingBo said:
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
Click to expand...
Click to collapse
There is a way to get that to read normal, but you must first get back to stock. Start there, and we will get the other taken care of.
good luck.
LingBo said:
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
Click to expand...
Click to collapse
You can find more about the process by reading this thread:
http://forum.xda-developers.com/showthread.php?t=2261573
If you want to be 100% stock like you were out of the box, you can do a factory reset/wipe in TWRP and then ODIN back to stock.
Factory reset will wipe all of your data - some of which is causing the custom icon at boot. You can wipe the cache and davlik cache as well to be sure.
Next, ODIN will remove root and custom recovery afterwards, leaving you completely stock.
My understand is that if you don't want to wipe all your apps and data, you can ODIN back to stock and then manually remove the files that are causing the custom icon, but I have not tried that.
jeffreii said:
You can find more about the process by reading this thread:
http://forum.xda-developers.com/showthread.php?t=2261573
If you want to be 100% stock like you were out of the box, you can do a factory reset/wipe in TWRP and then ODIN back to stock.
Factory reset will wipe all of your data - some of which is causing the custom icon at boot. You can wipe the cache and davlik cache as well to be sure.
Next, ODIN will remove root and custom recovery afterwards, leaving you completely stock.
My understand is that if you don't want to wipe all your apps and data, you can ODIN back to stock and then manually remove the files that are causing the custom icon, but I have not tried that.
Click to expand...
Click to collapse
I am not the one seeking this info.
It is for the OP. Good info though.
TheAxman said:
I am not the one seeking this info.
It is for the OP. Good info though.
Click to expand...
Click to collapse
My bad - clicked on the wrong reply button!
TheAxman said:
I am not the one seeking this info.
It is for the OP. Good info though.
Click to expand...
Click to collapse
Yeah! I got everything back to stock 4.2.2 UCUAMDL. The lock custom logo is gone. I checked for OTA update, but it said the software was up to date. Obviously it is not the latest. What can I do to get the latest update?
Thank you!
Man, I got everything back to stock and installed the latest OTA manually. Thank you so much!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Problem solved ! Thank you!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
LingBo said:
Problem solved ! Thank you!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear.
Edit your header to say problem solved, so others will see that if they need this info, there is a fix.
LingBo said:
Man, I got everything back to stock and installed the latest OTA manually. Thank you so much!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Did you use Odin to do the OTA update manually? I was rooted and had custom recovery and used Kies to get back to "stock" but only to MDL. Phone checks for updates and it says im on the latest as well.. I want to update the phone to MF3 but I cant find it anywhere... Can you me out?
tiptoekirk said:
Did you use Odin to do the OTA update manually? I was rooted and had custom recovery and used Kies to get back to "stock" but only to MDL. Phone checks for updates and it says im on the latest as well.. I want to update the phone to MF3 but I cant find it anywhere... Can you me out?
Click to expand...
Click to collapse
I would use this one, if you are rooted...
http://forum.xda-developers.com/showthread.php?t=2364635
Follow the instructions there...
Thanks you
Good luck.
TheAxman said:
I would use this one, if you are rooted...
http://forum.xda-developers.com/showthread.php?t=2364635
Follow the instructions there...
Thanks you
Good luck.
Click to expand...
Click to collapse
I want it stock as stock gets if possible.. I don't want to deal with recovery's and such.. I have to warranty the phone once I come up with the $$ for the deductible because the screen is cracked and I don't want them saying my warranty its void...
Will getting to MF3 this way cause me to have the custom unlocked symbol on the startup screen again??
I tried to use GooManager to install TWRP, and now every time I try to reboot, the phone gets to the "Samsung Galaxy Note 3" page with three lines at the top - they say:
Recovery booting.....
Recovery is not seandroid enforcing
Set Warrant Bit : Recovery
I was on the leaked KitKat firmware. Can I fix this without losing everything? Or should I just restore the 4.4 using ODIN and re-root?
ManUtdRul3 said:
I tried to use GooManager to install TWRP, and now every time I try to reboot, the phone gets to the "Samsung Galaxy Note 3" page with three lines at the top - they say:
Recovery booting.....
Recovery is not seandroid enforcing
Set Warrant Bit : Recovery
I was on the leaked KitKat firmware. Can I fix this without losing everything? Or should I just restore the 4.4 using ODIN and re-root?
Click to expand...
Click to collapse
I read one post that says TWRP hasn't been updated yet to run kitkat. Try CWM.
hey_joe said:
I read one post that says TWRP hasn't been updated yet to run kitkat. Try CWM.
Click to expand...
Click to collapse
I've managed to completely restore my phone. Just need to re-root now; can you provide a link to the up to date CWM?
ManUtdRul3 said:
I've managed to completely restore my phone. Just need to re-root now; can you provide a link to the up to date CWM?
Click to expand...
Click to collapse
Here you go
hey_joe said:
Here you go
Click to expand...
Click to collapse
You're awesome, thank you!
hey_joe said:
Here you go
Click to expand...
Click to collapse
I've just got one more question.
I can root using this right? https://plus.google.com/+Chainfire/posts/QbVy3arpymx
I did this a few days and it worked fine. When I went to do it again earlier it ****ed up and let to that error again.
That's when I restored everything again and asked you for CWM.
Someone on there (third from bottom) mentioned they had the same error.
ManUtdRul3 said:
I've just got one more question.
I can root using this right? https://plus.google.com/+Chainfire/posts/QbVy3arpymx
I did this a few days and it worked fine. When I went to do it again earlier it ****ed up and let to that error again.
That's when I restored everything again and asked you for CWM.
Someone on there (third from bottom) mentioned they had the same error.
Click to expand...
Click to collapse
Yup use CF Here - should work spot on
radicalisto said:
Yup use CF Here - should work spot on
Click to expand...
Click to collapse
Thanks. Any idea why it came up with that other error/problem/bootloop?
ManUtdRul3 said:
Thanks. Any idea why it came up with that other error/problem/bootloop?
Click to expand...
Click to collapse
It seems it does it every now and again for whatever reason, I was lucky my root worked right away but my flashing of 4.4.2 didn't lol -- Reflash 4.4.2 via Odin then re-root. Should be good to go mate
EDIT: Careful if you are restoring anything via CWM, as it has just been done for 4.4.2 there *may* be issues with it that haven't been noticed.
radicalisto said:
It seems it does it every now and again for whatever reason, I was lucky my root worked right away but my flashing of 4.4.2 didn't lol -- Reflash 4.4.2 via Odin then re-root. Should be good to go mate
Click to expand...
Click to collapse
I just used that root and it happened again?
It's bootlooping again?
radicalisto said:
It's bootlooping again?
Click to expand...
Click to collapse
Yeah :/ I'm so confused, this worked the first time I rooted KitKat
ManUtdRul3 said:
Yeah :/ I'm so confused, this worked the first time I rooted KitKat
Click to expand...
Click to collapse
OK, so you'll defo have to reflash from scratch, then boot her up and set up, then re-root - try not to restore anything.
radicalisto said:
OK, so you'll defo have to reflash from scratch, then boot her up and set up, then re-root - try not to restore anything.
Click to expand...
Click to collapse
When you say don't restore anything, you mean that automatic restore from Google?
ManUtdRul3 said:
When you say don't restore anything, you mean that automatic restore from Google?
Click to expand...
Click to collapse
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
radicalisto said:
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
Click to expand...
Click to collapse
Hmm okay. Just a piss take how I'll have to keep re-installing all the things I need!
Yup it's a proper ballache for sure, been there myself many many times and prepared to be there again a few times yet lol
radicalisto said:
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
Click to expand...
Click to collapse
Reflashed stock ROM, rooted without restoring anything and it's happened again...
ManUtdRul3 said:
Reflashed stock ROM, rooted without restoring anything and it's happened again...
Click to expand...
Click to collapse
OK Your phone HATES you lol,
Last thing I can think of, is you may have had the wrong file try This one at the bottom of the page is the link. If you already have this one, then Re-flash Stock to fix yourself, and hold tight on root until it can be figured out 100% for now.
radicalisto said:
OK Your phone HATES you lol,
Last thing I can think of, is you may have had the wrong file try This one at the bottom of the page is the link. If you already have this one, then Re-flash Stock to fix yourself, and hold tight on root until it can be figured out 100% for now.
Click to expand...
Click to collapse
Yeah that's the one I had :/ This is horrible haha
Now I regret messing around this morning at college, using GooManager while I should have been studying...
I just want root back so I can install Xposed, Greenify and Titanium Backup to freeze the bloat
Hi guys.
I'm really stuck here. My fingerprint sensor suddenly started showing me 'no match' when I try to scan it, but I can unlock my screen with the emergency password.
However, if I try to access private mode, neither my fingerprint nor my backup password works.
Can anyone shed some light on this matter?
Thanks.
EDIT: My phone is an SM-910F.
s18067 said:
Hi guys.
I'm really stuck here. My fingerprint sensor suddenly started showing me 'no match' when I try to scan it, but I can unlock my screen with the emergency password.
However, if I try to access private mode, neither my fingerprint nor my backup password works.
Can anyone shed some light on this matter?
Thanks.
EDIT: My phone is an SM-910F.
Click to expand...
Click to collapse
Try deleting your fingerprints and adding them again, or maybe restarting the phone would help.
Ashatar said:
Try deleting your fingerprints and adding them again, or maybe restarting the phone would help.
Click to expand...
Click to collapse
I can't even access my fingerprint manager. And I've restarted a few times to no avail.
It also seems that the only place my emergency password works is the lock screen. I can't even change my lock type.
s18067 said:
I can't even access my fingerprint manager. And I've restarted a few times to no avail.
It also seems that the only place my emergency password works is the lock screen. I can't even change my lock type.
Click to expand...
Click to collapse
Are you rooted with custom ROM?
Ashatar said:
Are you rooted with custom ROM?
Click to expand...
Click to collapse
Yes, I'm on a custom ROM. I've been on a custom for months now and it's been fine, though..
Check if runtime is Dalvik.my private mode isn't working on art,completely stock no root
Sent from my SM-N910G using XDA Premium 4 mobile app
RISHI RAJ said:
Check if runtime is Dalvik.my private mode isn't working on art,completely stock no root
Sent from my SM-N910G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't even find the option to switch runtimes in my dev options. I'm running a Lollipop custom ROM.
Bump
s18067 said:
Bump
Click to expand...
Click to collapse
Maybe you should try wiping data and starting all over again, but I'd recommend installing an official ROM from Samsung....
Ashatar said:
Maybe you should try wiping data and starting all over again, but I'd recommend installing an official ROM from Samsung....
Click to expand...
Click to collapse
I was hoping it wouldn't come to that... Oh well...
s18067 said:
I was hoping it wouldn't come to that... Oh well...
Click to expand...
Click to collapse
It's a bummer.Good luck.
having same problem on N910T, wondering what finally fixed it.
So recently I rooted my S4 with Kingo and went fine. After a few weeks, I decided to uproot to get the Lollipop OTA. Unrooted through SuperSU app then factory reset. Finished OTA download with no issueand then it failed after two attempts, saying error and I should try using Kies.
That's strange I thought. Then after looking through the phone again, I discovered GSam Root companion is now a system app that can't be uninstalled. Other than re rooting and re uprooting or flashing stock firmware, is there another option. My computer is currently under repair for a broken LCD, so any fix that doesn't need that would help. Thanks!
Not much you can do without a pc
theDman68 said:
Not much you can do without a pc
Click to expand...
Click to collapse
So I guess bring it in to Samsung to flash stock firmware?
AB__CD said:
So I guess bring it in to Samsung to flash stock firmware?
Click to expand...
Click to collapse
Is your phone working or isn't it working? I can't figure it out based on your posts.
Lennyz1988 said:
Is your phone working or isn't it working? I can't figure it out based on your posts.
Click to expand...
Click to collapse
It is working just with an annoying "system" app and can't upgrade. May have over exaggerated a bit...
AB__CD said:
It is working just with an annoying "system" app and can't upgrade. May have over exaggerated a bit...
Click to expand...
Click to collapse
I then assume that you still run an old version of kitkat (because of the kingo root).
Why not reroot and delete the file? I think you can still use Towelroot because I think you are on an old version. That's an app that you need to install.
Do you have a custom recovery? And did you factory reset before trying to update ota?
Lennyz1988 said:
I then assume that you still run an old version of kitkat (because of the kingo root).
Why not reroot and delete the file? I think you can still use Towelroot because I think you are on an old version. That's an app that you need to install.
Do you have a custom recovery? And did you factory reset before trying to update ota?
Click to expand...
Click to collapse
Can't use towelroot and don't have a custom recovery. I'll re root once I get the update on Kies(borrowed a friend's laptop) , which currently isn't available yet.
AB__CD said:
Can't use towelroot and don't have a custom recovery. I'll re root once I get the update on Kies(borrowed a friend's laptop) , which currently isn't available yet.
Click to expand...
Click to collapse
What i don't understand is why you are so stuck on getting this OTA update... just borrow your friends laptop, and flash the Lollipop that you want through ODIN. Then factory reset, DONE...
theDman68 said:
What i don't understand is why you are so stuck on getting this OTA update... just borrow your friends laptop, and flash the Lollipop that you want through ODIN. Then factory reset, DONE...
Click to expand...
Click to collapse
Took it to Samsung and let them do that for me. Didn't lose any data either, and GSam Root let me Uninstall it afterward, which was something I didn't expect. Anyway, thanks for the effort guys!