yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Q&A, Help & Troubleshooting] User_99:
Similar, but Cellular Networks (GSM, UMTS, LTE) are different. I won't flash other Roms.
[Galaxy S5 Mini Q&A, Help & Troubleshooting] atego:
+1

Why do you want to flash 800H on a 800 F ??:confused:
[Galaxy S5 Mini Q&A, Help & Troubleshooting] RicSou:
by networks LTE...possible?

Enviado desde mi MB526 usando tapatalk
[Framaroot] harshcr7:
i want to root my android

i try all methods to root but not worked

pls hrlp anyone
[Framaroot] iqbalwww:
Wiio Wi5 Working Root Method

Yes !!!

I have also Wiio Wi5.

I have successfully (SUCCESSFULLY) rOOTED MY handset....with latest version of iROOT (English Version)..

download iRoot....

Rest is yours:laugh:
[Ascend Mate 7 General] ml_taz:
There is a new OTA Update for international version of Ascend Mate 7:

Firmware B137SP03

It seems to be a performance update with optimized stability for system and while roaming.

Base is still Android 4.4.2 and EMUI 3.0.

First Impression is a better network connection, espacially with 4G.

Source and download: http://www.huaweiblog.de/huawei/firmwareupdate-b137-fuer-mate-7-ota/
[Ascend Mate 7 General] boovilly:
Updated to this about a week ago. A few cosmetic tweaks (call screen, status/navbar) but the biggest seems to be 1080p play back on YouTube. No idea about 4g as we are a month or so away from getting it here.
[Ascend Mate 7 General] tuddu:
Is this update for the ALL the MT7-L09 versions (all European Countries)??

The file is 65mb only...how to use it?? DLOAD+3buttons?? Normal Update??

I don' t think it could work...file is too small (not complete ROM).
[Ascend Mate 7 General] ml_taz:
[MENTION=5644492]tuddu[/MENTION]

It's just the OTA update file (B127 -> B137SP03).

So you need to have B127 installed. Then put the "update.zip" in dload folder (exteranl SD) and install by local update.
[Ascend Mate 7 General] matematto:
I suppose it's the same for B130 -> B137... right ?
[Ascend Mate 7 General] kpyhere:
I tried with 130 to 137 and it failed :(
[Ascend Mate 7 General] paullu:
Can I update from b130?or must update from b127?
[Ascend Mate 7 General] matematto:
Reading translation (thanks Google :D it's all clear

"... Furthermore, we will of course try the full version of firmware B137 for you to download to make available. Until then, we can provide you the update.zip available. It is the downloaded OTA update, which we have extracted. This is update.zip for the update process of the firmware B127 to the new firmware suitable B137SP03. Who another firmware installed, should start at the latest official firmware B127 update.

By itself to perform the update, you must download the update.zip and you just copy them into the folder dload on the external memory card; the update.zip may not be unpacked! "...
[Ascend Mate 7 General] tuddu:
Tried myself MT7-L09 from B130... doesn't work...as indicated in the link... Must have 127 in order to update...
[Ascend Mate 7 General] Simona Simmy:
I checked and nothing .. no OTA ?

EDIT ; alright reverting to 127

EDIT 2 who ever said u need to be on 127 is FULL OF CRAP !!! not working !!

EDIT 3 : updated to 137 and phone bloody lags as hell !!! boot animation il like slowmotion sht fuk u messed my phone here !!!!
[Ascend Mate 7 General] qkrusty:
i just got an OTA Update as you can see here.... http://goo.gl/6jUwEW
[Ascend Mate 7 General] Simona Simmy:
i did it all manually

i did it all again and now am on 137

animation is not lagging anymore..
[Ascend Mate 7 General] hori79:
after update still have CWM and root.?i have custom cwm.
[Ascend Mate 7 General] tuddu:
Simona, how did you succeded in updating? Which procedure did U followed please?
[Ascend Mate 7 General] manospr:
For those who are root and have a custom recovery can we flash the update or do it manualy?
[Ascend Mate 7 General] Simona Simmy:
I always put stock recovery back after root deleting those gapps unnecessary that system looks original... and still rooted and everything
[Ascend Mate 7 General] tuddu:
Is there someone who has been able to install this update, starting from B130?

If so, how to do that?
[Ascend Mate 7 General] Simona Simmy:
Well when ppl been saying you need to be on 127 so I downgraded checked OTA and nothing ..

Downloaded update.zip from first post and installed as usual dload SD card .. local up etc..

But after that boot animation become laggy from weird reason .. so I flashed 127 back and boot anim. lag still persisted..

So I downgraded to beginning B120 .. then all was great.. upgraded to 121 all good then up to 127 all perfect then I SKIPPED 130 and upped B137SP03 from 127 ..

All perfect..

Flashed/Rooted CWM SuperSU v2.46.zip

Flashed stock recovery back
[Ascend Mate 7 General] tuddu:
Thank you Simona. I trust I'll remain on 130 for the moment... Too much troubles to install 133 in that way.

Thank you anyway.
[Ascend Mate 7 General] Simona Simmy:
not 133 but 137

try it from 130 it might work just put it in dload sd card try local ..
[Ascend Mate 7 General] tuddu:
Yes, already tried that but didn't worked, both local update or 3buttons...
[Ascend Mate 7 General] Simona Simmy:
downgrade to official 120 as I did ..
[Ascend Mate 7 General] manospr:
Good you please inform me how you flashed stock recovery .What file?
[Ascend Mate 7 General] Simona Simmy:
here : https://mega.co.nz/#!FxRTmLza!g2oX4WpdVzjkzHS8wm0WK5l4mJuxHpdf4VUzRiFjcVw

if you on 130 flash 127 stock recovery and flash 127 first

report
[Ascend Mate 7 General] manospr:
if you on 130 flash 127 stock recovery and flash 127 first

report[/QUOTE]

I have one MT7-L09 B127 right now with root and custom recovery and i want to flash stock recovery in order to update to 137.Do I have to flash stock with flashify the stock img?
[Ascend Mate 7 General] Simona Simmy:
I have one MT7-L09 B127 right now with root and custom recovery and i want to flash stock recovery in order to update to 137.Do I have to flash stock with flashify the stock img?[/QUOTE]

oh .. you need stock recov. ofcourse.. try it with flashy..and up to 137
[Ascend Mate 7 General] Mohsen.RN:
B126

I'm on B126 , What should i do ? , plz help , i'm not a professional...
[Ascend Mate 7 General] Simona Simmy:
try flash straight to 137
[Ascend Mate 7 General] tuddu:
I can't understand why the update accept 127 only and not 130...strange...
[Ascend Mate 7 General] leonardus_magnus:
HI Simona,

updated my MT7-L09 without any problem from B130 following the procedure you suggested... B127 stock recovery>flash B127>flash B137 and then obviously CWM Recovery and SuperSu 2.46... Thanks!!

For what concerns the update, I noticed that now it takes more time to connect to operator at boot... before update the connection was almost immediate...
[Ascend Mate 7 General] Simona Simmy:
Yeah it hapened to me same I mentioned it above

I just was completelly upset bout it and I did all flashings again and it is fast again..

I have no idea what this causing..

Leave it for while and It eventually be fast again..

It is like settling

I have forecast widget and was slow but it is fast again even signal and OP logo
[Ascend Mate 7 General] lichtenfeld:
Hi

nobody have it in zip flash for cwmr ?

i have a cust failure and the only way for me is flash non update.

Thank's for
[Ascend Mate 7 General] Simona Simmy:
it wont work like that.. you need do officially
[Ascend Mate 7 General] leonardus_magnus:
Yes... Same here... after one day and a rebooting a couple of times... everything works fast as before...
[Ascend Mate 7 General] Toss95:
When I flash this update, in the stock recovery I have a "Huawei clust fail", can someone explain me what that means plz?
[Ascend Mate 7 General] tarek2010:
Did anybody try to flash stock recovery image using Flashify or Rashr Flash Tool? Please advise..
[Ascend Mate 7 General] Fooox1:
Can use this. Easy and fast.

http://xdaforums.com/mate-7/orig-development/custom-recovery-tool-mt7-l10-l10-mt7-t3022424
[Ascend Mate 7 General] tarek2010:
Thanks [MENTION=2336653]Toss95[/MENTION]. I usually use the mentioned run.bat to flash back and forth CWM and Stock Recovery. This is just a faster way to do from mobile if it really works fine with our Mate 7. So that's why I was asking if someone already tried any of the mentioned tools to flash Stock recovery or/and CWM without problems..
[Ascend Mate 7 General] tarek2010:
Upgraded successfully to B137-SP03 from B127 and here are some notes worth consideration:

1- Don't use Flashify or Rashr Flash Tool to flash Stock Recovery or CWM as it is not working properly and rendered my Recovery useless (couldn't enter Recovery or Download after a bad flash and had to enter Download using ADB and then use the run.bat script to reflash Stock)

2- Tried to upgrade (Local) from B127 to B137-SP03 which failed on the first trial.

3- Reinstalled B127 (Local) successfully.

4- Reinstalled B137-SP03 successfully afterwards.

5- Flashed CWM using run.bat script and rooted.

6- The Stock Recovery image found in the run.bat script seems old dated and not suitable to install B137-SP03 from B127 (That's why some people fail to upgrade from B127 to B137-SP03 after flashing Stock Recovery using run.bat)

7- No need to reinstall consecutive B12x till B127 to install B137-SP03, you just have to have an installed B127 version with its own original Stock Recovery not the one in run.bat, or replace the Stock Recovery image found in the script folder with the B127 proper one as I belive there are minor differences in Stock Recovery images of different ROM versions.

8- B137-SP03 is only a service patch and not a full ROM replacing some system apps and adding new functionality.

Hope that helps people who had some problems upgrading from B127 to B137-SP03.

---------- Post added 25th March 2015 at 12:10 AM ---------- Previous post was 24th March 2015 at 11:53 PM ----------

System apps that were updated with B137-SP03 upgrade:

1- Backup

2- Finger print services

3- Play Store 5.3.6

4- Videos

5- Power Genie

6- Music

7- Huawei Swype

8- Updater
[Ascend Mate 7 General] Kumar07:
More on [MT7-L09] with B137 SP03

I am very new to ANDROID phones,bought MATE 7 in Germany.

I have no idea of what is root before, which I learned from Internet alot now and took decision to root my MATE 7.

Please help to root my MATE 7

Firm ware is MT7-L09- B137SP03.

Can I able to root my phone or not with this above Version?

If yes, can you tell me how? because I saw in this Forums root with other Versions only.

Cheers!!!
[Ascend Mate 7 General] tarek2010:
[MENTION=6534910]Kumar07[/MENTION] sure you can by following the steps mentioned in the following post to unlock Bootloader and install CWM then Root your device:

http://xdaforums.com/showthread.php?p=56780779

You can download SuperSU latest version 2.46 zip file from Chainfire SuperSU xda forum and copy it to your mobile instead of the outdated 2.2 attached version.

http://xdaforums.com/showthread.php?t=1538053

Hope it helps.
[Ascend Mate 7 General] tuddu:
Please check here, should be same as your model, even if starting ROM is a little different.

Procedure SHOULD be the same. As always: backup, etc. etc.

http://xdaforums.com/mate-7/general/guide-european-model-bootloader-unlock-t2944284
[Ascend Mate 7 General] tarek2010:
[MENTION=5948085]zziiad[/MENTION] Of course not. You have to stick with ROM updates released for your specific handset model.. :)
[Ascend Mate 7 General] gilbert5107:
Hi All,

im currently in version MT7-LO9V100R001C00120SP04

i had root my unit. need to recover back to stock and do the update? then root it back?

It is the way?
[Ascend Mate 7 General] vonotny:
I think you can just drop the update on your SD card, reboot into recovery (you'll need stock recovery though) and install the update. You may need to re-root afterwards.
[Ascend Mate 7 General] sho.mcgregor:
[MENTION=2021504]huawei[/MENTION] are not responding to emails. Is there another way to get code?

---------- Post added at 05:33 PM ---------- Previous post was at 05:27 PM ----------

Hi, Huawei are not answering emails. Is there another way to get the code?

Thanks

---------- Post added at 05:33 PM ---------- Previous post was at 05:33 PM ----------

Hi, Huawei are not answering emails. Is there another way to get the code?

Thanks
[Ascend Mate 7 General] gthebest:
Hello. Does anyone knows where I can find the stock recovery B137SP03 file for MT7-L09?
[General Accessories] irv777:
Does anyone know any compatible batteries for the Asus P535 with a higher capacity?.....thanks in advance
[General Accessories] sokomind:
P525

p535

p750

o2 xda zinc

o2 atom v

sbp-06 batteries
[Android Q&A, Help & Troubleshooting] MOSHETVITO:
I have en xiaomi mi3w v6 5.2.13

and i want to install a screen mirroring app

and i can not

please some one helpe me with that
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
Hi,

the mod threads for the various cm12 builds claim that NFC is working, and there are also several user replies with reports that it works fine. Yet it doesn't work correctly for me, and at least some others: The device reports that NFC is working, I can activate and deactivate it, but accessing cards only works partially or not at all. The funny thing is that after flashing cm12, restoring an old cm11 nandroid backup does not restore NFC functionality. It doesn't matter if I do a clean install/full wipe. With Lollipop TW roms (I've tried XtreStoLite), NFC works fine.

I'll try to keep this top post up to date. Last update: 2015/03/15

We've found the issue that caused the major part of the problems. A configuration file must be adapted to the latest firmware. (update.zip version) This fix has been accepted upstream and is included in nightlies starting from 20150316.

There are cards/tags that still don't work, but do with stock, though. I've tested:

German eID (works)

Mifare Ultralight (works)

Beam (works)

EMV (works)

Mifare Classic (e.g. German "Mensacard", membership card from gym / McFit, ..) does not work. See below for debug output of libncf-nci.
[Galaxy S 5 Q&A, Help & Troubleshooting] flyingbiker:
Hi there,

I have exactly the same problem. NFC doesn't work for me neither. My device is a G900F from Germany, bought via Amazon using Euphoria OS which is based on CM12.

Ah, and just to get that straight, european G900F is klte without any other letters, right?
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
After doing some more digging, I discovered that running

setprop nfc.nxp_log_level_global 3

as root enables tons of debug messages.

Maybe it's the firmware

Obsolete: This is unlikely. Its only Mifare cards that don't work, and the protocols are, as far as I can see, implemented in the userland library.

I noticed that after enabling NFC, one of the logcat outputs is

D/NxpHal ( 1081): FW version for FW file = 0x118
D/NxpHal ( 1081): FW version from device = 0x8011f
D/NxpHal ( 1081): FW image older than device's, skip update

Maybe this helps. (Could anyone with working NFC check which FW their device has? Should work the same way: Run setprop.. as root, enable NFC, search logcat output for the FW info, then reset the log level to 0.)

Mifare cards

I further noticed that holding a Mifare card near the antenna does trigger a reaction:

D/NxpTml ( 2317): PN547 - I2C Read successful.....
D/NxpNciR ( 2317): len = 23 > 61051401808000FF010904000454566739010800000000
D/NxpTml ( 2317): PN547 - Posting read message.....
D/NxpHal ( 2317): read successful status = 0x0
D/NxpHal ( 2317): NxpNci: RF Interface = MIFARE
D/NxpHal ( 2317): NxpNci: Protocol = MIFARE
D/NxpHal ( 2317): NxpNci: Mode = A Passive Poll
D/NxpExtns( 2317): const CNfcParam* CNfcConfig::find(const char*) const found MIFARE_READER_ENABLE=(0x1)
D/NxpTml ( 2317): PN547 - Write requested.....
D/NxpTml ( 2317): PN547 - Invoking I2C Write.....
D/NxpTml ( 2317): PN547 - Read requested.....
D/NxpTml ( 2317): PN547 - Invoking I2C Read.....
D/NxpNciX ( 2317): len = 7 > 20020401800100
D/NxpTml ( 2317): PN547 - I2C Write successful.....
D/NxpTml ( 2317): PN547 - Posting Fresh Write message.....
D/NxpTml ( 2317): PN547 - Tml Writer Thread Running................
D/NxpHal ( 2317): write successful status = 0x0
D/NxpTml ( 2317): PN547 - I2C Read successful.....
D/NxpNciR ( 2317): len = 4 > 40020106
D/NxpTml ( 2317): PN547 - Posting read message.....
D/NxpHal ( 2317): read successful status = 0x0
D/NxpHal ( 2317): > Deinit workaround for LLCP set_config 0x0 0x0 0xa
D/NxpHal ( 2317): phNxpNciHal_print_res_status: response status =STATUS_OK
D/NxpTml ( 2317): PN547 - Read requested.....
D/NxpTml ( 2317): PN547 - Invoking I2C Read.....

But nothing ever shows up in an NFC test app and I have to deactivate and reactivate NFC at this point to scan any of the working smartcards. So likely something in the mifare reader code does not work.
[Galaxy S 5 Q&A, Help & Troubleshooting] TheATHEiST:
No NFC for me either :(
[Galaxy S 5 Q&A, Help & Troubleshooting] Virnik0:
Running yesterday's nightly 20150310 on klte, no NFC either.
[Galaxy S 5 Q&A, Help & Troubleshooting] Etnoy:
Any news? I have a SM-G900F and am unable to read NFC tags since updating to CM12 (now using 20150313).
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
My NFC was gone too after I updated to the latest nightly yesterday. It appears that copying the firmware file and configuration from XtreStoLite fixed that, and that I'm back to the situation I described in the top post again now. I'll attach both files (in one archive). They should be placed in the according directories in the /system partition, i.e.

etc/libnfc-nxp.conf -> /system/etc/libnfc-nxp.conf

system/vendor/firmware/libpn547_fw.so -> system/vendor/firmware/libpn547_fw.so

Could you test if copying them & rebooting (partially) restores NFC for you, too? (This should be possible with a file manager like X-Plore) If you don't want to use my archive, download XtreStoLite and extract the same files from their zip. Flashing CM should restore the original files in any case.
[Galaxy S 5 Q&A, Help & Troubleshooting] Etnoy:
Hey, that actually worked! I tried with an NFC reader app, and my nfc tag popped up right away.
[Galaxy S 5 Q&A, Help & Troubleshooting] Virnik0:
So now we're missing only flashable zip :)

I will try this one and if it will work, I will try my scripting luck :)

And here it is, enjoy :)
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
I believe that it might suffice to update the configuration file. According to the logs, at least on my phone, the firmware file isn't used anyway.
[Galaxy S 5 Q&A, Help & Troubleshooting] andzno1:
WOHOOOO! Thank you very much. My klte's NFC stopped working after flashing some alpha CM12. Some days ago I flashed cm-12-20150310-NIGHTLY-klte and the NFC problem remained. Now I replaced /etc/libnfc-nxp.conf with the config file you attached and NFC is working again.
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
Great! I've submitted this upstream, hopefully they'll accept this. It would be good to get feedback from someone who didn't experience any NFC issues in the first place, though, to make sure that this does not break NFC for anyone.
[Galaxy S 5 Q&A, Help & Troubleshooting] Etnoy:
How awesome. NFC is really stable too and I think we have found the fix. I belive that many galaxy s5 CM12 users will be happy :)
[Galaxy S 5 Q&A, Help & Troubleshooting] Etnoy:
Seems like the fix will be in the next nightly, too.
[Galaxy S 5 Q&A, Help & Troubleshooting] ostauss:
Still some Problems :(

Hello,

first at all thanks for your research!

I installed your fix for the NFC (tried both zip and "self" copy) but NFC is not working correct:

* sometimes when enable/disable NFC i get a sound (not allways)

* When i scan a tag (the first time after enabling nfc) i get a sound for scanning, but NFC TagInfo and Tagstand Writer did not recognize the tag.

* Sometimes NFC TagInfo by NXP is working but one one time... (hard to explain, often the scanning works when i open the settings?)

* The Scanning works only once till i deaktivate/active NFC

I used the the fix with cyanogenmod nightly 14-03-2015 and now with the Unofficial build [ROM] CyanogenMod 12.0 | Android 5.0 Lollipop | [03/13/2015]

Also installed the latest Xposed framwork and SELinux "Permissive" ...

Any ideas?

Thanks in advance
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
Which variant do you have? (I, and afaik all others that reported here, have a g900f)

What kind of NFC tag do you try to scan? (As I've already written in the top post, Mifare Classic does not work.)

The relevant logcat (see a few posts up, I've posted a setprop-command that enables debug output) would also be interesting.

Btw., the only sound I get is for the recognition of a NFC chip and its removal. Enabling/disabling makes no sound whatsoever.
[Galaxy S 5 Q&A, Help & Troubleshooting] ostauss:
What i forgot i have G900F :)

Sometimes i really got sound for enable/disable!?!

Hard to tell you what type of NFC tag i use, bacuse i cannot read them at all.

I tried

* a writable tag from androidbands.com

* a company card

* a skiing card

I will try to logcat later this day....
[Galaxy S 5 Q&A, Help & Troubleshooting] ostauss:
Here is a loccat (created with logcat extrem app - currently no adb available for me)

Actions:

Activate NFC // Scann androidbrands.com Tag // Deactivate NFC

Looks like problems with the "libpn547_fw":

Line 191: D/NxpFwDnld( 447): @@@/system/vendor/firmware/libpn547_fw.so
Line 193: E/NxpFwDnld( 447): NULL handler : unable to load the library file, specify correct path
Line 199: E/NxpFwDnld( 447): Image extraction Failed - invalid imginfo or imginfolen!!
Line 201: E/NxpFwDnld( 447): Error loading libpn547_fw !!
Line 209: E/NxpHal ( 447): Wrong FW Version >>> Firmware download not allowed

The file exists in "/system/vendor/firmware/libpn547_fw.so" with "rw-rw----"
[Galaxy S 5 Q&A, Help & Troubleshooting] ostauss:
changed permissions to "rw-rw-r--" looks like lib is correctly loaded, but scanned androidbands.com Tag still not recognized by TagInfo...
[Galaxy S 5 Q&A, Help & Troubleshooting] Virnik0:
Update to latest NIGHTLY. Fix was released yesterday. At least it works perfectly on my SM-G900F. No need for ZIP or manual filecopy anymore.
[Galaxy S 5 Q&A, Help & Troubleshooting] FirebirdDE:
Maybe /etc/libnfc-nci.conf also has wrong permissions? Did you run setprop nfc.nxp_log_level_global 3 in a root shell before enabling NFC? There should be a lot more to see in logcat if you did.

The fix in the nightly is (mostly) what I've posted earlier. If the flashable zip doesn't help, the nightly won't either.
[Xiaomi Redmi 1S] skarthickbabu:
Dear All,

Please help,

I have purchased the Redmi1s in Singapore, it worked good there,

When i travelled to india, with the indian sim card it worked well.

But now i am in Netherlands, but when i try putting the new local sim card, the system keeps going auto reboot continuously.

Somebody please help me or suggest tips to overcome this.

Lots of thanks in advance,

regards

Karthick
[Focus General] aandason:
Has anyone ever realised that whenever you update an app, data that's stored in sd card will automatically store back in device storage?

This has never happened to me before upgrading to Lollipop.
[One (M8) Q&A, Help & Troubleshooting] AttachedSilver:
So my usb port is messing up as now I have to add pressure to the cable in order for it to charge. I have cleaned the port and while there was a good amount of lint in it, it still needs pressure for it to charge. I have contacted HTC and they gave me the option to send it for repair or get a new one and send the old one in. However since it is S-OFF & rooted, I was wondering if flash the RUU and switch back to S-ON will it be ok? Since they had told me that if the boot loader had been unlocked etc it no longer is covered by the warranty. Sorry for the long post
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
If you have an RUU available and can flash it and get back to locked/Not tampered/S-ON you'll be fine (in theory)
[One (M8) Q&A, Help & Troubleshooting] AttachedSilver:
On the boot loader, it says "official software" and doesnt say "tampered" however I think it'll say relocked. Is that fine?
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
It'll have to do! It's up to them if they accept it, though...
[One (M8) Q&A, Help & Troubleshooting] .Ryker:
Theres a way to can edit it to say locked, if necessary ahaha