Root [RECOVERY] Clockworkmod Recovery for Hwawei Y301-A1

[EagerestWolf]

This is the release of Clockworkmod for the Huawei Valiant. While you are more than welcome to flash this to your device, there are a few things to note:

1. First and foremost, this WILL void your warranty, so if you have any issues with your device after this, they are longer covered by Huawei or MetroPCS.
2. Secondly, rooting your device and/or flashing a custom recovery is directly against MetroPCS's (and most carriers') Terms of Use. If Metro catches you with either of these, they will suspend your account.
3. Thirdly, I am in no way, share or form responsible for what you do to your device. If you are not okay with this, then do NOT flash this recovery.
4. Fourth and finally, this process requires that your device's bootloader is unlocked. If you do not know how to do this, then refer to the thread I will be creating later.

Proceed if and only if you agree to ALL of those terms


Credits

• Totempoke for starting the project, I would have never decided to start it if I hadn't seen that he was stalled
• jonhaney from UnleashedPrepaids for analyzing the partitions and giving a partition map for this phone
• KainXS for giving me the solution to the "dancing" screen issue

Download
The files for this device are hosted on my Github. The more recent download can be retrieved from the link below. If you want an older release, then you need to go to the third post in this thread (Release History).

Download Link: https://github.com/Eagerestwolf/cwm-recovery-y301a1/releases/latest


Installation Instructions

1. Download the file listed above
2. Install the Android SDK on your PC. For more information on doing so, Google it.
3. On your phone, open the settings app, swipe to the left so you are on the all tab, and scroll to the bottom. You should see an option that says Fast Boot. Make sure that option is turned off.
4. Turn off the device.
5. Pull the battery for 10 seconds (annoying, but necessary)
6. Place the battery back in your phone, and press and hold POWER + VOLDOWN for 10 seconds, when you release the buttons, your phone should stay at the Huawei Logo if you did everything correctly
7. If your phone booted normally, just repeat steps 4 - 7
8. Open a terminal (Linux and Mac) or Command Prompt and change to the directory you downloaded the file to.
9. Next type

   fastboot devices

10. You should see a line that says something like

    34230cc2        fastboot

    If you don't, check your drivers.
11. Now type the following command and MAKE SURE YOU TYPE IT CORRECTLY, if you don't, this process can brick your device

    fastboot flash recovery {filename}

12. Now type

    fastboot reboot

13. As soon as your phone's screen goes blank press and hold the VOLUP button until your device boots into recovery.
14. If your device opens Clockworkmod, good you are done. If it pulls up Huawei recovery, then you have an issue, leave a reply to this thread and I will help you to the best of my ability.

 

[EagerestWolf]

FAQ

Q: Where can I get fastboot and adb?
A: They are both available as part of the Android SDK, which can be obtained here.

Q: Where can I find all of the releases (current and older)?
A: My Github (https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases)


More to come...

 

[EagerestWolf]

Complete Listing: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases

Releases
Version 2.0.0 (Based on Clockworkmod 6.0.4.3)
Download Link: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases/tag/v2.0.0

Version 1.1.0 (Based on Clockworkmod 6.0.3.7)
Download Link: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases/tag/v1.1.0

Version 1.0.1 (Based on Clockworkmod 6.0.3.7)
Download Link: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases/tag/v1.0.1

Version 1.0.0 (Based on Clockworkmod 6.0.3.7)
Download Link: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases/tag/v1.0.0

Version 0.5.0 (Based on Clockworkmod 6.0.3.7)
Download Link: https://github.com/Eagerestwolf/cwm-huawei-y301a1/releases/tag/v0.5.0

 

[Spec2nirvash]

Oooooh! CWM for the Valiant? Damn wolf, haven't seen you in a long time!

So this is good eggs. A couple of things:

About that weird screen issue.... There is a CWM built for the Huawei M931 Premia. The final result is most crucial functions work, but the scrolling screen jump is something that couldn't be fixed, probably due to time spent on it. But it works

Also, I think over in the Huawei Vitria forums, KainXS has/found a CWM in the works? My question is:

I own a Valiant (Y301-A1) as well as a Vitria (Y301-A2). These phones seem pretty much identical except for the Valiant being a 3G, Dual core 1GHz/1GB RAM. Vitria is 4G capable, 1.2GHz/1GB RAM. So can anything from Vitria be used with Valiant? I know CPU difference is one of many factors that decide if it can or not, but maybe?

I dunno, just throwing that out there. Good to see you back!

 

[EagerestWolf]

Thanks, it's nice to be back, and in full swing no less. I will jump over there, and see what I can get. Only thing I really want to do at this point is confirm for sure the sdcard0, sdcard1, and sd-ext partitions. Beyond that and the screen issue, this is in release ready state.

As for your question, I would say almost definitely not. CPU is the deal breaker, plus the Vitra for some odd reason runs on a completely different chipset. Plus it has flash, which leads me to believe the camera may be different, not sure though.

 

[DeadDude]

I don't know if this helps but changing the SD card to save on external seems to swap SD0 and SD1.

And there is a just over 1 gigabyte internal sd card that once you toggle external storage for install location it seems to no longer permit saving data to that internal SD storage.

I really don't know much about what I'm talking about

But if anyone out there needs more details please feel free to message me or someone who knows more.

I would test this except I don't know if I would lose data because my machine says if I change that setting programs will no longer have access to my sd card. Its not that I have a lot of data to lose I've just never gone through the steps myself on an Android device. It doesn't seem to be something you can toggle try out and then toggle back and be right back where you were can anyone confirm?

Thanks in advance for all the help and headway you guys have been making, and if there's any way a total newbie can help let me know.

 

[EagerestWolf]

Actually what happens with clockworkmod is you can only access your external sdcard right now. I am trying to change that, but I don't want backups to save to the internal sdcard (no room)

 

[EagerestWolf]

New bug, for anyone who is actually following this thread devoutly. In my testing of Cyanogenmod, I came across a very unsavory bug: Clockworkmod cannot install zip's. Every single zip you try to install (with or without asserts) will result in "(no error reported) the script has ended suddenly. Stopping. (Status 7)". As a result Cyanogenmod is on hold until I can fix this bug.

 

[EagerestWolf]

A quick update on the progress of this. It turns out the script install errors were because Clockworkmod does not recognize the ext4 filesystem by default unless you put a certain flag in your BoardConfig.mk. As for storage, it turns out the HWUserData partition is the internal storage, so I will be getting that setup soon, hopefully.

 

[DeadDude]

Yay!

 

[EagerestWolf]

Updated. Now supports internal and external storage. Still cannot format partitions ext4.

 

[EagerestWolf]

Okay, so in the process of making a new version of Clockworkmod because you have to have the newest version for KitKat, and I am having a new issue, for some reason, the device will not boot into recovery. Instead it just reboots back to Android. I am sure this is a generic issue. Probably just a misconfiguration somewhere. But, I just want people to know this project is not dead. I am just kinda stuck in a build/test/clean/repeat cycle at the moment.

 

[EagerestWolf]

Found all of my errors. I have been using the wrong defconfig. For some reason, even though the build.prop says it does, this device does NOT have a Qualcomm msm7x27a chipset. It has a Qualcomm msm8x25 chipset. Found this in the /proc/config.gz

CONFIG_MACH_MSM8X25_Y301_A1=y

 

[DeadDude]

Forgive me, but I am lost...

To tweak your android operating system, you need a custom recovery in case you brick, right?

I've tried to read up...

I thought the recovery partition had nothing to do with the system os? Aside from loading it of course?

Also, I thought KitKat needed a min one gig of RAM?
Won't it be over powered or laggy?

I don't require a personal response, I can click a link and read..

 

[rbheromax]

Forgive me, but I am lost...

To tweak your android operating system, you need a custom recovery in case you brick, right?

I've tried to read up...

I thought the recovery partition had nothing to do with the system os? Aside from loading it of course?

Also, I thought KitKat needed a min one gig of RAM?
Won't it be over powered or laggy?

I don't require a personal response, I can click a link and read..

recovery is just for flashing which can be used to apply themes, scripts, mods etc

you dont NEED It right now, because if you bootloop your phone, you can always boot to fastboot, flash cwm and fix stuff

Minimum KitKat requirements:
1 GHz Single Core msm7x30 or higher (this one is a msm8625 which is a beefed up 7x27a)
512 MB RAM or higher
Adreno 2xx or higher

It'll run KK no problem

 

[DeadDude]

recovery is just for flashing which can be used to apply themes, scripts, mods etc

you dont NEED It right now, because if you bootloop your phone, you can always boot to fastboot, flash cwm and fix stuff

Minimum KitKat requirements:
1 GHz Single Core msm7x30 or higher (this one is a msm8625 which is a beefed up 7x27a)
512 MB RAM or higher
Adreno 2xx or higher

It'll run KK no problem

I thought flashing required CWM? To clarify, doesn't CWM mean clockwork mod recovery?

I realize a PC can be utilized to flash the ROM, but the only on_the_go solution it's CWM, right (or TWRP)?


Maybe I should just ask outright...

What do I need to be able to safely modify my device without a PC present?

I am looking into activating USB Host, as an example.

I am fiddling with DPI settings.

I am tweaking GFX in system files.

I am trying to load more fonts directly.

I am tweaking my keyboardS.

I want to move my status bar to the bottom of the screen.

I want to change the behavior of the hardware buttons in specific situations.

I want to stop screen dimming before turning off.

Found three ways to manually modify my battery icons... I know at least one can brick me. Specifically, editing the resource file(s).

Most importantly, I need to be able to load a backup ROM without a PC present.

Sorry for the list, but I wanted enough examples so you can tell me what I need.

I have already managed to soft brick twice...

I thought CWM was the correct tool...? Safety net?

 

[DeadDude]

Oh yeah... and I'm running out of space, since I copy the files I edit in place with .bak appended.

 

[rbheromax]

I thought flashing required CWM? To clarify, doesn't CWM mean clockwork mod recovery?

I realize a PC can be utilized to flash the ROM, but the only on_the_go solution it's CWM, right (or TWRP)?


Maybe I should just ask outright...

What do I need to be able to safely modify my device without a PC present?

I am looking into activating USB Host, as an example.

I am fiddling with DPI settings.

I am tweaking GFX in system files.

I am trying to load more fonts directly.

I am tweaking my keyboardS.

I want to move my status bar to the bottom of the screen.

I want to change the behavior of the hardware buttons in specific situations.

I want to stop screen dimming before turning off.

Found three ways to manually modify my battery icons... I know at least one can brick me. Specifically, editing the resource file(s).

Most importantly, I need to be able to load a backup ROM without a PC present.

Sorry for the list, but I wanted enough examples so you can tell me what I need.

I have already managed to soft brick twice...

I thought CWM was the correct tool...? Safety net?

as long as you dont go out and start fiddling with stuff with backups to sd you shouldnt need a pc

usb host needs to be enabled in kernel ( i may be able to help with that later)

the rest of those mods SHOULD (stuff does happen to break here and there) be safe to mod thru Xposed. things like themes and mods cant be applied to odexed roms (which im sure you have on stock)

 

[DeadDude]

Methinks I need to find a decent primer on the topic.

I would like to take my Xposed tweaks and make them direct edits.

I would like to write some of my own as well.

I currently enjoy custom DPI settings on a per app basis... Would like to break away from "man in the middle" tweaking.

Want to over clock. Have reason to want to remove metropcs crap forever. I don't expect Huawei to ever update the firmware...

I've toyed around with the idea of loading system apks from other devices. (It should be safe if the chips match, right?)

I'm not sure if you would call the end result a custom ROM or what... based on stock...? Thanks for the help!


EagerestWolf- I have been trying to upload my system.img file, drop box errors out over night.

 

[EagerestWolf]

Methinks I need to find a decent primer on the topic.

I would like to take my Xposed tweaks and make them direct edits.

I would like to write some of my own as well.

I currently enjoy custom DPI settings on a per app basis... Would like to break away from "man in the middle" tweaking.

Want to over clock. Have reason to want to remove metropcs crap forever. I don't expect Huawei to ever update the firmware...

I've toyed around with the idea of loading system apks from other devices. (It should be safe if the chips match, right?)

I'm not sure if you would call the end result a custom ROM or what... based on stock...? Thanks for the help!


EagerestWolf- I have been trying to upload my system.img file, drop box errors out over night.

It's cools. Whenever you get it. I have been working hard on this stupid Cyanogenmod stuff. Also, you mentioned earlier that recovery and OS are unrelated. In general, yes, that is true. However, KitKat and 4.3 require SELinux to boot (SE Linux is a basically a boot manager), and that is only available in Clockworkmod 4.0.3.8 (the KitKat version). The downside to this is that we can no longer do getprops and asserts (commands to make sure you are running the correct phone) because Google changed how these work in KitKat. So, yeah, fun. Whenever you get it, you get it. Overclocking will come eventially, once I actually feel like doing a menuconfig on the kernel to enable it because I am not reading a defconfig to find the option.

 

[rbheromax]

It's cools. Whenever you get it. I have been working hard on this stupid Cyanogenmod stuff. Also, you mentioned earlier that recovery and OS are unrelated. In general, yes, that is true. However, KitKat and 4.3 require SELinux to boot (SE Linux is a basically a boot manager), and that is only available in Clockworkmod 4.0.3.8 (the KitKat version). The downside to this is that we can no longer do getprops and asserts (commands to make sure you are running the correct phone) because Google changed how these work in KitKat. So, yeah, fun. Whenever you get it, you get it. Overclocking will come eventially, once I actually feel like doing a menuconfig on the kernel to enable it because I am not reading a defconfig to find the option.

If you can get CyanogenMod to boot, Ill get the overclock done, although i'll need someone with fastboot experience to test it

 

[EagerestWolf]

Fastboot I can do no problems. Over the course of my testing, I have gotten really REALLY good at using fastboot.

Also, changing the kernel config does now allow Clockworkmod to boot, however my display does not initialize. I removed the TARGET_RECOVERY_PIXEL_FORMAT which may bring back the dancing, but it should also help the display initialize.

 

[EagerestWolf]

Updated. Can now format partitions via update-scripts. Touchscreen now functions as a back button. Off-mode charging now works. All of that said, let the ROM making commence (For everyone else that is, I have to focus my efforts on Cyanogenmod).

 

[District520]

Hey how did you unlock the boot loader? I tried sending a email to huawei's email address mobile@huawei.com and its been a week and no response also I tried DC-Unlocker and it won't detect my device when in download mode. Are there any other alternatives to try?

 

[EagerestWolf]

Idk then. Just be patient, it is around the time of Chinese New Year so Huawei may be a bit backed up. DC-Unlockr will only work on 32-bit windows and you have to follow their instructions to the letter. It works I used it after I emailed huawei just so I could confirm that it works