• Announcements

    • 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 softwareNintendo 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 authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • 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.

[JB] [CM10] [4.1.1] CyanogenMod 10 for the ZTE Crescent [ROM] [Last updated: 01/09]

780 posts in this topic

Posted

Delete /system/media/bootanimation.zip, might just be the problem all the ZTE devices are having.

0

Share this post


Link to post
Share on other sites

Posted

Delete /system/media/bootanimation.zip, might just be the problem all the ZTE devices are having.

I'll try to adb shell at boot animation

0

Share this post


Link to post
Share on other sites

Posted

New builds are up.

0

Share this post


Link to post
Share on other sites

Posted

If you're going to use adb...

remount filesystem in rw mode

cmd: adb shell mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system

2. make a copy of the file before deleting

cmd: adb pull /system/media C:\andbackup

3.login into shell to delete file

cmd:

adb shell

cd /system/media

rm bootanimation.zip

exit

0

Share this post


Link to post
Share on other sites

Posted

eh... something just happened and I'm at the initial setup screen ???

0

Share this post


Link to post
Share on other sites

Posted

That's completely unnecessary.


adb shell
> mount -o remount,rw /system
> rm /system/media/bootanimation.zip
[/CODE]

0

Share this post


Link to post
Share on other sites

Posted

If you're going to use adb...

thanks, I was trying to get su in adb shell and it was saying permission denied.... then i tried rm /system/media/bootanimation.zip and obviously it said that its a read-only FS. but then I looked at the screen and I was at the android setup screen. I have no idea how ...

0

Share this post


Link to post
Share on other sites

Posted

New builds are up.

should i sync again and install?

0

Share this post


Link to post
Share on other sites

Posted

Isn't that what I just posted, reformatted?

Anyway....

Will lalit's build of gapps with the working Google Now work? (http://goo.im/devs/tilal6991/gapps)

0

Share this post


Link to post
Share on other sites

Posted

No, because I'm not screwing around with this "codepage=utf8,vfat,xattr,check=no /dev/stl5".

...and considering the Crescent and Skate are just two of the million variations of the Blade, then yes it will work.

0

Share this post


Link to post
Share on other sites

Posted

should i sync again and install?

Hmm?

0

Share this post


Link to post
Share on other sites

Posted

That's completely unnecessary.


adb shell

> mount -o remount,rw /system

> rm /system/media/bootanimation.zip

1|shell@android:/ $ mount -o remount,rw /system

mount: Operation not permitted

How do you get around the root problem

0

Share this post


Link to post
Share on other sites

Posted

1|shell@android:/ $ mount -o remount,rw /system

mount: Operation not permitted

How do you get around the root problem

Your build is userdebug right?

You're a bit buggered. You can't "su" as you have to enable it in developer options, which is out of reach...

0

Share this post


Link to post
Share on other sites

Posted (edited)

I have no idea how the boot fixed itself, but i've removed the bootanimation anyway.

Installation of paid apps from the play store doesn't seem to be fixed yet.

I need to get some sleep, will test tomorrow

Edited by MadEye Moody
0

Share this post


Link to post
Share on other sites

Posted

How to brush into the?如何刷入?

0

Share this post


Link to post
Share on other sites

Posted (edited)

Notification light - working

Power widget - working

Google Now - crashed after setup, trying tital's gapps + google voice search apk

Bluetooth - no audio. pairs with headset, shows (no phone). wont play music either

Play store - error when installing paid apps

BTW, A2SD was working in R1 as well, you just needed to free up some space in system before installing it.

Edited by MadEye Moody
0

Share this post


Link to post
Share on other sites

Posted

Are you using tilal's Google apps? It shouldn't crash if so.

The goo.im ones I think have some ARMv7 weirdness.

0

Share this post


Link to post
Share on other sites

Posted

Are you using tilal's Google apps? It shouldn't crash if so.

The goo.im ones I think have some ARMv7 weirdness.

Havn't yet tried with tital's gapps ...

0

Share this post


Link to post
Share on other sites

Posted

New builds up!

0

Share this post


Link to post
Share on other sites

Posted

New builds up!

wow... 2 builds in a day, and its not a fix build either

0

Share this post


Link to post
Share on other sites

Posted

Hi just flashed latest build, it all seems great but I am having an issue with USB mass storage I get the UI is not responding and it closes. I ran an adb log cat and got the following info..

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity.checkStorageUsersAsync(UsbStorageActivity.java:299)

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity.access$900(UsbStorageActivity.java:60)

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity$9.run(UsbStorageActivity.java:279)

E/AndroidRuntime( 3507): at android.os.Handler.handleCallback(Handler.java:615)

E/AndroidRuntime( 3507): at android.os.Handler.dispatchMessage(Handler.java:92)

E/AndroidRuntime( 3507): at android.os.Looper.loop(Looper.java:137)

E/AndroidRuntime( 3507): at android.os.HandlerThread.run(HandlerThread.java:60)

W/ActivityManager( 324): Force finishing activity com.android.systemui/.usb.UsbStorageActivity

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:7802880 fd:30

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x57bc4000 size:8171520 offset:7802880 fd:258

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:1536000 offset:12533760 fd:52

D/memalloc( 458): /dev/pmem: Mapped buffer base:0x548c0000 size:14069760 offset:12533760 fd:46

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:1536000 offset:14069760 fd:65

D/memalloc( 458): /dev/pmem: Mapped buffer base:0x56c08000 size:15605760 offset:14069760 fd:52

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x52034000 size:4608000 offset:3072000

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x52d04000 size:6266880 offset:4730880

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41aca000 size:1536000 offset:3072000 fd:32

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41c5f000 size:1536000 offset:4730880 fd:45

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x53300000 size:7802880 offset:6266880

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41dd6000 size:1536000 offset:6266880 fd:49

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:8171520 fd:32

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x58390000 size:8540160 offset:8171520 fd:257

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:8540160 fd:45

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x59a94000 size:8908800 offset:8540160 fd:263

It mounts fine still in clockwork mod recovery. Any ideas?

0

Share this post


Link to post
Share on other sites

Posted

[/quote

Hi just flashed latest build, it all seems great but I am having an issue with USB mass storage I get the UI is not responding and it closes. I ran an adb log cat and got the following info..

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity.checkStorageUsersAsync(UsbStorageActivity.java:299)

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity.access$900(UsbStorageActivity.java:60)

E/AndroidRuntime( 3507): at com.android.systemui.usb.UsbStorageActivity$9.run(UsbStorageActivity.java:279)

E/AndroidRuntime( 3507): at android.os.Handler.handleCallback(Handler.java:615)

E/AndroidRuntime( 3507): at android.os.Handler.dispatchMessage(Handler.java:92)

E/AndroidRuntime( 3507): at android.os.Looper.loop(Looper.java:137)

E/AndroidRuntime( 3507): at android.os.HandlerThread.run(HandlerThread.java:60)

W/ActivityManager( 324): Force finishing activity com.android.systemui/.usb.UsbStorageActivity

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:7802880 fd:30

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x57bc4000 size:8171520 offset:7802880 fd:258

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:1536000 offset:12533760 fd:52

D/memalloc( 458): /dev/pmem: Mapped buffer base:0x548c0000 size:14069760 offset:12533760 fd:46

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:1536000 offset:14069760 fd:65

D/memalloc( 458): /dev/pmem: Mapped buffer base:0x56c08000 size:15605760 offset:14069760 fd:52

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x52034000 size:4608000 offset:3072000

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x52d04000 size:6266880 offset:4730880

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41aca000 size:1536000 offset:3072000 fd:32

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41c5f000 size:1536000 offset:4730880 fd:45

D/memalloc( 3507): /dev/pmem: Unmapping buffer base:0x53300000 size:7802880 offset:6266880

D/memalloc( 113): /dev/pmem: Freeing buffer base:0x41dd6000 size:1536000 offset:6266880 fd:49

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:8171520 fd:32

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x58390000 size:8540160 offset:8171520 fd:257

D/memalloc( 113): /dev/pmem: Allocated buffer base:0x417dc000 size:368640 offset:8540160 fd:45

D/memalloc( 324): /dev/pmem: Mapped buffer base:0x59a94000 size:8908800 offset:8540160 fd:263

It mounts fine still in clockwork mod recovery. Any ideas?

Probably Just a CM10 Problem. Its not your phone, man. And it will work in CWM because that has nothing to do with CM10 :)
0

Share this post


Link to post
Share on other sites

Posted

I know it is not my phone it was just a report of an issue and hopefully with some useful info to fix it. Love this CM10 Rom some great work by Dazzozo and all the others who help bring it to our phones

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-2015. MoDaCo uses IntelliTxt technology.