yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 General] Sagitario:
Has anybody had the following problem.. and ofcourse, a solution:

I've come to accept Windows Live syncing my contacts on the phone and making a mess with the others. I ended up consolidating with duplicates.

My problem is that I have fully added my contacts again to Messenger and at first everything works fine. I sync with activesync and everything goes well. The issue begins when I soft reset. After I do, Windows live now begins not being able to sync my contacts. It always gives me an error. To make it worse, my contacts are still in the messenger, but they never appear online. People can see me and message me, and I can answer, but I don't see anybody online as I did before I softreset. I can imagine I don't see them because they don't sync. I set sync settings for "as they arrive" for my mail to work like if it were pushed.

Anybody know why that happens? Trust me, I've hardreseted like crazy, I even created a new account and added everybody from scratch and it still happens.

I use the new WM6 update for an unbranded HTC p4350 in Spanish.

Thanks.
[Wing, P4350 General] johnny88:
Did you regedit and hide SIM contacts... I have the same problem with Windows Live Contacts and I guess it's because that registry modification, so I'm trying to restore that key to show/UNhide SIM contacts...

...updates next...
[Wing, P4350 General] johnny88:
Updates... It' an issue related to the HTC 3 button Plugin... if you disable it from Settings tab you will see all contacts... :(

Now I'm trying to enable again the Plugin...

...updates caming next...
[Wing, P4350 General] Sagitario:
Didn't work

Hey.. thanks for your help but none worked.

I haven't touched the registry in what pertains to windows live. Every time I try to sync it tells me it failed to start syncing the congacts.

What I dont understand is why, if I errase the account and sign in again, I do get to see them; but once I softreset, though they are still there, they all appear offline. They can see me but I cant

Thkz
[Wing, P4350 General] johnny88:
Now I am OK and Windwos Live works fine (sync and online contacts).

1)I disable the 3 Button Home Plugin.

2) restart the phone and it boots correctly without the Plugin activated. I connect via WI-Fi to Windows Live and it works correctly.

3) re-enable the 3 Button Plugin and all things still work.

I dunno why but after this it's ok... :)
[Wing, P4350 General] johnny88:
Updates: It worked but this is not the solution...

I'm trying find the core of the problem...

...updates coming next...
[Wing, P4350 General] johnny88:
Erase all things I wrote before :( (sorry but I was testing...)

Searching in google I found many people with this problem (WM6 + Windows Live).

Right now the only real thing to do is a work around. From Windows Live you have to tap on Menu, then on Account Options then choose "Change Account" and reconfigure it anytime you Soft Reset your Herald... :mad: :confused:

I know it is not a solution, but in this way it works... :(
[General Questions and Answers] galinha:
Hello :

in ios (jailbreaked) i had some tweeks that are ver usefull

- With facebook ++ i can copy / download videos to my device (in app tweek )

- With Safari Downloader / Video downloader i can download embed videos from web pages .

- With Cercube / Youtube++ i can download videos without leaving the Youtube app

- With watsui / whatspp tweak alow send large videos.

There are a lot of tweeks to social apps that alow to easly oflline copy

Is there any tweeks to a rooted s6 like this ?

Thanks in adavance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gmdurrence@ bellsouth.net:
I loaded various ROMs on my Samsung S3 I747. I then went back to stock ROM by flashing UCUFNJ1_Rooted.zip with CWM recovery. I then

flashed UCUFNJ2_Rooted.zip. and my phone works fine, but when I try to turn on WI-FI, it stays greyed out. I flashed

d2att_I747UCUEMJB_bootloader_modem_4.3.zip but that didn't help. Does anyone have any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Sounds like your firmware doesn't match your ROM. That can cause problems like wifi not working with stock kernels. Before you do anything verify what bootloader and modem you have on your phone. Either install the Samsung phone info app from the Play store or enter these commands in a terminal or adb shell:

getprop ro.bootloader
getprop gsm.version.baseband

Based on your post those should both end in MJB, but it never hurts to make sure (and sometimes it hurts a lot when you don't make sure).

You need to get your bootloader/modem to match your ROM to get everything working right since you're running stock. Since your already running the NJ2 ROM, and it contains at least partial fixes for some of the Stagefright vulnerabilities your best bet is to update your bootloader/modem firmware to NJ2 to match your ROM.

This can be done pretty quickly and easily with zips enewman17 has posted, but there is always a risk when messing with bootloaders. These need to be flashed incrementally in the proper sequence and you need to reboot into your ROM between each flash. The proper order is MJB -> NE4 -> NJ1 -> NJ2. As long as both your bootloader and modem are MJB, you can start with NE4. Just be absolutely sure to flash in the correct order and always reboot into your ROM after each flash or hard bricks can occur when messing with this.

Samsung made it pretty hard to update the firmware on this phone after they introduced Knox, and AT&T does us no favors by not releasing full firmware packages for their devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Do as [MENTION=5927992]jason2678[/MENTION] stated. If you find the versions end in something other than MJB, then start your bootloader/modem fixes at the version on your phone and go on to match your rom.
[Galaxy Note 4 Q&A, Help & Troubleshooting] tothehawks:
Hi, all.

My not-so-tech-savvy mother purchased an SM-N910U (Hong Kong model, I think) from a not-so-reputable Chinese retailer several months ago.

The phone worked without issue for around a month. Then, when she went on holiday to Spain, she said that the phone stopped recognising her SIM card about a day into the trip. That was strange, considering she's always been able to get signal there before.

Anyway, fast-forwarding to her return to the UK, the issue was still present. We tried multiple SIM cards across multiple networks (Three, Vodafone and O2), and none of them were recognised. It just said there was no SIM inserted. All those SIM cards worked fine in other phones. Clearly the issue is with the phone itself.

We couldn't get the phone repaired officially by Samsung under warranty, because it's a non-EU device (Hong Kong model), which was irritating. We had to send it off to Hong Kong to the retailer, who then tested the phone for themselves and found that they couldn't replicate any of the issues we described. I was sceptical and thought they were just being disingenuous to save a bit of cash, but they sent me a video showing the phone working, making a call, surfing the web, having signal etc. and went to settings to confirm the IMEI number and serial number of the device. There are no doubts as to the authenticity of their word, now.

And that is what perplexes me now. Naturally, when we received the device back some weeks later in the UK, the issue was still present, apparently unhindered. Any amount of Googling will show that many Note 4 and S4 users specifically have the issue of SIM cards not being recognised. There have been any number of causes and resultant solutions proposed, among them being: issues with the motherboard, issues with the SIM tray itself etc. And yet, the phone was clearly working fine in Hong Kong when they tested it.

To my knowledge, the SM-N910U isn't region-locked, and even if it were, it wouldn't make sense that it worked for a month in the UK before the issues popped up.

I'm also not sure if the fact that it occurred in Spain, a foreign country, is relevant, at all. I'm sure it's just a coincidence, because I can't think of anything plausible.

Any suggestions would be greatly appreciated.

Thanks in advance.
[Galaxy Note 4 Q&A, Help & Troubleshooting] tothehawks:
Bump.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaii_Versace:
I Used To Own A Tmobile S3 Which I Enjoyed Using Custom Roms Like Cm 12, LiquidSmooth 4.1 And Pac Rom Just To Name A Few And The Lcd Broke . So One Of My Friend Is Selling Me A Used At&t S3 On Stock 4.4.2 For Quite Cheap. But My Problem Is ( Correct Me If Im Wrong) I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ? An S3 Serves No Purpose To Me On Stock TOUCHWIZ :( . So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
The bootloader is not locked on the AT&T S3 (I747). You can use Odin to flash a custom recovery and flash any ROMs for d2att/d2lte you want. No unlocking required. It is a pretty modder friendly phone.

The thing you cannot do on the newer bootloaders is downgrade the bootloader. Attempts to downgrade anything beyond the 4.3 bootloader will result in a hard brick. This also prevents you from using the free sim unlocking method because it involves a firmware downgrade to 4.1. If you need to sim unlock the phone to use it on a different network you'll have to get a code from AT&T (they should provide one since a phone this old just about has to be off contract) or purchase one from a third party.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I concur with [MENTION=5927992]jason2678[/MENTION]

I have an AT&T SGS3 (d2att/i747) that is on the NE4 bootloader and modem (4.4.2) and am running CM11 atm. As a matter of fact, none of the CM or AOSP roms since late in 4.4.2 development will run unless you are on one of the 4.4.2 bootloaders (NE4, NJ1, NJ2)

What you stated, quoted above, is true for the Verizon SGS3 (d2vzw/i535).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] car2carl:
Hello I am new here and could you please tell me the status of my phone since the phone does not provide me with option to enter unlock code after I inserted other carrier SIM.

I already have my unlock code given by AT&T.

I have CWM custom recovery installed

My phone info from Samsung Phone info Apps is

Bootloader version : I747UCUEMJB

PDA Version : I747UCUFNE4

CSC Version : I747ATTFNE4

Baseband Version : I747UCUEMJB

I have searched and tried with service mode method *#197328640# without success

Is Sim unlock related to bootloader

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It appears that you have an NE4/Android4.4.2/KitKat rom installed over 4.3 bootloader and modem. I have seen several custom TouchWiz roms that run fine with this setup as long as one of a couple of custom kernels were installed. CM and AOSP roms will also run in this condition. BUT, from what I have read you will not be able to use the unlock codes. My reading indicates that you must be on complete stock ROM for the code to work, including stock recovery instead of CWM. ALSO, what I have read says that you only gt five attempts before the code becomes invalid.

I don't know why your phone is not asking for the unlock code, unless it has already been carrier unlocked. Even thouhg it is not asking for the code, does it function as it should?

Frequently the service modes do not work on custom roms, even TW based ones, because they are not using the stock dialers. I have also seen it reported that some were disabled with the 4.3 update and others in more recent updates.

Proceed carefully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
You may be able to enter the unlock code if the phone is running a stock dialler with a matching bootloader and modem combination.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] car2carl:
Thanks for respond

I had this phone since 3 years ago (new from ATT) and rooted stock rom with CWM 6.0.4.7 recovery touch . and I remember that I could unlocked through SERVICE MODE when I was overseas. ( sure I had used this phone with Other carrier) about 1 year ago I put this phone in my drawer I did factory reset and installed Stock firmware and update OTA to 4.3.

Last week I want to use this phone with Tmobile SIM but got Phone Not Allowed MM#6 message . The rom was still 4.3, Contact AT&T and got Unlock code.

but this phone didn't ask for unlock code entry option and still 4.3 , tried the whole weekend with service mode and upgrade to 4.4.2 via CWM recovery.

and still no luck

With your suggestion , it means that I don't have choice to downgrade back to 4.3 rom same with my bootloader and baseband? I heard we can't downgrade if we already in 4.4.2 , is that true?

But I still use stock recovery from CWM.

Before I proceed with replacing with stock recovery, is the stock recovery have to be 4.3 stock recovery or any version for S3? do I need to use odin to change to stock recovery?

if you have good link please help?

Thanks again

---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------

Stock dialer means the entire Rom must be replaced to match my bootloader and modem combination or just replace the dialer in my case and still use 4.4.2?

Appreciated if you can help, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Stock dialler requires a stock Samsung kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
From what I am seeing, you are on the 4.3 bootloader and modem. As I said before, there are custom TouchWiz 4.4.2 Roms that will run on the 4.3 bootloader and modem. Changing to a 4.3 rom, stock or otherwise, therefore would not be downgrading your bootloader and modem.

What rom are you on?

Some of the custom TouchWiz roms use dialers from the S5, therefore not stock for the S3.

Some of the custom TouchWiz Roms use the stock kernel, some use a custom kernel.

Did you flash a custom kernel?

What is your kernel version? (check under Settings > About Phone)

With the answers to the questions I asked, audit13 and I may be able to give more definite guidance. It could be as simple as flashing the stock kernel and a stock dialer. But, I can't tell at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Are you saying you unlocked it before? If so it should still be unlocked. Flashing/wiping won't affect that, so it's pretty much a permanent thing. If so, maybe the Sim card you're using is an older one? they don't always work on tmobiles networks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] car2carl:
audit13, dawgdoc, DocHoliday77

Thank you for your responses , Sorry I couldn't response any sooner as I worked in mountain/forest area that browsing the web is luxury :)

(yes I remember for sure I have used this cell phone overseas couple times and the way I unlocked through service mode. Way before AT&T OTA update since new)

I have weird situation that make me wondering if I had unlocked my S3 since message

"PHONE NOT ALLOWED MM#6" comes up if I use any other carrier beside AT&T

Per http://xdaforums.com/showthread.php?t=2789917

thanks to OP

I just managed to change my bootloader to I747UCUFNE4 and also my baseband version to I747UCUFNE4

I still keep my CWM 6.0.4.7 recovery touch

I have Flashed with countless other rom such below:

I747UCUFNE4_Stock_Rooted_Odex.zip

I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip

I747UCUFNE4_Stock_Rooted_3-31-15.zip

and even custom rom without any success

This was happened with my S3 after flash.

if I flashed with inserted active SIM Card (T Mobile or foreign SIM Card)

I will see PHONE NOT ALLOWED MM#6 after reboot

if I flashed without any SIM Card inserted after reboot :

- inserted foreign sim card and reboot again

I will have AT&T as roaming provider and for about few seconds received text message about fee from SIM issuer roaming to AT&T so means My S3 is unlocked...

(no... not so much!!!) in few minute I will have "PHONE NOT ALLOWED MM#6" and phone is useless as emergency only.

- inserted T-Mobile Sim Card and reboot again it shows "PHONE NOT ALLOWED MM#6" immediately

My Kernel Version :

3.4.0-1514807

dpi@SWDD3003 #1

Mon May 19 21:00:05 KST 2014

Thank you if you can help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
So you are not getting asked enter a network unlock code when running a stock rom with a foreign sim?

Does your provider use aws frequencies? The i747 does not natively support T-Mobile aws frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] car2carl:
No, It doesn't ask at all. just pop up "Phone not allowed MM#6."

my foreign SIM is ok.

I tested on Galaxy Note 4 T-Mo (unlocked) it grabbed ATT roaming,

tested on Iphone 4S (ATT-unlocked) it grabbed Tmobile roaming:laugh:

I just flashed stock recovery and still no go..:mad:

do I need to unroot?

Can I flash stock root rom with stock recovery

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
What rom was on the phone when you inserted a foreign sim?

If you are running a Samsung rom, try this:

Www.unlockriver.com/Samsung-unlocking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] car2carl:
I am using I747UCUFNE4_Stock_Rooted_3-31-15.zip

I just replaced CWM recovery with UCUFNE4 stock recovery

I did unroot with SuperSU and also

do factory setting through setting menu

basically my phone just as new factory setting but with UCUFNE4

the funny thing is :System Status: Custom is this related I have rooted this device before?

When I turn on bootloader mode (Odin Mode)

product name : SGH-I747

Current Binary: Samsung Official

System Status: Custom

Qualcomm secure boot : enable

warranty bit: 1

bootloader ap Swrev: 3

as I have stated at my 1st post that I had official unlock code from AT&T and got email from them the unlock PIN

but there is no option asking to key in the PIN with other carrier sim inserted .

I have checked also with Swappa esn check

and result is

Blacklisted =>	Not Indicated

This device does not appear to be globally blacklisted.

spent countless hours just to beat solving this device and read the threads and no result. And still "PHONE NOT ALLOWED MM#6"
[Sony Cross-Device Development Themes and Apps] abo hani:
Hello folks!, Here's my Overlays Collection for Batteries Icons, Which will be updated, And i will add more new icons soon!​

Useful Links :

What Is Overlay ? .

Full AOSP SystemUI

Info :

Collection Sets : AOSP / Sense / Galaxy / Black & White

WiFi/Signal Icons Will Be In A Different Thread .

This Will Change ONLY Battery Icons Without % Mod.

You May See Extra Small Gap, Thank Sony for making a gappy SystemUI ( it's not overlay related bug ) .

How To Install :

Download & Move to system/vendor/overlay .

Reboot.

Disable % from Settings/Personalization/System Icons .

Download :

Index - Press Me .
[Sony Cross-Device Development Themes and Apps] abo hani:
Screenshots

AOSP - With Stamina Icon

Galaxy - With Stamina Icon

Black & White - With Stamina Icon

Sense - No Stamina Icon

​
[Sony Cross-Device Development Themes and Apps] Pandemic:
nice :)
[Sony Cross-Device Development Themes and Apps] punkt:
Just awesome!
[Sony Cross-Device Development Themes and Apps] abo hani:
Glad you liked them!
[Sony Cross-Device Development Themes and Apps] whalesplaho:
good jab buddy.....

#Suggestion- why not make it an xposed module so as to change icon anytime..... thanks!
[Sony Cross-Device Development Themes and Apps] itsnie:
Can you make black battery like z5 ?
[Sony Cross-Device Development Themes and Apps] abo hani:
There are already many Xposed modules to change icons, but this collection for non-xposed users, like me .

Or for anyone wanna use multi-overlays .

I've made a Light_SystemUI, it's out there in the forums, there are 2 ways to get this :

- Light Framework Support, just like Z5 .

- Manual modify on SystemUI, just like what i did .

As an overlay, you will get errors, a lot of errors.
[Sony Cross-Device Development Themes and Apps] Dark_samurai:
Help

I tried all of them but the battery icon still same I even close the % option but it doesn't show any positive result
[Sony Cross-Device Development Themes and Apps] whalesplaho:
#

okay brov..... thanks!!:good::good:
[Sony Cross-Device Development Themes and Apps] abo hani:
Did you move to system/vendor/overlay, and corrected the permissions, after that rebooted ?

Move only one overlay.
[Sony Cross-Device Development Themes and Apps] Pandemic:
Link to it bro [MENTION=5097981]abo hani[/MENTION] ^^

“Sent From MWE V7.0.0 On My Z3”
[Sony Cross-Device Development Themes and Apps] abo hani:
http://xdaforums.com/sony-xperia-z1-compact/themes-apps/mod-dark-dark-light-systemui-14-11-t3248507

Modded Files :

- Drawable folder

- Layout .

- Colors.xml / Drawables.xml / Styles.xml .

- Images in Drawable-xhdpi .

And still some visual bugs, So the real way is to add Light Theme function from Z5 framework.
[Sony Cross-Device Development Themes and Apps] Dark_samurai:
Help

Dude I done everything as u said but still same result it doesn't change battery icon and there is another pblm about ur previous post (aosp system ui overlays when I put aosp overlays on vendor with correct permission and rebooted it after reboot it was chane jst wifi and network icon even notification toggle doesn't change and battery icon also doesn't change)

By the dude srry for my bad English
[Sony Cross-Device Development Themes and Apps] levone1:
My black&white is not black&white...
[Sony Cross-Device Development Themes and Apps] abo hani:
No problem mate, for my previous mod ( toggles ) it's caused by skin permissions maybe, or dpi different .

For this overlay Mod, and the previous one, as you are having a problem in Battery changing, means it's a dpi different problem ( maybe ) .

So, What's your screen DPI ? or What's your device Model .

Note: Changes only happen in " without % " mod .

As i can see you are have AOSP SystemUI, which it may be related to the problem ?

Because i've checked the overlays, they are correct.
[Sony Cross-Device Development Themes and Apps] levone1:
Stock based sysui - status bar icons are from Xstana. I'll try disabling and see if any difference...
[Sony Cross-Device Development Themes and Apps] levone1:
Disabled Xstana - battery still stock. What am I missing?
[Sony Cross-Device Development Themes and Apps] Dark_samurai:
Help

My device is Xperia z1 c6903 running 5.0.2
[Sony Cross-Device Development Themes and Apps] abo hani:
What's your device model?

Plus, Any modded SystemUI?

*if you can upload your SystemUI it would be much helpful

Will check 5.0 SystemUi and update .
[Sony Cross-Device Development Themes and Apps] Dark_samurai:
Help

Cant install to 5.1.1 I dont know why I even tried to update my phone with pc but update was failed but its ok I m ok with that
[Sony Cross-Device Development Themes and Apps] levone1:
Model D5503. ROM is Dstriker, so may be nodded System ui...
[Sony Cross-Device Development Themes and Apps] abo hani:
Upload and i will check it.
[Sony Cross-Device Development Themes and Apps] levone1:
Thanks

https://mega.nz/#!BgU0CD6Z!3X7mawlx-TGYQq5q-8Sa-4MyvSkeAXLUSgDLO6nr2FE
[Sony Cross-Device Development Themes and Apps] levone1:
Sorry, just remembered when I was scrolling through my settings - I installed your 'full dark system ui' mod. That's probably what it is...(I forgot about it bc I also have Xperienced's dark-res mod and I didn't think that would cause it).
[Sony Cross-Device Development Themes and Apps] abo hani:
Fully dark doesn't change the SystemBar icons, it changes only Backgrounds Colors .

Any overlay / Mod / Xposed Module that change / effect SystemUI will stop my battery overlays from working .

Simple Answer :

My overlay will " override " the icons .

Then the xposed module will " override " my icons .

that's how it works .
[Sony Cross-Device Development Themes and Apps] levone1:
OK, maybe it's Gravity Box. I'll check it out... Thanks
[Sony Cross-Device Development Themes and Apps] Dark_samurai:
Help

Abo hani I told u before my battery icon doesn't change I tried everything I don't know why it didn't work plz help me
[Sony Cross-Device Development Themes and Apps] :
Tested

AOSP & Galaxy

Both not Work