yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] Nikon5400:
Got my phone unlocked and running on lollipop. Happy so far.

Huawei works on Marshmallow, but I don't know if that upgrade is worth it. I experience some touch issues with s7e and I know others have same issues with note 5.

Has anyone tried CM? Are they just as stable as Huawei lollipop? (I haven't played enough with the phone yet, don't know how stable it is.. but it wasn't that good with 4.3, some apps crashed others failed to launch)

Thanks for the help.

P.S. in case anyone is looking to unlock - mnz.technologies (ebay) is the guy I got my code from. He wanted 7£, but agreed to $8. Turnaround time was about 7 days. Others say they can do 1-4 days for the same price, but I went with this guy because he replied first. he sent a few codes, I tried the 3rd one first and it worked.
[Huawei Ascend Mate 2] VelcroJ:
When I try to do the three button to go to upgrade, it goes to recovery instead. What am I doing wrong?

I have a Wind Phone
[Huawei Ascend Mate 2] m.reidy:
I really need some help here. I've been at this for a while, and I can't figure out what to do next.

(I have an Ascend Mate 2 LO3 with WIND mobile).

I have been following the guide step by step. When I get to step 4, and I try to copy the TWRP to the fastboot directory, it opens up the command prompt, and says "Waiting for device"

I tried searching for a fix, and found that I need to enable fastboot mode. So, I turned off the phone, held down the +/- volume buttons, and powered back on, and was met with a message saying my Bootloader is Locked.

What do I do?? I'm going insane.
[Huawei Ascend Mate 2] turtleblitz:
Sorry if I sound like a noob but what does cc mean?
[Huawei Ascend Mate 2] coldfusion182:
Guys, if anyone is interested (I coudn't find anything about this here) the Mate 2 Slim (Walmart Version) (which btw is also a MT-L03 but with 8 GB of interal memory instead of 16 GB) can also be flashed to stock Mate 2 using this guide, I did this yesterday and now I am on official lollipop, the only unusual thing is that it is now showing that it has 16 GB of internal memory (which I guess it was because of the repartition thing that the OEM file does, I don't think it now is has 16 GB of internal memory but just a software error) so far so good... will update if anything bad happens.
[Huawei Ascend Mate 2] br@inmatr:
Thank you guys for all the support on this aging slab of a smartphone!:good:
[Huawei Ascend Mate 2] br@inmatr:
Consumer Cellular - that's the regional carrier that supplies and supports this phone (so to speak). :)
[Huawei Ascend Mate 2] 486dx100:
Hi Nikon 5400 and Davinci50

I have just run in the exact same error as you both, I had a Wind mobile Huawei ascend mate 2 and just followed this guide to get it up to B322 and it has been happily running with Lollipop 5.1 and EMUI 3.1

I was so thrilled that I could now play pokemon GO and get outside and I realized how bad wind's network here is in Canada so I have went and rushed and signed up for Fido and want to change providers.

same situation is I have the sim icon with the exclamation mark showing and I can not enter my unlock code, I have purchased it directly from Wind for 30$ added to the bill. Frustrating as hell! I am stuck with two

cell phone bills active at the same time, please help if this will work with Wind, I am downloading the Jellybean downgrade package

we need to make amends to this original post because knowing this * wishing I have read this now! prior to upgrading because I do not have a backup of my OEM partition copied to my SD card by TWRP

so I am fearing the worst. can we amend the first post of this thread to identify that if you perform this upgrade on a carrier locked HAM 2 you will NOT be able to enter an unlock code!

grrr

thanks for these useful posts and I quote ---

-0- link removed- less than 10 posts

Follow the directions attached.

Put the dload file on the sd card and press all three buttons to begin the downgrade process. This WILL erase all your data you have been warned.

This is all I have to offer.

Good Luck[/QUOTE]
[Huawei Ascend Mate 2] Nikon5400:
Unfortunately I don't have this phone any longer, so I may not be much help

I had an issue with entering unlock code. Also, I believe with t-mobile sim all menus were disabled. I had reinstall stock rom ( I believe I downgraded Lollipop to Jelly bean) and it started asking for unlock code again. I entered code, THEN upgraded to lollipop and it was all good after that.

Hope this helps. Good luck

P.S. I miss this phone and may get it again. Only this time I may go with unlocked version, so that I get marshmallow from huawei if they have it.
[Huawei Ascend Mate 2] PhaseDragon:
Upgrade help

I am stuck while following the steps.

I get to step 7 and when I reboot into twrp there is no option to backup

If I try to skip the backup and try and just install there is no option for that either.

I have the Update.app file on my SD card (on the root directory)

I have the OEM.zip on the SD card also (on the root directory)

Can someone help me?
[Huawei Ascend Mate 2] Wmateria:
Hmmm I'm getting back to my HAM2 again.. ordered a new phone but the damn amazon fave me a CC version and.. uf.. ok... So despite with the many steps here... Let's see what happens. Update: Thank you!!!!!! The Huawei logo :D :D Finally can start the update to 5.1 and beyond
[Huawei Ascend Mate 2] FaFlaFlunky:
Thanks to the OP

Thanks OP.

Gonna try and install Lineage 14.1 on this device.
[Huawei Ascend Mate 2] stuntman_mike:
Thank you

Kostyan_nsk:

Thank you. I was able to recover my phone by following your instructions.

I was starting with an unlocked/rooted Consumer Cellular (CC) phone with a version of TWRP installed, not the one you provide.

Somehow I had managed to end up in a situation where I could not go back to, or reboot to the original B147 version of the ROM/firmware.

I tried contacting Huawei and searching the internet for a copy of the B147 firmware to no avail.

I used the files you provided and followed the procedures and everything worked flawlessly.

Once I was up and running with B148, I was able to upgrade to B322 from an SDcard.

What I learned from the whole ordeal was that the Consumer Cellular version of the MT2L03 is partitioned differently than the OEM version of the MT2L03 .

I would appreciated it if you could expand on your original post and explain the partitioning differences, and perhaps other methods for re-partitioning the phone (i.e. possibly using TWRP, adb...?).

Thanks again! P.S. Your English is excellent, much better than most that post.
[HTC One X] Uruloki64:
Hi, anyone try xposed framework for LP roms?
[One (M9) Q&A, Help & Troubleshooting] yoitsjustin:
I no longer have Xposed framework installed yet Sunshine insists I do. Can I override it anyway? Is there a way to delete the thing it thinks is Xposed framework? Thanks!

EDIT: FIXED
[HTC Excalibur] giannibern:
Hi

I have problems to Update my S620 with the T-Mobile Rom.. i have unlock my device with the imei-check tool..

If i start the T-Mobile Update the transfer will beginn. After 3% it's failed with Error 244: Invalid Model ID...

What can i do?

Greetz

Gianni
[HTC Excalibur] UnicornKaz:
Search is your friend !!! :p

http://xdaforums.com/showthread.php?t=312963
[Galaxy Note II Q&A, Help & Troubleshooting] lucaslc7:
I have agni 4.5 dn4 2.4, I just change sound configuration in agni app, and my speak not work any more, is second time this happen, I like fix this without full wipe.
[XDA Assist] rayabandi:
Hi, i am using xiaomi mi4i and i have installed google app and i am trying to use ok google option but i am unable to do that please help me. please provide the steps to enable ok google option
[XDA Assist] rirozizo:
Hello, thank you for using XDA Assist.

Go to Google Now Settings –> Voice –> OK Google Detection and enable hotword detection from any screen.

If it didn't work then try THIS GUIDE

if still not working please do tell us :)
[MX Player] dhruvdave:
Auto play of audios and videos i.e. continuous play are not working after updating to latest nightly.It was working fine in 1.7.40 Please fix it
[MX Player] bleu8888:
Check if 'back to list' is checked on Settings > Player > Back to list.

Loop/Shuffle will be disabled if 'back to list' is enabled in nightly version.
[MX Player] dhruvdave:
back to list is not checked.i have not changed any settings
[MX Player] bleu8888:
This should fix this bug: https://sites.google.com/site/mxvpen/translation/test-build

Thanks for reporting.
[MX Player] dhruvdave:
Thanks.Its fixed
[Galaxy S6 Q&A, Help & Troubleshooting] mojo_jodroid:
hey,

before the soft brick my phone was on G920IDVU1AOC4 stock firmware but i noticed the cell standby was draining my battery.

previously, i had flashed G920IDVU1BOE3 WITHOUT the hidden.img and i didn't have this problem so i decided to flash the AOC4 firmware WITHOUT the hidden.img

now, i cannot get passed the system.img part in the odin process and it driving me insane.

can anyone provide any suggestions/solutions?
[Galaxy S6 Q&A, Help & Troubleshooting] roydok:
Reflash again and again until you succeed.
[Galaxy S6 Q&A, Help & Troubleshooting] mojo_jodroid:
been doing that for 30+ hours :(
[Galaxy S6 Q&A, Help & Troubleshooting] roydok:
Reflash stock 5.1.1 ROM.
[XDA Assist] tribalar:
Hi, i am using Nokia X2ds.. i have recently install custom rom nokdroid, before nokdroid i was using lollipop custom rom. Now the problem is when my phone starts its shows an error ( something went wrong please contact you service provider or nokia care) by pressing ok after that my sim card stays offline and no network signals appear on status bar. Now what should i do,please help... what kind of problem is this?
[XDA Assist] Razvan:
Hi there,

You'd be best served asking for help from the experts who own your device here:

X2 Q&A, Help & Troubleshooting

Good luck
[Android Q&A, Help & Troubleshooting] boonmathew:
In reference to the post

http://xdaforums.com/lenovo-p780/development/miui-v6-5-4-2-beta-row-lenovo-p780-t3078026

download the ROM

https://drive.google.com/file/d/0B-iNKtOAw2CcWXgtVFVQdkFJeGM/view

>>All credits to the above mentioned post<<

Since my lenovo P780 was upgraded to kitkat it was not possible to root it with Framaroot.

So i rooted it with Kingo Root

If you have stock rom in your P780(ICS), you can use Frama root

So my steps follows like this.

1. Installed Kingo Root in my PC, connected my phone via USB (USB debugging must be ON), then follow the procedures in kingoroot.

2. After P780 is success fully rooted, download CWM for P780 from this >>link<<

3. Extract it and put it in your SD Card.

4. Install Mobile Uncle tools from Google play store. select update recovery6. select recovery_P780_CWM_6.0.1.5.img and update 7. you are done

8. You now have English CWM Recovery v6.0.1.5 in your P780

9. Copy the above MIUI ROM in this forum post in to your SD Card.

9. Reboot using Power button and both volume keys to enter into CWM.

10. Then wipe data/format and wipe cache and wipe dalvik cache (important).

11. Install this ROM.

12. After reboot its ready.

13. I had a problem in detecting my P780 in PC. But i rerooted it with the same Kingoroot and its ok now. Didnt check OTG, needs to check.

But i have notification for new update for miui. when i download and its 100 %, it says that

cannot verify the source of this update and it goes of.. :confused: :confused:

But never mind.

[IMG="home page"]http://dl-1.va.us.xda-developers.com/3/3/9/0/1/1/9/Screenshot_2015-07-04-10-12-56.jpg?key=fgSP6jyrSJ0A4jCWIzPHzA&ts=1435989428[/IMG]

[IMG="dialer"]http://dl-1.va.us.xda-developers.com/3/3/9/0/1/2/0/Screenshot_2015-07-04-10-14-07.png?key=YobeUKq090vhlvBDGacs3w&ts=1435989468[/IMG]
[Moto X General] sroy001:
Hi Folks,

I've noticed wave to wave feature no longer works after OTA upgrade to Lollipop.. I've read in some blogs that it was a defect in KitKat and wasn't intended post the release, which has now been fixed in the 5.1.1 OTA

I've rooted my device post OTA and installed some great XPOSED modules like Amplify, Greenify and Gravity Box.. Been running great with appox 2 days battery life with moderate use :)

BUT!!! I really miss the WAVE TO WAKE

Any possible ideas how to get it back? I know there's a TASKER method to get it but that's another activity running in the background which I DON'T want.. Any other options? Any XPOSED module that you all are using?

Thanks
[Moto X General] md07:
there no Stock 5.1.1 version for Moto X, just 5.1
[Moto X General] sroy001:
My bad.. Meant 5.1 stock OTA
[Moto X General] bkk99213:
Wave to wake is workbut it need sometime...

Around 4 second , hold your hand over the sensor.

And then leave, phone will wake.
[Moto X General] sroy001:
LOL:p:p It does work! We need to know how to make less than a second!!
[Moto X General] tazlooney89:
Gravity Screen ON/OFF I'm currently using on stock Retail_US and working properly, the battery consumption and RAM is minimal.

Enviado desde mi Moto X mediante Tapatalk
[Moto X General] sroy001:
Where in Gravity?
[Moto X General] rodaven:
It's an app.

https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree

Enviado desde mi XT1058 mediante Tapatalk
[Moto X General] St.Noigel:
Look here
[Moto X General] sroy001:
Okay so Gravity Turn Off/ Turn on wakes the whole screen and not just the notification pixels(like before)

Am I missing any setting?
[Moto X General] bkk99213:
More app more battery.

The app's developer also said that will get 6% extra battery after use.

I think make a xposed is better but I don't know how:p
[Moto X General] kain83:
Hi all, I have just installed this app to have back wave to wake function:

https://play.google.com/store/apps/details?id=simone.cascino.airon&hl=it

So far it seems to work very well: on the default configuration you need to cover, uncover and cover again the proximity sensor in order to wake up the display. I think that if you buy a premium key you are able to change this configuration (even if the default configuration is suggested solution).

There shouldn't be any battery drain, because proximity sensor still uses low power core, but any feedback is welcome :). Last thing: you must leave notification app on, otherwise it doesn't work.
[Moto X General] bazantik:
After few month... if you want this "Jedi" gesture back on 5.1 ROM, try [ROM] Moto X L!te FW 5.1.0 LPA23.12-15.5.EU.ML by [MENTION=6473170]CrashXXL[/MENTION] - "based on the stock, and includes all updates and patches". Very good :)
[Moto X General] mastarifla:
Interesting find!

I'm downloading the ROM now and I'll pull the APK's that make this work and upload them so people won't have to flash a custom ROM

Edit: Okay guys here it is, I tried creating a flash-able zip that you can just flash via your custom recovery, big thanks to hachamacha for fixing the patch :)

Here is the manual way...

1) Download the zip

2) Open the system/etc/firmware folder and grab the bins/text files

3) Delete the same bins and text files on your phone

4) Copy these to the same directory on your phone

5) Set the permissions to be rw-r--r-- (0644) on each file

6) Reboot and click on the notification to revert your firmware

7) Uninstall/Revert the firmware and it will reboot for the last time and you'll have wave-to-wake back :)
[Moto X General] bart.found:
no way to do this on an unrooted phone? Via adb or something?
[Moto X General] hachamacha:
Good job. The only thing that kind of jumps out at me in the .zip version is that in the META*/*.../ folder where updater-script is, you don't have a copy of updater-bin. I can't recall seeing another script like that. I suppose if it's in the $PATH somewhere, it might not matter.

---------- Post added at 03:56 PM ---------- Previous post was at 03:44 PM ----------

[MENTION=5735314]bart.found[/MENTION] : Is there some rule against booting the phone into fastboot mode (adb reboot-bootloader) without root? I'm thinking not. If you can do that, then you can possibly flash recovery (twrp) and then boot into recovery, which has it's own rooted environment and once the .zip file is working (monitor this thread), just flash it from there. Also TWRP (or Philz) have their own file managers, so in theory, you can do it all manually from recovery as well.

Good luck.

Anyone that disagree's please post in this thread. I've got a bad cold today and am thinking on about 2 out of 8 cylinders ;;). Appreciate it.

Edit: Damn, I am stupid. While that ^^ might or might not work, it might be a lot simpler to just adb reboot to fastboot, then boot into TWRP without installing it on the phone. That eliminates some risk. Once in fastboot the command should be $fastboot boot {twrp-image-name-for-motox}, (e.g. fastboot boot twrp.img).
[Moto X General] hachamacha:
I took a moment this morning to add a version of update-bin to the original zip file by [MENTION=3015269]mastarifla[/MENTION] and will attach it to this post. It worked fine for me. Wave to wake is back (xt1060). I couldn't find any errors with the updater-script. I also made a "revert-{version of the wave to wake}" zip file and will include that as well in case something unexpected happens.

The update-bin file I added was one I'd used in numerous scripts here on XDA that I knew worked fine with the moto x.

When you reboot the first time after running in recovery, please recall to look at the notification that asks if it's OK to revert the firmware and say yes. It'll reboot, and after that 2nd reboot, it should work with wave to wake as in 4.4.4.

Cheers.
[Moto X General] hachamacha:
!! credits to [MENTION=3015269]mastarifla[/MENTION]
[Moto X General] mastarifla:
Awesome work dude!

I went ahead and downloaded both of them and added your name to the beginning of the script for helping

I'll re-upload them in my post :)
[Moto X General] timmytucker718:
Wave to wake is working.

But now my chop chop light is broken....

Now I have to decide which is more useful to me....

Unless you fine people can pull your magic to get both working....
[Moto X General] jco23:
chop chop light was never working for me - and I have the modded version... but wave-to-wake is now (modded stock 5.1)
[Moto X General] bazantik:
I thought "chop chop light" was available only for Moto X 2nd gen.. It worked also on 1st gen for you?
[Moto X General] timmytucker718:
Yeah there was a work around to get it to work.

https://www.reddit.com/r/MotoX/comments/3k1xle/okay_after_quite_a_bit_of_effort_here_is_chop/

Reverting the sensor firmware to 4.4 for wave to wake breaks it though.
[Moto X General] hachamacha:
For some unfathomable reason, I got curious about how the Moto X was figuring out how to do the things it was doing via "touchless" (or like "chop chop to xxx") controls, so I did a git from MM on the 5.1 kernel and read through a few of the driver files after a grep for 'msp'. I'm pretty sure no one cares, but it's interesting to me because I did one job on the TI MSP430 chip (there are many types of them and mostly are for medical uses like in .. pacemakers, or pumps).

I realized that the Moto X's have an MSP430 on the motherboard and that is the chip that is the recipient of the firmware files we've been messing with (mspfirmware.bin, *_1/2/3/etc). So if someone wants to be able to do more of the actions that are either proximity sensor driven, or .. "chop chop" driven, then things likely get kind of complex.

First you'd have to dig into mspfirmware.bin(s) files and figure out what format that was written in. TI gives out a free compiler on their website for the msp430 chip series, so that maybe could be used and they also give a bunch of tools out for the 430, so in some vague fantasy, maybe someone could figure out how the firmware for either chop-chop or proximity works, and rewrite the entire mess to do whatever you wanted it to do. That is probably the easy part and that's not easy.

The hard part would be packaging it up the exactly correct way so that the processor (CPU) could access it, make sure the kernel is OK with it, and then throw it all back together. It seems a lot to go through when you can just do this

(Talk to your phone as follows):
"OK Moto X, Flashlight ON"
"OK Moto X, Flashlight OFF"

;;)

And here's a few example lines from the kernel code regarding the msp430:

arch/arm/boot/dts/msm8960ab-ghost-p1b4.dts:/* Note, P1B4 msp430 uses fw common with P2 (NOT common with P1) */
arch/arm/boot/dts/msm8960ab-ghost-p1b4.dts: msp430@48 {
arch/arm/boot/dts/msm8960ab-ghost-p1b4.dts: msp430_fw_version = "_p2";

I guess the good news for me was that it kind of got me interested in android kernels again. Also: There's always some oddball chance that by mixing and matching mspfiremware files around (I hate this idea) that you'll get lucky. There is a much higher chance that you'll crash the msp chip and that'll be the last thing that any detection or touch sensors do for awhile.
[Moto X General] mastarifla:
Cool, I have been looking at this as well, the bin files are in standard TI-Text format, and I was able to convert it to the Intel Hex format (.a43), now I just need to de-assemble the files in order to understand where I need to make changes... And what those changes between 4.4.4 and 5.1 include...
[Moto X General] CrashXXL:
hmmmm

copy past techology (c)

I am not satisfied, it is necessary to indicate the source

Only that can copy ....
[Moto X General] Anachronizer:
Great job guys. Kudos!! :good: :good:

BTW, does this also revert the sleep timer feature of the new Moto Display i.e. it stops/goes to sleep after approx 10 mins of pulsing?
[Moto X General] mastarifla:
My post had the quote with your name in it, that isn't enough credit? I also went to your posts and gave thanks to each of them

There are people who don't want to flash an entire ROM to have this feature, so I gave them the option to do it via this method :)
[Moto X General] hachamacha:
Just another day at the XDA farm.. Only in a computer forum can someone find a reason to get irritated at someone for giving them a choice that wasn't there (or at least hadn't been neatly packaged and presented) before.

But onto other things: I had to re-fetch all the CCSM (msp430, etc) tools from TI because all my old one's expired, but I'm setup again on a Linux VM and starting to look into this stuff.

One thing that kind of bugs me is that the "chop chop for flashlight" is basically taking one of the least energy-hungry devices ever put on a smartphone (the msp430 and the low-power core of the x6) and using it to turn on the MOST energy hungry device (a flashlight). Does that really seem necessary or even very handy when there are already a thousand widgets that can do that function?

Doesn't really strike me but people get used to everything and grow to like a certain way of doing whatever they do. I was thinking more along the lines of figuring out some more interesting functions that aren't energy-hungry and adding those to a new version of the mspfirmware/etc/etc...

More later, gotta run.

Cheers.
[Moto X General] mastarifla:
Why not grab the intent via Xposed and use the gesture to open an app or to trigger something different?

Update on my end, I went ahead and grabbed the firmware files from the various updates that our phone has had and found that there are a total of 5 different released MSP firmware versions...

Android Ver Firmware Ver
4.2.2 3-3 (33)
4.4 3-9 (39)
4.4.2 3-11 (3D)
4.4.3-4.4.4 3-13 (3F)
5.1 4-5 (45)

Inside the MSPUpdater package it specifies that we can load custom firmware, in this case, I would recommend tweaking the 4.4.4 KitKat version and using the following msp version numbers...

mspversion 40

mspversion_p0 08

mspversion_p1 40

mspversion_p2 40

Oh and keep the 4.4.4 mspfirmware_p0, as there seems to be no changes to it between 4.4.4 and 5.1, Currently I'm still trying to figure out how to best load and test the binary files into a MSP430 simulator