Everything Huawei Y550 - Root/CWM/TWRP

Search This thread

szty0pa

Member
Sep 18, 2015
46
24
I think the QPST-tool may be helpful, see these instructions and downloads.

Question is: which parts (partitions) from the working device would I need to flash for 'Phone image' and 'Boot image'?

update 1 - I'm going to try connecting the device to a virtual Windows and run the QPST tools. The drivers are included, and I've got a BOOT.img and SYSTEM.img from the Y550's original firmware. To be continued :).

update 2 - I can 'see' the phone as 'Phone in Download Mode', but that's all. The tool insists on a valid .hex file format for anything to be flashed. If I try to rename Huawei's SYSTEM.img to SYSTEM.img.hex, it says it isn't a valid HEX-file. Which is true, of course. Do you have any insights?

Kind regards,
FWieP
Sorry i was away from home today.
So first things first: checking out the partition map of Y550 i think there is no calibration data stored so it should be safe to overwrite all of the eMMC. (If you issue "ls -la /dev/block/platform/XYZ/by-name/" you should see the names of the partition. More on that here.)
I found this guide that might come in handy as it uses a dd-saved image as you have. (I am not sure about the .hex format image the other tool wants...)
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
If you issue "ls -la /dev/block/platform/XYZ/by-name/" you should see the names of the partition.
This is the partition info from the rooted working Y550:
Code:
y550:/ # ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name/ | cut -d ' ' -f 9,10,11
 
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p7
boot -> /dev/block/mmcblk0p18
cache -> /dev/block/mmcblk0p21
cust -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p14
fsg -> /dev/block/mmcblk0p13
hyp -> /dev/block/mmcblk0p2
log -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p12
modemst1 -> /dev/block/mmcblk0p10
modemst2 -> /dev/block/mmcblk0p11
oeminfo -> /dev/block/mmcblk0p9
pad -> /dev/block/mmcblk0p8
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p19
rpm -> /dev/block/mmcblk0p5
sbl1 -> /dev/block/mmcblk0p1
sec -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p15
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p6
userdata -> /dev/block/mmcblk0p24
I hope I'm not taking too much of your time, but I still would not know what to do next :(.

Kind regards,
FWieP
 

szty0pa

Member
Sep 18, 2015
46
24
This is the partition info from the rooted working Y550:
Code:
y550:/ # ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name/ | cut -d ' ' -f 9,10,11

DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p7
boot -> /dev/block/mmcblk0p18
cache -> /dev/block/mmcblk0p21
cust -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p14
fsg -> /dev/block/mmcblk0p13
hyp -> /dev/block/mmcblk0p2
log -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p12
modemst1 -> /dev/block/mmcblk0p10
modemst2 -> /dev/block/mmcblk0p11
oeminfo -> /dev/block/mmcblk0p9
pad -> /dev/block/mmcblk0p8
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p19
rpm -> /dev/block/mmcblk0p5
sbl1 -> /dev/block/mmcblk0p1
sec -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p15
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p6
userdata -> /dev/block/mmcblk0p24
It looks the same as mine. :) I don't know what a few of them stores exactly, the linked thread did not mention them either. On some older routers there used to be a partition called 'art' which were believed to be storing calibration data. I think on the Y550 there is no such thing, or if there is it might be on 'oeminfo' or 'persist'? However I believe you should only overwrite 'sbl' (second-stage bootloader) at first try, which is the first 0.5MB of the eMMC.

I hope I'm not taking too much of your time, but I still would not know what to do next :(.

Kind regards,
FWieP
No, of course you are not taking too much of my time! :)
I am trying to find out how it is supposed to work as well. I suspect .hex, .mbn and other proprietary image formats should be _mostly_ interchangable. So if you back up the partitions of your working phone the same way you did with the whole eMMC only issuing 'dd' on '/dev/block/mmcblk0pX' and no 'count' (so that it will extract the whole partition as it is) you will be able to overwrite partitions one-by-one. (Start from '/dev/block/mmcblk0p1' (sbl) - I suspect this should already make you able to boot at least to TWRP.)
Sadly I don't know the Qualcomm tools, but there is a load of (better or worse) articles about them - one I just found for example -, that I can't help you with sadly as I don't have a dead phone at hand at the moment.
Hope this helps! I'll try to assist if not anyway.
Best of luck!
 

trizoide

Member
May 6, 2015
13
2
Hi, I have a big problem, my wifi does not reach much signal, it barely detects only 2 networks and when it connects it disappears. No matter how much I update the room, they still have the same problem, I used to solve it with a wifi flix but the file has disappeared
 

Blank tape

Member
Oct 5, 2014
23
8
Hi, I have a big problem, my wifi does not reach much signal, it barely detects only 2 networks and when it connects it disappears. No matter how much I update the room, they still have the same problem, I used to solve it with a wifi flix but the file has disappeared
I hate to say it. but my "fix" was to go back to a stock ROM. However, since KitKat 4.4.4 is now too ancient to receive updates to Google apps as well as below the minimum required by many other apps., I've decided to bite the bullet and just live with all the drawbacks though admittedly there are some nice newer things. Still, I'll miss the stock ROM. Dumb questions from me follow.
 
Last edited:

Blank tape

Member
Oct 5, 2014
23
8
I need to upgrade the ROM on my phone to at least Android 6. Retaining the same level of WiFi and battery performance would be nice but one can't have everything! I also prefer some of things the stock ROM does. I like local calendar entries for example.

Anyway with that said, is LOS 14.1 the best choice? Or really the only choice because it is the only one getting security updates. Mind you I never worried about that with the stock ROM. I still haven't applied the last update.

Does anyone have advice of how to safely repartition the device to maximise useable storage? I'm thinking about using the Open GApps pico package in contrast to fwiep's guide which recommends micro. It seems to me there is little need to bake Google apps into the ROM when they are going to be replaced anyway and probably be available in the Play Store before I get around to updating Gapps.

Could someone with pico Gapps installed tell me how space is occupied in their system partition?
Can the cust partition be removed altogether? Can any other partitions be shrunk or removed?

Is fdisk under twrp sufficient to rewrite the partition table?

I'm also wondering whether I should go with adoptable storage this time or use Link2SD. The latter seems safer and offers more control but the former seems easier.

Any suggestions welcome.
 

szty0pa

Member
Sep 18, 2015
46
24
I need to upgrade the ROM on my phone to at least Android 6. Retaining the same level of WiFi and battery performance would be nice but one can't have everything! I also prefer some of things the stock ROM does. I like local calendar entries for example.
I haven't noticed any decrease in performance between stock and current LineageOS. There are even local calendar entries - though you have to decline linking your google account every time you start the integrated calendar app... For example this could solve the issue.

Anyway with that said, is LOS 14.1 the best choice? Or really the only choice because it is the only one getting security updates. Mind you I never worried about that with the stock ROM. I still haven't applied the last update.
As far as I know @fwiep's builds are the best option for this specific phone. (Still as Qualcomm's code is not updated any more for the Y550 there are a couple of known unfixed RCEs, so one should not expect really tight security! But is there such a thing anyway? Especially on Android?)

Does anyone have advice of how to safely repartition the device to maximise useable storage? I'm thinking about using the Open GApps pico package in contrast to fwiep's guide which recommends micro. It seems to me there is little need to bake Google apps into the ROM when they are going to be replaced anyway and probably be available in the Play Store before I get around to updating Gapps.
I did it in the past as well: delete /system (/dev/block/mmcblk0p23) and /userdata (/dev/block/mmcblk0p24), and recreate them to the desired size. (As far as I know you can delete /cust too but then you probably have to move /cache and /misc as they are allocated inbetween so it might now worth the effort...)
The stock allocation of /system is really crazy because of the included bloatware but you should also think about how many apps you need on the phone and how often you plan to upgrade the OS. When you upgrade a repartitioned phone you can't use an image straight away, you have to resize it to fit your configuration which is a real PITA. I think I have done it 10-20 times (monthly updates) and then I went back to the stock layout. /userdata is (was) mostly enough for all the apps I was using (OsmAnd was tricky though, but that is a monster) while pictures, documents (and maps) were on an SD-card.
Gapps pico should be enough, but if you only plan to use push notifications and the location service, MicroG is a better choice. There are alternative PlayStore implementations, though they don't have access to your already paid-for content of course...

Is fdisk under twrp sufficient to rewrite the partition table?
Yes.

I'm also wondering whether I should go with adoptable storage this time or use Link2SD. The latter seems safer and offers more control but the former seems easier.
Sorry no idea. I always used the SD-card as external storage, all the apps I used (almost) fit on /userdata. One advice though is to format the card to f2fs (either in a computer or in TWRP) that performs better than ext2/3/4 and way much better than fat32/ntfs!
 
  • Like
Reactions: Blank tape

Blank tape

Member
Oct 5, 2014
23
8
When you upgrade a repartitioned phone you can't use an image straight away, you have to resize it to fit your configuration
That sounds like I won't be able to use the installation recipe given by @fweip. I see that there is system.new.dat in the zip file but resizing that (assuming it is a complete system image which I don't think it is) looks like it might require me to adjust whatever integrity checking applies. There is a hash in a couple of manifest files but wouldn't these manifests be signed somehow?

Applying the (important bits) of the updater-script in META-INF/com/google/android looks like it could be the way to go, but so far I've yet to find the primitives it is using and work out what they do. There is also an updater-binary in the same directory which I have no idea about. Goodness knows why there would be two ways of doing the same thing.

Thanks for your help.
 

szty0pa

Member
Sep 18, 2015
46
24
That sounds like I won't be able to use the installation recipe given by @fweip. I see that there is system.new.dat in the zip file but resizing that (assuming it is a complete system image which I don't think it is) looks like it might require me to adjust whatever integrity checking applies. There is a hash in a couple of manifest files but wouldn't these manifests be signed somehow?
It is actually not that difficult, only tedious. Integrity checks are not enforced in our case, at least I never saw working example of it in case of custom ROMs. (I don't actually know how could we make it work? Probably one should calculate a checksum of the image and sign it cryptographically to let TWRP check the validity of it. I don't think this has added security benefit in our case as at least the baseband and probably the proprietary Qualcomm kernel modules already have known RCEs...)

system.new.dat is actually the complete image of the /system partition (which would not fit when you resize that partition).
Resizing is actually pretty easy:
1, you extract system.new.dat somewhere
2, use a tool to convert this 'sparse image' to a normal ext3/4 image
3, with standard linux resize2fs you can resize the 'unsparsed' system image
4, convert the resized image back to a 'sparse' image for TWRP to handle
5, copy the resulting system.new.dat back into the update zip file and you should be good to go.
 

Blank tape

Member
Oct 5, 2014
23
8
Probably one should calculate a checksum of the image and sign it cryptographically to let TWRP check the validity of it.
@fweip does sign the md5 hash of the zip file in every release. I've no idea whether TWRP bothers to check the signatures in asc files if they happen to be provided. Probably not, I would guess. In any case, I would guess fwiep's current public key wouldn't be included in TWRP.

I don't think this has added security benefit in our case as at least the baseband and probably the proprietary Qualcomm kernel modules already have known RCEs...)
As my friend would say, "It keeps the honest people out."

2, use a tool to convert this 'sparse image' to a normal ext3/4 image

That's a useful clue. However, my version of file (Debian buster/stable) does not identify it as a sparse image. At first, I assumed my version is simply just not up to date but googling system.transfer.list reveals a different sparse image format. I don't know why I didn't google that before.

Thanks for your help. Time to bite the bullet.
 

snorhaar

New member
Jan 2, 2018
2
0
Hi, I'm trying to unlock the bootloader of a Huawei Y550-l01. Since 2018 I'm guessing developers are trying to gain money to help users to get the unlock key, wich is understandable. Though I like to search for a solution that's asking for more effort and less money. So far it didn't work.

My plan was to get the phone into factory mode and then try to use Potatonv to get the unlock code. But I can't succeed in the first step. Is there any keypress or fastboot command I can use to achieve the same thing?

Any other method I can try?

Thanks in advance,
Wouter
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Thanks to the LineageOS-developers this is today's build containing the April-2021 security patches.

Recent changes: LineageOS 14.1
Kernel: https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1

This build has the Wireguard sources built in. I don't plan to build without them - not unless someone reports problems having them included.

Please test the Wireguard functionality. I've tried myself, but the Wireguard app always says: "Go userspace backend" Do I need to have root access or give some special permissions?

Known bugs:
- the WiFi MAC-address sometimes switches between a Huawei-prefix 68:a0:f6 and an Airgo-prefix 00:0a:f5 on reboot
(I've observed this on a Moto G6 with RROS OTA, too - so it's probably a generic custom-ROM issue)

Update: download links have been removed. Please use the most recent ROM, see this link:
Unofficial LineageOS 14.1 (Android 7.1.2) ROM with June-2021 security patches

Kind regards,
FWieP
 
Last edited:
  • Like
Reactions: bahram360

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
@fwiep does sign the md5 hash of the zip file in every release. I've no idea whether TWRP bothers to check the signatures in asc files if they happen to be provided. Probably not, I would guess. In any case, I would guess fwiep's current public key wouldn't be included in TWRP.

No, the .asc-file I provide is meant for you, dear downloaders out there. I learned about GPG signing and this was about the only thing that made sense for me to sign (except my e-mail messages, but that's another story). So, please use it if you can, ignore it if you wish.

Kind regards,
FWieP
 

rudolfm

Senior Member
Apr 11, 2014
131
38
Please test the Wireguard functionality. I've tried myself, but the Wireguard app always says: "Go userspace backend" Do I need to have root access or give some special permissions?
To use the kernel modules, the Wireguard app needs root. If I deny root, it goes userspace.
Your kernel does not have wireguard. There is no /sys/modules/wireguard when your kernel is running. I would look at the kernel config file whether wireguard is being compiled.
The kernel I mentioned in:
has support, has the /sys/module/wireguard/, and the app says it is using the kernel.
I tested this by flashing the old kernel to your rom posted above. This is the easy way to compare.
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
To use the kernel modules, the Wireguard app needs root. If I deny root, it goes userspace.
Your kernel does not have wireguard. There is no /sys/modules/wireguard when your kernel is running. I would look at the kernel config file whether wireguard is being compiled.

Thank you for your persistent push to look into this. Today I have learned that it is not enough to simply include the Wireguard sources; they have to be enabled, too! Once I modified my kernel config and added "CONFIG_WIREGUARD=y", the module was actually built and included.

Have just tested it with the addonsu package from LineageOS and the Wireguard apk from f-droid. It works!

------

Thanks to the LineageOS-developers this is today's build containing the April-2021 security patches.

Recent changes: LineageOS 14.1
Kernel: https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1

This build has Wireguard built into the kernel:
ZIP: lineage-14.1-20210426-wg-UNOFFICIAL-y550.zip
MD5: lineage-14.1-20210426-wg-UNOFFICIAL-y550.zip.md5
ASC: lineage-14.1-20210426-wg-UNOFFICIAL-y550.zip.md5.asc

Known bugs:
- the WiFi MAC-address sometimes switches between a Huawei-prefix 68:a0:f6 and an Airgo-prefix 00:0a:f5 on reboot
(I've observed this on a Moto G6 with RROS OTA, too - so it's probably a generic custom-ROM issue)

Kind regards,
FWieP
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Thanks to the LineageOS-developers this is today's build containing the May-2021 security patches.

Recent changes: LineageOS 14.1
Kernel: fwiep/android_kernel_huawei_y550

This ROM has Wireguard support built into the kernel.

Known bugs:
- the WiFi MAC-address sometimes switches between a Huawei-prefix 68:a0:f6 and an Airgo-prefix 00:0a:f5 on reboot
(I've observed this on a Moto G6 with RROS OTA, too - so it's probably a generic custom-ROM issue)

Update: download links have been removed. Please use the most recent ROM, see this link:
Unofficial LineageOS 14.1 (Android 7.1.2) ROM with June-2021 security patches

Kind regards,
FWieP
 
Last edited:

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Tutorial update

Hello all,

After the may-2021 security patches were merged into LineageOS 14.1, I immediately started the build for our Y550 devices.
It promptly failed saying
Code:
SSL error when connecting to the Jack server. Try 'jack-diagnose'.

Thanks to StackOverflow a quick fix was around the corner. Apparently, Ubuntu (or openjdk-8) received an update putting TLSv1 and TLSv1.1 on some sort of blacklist. This fix removes them from that list.

I have edited my build tutorial accordingly. While there, I also revised all hyperlinks and updated, among other things, the local manifest entries.

Kind regards,
FWieP
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Hope this helps! I'll try to assist if not anyway.
Having some spare time, I've given this phone another try. Sadly, I don't get anywhere. :(

Note: I'm still using an SD-card with a complete image pulled from a working Y550 with LineageOS 14.1.

When I put the battery and SD-card into it, it boots to a fastboot-like mode. It says: "PHONE Locked" Error: allocating memory for ssd buffer.

When I remove the battery (keep the SD-card in) and connect it via usb, it boots to fastboot mode. I can see it with 'sudo fastboot devices' and it processes my commands. It still says "PHONE Locked". So I enter 'sudo fastboot oem unlock xxxxxxxxxx', having my original unlock code received from Huawei several years ago. Its response: "Cannot get the valid key! the key is invalid". So I try using the original unlock code from the donor-Y550: same result.

...you will be able to overwrite partitions one-by-one. (Start from '/dev/block/mmcblk0p1' (sbl) - I suspect this should already make you able to boot at least to TWRP.)

How do I go about doing this? How can I flash partitions when the phone thinks it's locked?

I feel like having all the puzzle's pieces, but being unable to actually put them together. Very frustrating :(. Do you have any advice?

Thanks,
FWieP
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Managed to buy 4 credits, got login details. Why do I keep getting this message when trying to login?
    ...
    2022.06.10 09:25:54.803 Test fail!
    Operation timeout

    I can't help you with this specific problem, but I know you'll get decent advice from the DC-Unlocker people via their chat; the big Message button on the bottom right of their site starts a conversation. If it's outside their business hours (GMT+2), you'll get an e-mail and the conversation will continue that way.

    Last week, thanks to the recent revival of this XDA thread, I tried to resurrect my old Y550-L01 once again. About two years ago, I somehow bricked it hard. Now, this made me contact the DC-Unlocker people and use their DC-Phoenix software. It all looked very promising (downloading the stock firmware, bootloader, etc. from their servers, detecting the device both in some kind of fastboot mode when an SD-card was inserted, and Qualcomm HS-USB QDLoader 9008 mode when not).

    The flashing failed repeatedly, so I chatted with them. Followed their advice, and chatted again. Followed their advice and mailed some logs... All to no avail. Their conclusion was (as is mine, and was ours in this thread, two years ago): the motherboard would have to be replaced to revive it. For me, that's not an option, so I handed it over to our city's recycling facility. I put a printed note inside pointing to this thread, so that anyone who tries his/her luck with the device, won't have to start from scratch.

    TL;DR: seek out the assistance of the DC-Unlocker people; I spoke to and mailed with Waldmeras and he was very knowledgeable and friendly.

    Good luck and kind regards,
    FWieP
    1
    Using Root explorer, I cannot seem to gain entry to the Root/Data directory, its stating the phone is not rooted. Superuser SU is not granting priveledges to Root Explorer. I had this problem on another phone, I installed Magisk, and it granted priveledges to Root Explorer. But as I am on Andoid 4.4.4, I'm struggling to find a version of Magisk which installs and works in the correct manner

    I believe magisk won't do this anymore, and Chainfire sold SuperSU to a Chinese company years ago! (Good on him!)... Magisk is now the defacto root solution, and it's open source to boot!...

    Do yourself a favour, cleanup SuperSU, ditch 4.4.4 and install this 7.1 c/o @fwiep w/ adopted storage working out of the box (just be sure to update baseband as I mentioned):
    https://forum.xda-developers.com/t/everything-huawei-y550-root-cwm-twrp.2923318/post-85363935

    Then install Magisk!... 😛 PW
    1
    Just reflash latest stock fastboot ROM then I guess. Best to do this before a custom ROM install in any case ... Cleanup options were in SuperSU app IIRC... PW
    1
    Yep I've the same problem, error message when trying to flash lineage-14.1-20210803-UNOFFICIAL-y550.zip.

    I thought fwiep fixed that but as I never tested that or subsequent versions I can't confirm the fix works. Finally, taking a looking at the most recent zip and the fix itself it does something different to what I suggested so I'm guessing not. Sorry to provide such late feedback Frans!

    Anyway, I worked around the problem with a setprop command in adb shell:
    setprop ro.product.device Y550-L02

    This must be done before an install is attempted. It seems values are cached.

    FWIW, I used twrp-3.3.0-1-y550 back then.
    1
    To pose a question myself: Is there a way I can use to return the phone back to B240 stock. B247 changed the boot process in such a way that while flashing TWRP in fastboot appears to work it does not replace the stock recovery.
  • 52
    Thread Index

    Rooting, CWM & TWRP Instructions LINK

    Latest TWRP
    TWRP 2.8.7.0 21/8/15 - CM12 compatible
    2.8.7.0 Final 25/1/16
    Older TWRP TWRP 2.8.4.1 31/1/14 - CM11 compatible
    Latest CWM 9/12/14
    Latest Superuser 9/12/14
    Latest Slim SDK 9/12/14

    Stock Rom Recovery Link (Install through fastboot - fastboot flash recovery recovery_y550.img)
    Updated LInk Here

    Latest Y550 (L01) Stock Rom
    5/11/14 Western Europe
    16/1/2015 Eastern Europe & Scandinavia

    Normal upgrade/reinstall using in built updater Link
    Forced upgrade/reinstall procedure Link
    Upgrade/Reinstall using Fastboot Link

    Google Stock Apps Link

    All Huawei y550 related apps and files (thanks to klaidone) Link

    Alternate unlock code methods Link Link
    And another Link


    L02 Files
    All At this URL
    Files:
    Update.zip - the latest OTA update for L02 Region Phones - Applied using inbuilt updater
    Y550-L02 Stock - CWM backup of the original L02 Stock Rom Link
    Y550-L02 (Build 346) - CWM Backup of the most up to date L02 Rom Link
    Credits to Happychappy on the Whirpool Forum
    Y550 (Prob L02) TWRP Stock Backup

    Faq/Tips
    Will the L01 rooting method work on my L02 Yes
    Can I change the Boot Animation? Link (And the following post)
    Can I use L01 firmware on my L02? Link
    Can I change the status bar and carrier logo? Link
    Does Exposed framework work on this phone? Link
    How do i remove the Kitkat write restrictions? Link

    Roms from HB72K

    Stable and suitable for everyday use. More information, install instructions, root etc from user @HB72K in This post

    AOSP Based Roms
    Carbon Rom from Hb72k Link & Install instructions - Known Bugs: Phone only rings once then mutes

    Stock Based Roms
    Y550 Stock Rom by Hb72k Link
    Y550 Stock Lite by Hb72k Link
    Y550 Stock (Gstock 2) by Hb72k Link
    Y550 Stock (Gamer 2) by Hb72k Link

    MIUI Based Roms
    MIUI 7 by Hb72k Link
    MIUI 6 by Hb72k Link

    CM Roms

    CM11 - Final XDA Build by Hb72k link
    Hecaex Build - 11 June 2015 Link Doesnt include Static Mac Address fix
    Hecaex Build - 30 May 2015 Link This is based on Patrick's march build with Camera modifications. Working Wifi (Random Mac), Camera working (But flash not working)
    Patrick KT Build - 11 March 2015 (CM11) Link - Wifi working but with random Mac. Camera not working
    Hecaex Build - 10 February 2015 (CM11) Link - Camera flakey, superuser and torch not working
    Patrick KT Build - 1 February 2015 (CM11) Link - Wifi and Camera not working

    Static Mac Address Fix Link
    Camera Patch Only Link

    2016 Roms

    Modded EMUI 3.0 https://mega.nz/#!Dt4gGQCD!zEvIGHsuZURN7Xl9F3LnAdRDviTo-BLzC0n42YH9ZjM
    Modded Miui 7.0 (Twrp backup) https://drive.google.com/folderview?id=0BzJ-jN4Pv2baSXFwRFpqcGoySUE&usp=sharing
    CM Patches/Fixes
    EMUI (Hb72k) http://forum.xda-developers.com/showpost.php?p=65241854&postcount=2268
    Pacman (hb72k) http://forum.xda-developers.com/showpost.php?p=65327203&postcount=2281
    Pacrom (Jeffta) http://forum.xda-developers.com/showpost.php?p=65353386&postcount=2284
    Miui7 (Dabi01 almost final) http://forum.xda-developers.com/showpost.php?p=65702075&postcount=2334



    Other Files

    Walkman (Zip) for Stock and Custom Roms Link

    IVE BRICKED MY PHONE!
    Download the full Huawei Y550 rom from Here (You want the penultimate file - y550 build 239
    Download the Huawei update extractor from the same link
    Run update extractor and extract the rom
    Copy the entire folder "dload" to the root of your sdcard (so there is a folder on your sd card called dload containing the update file)
    Hold down all physical buttons on your phone - volume up, volume down and power at once
    24
    DISCLAIMER - THIS CWM AND ROOT METHOD IS DESIGNED FOR THE G620 - IT IS ESSENTIALLY THE SAME PHONE BUT LIKE ANYTHING THERE ARE ALWAYS RISKS WITH INSTALLING CWM AND ROOTING YOUR PHONE. IT WORKED FOR ME, BUT I BEAR NO RESPONSIBILTY IF IT DOESNT WORK FOR YOU, BRICKS YOUR PHONE, OR TURNS YOU INTO A PUMPKIN.

    Ok, rooting the Huawei Y550..
    Source Credits Here and Here
    Originally this is the boot image for the G620 but it has the same partition table as the Y550

    Three step method - first you need your bootloader unlocked, then CWM installed, then superuser installed.

    First you will need your bootloader unlocked. You can get this by emailing Huawei
    to get your unlock email Huawei on [email protected]

    Send them a request for bootloader unlock with the following info:
    Serial Number: under battery
    IMEI: under battery
    Product ID: call * # * # 1357946 # * # * to get it
    Model: HUAWEI Y550-L01

    Once you have your code...
    switch device off
    boot into fastboot mode "volume down and power"
    connect by usb to your PC
    wait for drivers to install (just install the huawei app to get the drivers)
    download and install ADB toolkit from google (or Android SDK Slim which ive attached as a zip)
    open the directory adb toolkit is in, shift and right click and select open command window
    type in... fastboot oem unlock 1234567812345678 where the number is your unlock code
    Your bootloader will now be unlocked. Source and more info

    Update: Alternate way to get the unlock code Link

    UPDATE - TRWP RECOVERY
    We now have TWRP thanks to patrik.KT. Source
    1) Download the TWRP Image file Link
    2) Place the image file in the same directory as fastbook.exe from the previous step
    3) Connect phone in fastbook mode
    4) Check compatability by booting only initially.
    Code:
    fastboot boot TWRP_y550_20150130.img
    5) if boots correctly go back into fastbook mode and run in the dos window
    Code:
    fastboot flash recovery TWRP_y550_20150130.img

    CWM Recovery
    Zip file download Link
    Extract zip file to computer
    Put phone in fastboot mode (Down volume and power button)
    Connect phone to PC and run the file - install-windows.bat
    This will install a CWM boot to your phone and then reboot it

    Contents of zip showed up clean with McAfee
    23rl4wm.png


    Superuser
    Dowloaded superuser.zip from HERE
    (Do not use Super-SU it doesnt work with stock roms)
    copy superuser.zip to your SD card.
    Boot into CWM (Volume up and power key)
    select english language if prompted
    install zip from SD card and install superuser.zip

    Boom....
    21cun13.jpg
    alkh3n.jpg


    Phone has CWM and Root.
    Only downside is parts of the CWM (notably the backup section) are in chinese

    Translation for backup section is:

    backup image to internal SD
    restore image from internal SD
    delete image from internal SD
    restore image with options from internal SD
    backup image to external SD
    restore image from external SD
    delete image from external SD
    restore image with options from external SD
    14
    Things to do after rooting

    A few comments now that I've rooted one of my Y550 phones:

    First thing I did was to permanently nuke the file restrictions on writing to the SD card, this was easily achieved in seconds. Now everything can read/write to the external SD card just like in every other release of android.
    *This was the main frustration and reason pushing me to root the phone.

    Next was to change the screen DPI to make everything look less blobby.
    After going through settings of 230, 220, 215 and 210 I've found that on the default Huawei EMUI launcher anything lower than 230 looks odd, although 220 is probably usable.
    With a setting of anything less than 220 the desktop icons are shifted into strange positions which is quite off putting, and having only 4 rows of desktop icons looks kind of odd when the icons are shrunk, there is easily enough room for 5 rows, on Nova launcher mine is set to 6 rows and it looks great.
    As always Nova cures most of the visual ills that appear in the supplied manufacturers launchers, so no problems...
    Anyone considering the Y550 should disregard any the negative comments from those who proclaim the screen is crap..!!!
    Obviously it is very slightly lower resolution than some models, but if you don't hold it next to another phone with a higher resolution screen to compare against then I can't imagine anyone would know.

    Running MX Player Pro the Y550 can easily play H.264 1080P videos scaled to full screen.
    *In MX Player Pro I set the sound playback for S/W Audio, the volume can then be increased to 200% which is great. I set the video to playback using H/W+ decoder which is impressive. The Y550 quad core combined with a better GPU obviously helps with smooth media playback. Using AllCast to playback video through the LAN to a big screen is also very smooth, it works a treat.

    And to top off my first round of rooting fun I installed AdFree to get rid of the nasty adds that appear in many apps, together with an old favourite called BatteryCalibration which is always worth running after installing CWM or TWRP.
    :good:

    ---------- Post added at 01:14 PM ---------- Previous post was at 01:08 PM ----------

    A quick "How to" describing the method for removing the stupid KitKat write restrictions on the External SD card.

    Perhaps a disclaimer first to say that if any of the following seems like techno-babble you should NOT do this, just leave it the way google intended it to be, or find a local droid geek to assist you...

    Out of habit I use ES File Explorer to edit my android system files directly on the device, it has a decent enough text (note) editor and also has the easiest way to visually confirm that the file permissions are correctly set after you have edited/moved/copied files.

    ================
    WARNING: Incorrect file permissions are your biggest danger, the phone will probably not boot if they are set incorrectly.
    Whatever happens you should proceed with extreme caution! Recheck everything several times before rebooting...
    ================

    In ES File Manager toggle the "Root Explorer" to on, and then navigate to the following file:
    /system/etc/permissions/platform.xml

    Note: You deserve to have problems if you don't make a backup of the original file first, so make a copy of it in the user memory space or on the SD card.

    Then open the file in the ES note editor and scroll down until you find: android.permission.WRITE_EXTERNAL_STORAGE and android.permission.WRITE_MEDIA_STORAGE lines.
    In the ES text editor click the top right menu and chose the pen, this will give a cursor to allow you to write text.
    These are XML sections, you need to make them look exactly like the strings below:

    <permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
    <group gid="sdcard_r" />
    <group gid="sdcard_rw" />
    <group gid="media_rw" />
    </permission>

    <permission name="android.permission.WRITE_MEDIA_STORAGE" >
    <group gid="sdcard_rw" />
    <group gid="media_rw" />
    </permission>

    Save the platform.xml file (do this by hitting the back hardware button once, it'll then ask if you want to save changes.
    Then exit the editor and refresh the directory listing, chose view and select "small detail" and make sure that platform.xml file permissions are set to "-rw-r--r--" (in geek speak it needs to be 644) before rebooting your phone.
    *Don't forget to turn off the "Root Explorer" toggle in ES File Manager after you have edited the file and confirmed the file permissions.
    That's it.

    Once again, if any of the above seems too hard then DON'T do it.

    *In the past I've tried apps from the playstore to perform this tweak on other devices, but none of them worked, so now I just do it myself, it only takes a couple of minutes to edit the file.

    =========================
    DISCLAIMER – THERE ARE ALWAYS RISKS WITH EDITING SYSTEM FILES, IT WORKED FOR ME, BUT I BEAR NO RESPONSIBILITY IF IT DOESN'T WORK FOR YOU, BRICKS YOUR PHONE, OR TURNS YOU INTO A WOMBAT.

    ---------- Post added at 01:19 PM ---------- Previous post was at 01:14 PM ----------

    ==================================

    I hope the above posts are helpful for those who've never edited system files before...
    It's bit scary the first couple of times, but it you take it slow and steady it is not hard at all.

    It's basically the same method for changing the display DPI, you'll need to edit the /system/build.prop file and look for this line:

    ro.sf.lcd.density=240

    and change the "240" to anything between 240 ~ 200 then reboot.

    Simple as...
    Just remember to check those file permissions before you reboot :good:

    =================
    Don't forget to press the THANKS button if any of this helped you ;)

    ---------- Post added at 01:30 PM ---------- Previous post was at 01:19 PM ----------

    I have achieved 7020p & 1080p resolution on Huawei Y550, I would advise 720p over 1080p as it is alot clearer on this little screen....

    Yours was an interesting post, I would never have considered trying to set a non native resolution on the device. I imagine this would cause all sorts of problems that could be hard to solve.

    If your intention is only to increase the information shown on the screen, then I think it is a much better idea to change the display DPI rather than setting a totally different screen resolution. The chances of upsetting the system are far less and there is no need for busybox, or soft keys because everything still works as it should...
    11
    So guys it's been a while but I'm working on CM12.1. But I'm quite busy with my job, so please be a little more patient ;) .
    I've got a new TWRP and I have a booting CM12.1. But there are some major things which need to be fixed.
    I will push some test build with new TWRP later.
    11
    So I noticed you dont have any working TWRP on the Y550, so I made one :cowboy:

    Make sure you only boot it first to check if its compatible
    Code:
    fastboot boot TWRP_y550_20150130.img
    and if it works just fine, then flash it
    Code:
    fastboot flash recovery TWRP_y550_20150130.img

    Download: https://docs.google.com/file/d/0B5KRmU8P96dlYTc4eS11QXItdlU/edit