Everything Huawei Y550 - Root/CWM/TWRP

Search This thread

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
As always, you seem to be the master of finding information on XDA. Thanks for the research! :)

I think I'll give it a go using the "Method B: Integrating into ROMs" - who knows what will happen.
When the November-2020 patches arrive, I'll build as usual without explicit WireGuard stuff - and then build a separate ROM with WG included.

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 December-2020 and November-2020 security patches.

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

ZIP: lineage-14.1-20201220-UNOFFICIAL-y550.zip
MD5: lineage-14.1-20201220-UNOFFICIAL-y550.zip.md5
ASC: lineage-14.1-20201220-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 my new Moto G6 with RROS OTA, too - so it's probably a generic custom-ROM issue)

Edit: Removed obsolete download links.

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

rudolfm

Senior Member
Apr 11, 2014
131
38
@fwiep said:
" I'd like your help in testing the WireGuard functionality in this ROM"
I used this Rom for over a year (2018/19) with wireguard and no problems. All I had to do was download the wireguard app from fdroid. Azire had a test phase where you could use it for free with wireguard. I was one of those "happy to test" folks :)

You also wrote that your Y550 is dying. If you need one to keep on supporting, I could send you mine.

Happy new Year!
 
  • Like
Reactions: pndwal

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
All I had to do was download the wireguard app from fdroid.
Thanks for this info. I hoped as much, and will not try to build in kernel support any longer.
The app itself is very capable of making the VPN work. I use it on my primary device regularly.

You also wrote that your Y550 is dying. If you need one to keep on supporting, I could send you mine.
Thank you, but luckily, my Y550 has returned from the dead. It's WiFi was truly fixed by a thorough return to stock.

Kind regards and a happy new year!
FWieP
 

rudolfm

Senior Member
Apr 11, 2014
131
38
Thanks for this info. I hoped as much, and will not try to build in kernel support any longer.
Wireguard support was already in the kernel when you took over. If you can just leave it there then please do.

I used wireguard with the Kernel support, and it worked fine. You can see the Kernel is used when you use the Fdroid Wireguard app, and it does NOT use the VPN slot. The app contains suport for the kernel module and also a userspace module. If the app finds a kernel module it will use that.

I don't really understand why you write that you would (not) try to build in kernel support. It was already inside. Or did you change the kernel?
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Wireguard support was already in the kernel when you took over. If you can just leave it there then please do.
...
I don't really understand why you write that you would (not) try to build in kernel support. It was already inside. Or did you change the kernel?
My mistake.
No, I did not change the kernel. I am very grateful that it was ported and developed to what we use today.
I was under the impression that the builtin Wireguard code was out of date and needed an update to work properly. That's why I started tinkering around with it (in a separate, local copy of the source). Rest assured: the kernel included in my builds is as untouched as it was when @desalesouche let me 'take over'.

Kind regards and a happy new year,
FWieP
 

rudolfm

Senior Member
Apr 11, 2014
131
38
@fwiep

I did some research. I thought you continued Desalecouches build, but now I see you started your own.

Desalecouche included wireguard into the kernel in build 20171219, see page 295 of this thread.
It continued until build 20180916, the last one I have with wireguard. I have a build 20181111 marked Desalecouche and a build 20181115 marked Fwiep which both have no wireguard. Later builds I have are yours. Maybe Desalecouche removed it.

I found that out by simply flashing different boot.img files copied out of the build zips, flashing them on a newer system, and seeing what the wireguard app says. It shows either kernel or userspace backend in the settings. You only need to install the app, it needs not be set up tho show if the kernel is used.

If you wish to have a short look, I have attached a .zip including the boot.img 20180916 with kernel support, a screenshot of "about phone" showing your build and the Desalecouche kernel, and a screenshot of the app showing kernel support.

I think that you could simply apply the same wireguard patches Desalecouche used, as you still use the same kernel version. Having wireguard in the kernel is better on battery and speed.
 

Attachments

  • wireguard.zip
    8.9 MB · Views: 13
Last edited:
  • Like
Reactions: pndwal

Yalmanlar

Member
Jan 8, 2021
6
0
Hi Guys I'm stuck on Custom room boot loop
Huawei y635-l01
Fix camera. zip caused it.it was running Remix Android 7.1 after I installed fix Camera.zip it stuck since in bootloop
I can't find a way out. I installed stock rom many times, it works well in stock rom but when I install custom rom it stuck in Boot Loop.
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Thanks to the LineageOS-developers this is today's build containing the February- and January-2021 security patches.
Regarding WireGuard integration: I have not yet found the time to work on this; maybe later.

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

ZIP: lineage-14.1-20210218-UNOFFICIAL-y550.zip
MD5: lineage-14.1-20210218-UNOFFICIAL-y550.zip.md5
ASC: lineage-14.1-20210218-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)

Edit: Removed obsolete download links.

Kind regards,
FWieP
 
Last edited:

fwiep

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

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

Regular, without Wireguard built into kernel:
ZIP: lineage-14.1-20210307-UNOFFICIAL-y550.zip
MD5: lineage-14.1-20210307-UNOFFICIAL-y550.zip.md5
ASC: lineage-14.1-20210307-UNOFFICIAL-y550.zip.md5.asc

With Wireguard built into kernel:
ZIP: lineage-14.1-20210307-wg-UNOFFICIAL-y550.zip
MD5: lineage-14.1-20210307-wg-UNOFFICIAL-y550.zip.md5
ASC: lineage-14.1-20210307-wg-UNOFFICIAL-y550.zip.md5.asc

Please test the Wireguard build. I've tried myself, but the Wireguard app always says: "Go userspace backend", no matter which of the two kernels I use. Do I need to have root access? Give some special permissions?


Update 1: Wireguard support was not actually included - please see my later builds from april 26, 2021 onwards.

Update 2: Removed obsolete download links.

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
 
Last edited:

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
Dear all,

I've built for the Y550 with another WG-implementation. The previous one (see last post) was with sources from wireguard-monolithic-historical. Now I'm using the sources from wireguard-linux-compat. The latter name sounds more current, more up-to-date.

Here are the download links:
lineage-14.1-20210308-wg-UNOFFICIAL-y550.zip
lineage-14.1-20210308-wg-UNOFFICIAL-y550.zip.md5
lineage-14.1-20210308-wg-UNOFFICIAL-y550.zip.md5.asc

My personal Y550-L01 has given up; permanently, so it seems. Yesterday, I was happily testing the WG stuff and switched it off using the power menu. This morning, there was no life in the device at all. Connecting the charger should boot up to show a loading animation, but does nothing. The battery itself is fully charged at 3,7V. I've taken the device apart to see if there's nothing obviously defective or loose - there isn't.

Update - when connected to a PC via USB, the device is detected as QHSUSB__BULK.
So, there's hope after all. I'm searching XDA for further instructions.

I hope my second Y550 will return to me in a few days time, but until then... I won't be able to test myself what I upload right here on the forum.

If any of you know a reanimation trick for a 7-year old smartphone - please tell me!

Kind regards,
FWieP
 
Last edited:

GotoDengo

Senior Member
Jul 29, 2018
85
34
Thanks to the LineageOS-developers this is today's build containing the March-2021 security patches.

Thanks for this. I've installed the standard version and it's working fine so far.

If any of you know a reanimation trick for a 7-year old smartphone - please tell me!

I would have suspected the battery myself (as I had to replace mine recently) but as you've tested that out it could be a motherboard failure! :(
 
Last edited:

szty0pa

Member
Sep 18, 2015
46
24
Dear all,

...

My personal Y550-L01 has given up; permanently, so it seems.
...
If any of you know a reanimation trick for a 7-year old smartphone - please tell me!

Thank you for your work as always! :)

I would suspect that your bootloader is corrupted. (So it might indicate NAND failure...) Were you able to restore your phone to a working state?
If not i think the way would be to extract the full raw disk image from a factory update file (especially the bootloader) and write it out to your phone's NAND as a raw disk image. Since you use linux dd would be the best choice.
Best of luck with it!
 

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
I would suspect that your bootloader is corrupted. (So it might indicate NAND failure...) Were you able to restore your phone to a working state?
Unfortunately, no.

If not i think the way would be to extract the full raw disk image from a factory update file (especially the bootloader) and write it out to your phone's NAND as a raw disk image.
Thank you for the pointing into this direction. Using these instructions I have pulled a mmcblk0.img from my second, working Y550. Then, I wrote that image to a blank SD-card and inserted it into the patient.

Using these instructions as a guideline, I booted the device with vol-down and connecting the charger. Yes, the phone came to life, scrolled lots of messages through the screen and even showed me a fastboot prompt. The screen showed that the bootloader is locked. Trying to flash or even boot TWRP via fastboot failed (not allowed). Somewhere, I read the message
Code:
error:allocating memory for ssd buffer

But then, it kept on rebooting showing about one hundred lines of
Code:
boardid:8096
Then the next reboot.

I'm sorry, but the repair of this device is beyond me. Luckily, its sister is in the house, again!

Kind regards,
FWieP
 

szty0pa

Member
Sep 18, 2015
46
24
Unfortunately, no.


Thank you for the pointing into this direction. Using these instructions I have pulled a mmcblk0.img from my second, working Y550. Then, I wrote that image to a blank SD-card and inserted it into the patient.

Using these instructions as a guideline, I booted the device with vol-down and connecting the charger. Yes, the phone came to life, scrolled lots of messages through the screen and even showed me a fastboot prompt. The screen showed that the bootloader is locked. Trying to flash or even boot TWRP via fastboot failed (not allowed). Somewhere, I read the message
Code:
error:allocating memory for ssd buffer

But then, it kept on rebooting showing about one hundred lines of
Code:
boardid:8096
Then the next reboot.

I'm sorry, but the repair of this device is beyond me. Luckily, its sister is in the house, again!

Kind regards,
FWieP

Sorry to hear that you didn't succeed at first try - it needs a lot of experience and some luck to do so, but don't give up so easily, you are about halfway there! :)

Modern ARM devices are almost impossible to "hard-brick" (by modern I mean ARMv7+ which Y550 certainly is)!
(As a side note I think I was wrong as the phone has eMMC, not NAND but that does not make any difference for us.)

So what can be concluded from your experiments is that the hardcoded (ROM) bootloader works alright as it loads and executes the second-stage bootloader from your SD card alright. You now have an mmcblk0 image (that is the second-stage bootloader) which is awesome and the key to success!!! :)
(Note that the instructions you linked for extracting the image are a bit vague and inaccurate but should _mostly_ work. The problem is that it does not pay attention to the size of the partition - that should not be a problem - and possible bad sectors - that could be a problem though. I recommend the command to be something like "dd if=/dev/mmcblk0 of=/link/to/dir/mmcblk0.img conv=sync bs=1M status=progress"; if: the partition you want to image, of: output image file, conv=sync: skip bad sectors, bs=1M: use 1 megabyte sectorsize to speed up the copy, status=progress: to show you how it's progressing.)

One thing I would try is that connect your (dead) phone so your PC sees it as a bulk disk (using linux would be easier for me to help you with), you should see an entry for it under /dev/. (If you issue a "dmesg | tail" after you connect it you should see how it is recognised.) It probably won't be a disk popping up your file manager. :)
Once you get the correct /dev/sdX entry use dd to copy mmcblk0.img back to the phone: "dd if=/path/to/mmcblk0.img of=/dev/sdX conv=sync bs=1M status=progress". Oh and don't forget to issue "sync" a few times (2 or 3 for safety and historic reasons - might be a bit of superstition) :) after you use dd - that makes sure the whole image is transferred and it is safe to unplug the phone!

Hope this helps reviving your phone mate! :)

[edit] It probably won't be /dev/sdX but /dev/mmcblkX. Oh and to copy only the bootloader the correct entry is probably /dev/mmcblk0p1? /dev/partitions will tell you that.
 
Last edited:
  • Like
Reactions: fwiep

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
I've tried the direct USB connection to my Linux-PC. dmesg shows the following:
Code:
usb 3-10.3: new high-speed USB device number 60 using xhci_hcd
usb 3-10.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
usb 3-10.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 3-10.3: Product: QHSUSB__BULK
qcserial 3-10.3:1.0: Qualcomm USB modem converter detected
usb 3-10.3: Qualcomm USB modem converter now attached to ttyUSB0
So, there's no block device to write to.

For your info, these are the commands I used to extract the mmcblk0.img:
Code:
y550:/ # cat /proc/partitions                                                  
major minor  #blocks  name

 254        0     524288 zram0
 179        0    3817472 mmcblk0
 179        1        512 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3         32 mmcblk0p3
 179        4         32 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7       5056 mmcblk0p7
 179        8       1024 mmcblk0p8
 179        9      65536 mmcblk0p9
 179       10       4096 mmcblk0p10
 179       11       4096 mmcblk0p11
 179       12      98304 mmcblk0p12
 179       13       4096 mmcblk0p13
 179       14       2048 mmcblk0p14
 179       15       2048 mmcblk0p15
 179       16      65536 mmcblk0p16
 179       17      32768 mmcblk0p17
 179       18      20480 mmcblk0p18
 179       19      24576 mmcblk0p19
 179       20     262144 mmcblk0p20
 179       21     196608 mmcblk0p21
 179       22       4096 mmcblk0p22
 179       23    1310720 mmcblk0p23
 179       24    1703919 mmcblk0p24
 179       32       4096 mmcblk0rpmb
 179       64   15183872 mmcblk1
 179       65   15181824 mmcblk1p1

y550:/ # dd if=/dev/block/mmcblk0 of=/storage/59DB-FABF/mmcblk0.img bs=1024k count=3728

Can I use the /dev/ttyUSB0 to restore the device?

Thanks,
FWieP
 

szty0pa

Member
Sep 18, 2015
46
24
I've tried the direct USB connection to my Linux-PC. dmesg shows the following:
Code:
usb 3-10.3: new high-speed USB device number 60 using xhci_hcd
usb 3-10.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
usb 3-10.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 3-10.3: Product: QHSUSB__BULK
qcserial 3-10.3:1.0: Qualcomm USB modem converter detected
usb 3-10.3: Qualcomm USB modem converter now attached to ttyUSB0
So, there's no block device to write to.

For your info, these are the commands I used to extract the mmcblk0.img:
Code:
y550:/ # cat /proc/partitions                                                 
major minor  #blocks  name

254        0     524288 zram0
179        0    3817472 mmcblk0
179        1        512 mmcblk0p1
179        2        512 mmcblk0p2
179        3         32 mmcblk0p3
179        4         32 mmcblk0p4
179        5        512 mmcblk0p5
179        6        512 mmcblk0p6
179        7       5056 mmcblk0p7
179        8       1024 mmcblk0p8
179        9      65536 mmcblk0p9
179       10       4096 mmcblk0p10
179       11       4096 mmcblk0p11
179       12      98304 mmcblk0p12
179       13       4096 mmcblk0p13
179       14       2048 mmcblk0p14
179       15       2048 mmcblk0p15
179       16      65536 mmcblk0p16
179       17      32768 mmcblk0p17
179       18      20480 mmcblk0p18
179       19      24576 mmcblk0p19
179       20     262144 mmcblk0p20
179       21     196608 mmcblk0p21
179       22       4096 mmcblk0p22
179       23    1310720 mmcblk0p23
179       24    1703919 mmcblk0p24
179       32       4096 mmcblk0rpmb
179       64   15183872 mmcblk1
179       65   15181824 mmcblk1p1

y550:/ # dd if=/dev/block/mmcblk0 of=/storage/59DB-FABF/mmcblk0.img bs=1024k count=3728

Can I use the /dev/ttyUSB0 to restore the device?

Thanks,
FWieP
I see! So you have the whole eMMC imaged then. I think the first megabyte or so would be enough to kickstart it. I will try to check the partition map to find out which partion stores what. (Trouble is that there might be calibration data somewhere which would be best kept intact if possible.)

/dev/ttyUSB0 is a serial console which can be used to restore your phone - but as you noticed is not a block device, so it needs a different way to utilise. If you have the time it's great learning experience to connect to it and see what you can do with it. Under linux minicom or screen (for example) can be used for that, under Windows i think PuTTY is the obvious choice. I suspect there must be some special Qualcomm tool for restoring the phone from an image. I'll try to look around for that.
 
  • Like
Reactions: fwiep

fwiep

Senior Member
Nov 17, 2016
164
232
www.fwiep.nl
I suspect there must be some special Qualcomm tool for restoring the phone from an image. I'll try to look around for that.
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
 
Last edited:

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