Develop Bugs

NFC does not initiate after returning from Cyanogenmod to Stock

good night
a time ago, for curiosity I wanted to prove a rom kitkat of Cyanogenmod 11... good, only I her used approximately 2 weeks since the truth did not convince me,
so I decided to return to the firmware of Telcel (mexico) on having installed to him the firmware ... the Wifi did not work already, it was not activated, so I tried to put another firmware of mexico, and I mark myself a strange error, whole, end up by putting the emergency recovery that KIES has
and there I was put by a firmware that is
version of Baseband I9195LUBUAMF3 and compilation
JDQ39. I9195LUBUBNC2
but from there ... the NFC did not work already ... the active thing, and it is deactivated only to 3 seconds,
later the speaker trumped me, send the team to guarantee, and in technical service they always iron the most recent firm, and it continues without raising the NFC
will it be any problem in hardware, or in the change of rom and firmware??
greetings and thank you very much

hello, good day....
to do tests,install Cyanogenmod 11 again, only to see that there the NFC works
and in this custom rom, if it works correctly, the question is, because in that of stock it does not work:S

there is already a thread about the not working nfc issue and a solution to fix this. look into it

junkyde said:
there is already a thread about the not working nfc issue and a solution to fix this. look into it
Click to expand...
Click to collapse
thanks
http://forum.xda-developers.com/showthread.php?t=2562485&page=3
I found the solution to my problem
thank you

Just got my Find 7, want to move to custom ROM from ColorOS

I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...

You just need to update to latest Color OS available first. Its right HERE. Then unify your storage. After that you're good to go.

Sent ya a message on hangouts mate!

Also, you've probably got a newer LCD panel - most ROMs and recoveries are not compatible with LCD Panel R63419.
Dialing *##*37847# should tell you the screen type.
Latest TWRP recovery and OmniROM are compatible with LCD Panel R63419.

pobbel said:
Also, you've probably got a newer LCD panel - most ROMs and recoveries are not compatible with LCD Panel R63419.
Dialing *##*37847# should tell you the screen type.
Latest TWRP recovery and OmniROM are compatible with LCD Panel R63419.
Click to expand...
Click to collapse
I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware :crying:
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...:fingers-crossed::fingers-crossed:

rahul.90 said:
I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware :crying:
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Omnirom is the only rom that support new lcd for now. Just follow the step.

StormTrooper89 said:
Omnirom is the only rom that support new lcd for now. Just follow the step.
Click to expand...
Click to collapse
he does not have the new lcd screen

suraj.das said:
he does not have the new lcd screen
Click to expand...
Click to collapse
Thats what happen when read while eat. :laugh:

915A - No root? No TWRP or CWM??

Am I just missing it, or is there no root or recovery ability for the 915A?
Marshmallow 6.0.1 ****ed mine up when it got pushed down, and Samsung's backup software (all 3 of them) failed to capture my apps and settings properly. Really wish I could've had a better backup ability.

Does or has anyone checked to see if the update to MM 6.0.1 has unlocked the bootloader on the SM-N915A like the Verizon variant?

How does one check?

Att have not released any M updates.

Mine updated to 6.0.1 the same day I bought it . Several small updates happened first. 5.0.1 to 5.1.1 then a small one, and finally 6.0.1. Since I had just bought it, resetting was a simple thought. But so far, no problems, I bought a PowerBear to make it last longer. :fingers-crossed:

Mine had a lot of issues after being updated. MMS didn't work at all. SMS worked sporadically, but would sometimes delete whole threads. Couldn't get a signal in many spots. Google Play Services wouldn't run and couldn't be fixed. Tried a cache-wipe and every other non-destructive method, but nothing worked. Ended up having to factory-reset, and since then the phone works as it should, but none of the backup methods captured key settings. Basically all it did was save contacts and APK's. Lost my 2-factor keys and everything.

I am with you! Since the update to MM, phone has been very laggy/unresponsive. Lock screen lights up for no reason sporadically and I have LOTS of dropped calls/deadspots. VERY irritating! I wish this release would have been tested a bit more before it was OTA pushed out

Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.

Could someone make this Windows compatible? http://androiding.how/dirty-cow-root-android/

JEANRIVERA said:
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Click to expand...
Click to collapse
Have you tried or someone. I'm already installing Linux into my computer.

juanfe1a said:
Have you tried or someone. I'm already installing Linux into my computer.
Click to expand...
Click to collapse
did you end up doing it?

Who else could get the root on sm-n915a ??? I also have problems with the transition from 5.1.1 to 4.4.4. (Kitkat). If anyone can help write please how to do this ??
I would also like to know if I am from russia and I need a Russian language that is not available on samsung galaxy note edge n915a. Is it possible to add it like that ?? Sorry for my bad english (googl translate)). Thank you. I am hope for your help

pleasseee i need debrick image for at&t not egde (SM-N915A)

winstonakime said:
pleasseee i need debrick image for at&t not egde (SM-N915A)
Click to expand...
Click to collapse
https://forum.xda-developers.com/note-edge/general/stock-att-note-edge-5-1-1-t3241314
You may need to know your build number tho

Just to keep this alive it is now November 2017 any news?

Dr.Lost said:
Just to keep this alive it is now November 2017 any news?
Click to expand...
Click to collapse
I wish...

Anything new?

Mi A2 lite keeps losing signal

Hi guys. I need your help
I bought this phone a year ago. It works fine at first, but then I'm not sure since when, the phone keeps losing signal and says "No service".
Network is up again when I restart the phone, but if I leave it for a while, it loses the signal and nobody can call me.
Is there anyway to solve this problem?

Tstella said:
Hi guys. I need your help
I bought this phone a year ago. It works fine at first, but then I'm not sure since when, the phone keeps losing signal and says "No service".
Network is up again when I restart the phone, but if I leave it for a while, it loses the signal and nobody can call me.
Is there anyway to solve this problem?
Click to expand...
Click to collapse
which version are you using, if it is A10 i have to say that is a bug not solved by the lazy xiaomi's devs
Best solution is to change to custom rom or return to android pie or oreo

Kaimilo said:
which version are you using, if it is A10 i have to say that is a bug not solved by the lazy xiaomi's devs
Best solution is to change to custom rom or return to android pie or oreo
Click to expand...
Click to collapse
How do I know which version my phone is?
Anyway, it's the bugged version it seems, so I guess I'm gonna downgrade it. Do you know where can I download the rom?
I found this site (xiaomifirmwareupdater.com/archive/miui/daisy/) but it's Miui rom, not the android one version

Tstella said:
How do I know which version my phone is?
Anyway, it's the bugged version it seems, so I guess I'm gonna downgrade it. Do you know where can I download the rom?
I found this site (xiaomifirmwareupdater.com/archive/miui/daisy/) but it's Miui rom, not the android one version
Click to expand...
Click to collapse
Go to the info system and scroll down you will see
That link is correct it shows the android one versions not miui and it has the name of the roms on it

Question TO BE CLOSED AS IS DEFUNCT

I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working

here is a video showing the angry warning text and the device booting and me using the camera

So there we have it! hopefully development will take off a bit now and also apologies!!!
Had i bothered to tinker in the last couple of weeks we may have known this earlier!!!!

Finally........

After testing i now know which file can fix the camera on B1 - its to risky to flash it on android 11 as i almost lost download mode SO I AM NOT GOING TO BRING ATTENTION TO THIS FILE JUST YET - THERE WILL BE ONE LOON WHO FLASHES IT ON A11 WHILST ROOTED AND LOOSES DOWNLOAD FOREVER
The camera issue was actually "fixed" in beta 2 ZUKA!!!
- i have tested this on B1 where camera broke on BL unlock and also on android 11 fixing the camera issue but causing download mode issuses.
What this means is that we have something to possibly bite back with should sammy lock down the cameras again
Big thanks to @dr.ketan for the help in finding this

Does f926n have to wait until Android 12 is updated to brush the machine normally, and the camera will not be locked

MartinJiao said:
Does f926n have to wait until Android 12 is updated to brush the machine normally, and the camera will not be locked
Click to expand...
Click to collapse
Flash beta2 or 3 for the N model and you should hopefully find you can unlock bootloader and camera will work.
We do not have root on beta yet though so it maybe a week or two till we can be rooted and use camera

Great for international folks. Meanwhile *cries in US*

domineus said:
Great for international folks. Meanwhile *cries in US*
Click to expand...
Click to collapse
do you still have cam lock on the US variant on Beta 2 or three?

Can anyone in Korea who has had the stable OTA please try and unlock bootloader to see if camera works?

exocetdj said:
do you still have cam lock on the US variant on Beta 2 or three?
Click to expand...
Click to collapse
it doesn't show up in the settings but that isn't a huge surprise

I'm pretty sure the ZUKG rom is the beta, isn't it?
You may find once the stable release hits out Folds this will once again be locked down and the cameras won't work once the bootloader is unlocked.

exocetdj said:
I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working
Click to expand...
Click to collapse
Awesome

exocetdj said:
I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working
Click to expand...
Click to collapse
Please can you post a link to the F926B rom that you used?
I cant find it anywhere.
Thankyou in advance

ParadoxLogic said:
Please can you post a link to the F266B rom that you used?
I cant find it anywhere.
Thankyou in advance
Click to expand...
Click to collapse
Yeah, I can't find that either.
I would also love a simple guide of some sort for stupid old people like me, how to root that unlocked boot loader beta version
Thanks in advance
Edit:
I wonder if that's the link for Beta 2 for 926B
Edit 2:
Aaaand I wonder if this is the link for Beta 3?

we cannot root beta yet (or i have been unable too and no one else has even bothered trying lol)
I think we will stand a better chance when we have full firmware and source code but early indications from the "stable" korean version is that Samsung are still killing cameras on bootloader unlock

exocetdj said:
we cannot root beta yet (or i have been unable too and no one else has even bothered trying lol)
I think we will stand a better chance when we have full firmware and source code but early indications from the "stable" korean version is that Samsung are still killing cameras on bootloader unlock
Click to expand...
Click to collapse
I tried unlocking BL of F926N (not B) after installation of OTA update a12 (BUL4) released on 12/15, but camera was still dead as mentioned above. And rooting via magisk didn't work well either. So I reflashed firmware of a11 (AUJ7) using Odin and rooted without TWRP.

EDIT: Samsung have really redeemed themselves! my moaning below is now moot
This all confirms that this has been a deliberate move by Samsung to impede the modding community
yes they have done this before with knox etc etc but killing a fundamental piece of the device's hardware just because they don't like rooting is wrong and also probably ILLEGAL if they are not advising in the Download mode screen that this is what will happen.
There has been no statement as to why, they are behaving like the insulting kid in class who hides behind the teacher when the class revolts at their actions lol.
I invite Someone from Samsung to explain whats going on and why they are doing this of course, but silence will prevail with all things Fold 3 (much like it did with the first "fix" that was trumpeted on twitter months ago)
I am hopeful that the workaround i have found with @dr.ketan will see us good for a bit when the release firmware for android 12 eventually lands in Summer of 2022 (yes im being a grumpy sarcastic child today lol) but that will no doubt be patched by these Sammy psychopaths against modding eventually.

Edit - now moot

exocetdj said:
Ill be selling my entire "samsung ecosystem" for a Pixel 6 pro come January i expect -> especially if this retarded madness spills over onto the S22 line
Click to expand...
Click to collapse
VERY much looking to jump the Sammy ship as well. Just seems like they aren't interested in listening to the customers...even us. I truly believe they are butt-hurt that the dev community makes better ROMs and improves their products.
But the Pixel and Sony are looking WAY better.