yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] p51d007:
Huawei stated on their site, NOT to share the beta builds FOR A REASON.

Limited release, allows a few to check it. Start sharing it and every Tom-**** & Harry

will be flashing, and, if it turns out there is a bug, they will ***** about it.

Also, It's been a struggle to get Huawei to update it to start with, and if people start

screwing around, they may just say screw it, it isn't worth the hassle. Might hurt them

globally, but, the global market, right now, isn't their CORE business.
[Huawei Ascend Mate 2] Moody66:
They are wanting to be a player in the US. That's the reason for selling them here.. Through providers... With current business model they won't make it here. Again. That's the point.
[Huawei Ascend Mate 2] p51d007:
Yes, but they DID NOT WANT this file shared. If you got it, you got it. If you didn't, you won't.
[Huawei Ascend Mate 2] TheIgster:
Oh no. How will I ever live?

You still didn't address the fact that you were WRONG. But then again, just go about your business of ignoring what doesn't work for you.
[Huawei Ascend Mate 2] Moody66:
Ota is ota.
[Huawei Ascend Mate 2] TheIgster:
And respecting a developers wishes is respect. Here at XDA, we should all know that better than anyone.
[Huawei Ascend Mate 2] Moody66:
I guess they need to work on their communication skills. Oh well. One more thing to add to the list of things they have to improve upon if they want to be global. Lol
[Huawei Ascend Mate 2] MikeyLee:
Last I checked this was a developer forum. If something becomes available it should be shared. There is absolutely no reason to even post about L builds here if they are not going to he made available by someone. Period. That's what the Huawei forum is for.
[Huawei Ascend Mate 2] Moody66:
Not to mention the fact android is open source.... A lot of people forget that. If you use android you have to release the kernel source. Or you lose the right to use it yourself.
[Huawei Ascend Mate 2] a_ahmed:
Man I'm still on 309... so many little annoying issues but wow what a difference from the crappy 4.3 os... love 5.1...

crashes and lock screen issues... audio playback hanging/freezing... (using poweramp or the regulr music player)

Missing notifications for some programs (skype for example, some prayer program i have), etc...
[Huawei Ascend Mate 2] p51d007:
I must have been the odd duck. I never had ONE issue with 4.3...NEVER. Other than the interface of 4.3 being a little dated,

I had excellent results. Had Huawei not had the easy option of going back to 4.3 from 5.1.1, I would have stayed on 4.3

The only issue so far, is I still can't get the launcher to stick. I rarely power off/reboot, so it's no biggie.
[Huawei Ascend Mate 2] MT2-User:
Huawei just announced public release of Lollipops for MT2L03 next week.
[Huawei Ascend Mate 2] TheIgster:
https://community.gethuawei.com/friendly_user_trials/mate_2_android_l_fut/b/weblog/archive/2015/08/28/public-release-of-android-l-coming-soon
[Huawei Ascend Mate 2] Moody66:
No worries. CM is pretty good already. The only bugs were found after a day or two. New build comes out we will be rocking stock android like a champ. Wakelocks were being an issue. I am getting better battery life now than I did on factory firmware. And of course we can now use xposed and such! Amazing how fast they did it in.
[Huawei Ascend Mate 2] a_ahmed:
I'm guessing you're talking about CyanogenMod when you say CM? I've never used CM before. Is it super awesome lol.

I love the new 5.1 android from Huawei, the interface and all it's beautiful. The old 4.3 was dated and ugly and blah...
[Huawei Ascend Mate 2] Moody66:
Lol ya. Dunno who decided that ugly grey bar was a good idea..... No business trying to do a layout on a smartphone. And of course the security flaws in 4.3.
[Huawei Ascend Mate 2] pckarma112:
Same here. I tried the first release of lp. What number? Can't rem. Does not matter. Did not like it. Battery issue mostly. So back to 4.3..Everyone is different. It is a good thing..right. I am hoping in the end. We will have a stable lp and cm. Best of both worlds..yea!
[Huawei Ascend Mate 2] p51d007:
Just got the notification for 322 evening of Sept3. Wasn't there on the morning of Sept3.

Probably parsing it out a little at a time to keep the server from blowing up. :eek:
[Huawei Ascend Mate 2] dizwikedcbr:
also got the notifications, installing the update now
[Huawei Ascend Mate 2] MT2-User:
Thought there would be a newer version than B322.
[Huawei Ascend Mate 2] :
Seems the pesky file that restores the stock recovery isn't found in B322. Glad to see this.
[Huawei Ascend Mate 2] Moody66:
Yep. Well sorta. Its in the first 322.. Not the final 322. Since its a public release I guess they aren't trying to block us installing twrp. Lol just my thoughts on it.
[Huawei Ascend Mate 2] :
Makes sense. I jumped from B148 to B322 using the public release. Figured I would mention this so as to not cause any confusion with other readers.
[Huawei Ascend Mate 2] Moody66:
Interesting. So the public 322 also has the file system change capabilities as 309 then?
[Huawei Ascend Mate 2] :
Correct, the public release does not require you to have B309 installed. You can be on JellyBean and B322 will install just fine. They mention the details on their site as well.
[Huawei Ascend Mate 2] Moody66:
I will get scoots to add that to his post. So none goes through all the updates from 148. Good find man. You probably saved a lot of people a lot of time. Lol
[Huawei Ascend Mate 2] :
No worries, the following versions can be upgraded to the B322 public release without any hassles:

B126

B148

B304

B308

B309

B316

B320

B321

Anyone can get more info about it from here
[Huawei Ascend Mate 2] :
CM 12.1 from TDM has the recovery-from-boot.p file. TWRP found it and renamed it for me. Wouldn't expect to see that in the Rom. I noticed it when unpacking the boot.img so I could change the kernel cmdline to load selinux as permissive.
[Huawei Ascend Mate 2] Moody66:
That was in the NEW release of 322? Hmmmm.
[Huawei Ascend Mate 2] :
File didn't exist in stock B322. Seems to exist in CM though. Not sure what it is doing there. Haven't deleted it yet because I found it strange and figured I would explore with it lol.

---------- Post added at 03:19 AM ---------- Previous post was at 03:17 AM ----------
[Huawei Ascend Mate 2] Moody66:
Wtf. That's even more weird. What would it be there for? Am I missing something? I know I am Rusty and L is way different but that is messing with my head.

---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------

Maybe it has something to do with cm updater?
[Huawei Ascend Mate 2] :
Not sure yet. Guess I can rename it and try flashing TWRP then reboot to see what happens lol. Very odd for it to be on a custom ROM.
[Huawei Ascend Mate 2] Moody66:
Lol the unknown.... Scares me.lol
[Huawei Ascend Mate 2] ScoobSTi:
Nvm lol. Disregard.
[Huawei Ascend Mate 2] superbass311:
Anyone wana explain to me what this kernel told us that was released?
[Huawei Ascend Mate 2] Moody66:
Camera mainly I think.
[Huawei Ascend Mate 2] :
Plan to toy around with it after work today as it has brought out my curiosity, but I feel it may not be something to worry about.
[Huawei Ascend Mate 2] Moody66:
No doubt. These guys are solid. I just wanna know what its use is. Wouldn't be there if it wasn't used. Lemme know what you find. Got the three year old wide open today. So won't be any tech playtime for me till late tonight.
[Huawei Ascend Mate 2] :
Doesn't seem to do anything from what I see. Just there to be there I suppose.
[Huawei Ascend Mate 2] Moody66:
The recovery provided with CM nightlies is different than the L recovery we have been using. Any thoughts on that?
[Huawei Ascend Mate 2] :
What do you mean specifically?

Edit: [MENTION=5530607]Moody66[/MENTION], the recovery image provided by the official nightlies is the Cyanogen Recovery. Completely different from TWRP. CM does not support TWRP officially because they provide their own recovery. I cannot vouch how well it will work for this device but I suspect it will work just fine otherwise CM wouldn't provide it to be downloaded. They most likely changed up the device tree to use their recovery instead of TWRP.
[Huawei Ascend Mate 2] Moody66:
Ahh makes sense. A couple had errors while flashing with twrp. Guess that's why then.
[Huawei Ascend Mate 2] :
I don't use their recovery so I don't know if this is still an issue but in the past TWRP backups and Cyanogen backups were incompatible with one another. Meaning you couldn't mix the two.
[Huawei Ascend Mate 2] Moody66:
Ouch...
[Huawei Ascend Mate 2] :
Yup lol. That is why I just stick with TWRP. Keeps it simple.
[Huawei Ascend Mate 2] superbass311:
Can we get Xposed and root on B322?
[Huawei Ascend Mate 2] Moody66:
Root yes. Xposed will not be doable.
[Huawei Ascend Mate 2] matthewlswanson:
Stuck on B309

Hi everyone, I flashed stock rom and flashed B309 from my SD card. There used to be a link for B322 on the Huawei website but it has been removed. Does anyone know where to get it from? Have had my phone on for several days but no update...nothing from HiSuite either.
[Huawei Ascend Mate 2] Shepxda:
Check the MT2 index page
[Huawei Ascend Mate 2] gadget1999:
It seems all the links to B322 are down. Can someone help to upload a mirror if still has it? thanks in advance!
[Huawei Ascend Mate 2] Davinci50:
The link on the index page worked for me if you can't get it, reply here with an email I'll send you a link
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for exFAT and NTFS fuse drivers easy build for any platform

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for exFAT and NTFS fuse drivers easy build for any platform. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] DeepInSleep:
Trying on 4.2.1.... It does not work.:( I got "volume operation failed" after manually run "recovery-update2.sh."
[Android Q&A, Help & Troubleshooting] Lurker0:
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.

/system/etc/recovery-update2.sh test

For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
[Android Q&A, Help & Troubleshooting] DeepInSleep:
Problem solved:) I deleted this part (the script does not run with him. I do not know why)

#!/system/bin/sh

logfile0=/data/local/tmp/exfat_mount.log
#logfile=$logfile0
logfile=/dev/null

if [ -e $logfile0 ]; then
logfile=$logfile0

I also changed the mount point from the /mnt/media_rw/sdcard1 to /mnt/sdcard2. With a device=/dev/block/mmcblk1p1 some programs have not seen hardware sdcard, only storage/sdcard1 patch. Then I replaced it on device=/dev/block/vold/179:97. Now it works fine for me:D

UPDATE: crashing with multiple read/write operations. Tested in bittorrent app
[Moto E Q&A, Help & Troubleshooting] vitumen:
Is possible make a flashable zip for stock AudioEffects app to be installed in AOSP roms?

I know some people hate the stock audio effects but i think that have better audio response than other equalizers and DSP managers i've tried (like DolbyAtmos, Viper, the AOSP's AudioFX, etc), at least in stock rom.
[Nexus 7 Q&A, Help & Troubleshooting] dvjulien:
MegaWipe on Nexus 7

Hello,

I have a Nexus 7 (2012) 8GB. I did several times reset with option on system Factory reset and with recovery mode, but i'm still experiencing some slow speed in application.

I wonder if it"s possible to format completely the storage like on PC maybe.

I found on other forum for samsung galaxy Note, that some scripts exist, Megawipe and SuperWipe.

Megawipe: Use this zip to completely format your phone. It will delete everything in your phone and will bring it to bare bones. After it install any ROM for a fresh experience without any conflicts with in the frame work.It deletes the Data, Cache, System and Preload partitions of your internal memory. So Beware!

Is it possible to do same thing on Nexus 7? or maybe some scripts already exist to do same thing?

Thanks in advance

regards
[P3300, MDA Compact III ROM Development] cp_yates:
Firstly, just want to say thank you to everyone on the forums for all the work they have put in. Made two attempts to upgrade, resulting in one bricked XDA Orbit, and one brand spanking new Orbit running b&b 3.7 :-) If it wasn't for the hard work of the forum members, i'm sure it would have been two bricked paperweights!!

Secondly, is a question/request, for the Windows Live WM6 software. Micro$oft has stated that this software is being released only as a component of new WM6 devices. Has anyone seen it on a device, or does anyone have a CAB file for the software, as i'm looking to implement the push-mail service for a hotmail account.

Hope someone can help, and many thanks once again.

Regards
[P3300, MDA Compact III ROM Development] imstill@g:
:) Its already installed on the b&b 3.7 rom. Hows that for easy install?? LOL
[G2 Q&A, Help & Troubleshooting] RomFor:
Strange Knock On

Hi, dear friends!!!

I have ls980 and a strange problem on the firmware based on aosp 5.1. The fact that the phone wakes up only after 5 tap on the screen, rather than after two tap as usually.

On stock and Cloudy all work.

Please tell me how to make the phone woke up after two tap?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Okay everyone, here's what happened (on a Droid Turbo XT1254):

I was running a 5.1 rooted image that I manually debloated. This image was running fine for months. Then suddenly the phone freezes and I have to force power it off. When I try to reboot it, I would see the boot animation and then the screen would go black. I restored 4.4.4 using rootjunky's method and rebooted, and it did boot after an absurd amount of time (it seemed like 10 minutes, but I was upset so it was probably more like 5). After it booted, I saw a message that it wanted to complete the uninstall of the motorola sensor firmware. I said okay, and it rebooted again, this time in a normal amount of time. Then everything seemed fine.

So I reflashed all the appropriate 5.1 images and the rooted 5.1 system image. At this point, I was suspecting that the recent Moto Actions update caused the motorola sensor update that destroyed my phone, but I stupidly decided to let it update again, figuring that I could just repeat the method I used before if it broke it again. It did break it again, and I restored 4.4.4 again, and I'm not seeing the uninstall message, and my phone continues to freeze until I have to force power it down. I can still get into recovery and bootloader modes just fine.

Does anyone know how to force uninstall the motorola sensor firmware? Why would a factory reset and/or total reflash of the stock 4.4.4 images not fix this problem? What partition is this firmware stored on?

Also, why is this only happening to me and not all of the other rooted Turbo users?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] my2cents:
YOU are the man! I tried all the basic things to get mine going, no luck. I flashed 4.4.4 so many times. I factory reset so many times. Nothing. It boots every once in a while, but as soon as the screen goes turns off, back to square one. :mad:

I'm glad that Motorola is replacing them. I sent mine off today. I didn't realize the 1/1 thing... If they complain, I am going to say that must have happened when I tried flashing it to 4.4.4 or something. I don't think it will be an issue though. I have an old Droid Ultra, that i put my SIM card in and it is working, so I can wait for the new turbo. Fingers crossed on 4.4.4 coming with it. I guess we will need to pay for Mofo again...

Thanks for logging this issue.

Also, I used the chop, chop feature as soon as it became available with the moto actions update. I wonder if most people aren't using it and as more people do, if this gets worse?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Thanks, but I'm not the man yet. The phone is still broken. I don't think it's the chop action specifically that's broken, I think it's everything that Moto does because it all uses different sensors. Why does the phone not wake up when it goes to sleep? Because it's trying to do the Moto Display thing, but it can't. Why is Moto Camera constantly crashing? Because it wants to figure out if you're doing the twisty thing to open it or not, but it can't. Why does the phone take a million years to boot? Because the system is trying to get the status of these sensors, but it can't, and it tries really hard before it gives up. This is all speculation, but it's my best guess.

I'm in the process of flashing a rooted 4.4.4 image minus the MSS app. I found out that you can install an older MSS app from the play store. I'll install that, reboot and see what happens. If nothing, I'll extract that apk, move it to my computer, insert it into the system image, and try again. Again, not optimistic, but I'm out of ideas.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Nothing has worked so far, as expected, but I might have had a breakthrough. In a why-didn't-I-think-of-this-sooner moment, I decided to poke around the MSS apk to see if it had the firmware files in it, and sure enough, it does! Now I finally know what I need to look for! More news to follow after my phone eventually boots.

Other less important update: I booted the phone in BP Tools mode and ran the CQA Test app. Every single diagnostic test in the "sensors" section of the app causes the app to crash. Go figure.

EDIT: The boot is taking too long and I need sleep. I discovered that the firmware files are located within system, so flashing a new system image would have replaced them, which is disheartening. I'll try a few more things tomorrow, but that will be the last day since my replacement should be here on Wednesday.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
FIXED! FIXED FIXED FIXED FIXED!!!!

This is what I did:

The firmware files located on the system image each have a corresponding text file that contains only a number, which is supposed to be the version of the firmware. I changed this number to one that was lower than the files contained within the MSS apk that I moved to system/priv-app in linux thinking that I could trick it into performing a firmware update operation. By the way, the MSS apk I'm talking about was one that came from the google play store, and the image I'm talking about is the rooted 4.4.4 image that you can get on rootjunky's website. Then I factory reset, wiped cache, rebooted and went to sleep. This morning, I setup my google account and opened Moto. I only tried the camera motion, which didn't work. I then powered it off and powered it back on, which happened ALMOST INSTANTLY!!!! Then everything was working! Display works, voice works and the twisty camera thing worked as soon as I updated the camera app in google play. I restarted the phone in BP Tools mode, which also happened ALMOST INSTANTLY, and started the CQA test. All sensor diagnostics now work!!!! YESSS!!!!!

The one side effect is that every time I boot now, I get a single "Motorola Sensor Services is not responding" message that I can close. But if my theory is correct, the problem should now be permanently solved (until I do whatever broke it in the first place again), so all you would have to do to fix that is flash the image of your choice.

I'm uploading the image to Mega now in case it helps anyone. I might play with it some more tonight just to see if I can break it again. If I can, that means there's some sort of incompatibility somewhere. If not, that means it probably was some weird fluke that the three of us experienced.

Cheers everyone! There will be celebration tonight!

UPDATE: I just did a factory reset, and it did it in a normal amount of time!! And the sensors still work!!!!

UPDATE2: Here's the link to the unbork image: https://mega.nz/#!ixZEzJDS!DUT-xzZAU2VuqQwfioA3NiOy-oIVPE_EIcMBIwCPwIo. To use it, first restore 4.4.4 update 1 with RSDlite, factory reset, wipe cache and then flash it with mofo. After the first boot, which will still take a really long time, you might need to leave it alone for a while to allow whatever it did to fix itself to happen. If you can get the wave over the screen thing and the camera twisty thing to work, you're probably good to go. I'm not sure if it matters, but I did all of this without a SIM card in the phone (because it's in my faithful old MDK bootloader Galaxy S4).
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] my2cents:
That's great news. Unfortunately, I already sent my phone off and I had took the official 5.1, so I would not have been able to test it for you anyway... Your dedication is admiring though! Nice work! :good:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Annnnd I got home and turned it on and now it's taking forever to boot again. Uhhhhggggg.

EDIT: False alarm. I forgot that I factory reset it before I left for work, so of course it's going to take a little bit more time. I'm pretty sure everything is still good.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
So I flashed a rooted, otherwise stock 5.1 image, and the problem returned pretty much as soon as I was done with the initial setup. No Google Play updates were necessary to cause the problem. This is so weird. Oh well. I think I'm going to leave it at that. Hopefully my replacement won't have this issue.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Epilogue:

I used the Verizon Upgrade Assistant to upgrade the broken phone to official 5.1. The bootloader still says modified as the system status. Using the repair function did not change this. Oh well. Who cares. I've flashed my debloated 5.1 image to the new phone, updated all apps and everything is working perfectly. I'll miss you, old Turbo. You were a loyal friend. Sorry I couldn't fix you.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] my2cents:
I after waiting forever for mine to boot to 4.4.4, I took the official 5.1 OTA and it changed from modified to official on the bootloader screen for me.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] andrescarre87:
would you check if there's a solution for xt1225??

I seem to have the same problem as you did.... and i'm clearly not as experienced in using adb and fastboot and editing firmwares....

i can use either the chilean stock 4.4 rom or the mexican one... would you take a look in the files you say are the source of the problem??

it seems that in Chile we don't get a new replacement phone as easy as in other countries :(

in this threads are the images of my phone

http://xdaforums.com/droid-turbo/development/quark-stock-firmware-moto-maxx-droid-t3063470

pleaaase!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
I'll take a stab at it. I'll send it your way when I'm done.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
So I had a little time to work on it, and for some reason I'm having trouble merging the chilean system img sparsechunks into an img that I can work with. I'm not sure why this is, but I plan on working on it more tonight. I'll try the mexican image too. If I were you, though, I'd keep trying to get a replacement from either Motorola or your cell phone provider. When/if I can get an image up and running, you'll need to unlock your bootloader in order to flash it. I'm not sure how to do this on an XT1225, so you'll need to figure that out. Keep in mind that unlocking your bootloader will probably ruin any sort of warranty that you might have, so only do that if you have completely ruled out the possibility of getting a warranty replacement.

EDIT: I just realized what I was doing wrong with the sparsechunks, so hopefully I'll be able to accomplish more tonight.