[Android Q&A, Help & Troubleshooting] khat17:
Hi all. Let's get right into this. I've searched through and not found anything relating to this model where de-brick or original ROM files are concerned. I did a lot of saerching online and found a file online -> HUAWEI_Y301-A1_V100R001C85B132_MPCS.rar <- which I've also uploaded to a Google drive. Still can't post links yet so change the link info so that you can get to the file.

hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCNGJMMkxScVZyLVU/view?usp=sharing

I had a power cut when this was being uploaded - I think it finished but here are the hashes just in case:

Size: 440800365 bytes

ADLER32: dd052c58

CRC32: 314ea95f

MD2: f715fbc043377f30f0c6f92c1383f873

MD4: cdf28659286b47bf28f0bfb6210fe0c9

MD5: 6e4630c80f13235f12b07fa5bd5e7346

SHA1: afd4f30c15ba10c3327fa4455390018f96ae5837

SHA256: 2574ab1738009dac9898e08b57ad1ca03ed3e1c81144a72878f995b1eac72e81

SHA384: 38957eed51fcd2454cc2a0d94c4444f328aecdbc137f08573d089efd4e53ce0d486c475444b24ef4fbf9a391ec469b86

SHA512: 0a90b915141e63acef101e16dc83ac1e6659f44a153f16d72c5e7c18d87ef7be1331ba9475a14940fccd5fe40d9aeb13ac8f38a26890759fee16b3da56065d8d

RIPEMD128: f45c58b04184e4e122c5d4d8012ec53d

RIPEMD160: 1ba1ad8a75d1fb8e1344d8a42202bc2def7605ac

TIGER128: 5c53dfde6780cac34be867d862b913b3

TIGER160: 5c53dfde6780cac34be867d862b913b319cda8df

TIGER192: 5c53dfde6780cac34be867d862b913b319cda8df8b6dc1ba

GOST: 78b80fd7833de57d4ded26b64a7ca0586e9601e7cd7243e448cd997653957adf

Some persons may also want the drivers for this to be recognized when plugged in. That's in the next link:

hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCMlBFQlNuYXZCeG8/view?usp=sharing

Hashes:

SIZE: 6698970 bytes

ADLER32: 769c16b0

CRC32: f0782916

MD2: a535a3cec1f0a612db9a580fd8b8fca9

MD4: 13580fd5702c7db7e0db223de67be8b4

MD5: f2d0ca441f5d28eb489e466afff7ead7

SHA1: 4af3bd670ffbe1b59bd193fd3ab03e5a2fc4d179

SHA256: b53efde84db8a8c93afcea30d0159e75af49ebf6352b7b34691fc4a142291eb1

SHA384: eaac94fcae45435bdbd44d98b6b001cc7b59adcf9f84c980cb3edba6d42eb8784323720df28a6076d59582788ff12af5

SHA512: bceef8964c38bcff785be78eb16aaa25de7c7510da8f63b31e118d5dc071c912399b40f5f5d9fccf6cd4dcd61b1d7543eb9175133aeff9404917a033f1aea3bf

RIPEMD128: 325cb61d9610cedd3aed33b2afd45a1d

RIPEMD160: ed2e20baaa9deb38ef4a792ddba127d23cf9ecab

TIGER128: 41646e0d7e97637ac837bfdc780513f6

TIGER160: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee

TIGER192: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee29d2db73

GOST: 23050f83375d15b1a22346c3ac7ddaa3d927ba97c81ba7b03d9f580a33b781e4

To continue here's the issue I'm having which I guess a few other persons have as well - the phone appears to be bricked. It powers on and either goes directly to a blue screen or shows the Huawei logo then goes to the blue screen.

After much searching I found the file I linked to. When extracted the file is 800+MB and gives you a file called UPDATE.APP when extracted and is in a folder called DLOAD which you're instructed to put in the root of your SD card and put in the phone.

My problem is this: It boots and seems to start a loading process but the bar sticks at about 30% and doesn't move. This may be because the memory in the phone is corrupted/bad but it could be that the file I'm using is wrong. Who knows? Anyways - this thread is started as both a question and an answer thread.

My questions would be - is there anything else to try?

The answers provided include the location of drivers, a firmware file and instructions on how to get it done.

I'd also like to add this document I found:

hxxps: //www .scribd .c0m/doc /215227240/Confidential-Huawei-y301-A2-v100r001c85b132-Upgrade-Guideline

This shows the process for the A2 but I believe it's applicable here.

Also I'd like to point out that I've found some other files online but the RAR file I mentioned is the only one with an UPDATE.APP file - others have actual files in there and I'm not sure if the UPDATE.APP is really just a ZIP file with the info or if it was created with some specialized program to have a certain structure or something.........not a dev so I don't know.

Additional info would probably be that I can get the phone to a pink/purple (I'm a guy - I'm color blind) screen by holding VOL+/VOL-/PWR but I'm unable to use any commands to find the phone - ADB or FASTBOOT - because the drivers I have only show the device as a COM port and a modem in Windows. Haven't tried in Linux.

Any assistance in this would be greatly appreciated. Thanks in advance.

When I get to my 10 posts or more then I'll post pics.

*EDIT*

I checked the SD card after the last update failure and found a file called SD_UPDATE.LOG. Contents are below: