• Announcements

    • PaulOBrien

      Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance) CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission) ROMs must give full credit to the original author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
tilal6991

[ICS] CyanogenMod 9 for the Ascend G300 [LINK UP]

367 posts in this topic

It installs but just sitting at the Huawei screen now.

Same with me

0

Share this post


Link to post
Share on other sites

As I said there was a possibility that it wouldn't boot. Could you get an adb logcat. And have you wiped data?

0

Share this post


Link to post
Share on other sites

I am not able to test as I am out at moment,but I wonder is it partition size preventing boot? What is system size of cm9.

Edit: forget that,I just looked at my system size And I have nearly 400mb system size,so that would not be an issue. :lol:

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Anyone?

0

Share this post


Link to post
Share on other sites

looking into it..

whats a adb logcat?

0

Share this post


Link to post
Share on other sites

hnmm seems to be jammed at "waiting for device"

0

Share this post


Link to post
Share on other sites

downloaded the SDK developer kit, ran

adb logcat

after puttiing the device into boot (volume down and power button held at boot) but im just getting waiting for device

1

Share this post


Link to post
Share on other sites

Then its the kernel / boot image at fault. I will look into it tommorow.

0

Share this post


Link to post
Share on other sites

Did you move the 2 DLL files. When you plug in the phone in bootloader mode, 2 DLL files are generated. I presume these are the driver links.These need to be moved to another folder which then links them to the phone.

0

Share this post


Link to post
Share on other sites

Nice to see this thread for the g300 :) Thanks tilal.

0

Share this post


Link to post
Share on other sites

copy the Adb.exe, AdbWinApi.dll and

AdbWinUsbApi.dll files, found in the <SDK

directory>/platform-tools directory, into the

<SDK directory>/tools directory.

0

Share this post


Link to post
Share on other sites

yep moved teh files across but still get waiting for device. I don't get the pop up internal drive with the drivers coming up either while using the rom, hnm maybe they don't come3 up anyway in this boot mode. my pc is kind of shaking though and im new at this so i may have made a mistake somewhere down the line

0

Share this post


Link to post
Share on other sites

This is all logcat gives me...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

- exec '/system/bin/sh' failed: No such file or directory (2) -

I'm sure this is something the guy messing with boot img and kernel etc mentioned in his thread at some point.

0

Share this post


Link to post
Share on other sites

I couldn't get anything off logcat either but I assumed it was because my ADB wasn't working properly (as usual)

0

Share this post


Link to post
Share on other sites

Adb is working for me for definite as you see above... small progress is still progress lol. I just hope tilal doesn't get too distracted from his exams. But still good to see him start on g300 stuff before he even gets one.

1

Share this post


Link to post
Share on other sites

Woo, I didn't expect Tilal to start working on CM9 this soon. This handset's got a great future ahead of it.

1

Share this post


Link to post
Share on other sites

There are 2 known people working on Ics for the G300

0

Share this post


Link to post
Share on other sites

There are 2 known people working on Ics for the G300

2.....who is other dev? I did not know about this.

0

Share this post


Link to post
Share on other sites

Omegemoon is working on it also.

0

Share this post


Link to post
Share on other sites

@Frankish

Could you do the following if you can:

Flash the rom.

Go to mounts and mount system partition in cwm.

Type adb shell chmod 777 /system/bin/* in your computer

And see if logcat works.

0

Share this post


Link to post
Share on other sites

Will do later. Unfortunately im on a late again so finish at 10.

0

Share this post


Link to post
Share on other sites

Flash the rom.

Go to mounts and mount system partition in cwm.

Type adb shell chmod 777 /system/bin/* in your computer

And see if logcat works.

Doesnt change anything, still

exec '/system/bin/sh' failed: No such file or directory (2) -

Edited by maaslo
0

Share this post


Link to post
Share on other sites

I may of done something wrong the first time, but the system folder did not flash at all, but after mounting system and flashing again all the files went into the right place.

did chmod on system/bin and rebooted. Still stuck on Huawei logo and adb logcat still shows

exec '/system/bin/sh' failed: No such file or directory (2)

so could it be that the system partition is not mounted during the boot process?

0

Share this post


Link to post
Share on other sites

exec '/system/bin/sh' failed: No such file or directory (2)

Common problem it seems... /system/bin/sh doen't exist.

@tilal6991: symlink /system/bin/mksh to /system/bin/sh in order to make this work

0

Share this post


Link to post
Share on other sites

Just tried to flash the CM9 system with the 3.0.8 kernel... System dies very early in the startup.

See the logging here

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.