Stuck at boot screen after installing a font pack - help?

18 posts in this topic

Hi I've got a Huawei Ascend Y300 which I decided to root last night. I used the method described here using the files from that page too, and it all went fine. I was installing some font packs afterwards which required me to reboot, after a few times it got stuck on the boot screen. I'm now not able to get it back up and running.

I tried the same method as I originally used to root (putting the same files in 'dload' on the sd card and restarting with both vol buttons held), that goes through and says update ok, but it still hangs at the boot screen.

Can anybody talk me through fixing this? I can get the phone on the pink screen (download mode? although I can't access it from the computer), and also into recovery mode. I've got a card reader so I can transfer files onto the phone that way. If you need any more info then please ask!

Share this post

Link to post

Share on other sites

U cant recover ur phone back to life with that b175 as most of the y300 have versions higher thn ths. So ur update will fail if u do with b175. Update needs same or higher version of firmware. This is my limited experience :-)

Share this post

Link to post

Share on other sites

That all sounds promising jackosterman! Could I trouble you in pointing me in the direction of more information/instructions on how to go about these things? I've read a lot in the last 12 hours and a lot of it is now blurring into one!

How do I go about unlocking the bootloader when the phone is in its current state? Did I read somewhere that I need some information from the phone to get a bootloader unlock code from huawei?

Share this post

Link to post

Share on other sites

There is easiest way than clean instal if you get bootloop after changing some system files. You need adb installed on your computer and files from orginal system (you can get them from updateapp via repacker - firstly you get img files, then you need some img unpacker or get from someone nandroid backup and unpack this). You also should know what was changed before bootloop. Than:

5 if you see line ended with # there all is ok. Use CTRL+C to back to cmd

6. Type:

adb remount system

adb push [destination of file you want to push from your pc for example C:/framework.res] [destinantion where file should go on device for example /system/framework]

7. If its not succes you can also try copy files to your sd. Than in cmd adb shell. Than you should mount your sdcard (i forgot command google it) and copy it to system with cp command.

And also this method of root is good for people like me. I don't want to loose warranty( in my country repair service provider use argument of soft modding often). Relocking bootloader before sending still leave some trace of unlocking. During unlocking bootloder DRM keys are deleted from hidden partition (forever - you can get them back, only if you make image of them before unlocking. But restoring process is even danger than flashing roms or make modyfication. It can really brick your phone with no return). Its really easy to check if your bootloader was unlocked and relocked. In same time, checking if there was root is almost impossible (if you flash stock they can only check how many times you flash your device).

Edited October 29, 2013 by ragan_y

0

Share this post

Link to post

Share on other sites

Yeah bick I was thinking earlier about trying a few custom ROMs to see what's what!

I've only ever messed with an older version of android before and I've had boot loop so many times (on the same phone) but I've always been able to flash it with no problems. That was ages ago now though and I must admit I felt a bit out of my depth here.