yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] Iguanadon:
As far as I can tell. There is a partition size problem.

Sent from my MT2L03
[Huawei Ascend Mate 2] ArkAngel06:
That's what I am using, I haven't flashed the new one yet. Screenshots in a minute.
[Huawei Ascend Mate 2] :
Could be. Recovery log would give insight if he sends it my way.
[Huawei Ascend Mate 2] Iguanadon:
One of the Walmart versions is 8gb internal vs 16gb. Not sure about CC or Wind

Sent from my MT2L03
[Huawei Ascend Mate 2] arampapaz:
I am now wondering if it has to do with the stock launcher. I installed Nova on day one, and never used the stock launcher. It might be worth checking out.
[Huawei Ascend Mate 2] chriss29:
I have purchased Nova long ago when it was on sale, but have never installed it on the HAM2. Might give it a shot if the Lollipop update doesn't arrive soon. thanks for the suggestion. I'm now going back and forth between my two phones, this one and the Oneplus One.
[Huawei Ascend Mate 2] rdbud:
I use Nova and still experience all the bugs I listed, minus the ones specific to the stock launcher.
[Huawei Ascend Mate 2] arampapaz:
I think it might help, plus there are a lot of options in Nova. One that I love, and use on all my phones, is that you can swipe down on the home screen to open notifications. It is great for larger screens using one hand. Also double tap to lock the screen, I use the gesture to greenify and lock, but there are other screen locks you can use as well.
[Huawei Ascend Mate 2] :
As long as you have the stock recovery to flash back over top of TWRP then you will be fine.

The only time an OTA will fail is if you try to accept the OTA with TWRP or any other custom recovery still installed or if you modified the system which messes up their checksums. OTA comes with patch files and before those patches are applied the system is checked for the ACTUAL file or executable and if the checksum doesn't match or isn't found then the OTA will fail. To resolve this issue should it become an issue is to make sure you install TWRP and before making any changes to your device other than installing TWRP you make a full backup. So if need be, you can restore using your TWRP backup, then flash back the stock recovery, then finally accepting the OTA.

If the TWRP backup was made after changes to the system was conducted then that individual will need to acquire a clean TWRP backup from another member.
[Huawei Ascend Mate 2] ScoobSTi:
You ever get some weird message saying that Nova has caused a serious crash and the phone suggests you uninstall it? I've never seen anything like that on any other phone.
[Huawei Ascend Mate 2] rdbud:
Haven't seen that one. And here I thought I had the buggiest HAM2
[Huawei Ascend Mate 2] chriss29:
Thanks for the thorough explanation, I'll do a bit more reading on the subject and might go ahead with it.
[Huawei Ascend Mate 2] oncouch1:
I have only experienced random reboots, and that is with aftermarket launchers as i rooted and modified immediately. I am using Z now and seams stable. I did do various build.prop mods found in other Huawei model forums and they seemed to help but quite possibly the plasibo effect.
[Huawei Ascend Mate 2] :
The one that was given to me currently has no issues. Haven't experienced anything negative yet and it is used frequently by the wife and daughter lol. Completely stock, no root, no twrp, etc etc.
[Huawei Ascend Mate 2] :
You will be fine. Grab TWRP and boot it vice flashing.

fastboot boot twrp.img

That will load up and boot TWRP without overwriting your actual stock recovery image. Now go ahead and make a full backup of your system, data, recovery and so forth. Once it is done you can reboot and your stock recovery will still be intact.

If you wish to overwrite your stock recovery after you have done the following above then the below will do the job for you;

fastboot flash recovery twrp.img

TWRP will root your device also so there really is no need to use third party software such as kingo for example. When you select to reboot while in TWRP it will let you know your system isn't rooted and ask if you would like to. Simply say yes and when it is done it will reboot your device. Once the device is booted up just go to the play store and install/update SuperSU. Open up SuperSU and update the su binary which the app will prompt you to do.

Should you make modifications to your device and decide to return to stock with stock recovery just boot up TWRP and select to restore using your backup. If you booted up vice flashing and made your backup then you successfully backed up your stock recovery as well since booting TWRP the first time did not overwrite your recovery partition. Cheers :)

---------- Post added at 09:10 PM ---------- Previous post was at 09:02 PM ----------

Also, everybody needs to know that once Android L arrives I would HIGHLY recommend making a complete new backup before modifying your device. If you are on Lollipop and restore using a backup made from 4.3 then their could be issues due to differences in firmwares from each OS. Such issues as static phone calls and possibly wonky data/wifi signal.
[Huawei Ascend Mate 2] p51d007:
Hey, I have thick skin...nope, not a shill, not a spokesperson for Huawei. You can see from my sig, I've had a lot of phones over the years.

I use to tinker with phones, flashing this rom or that rom, but it isn't worth it to me to screw around with them, I just want them to work, and

work properly. My previous phone, Galaxy Note (international one without LTE), ran me for almost 3 years before the Mate2. Once 4.1.2

was officially released, for me, it was flat out stable. Might be because I left it alone. Hey, it's your device, you do with it as you please.

I've been involved with electronics for almost 42 years since I was 12 years old. (yes, I'm that old). As an amateur radio operator, I screw

around with radios, antennas, and my profession, I work on production size reprographics, digital signage, computer networks and the like,

so I do know a little bit about electronics.

I stumbled onto the Mate2, believe it or not, on the OnePlus One user forum, last year while waiting for the invite, thought for 300 bucks

on Amazon, I'd give it a try and send it back if I didn't like it. I liked it so much, when the One came, I bought it, and got rid of it because

of the Mate2 battery life and huge screen.

I'm sorry your Mate2 has been "buggy", perhaps if you would send it back under warranty, they would replace it. Perhaps you have flashed it

with a damaged/buggy rom or something else that might be causing the issue, or perhaps I was the one in a million that got a perfect copy of it?

Anyway, I hope you have better luck with whatever you decide to do with your mate2.
[Huawei Ascend Mate 2] bornagainpenguin:
Is there a dedicated thread for all these bugs? I never saw any of these issues mentioned before this post and that has me concerned.
[Huawei Ascend Mate 2] :
I have not experienced bugs on this device. Personally, I think some of these guys who are experiencing bugs either popped up out of nowhere to spam or they began modifying their device which began to display issues and they can't put the two together. A lot of these guys use xposed modules - which is known for causing bugs to start appearing. My bet is the bugs they are experiencing are from them making poor decisions when modifying their device.

I believe one or two may actually be experiencing bugs who have not tampered with their device. To those people, they should send it back for warranty and get another one instead of complaining. Most probably a bad batch that slipped by.
[Huawei Ascend Mate 2] ScoobSTi:
I fall in here, but I'm honestly too lazy to go and fix it. :p I also think I have a largely decreased battery life and quite a lot of lag/stuttering. Again, too lazy to reset.

Maybe once Huawei's L or CM11/12 arrive, I'll be more willing to start fresh.
[Huawei Ascend Mate 2] p51d007:
Yeah, over the 8 years I've been hanging out on XDA (since the HTC tilt), not all, but A LOT of issues I see pop up, are related to flashing.

Sometimes, people are usually better off leaving what they do not understand, alone.

I have some of the same issues with the field techs I supervise. Sometimes they get in a hurry, don't read or understand the directions and

it ends up causing issues down the road. I've even had some techs, update a main rom in a device, but not also update the rom in an

accessory, they "think" the machine runs fine, and then a few days later the customer will call back with an abnormal issue with an

accessory, only when doing a certain task. Then come to find out the accessory rom wasn't updated, along with a main rom.

Some of my machines that I service, the hard drives have 8 partitions, there are multiple roms, and changing a board requires dumping

the backup data from one rom to the new board, and if you attempt to replace two boards at once, it is classified as a security issue,

since these have hard drives, and the security software will do an automatic data dump, all because someone "thought" they new the

steps, or, the procedure they did on the previous model, is the same as the new model.

Not sure what the issue is, but, it appears that if you have a mate2 out of the box with issues, you should send it back, and, mostly that

if you leave it alone, it runs fine. Mine sure does!
[Huawei Ascend Mate 2] :
[MENTION=647747]p51d007[/MENTION], I'm not a tech by profession just only as a hobby but I can definitely relate with you lol.
[Huawei Ascend Mate 2] MikeyLee:
I'm not sure what version of this device you have but mine is not and never has been buggy.
[Huawei Ascend Mate 2] rdbud:
I know that it seems I popped up out of nowhere, but it's mainly because I don't like the UI of the phone and was hoping for CM or stock android. I figured this was the place to keep tabs on it. I'm not spamming, so I apologize if it seems like that. The device is running stock - I have not modified it in any way. I put Nova Launcher on it, but I haven't rooted it or flashed anything. After a little research, the notifications bar bug I mentioned may be a bug for Nova and not the device.

Are you using the stock UI? The bugs I referred to were actually reported in a few reviews of the phone. I knew about them before I even bought it. I'm not the only person who experienced the audio issue. As for the other things, are those legitimate warranty claims? The phone works. It's not unusable, it just has a few minor annoyances that other people probably don't notice. Are they really going to replace the phone for that?
[Huawei Ascend Mate 2] Moody66:
Again. Remember where we are posting. This forum and XDA itself is here for the purpose of Roms...Mods.. Etc. That is why people come here and do what they do. Most expect a few bugs here and there. That is the purpose for rooting and such to start with. In fact there are more phones running the newest version of android due to developers than there are unmodified factory phones running it. By a large margin. Its like posting on a DIY forum why its better to just buy or pay for someone else do to it for you. Food for thought.
[Huawei Ascend Mate 2] :
Ah, well that may be your problem then lol. Use my build to restore with that backup.

---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------

Useful information bro

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

Check it out guys. If grabbing the 5.1 TWRP backup and you are still on 4.3 then you must use my build when you restore with that 5.1 backup.

Likewise, if you are on 5.1 and wish to restore using a backup made from 4.3 then you must use the other TWRP build and not mine.

Make sense to everyone? I hope so lol
[Huawei Ascend Mate 2] ArkAngel06:
I'm aware, but it should work in theory. It's the same phone.

Everyday that passes I just wish I had paid the extra $30 and got the unlocked version. But I broke my last phone (OnePlus One)and needed a new one that day and Sears had them in store, so that's what I did.

Now I desperately want to leave Jellybean in the past where it belongs.
[Huawei Ascend Mate 2] medwatt:
Should we restore the CUST backup made from L 5.1 or the that which we have currently on our phones ? Wasn't it the case that the CUST folder contained information such as the IMEI ? For example, when I was flash the stock v148 ROM, I restored my own copy of the CUST folder which was in fact not present in the zip file provided by xordos.
[Huawei Ascend Mate 2] :
If the leaked Rom takes no part in updating the Cust partiton then I would leave it alone.

---------- Post added at 11:31 PM ---------- Previous post was at 11:31 PM ----------

Hopping off. Good luck everyone :)
[Huawei Ascend Mate 2] mark manning:
Hey all,

Sorry for dropping in but I just want to remind everyone that the sharing of closed beta roms, apps, or whatever is against XDA rules and will be removed.

-XDA Staff
[Huawei Ascend Mate 2] medwatt:
Have you started uploading ?
[Huawei Ascend Mate 2] ArkAngel06:
He did make one with the cust partition. Thats all I have always used.

Regardless, that's not the problem we are having now. This is:
[Huawei Ascend Mate 2] medwatt:
Why didn't you restore everything but the CUST partition ? BTW, where is the new link of the backup file that has the CUST backup ?
[Huawei Ascend Mate 2] ArkAngel06:
I think it's done with now, mod said any links will be removed. Guess it's back to waiting. :(

---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------

Errors.
[Huawei Ascend Mate 2] :
Looks like this Rom is limited to only one Mate2 until the official release guys. Seems TWRP isn't enough at the moment for you other owners.
[Huawei Ascend Mate 2] TheGeekRedneck:
OK after some research I'm concerned that the 'cust' partition may in fact contain the IMEI and serial number of the phone, so until someone can convince me otherwise I'm not going to include that. I've read several accounts of people accidentally wiping the cust partition on Huawei devices and trashing their IMEI, or worse flashing someone else's backup of that partition and cloning their IMEI.

I restored the original link in my earlier post for those who want to putter around with it and try and get it to work on their Consumer Cellular phones.

I've also now restored this backup on a SECOND HAM2 (MT2-L03) that was running the original Android 4.3 ROM and had no issues whatsoever. (Again, I used SHM's special build of TWRP mentioned earlier in this thread).
[Huawei Ascend Mate 2] :
[MENTION=2667067]ArkAngel06[/MENTION], I need to look at the recovery log. Do it again, then save the log to your device and send it my way please. May be possible the partition layouts are different. The recovery log should give me some insight.

---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------

As of right now TWRP for Lollipop should only be used by Mate2 owners not pertaining to CC, Wal-Mart, and any other unnatural marketing brand until further studies on them has been looked into. Seems they may be different from the actual MT2-L03.

---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------

Good info and glad to here it is working like it's suppose to. Thanks for your input.
[Huawei Ascend Mate 2] ArkAngel06:
Fair enough. xordos' flashable version had the cust partition, and I can't remember if his TWRP version did or not. Even if it did, it's possible he knows what he's doing and removed the necessary info.

I know when backing up and restoring, I backup my own cust and wipe it before restoring and haven't had any issues, but again, that's all mine, and not anyone elses.
[Huawei Ascend Mate 2] p51d007:
First half of 2015

It's getting late where I live, and my mind is drifting...but, ponder this wacky idea!

We've all heard, Huawei say that the update, will come "in the first half of 2015". Now, most of us are ASSUMING that means before the 1st of July 2015. Here's where it gets strange. Huawei, granted for me anyway, sells the device direct in the USA, shipping from California.

BUT, the company, is based in CHINA. Perhaps the "first half of 2015" is going by the CHINESE calendar, not the one most other people go by.

IF that wacky idea that popped into my head pans out, then since the Chinese new year, for 2015, was February 19th, then the update still has

up to 2 more months, before it would "technically" be outside the "first half of 2015".

I'm going to bed now...

:silly::silly::silly::silly::p;):cyclops::eek:
[Huawei Ascend Mate 2] Kostyan_nsk:
I assure you, cust partition doesn't contain any personal info. It's a part of firmware that flashes with every update. System will boot without this partition but won't work some device specific functions, like gestures for example.

So if you want to make full system backup, you should include cust partition in this backup.
[Huawei Ascend Mate 2] Kostyan_nsk:
I took a look at your video and I wonder that Huawei supplied vendor update.

Could you give that small 14.8MB UPDATE.APP to take a look what's inside there, seems like there's an original way to convert device from CC to OEM version using stock recovery. If I'm not mistaking presuming contents of this file...
[Huawei Ascend Mate 2] xordos:
we need more work to do to flash vanilla 5.1 to CC using twrp instead of dload method.

Vanilla B148 to B308 upgrade(dload method) has resized several partitions, most significant one is /system, from 1GB to 1.8GB, and 5.1 system has used 1.5G, so a simple system dump cannot restore to CC old 1.0G system partition.

Two ways I can think of:

a). trim L system to under 1.0gb

b). we need some twrp script to resize partition

b) is the way to go, but it is risky.

OK, back to bed

ps, [MENTION=6367467]SHM[/MENTION], maybe you can help us for those resizing script, or let us know how risky it is.

Below is vanilla mate2 old and new partition map, and need someone has CC can share their current map.

B148 partition info /data/tmp/parted /dev/block/mmcblk0

Number Start End Size File system Name Flags

1 17408B 541695B 524288B sbl1

2 541696B 574463B 32768B sdi

3 4194304B 4227071B 32768B DDR

4 8388608B 8900607B 512000B rpm

5 8900608B 9412607B 512000B tz

6 9412608B 15138815B 5726208B aboot

7 15138816B 16187391B 1048576B pad

8 16187392B 83296255B 67108864B oeminfo

9 83296256B 87490559B 4194304B modemst1

10 87490560B 91684863B 4194304B modemst2

11 92274688B 192937983B 100663296B fat16 modem

12 192937984B 197132287B 4194304B fsg

13 197132288B 197133311B 1024B fsc

14 197133312B 197141503B 8192B ssd

15 197141504B 230695935B 33554432B ext4 log

16 234881024B 301989887B 67108864B bkbootup

17 301989888B 310378495B 8388608B ext4 persist

18 310378496B 322961407B 12582912B boot

19 322961408B 339738623B 16777216B recovery

20 339738624B 608174079B 268435456B ext4 cust

21 608174080B 809500671B 201326592B ext4 cache

22 809500672B 813694975B 4194304B misc

23 813694976B 1887436799B 1073741824B ext4 system

24 1887436800B 8329887743B 6442450944B ext4 userdata

25 8329887744B 15634251263B 7304363520B fat32 grow

B308 partition map

Number Start End Size File system Name Flags

1 17408B 541695B 524288B sbl1

2 541696B 574463B 32768B sdi

3 4194304B 4227071B 32768B DDR

4 8388608B 8900607B 512000B rpm

5 8900608B 9412607B 512000B tz

6 9412608B 15138815B 5726208B aboot

7 15138816B 16187391B 1048576B pad

8 16187392B 83296255B 67108864B oeminfo

9 83296256B 87490559B 4194304B modemst1

10 87490560B 91684863B 4194304B modemst2

11 92274688B 192937983B 100663296B fat16 modem

12 192937984B 197132287B 4194304B fsg

13 197132288B 197133311B 1024B fsc

14 197133312B 197141503B 8192B ssd

15 197141504B 264250367B 67108864B ext4 log

16 268435456B 335544319B 67108864B bkbootup

17 335544320B 343932927B 8388608B ext4 persist

18 343932928B 411041791B 67108864B boot

19 411041792B 478150655B 67108864B recovery

20 478150656B 746586111B 268435456B ext4 cust

21 746586112B 947912703B 201326592B ext4 cache

22 947912704B 952107007B 4194304B misc

23 952107008B 2831155199B 1879048192B ext4 system

24 2831155200B 15634251263B 12803096064B ext4 userdata

and attached is the utility to dump the partition map

# /data/tmp/parted /dev/block/mmcblk0

unit B

print
[Huawei Ascend Mate 2] medwatt:
This is what I got from my CC HAM2:

Model: MMC MAG2GC (sd/mmc)

Disk /dev/block/mmcblk0: 15634268160B

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 17408B 541695B 524288B sbl1

2 541696B 574463B 32768B sdi

3 4194304B 4227071B 32768B DDR

4 8388608B 8900607B 512000B rpm

5 8900608B 9412607B 512000B tz

6 9412608B 15138815B 5726208B aboot

7 15138816B 16187391B 1048576B pad

8 16187392B 83296255B 67108864B oeminfo

9 83296256B 87490559B 4194304B modemst1

10 87490560B 91684863B 4194304B modemst2

11 92274688B 192937983B 100663296B fat16 modem

12 192937984B 197132287B 4194304B fsg

13 197132288B 197133311B 1024B fsc

14 197133312B 197141503B 8192B ssd

15 197141504B 230695935B 33554432B ext4 log

16 234881024B 301989887B 67108864B bkbootup

17 301989888B 310378495B 8388608B ext4 persist

18 310378496B 322961407B 12582912B boot

19 322961408B 339738623B 16777216B recovery

20 339738624B 608174079B 268435456B ext4 cust

21 608174080B 809500671B 201326592B ext4 cache

22 809500672B 813694975B 4194304B misc

23 813694976B 1887436799B 1073741824B ext4 system

24 1887436800B 8329887743B 6442450944B ext4 userdata

25 8329887744B 15634251263B 7304363520B fat32 grow

It is identical to your b148.
[Huawei Ascend Mate 2] ArkAngel06:
I don't have much experience here, but is there any way to change partition sizes? I mean obviously not right now, but with the proper TWRP or something?
[Huawei Ascend Mate 2] :
Still reviewing the log you sent me. Errors all over the place. A lot has to do with your device running out of space. So obviously there is a size difference.

As for whether or not it is possible to resize the partitions, yes, it is possible, and yes, it is risky, but to pull it off requires someone who really knows what they are doing. I could easily write a script for something like this since I have done this stuff many of times on my own devices. However, I will not for this device because when you write scripts you must be able to test and debug them to insure all errors are fixed prior to releasing and I am not capable of doing this on my end since the bootloader is still locked. This is one test I will not rely on other members.
[Huawei Ascend Mate 2] :
I included the device tree used to make the TWRP build.

Click here for post #303 and see attachments
[Huawei Ascend Mate 2] xordos:
understand, and exactly my feeling when I build the flashable zip last time, some early booting stage image (like aboot) is in huawei B148 update, but I don't want to include it because it is risky, it is one way trip that if that fails just 1 bit, it cannot even boot into twrp.
[Huawei Ascend Mate 2] :
OK guys......a fellow Moderator just visited and removed links to this beta software, and then it`s posted again. Not cool!

Doesn't matter if "anyone" can sign up for the beta, it still should not be distributed here until it's released to the public.

Anymore links to the beta here and thread may be closed, as well as any new ones that pop up. And members posting links will get special attention as well. ;)

Please respect XDA's wishes on this, as anything that can get the site in trouble with Manufacturers or anyone else is not permitted.

No more please,

Darth

Forum Moderator
[Huawei Ascend Mate 2] :
Read this: https://github.com/omnirom/android_bootable_recovery/commit/a2719156c236c8be02403ef028490f001d393d8e

Also here: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html

---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------

Currently working on compiling a static binary of Perl for Android so I will be busy for a bit guys.
[Huawei Ascend Mate 2] ArkAngel06:
Both pages giving a 404 for me.
[Huawei Ascend Mate 2] :
Use a different browser
[Huawei Ascend Mate 2] ArkAngel06:
Tried chrome and firefox, but if its just me, don't worry about it.