[ROM][Unofficial][4.1.2] CyanogenMod 10 Nightlies for the Wildfire S (marvel)[16-04]

Status
Not open for further replies.
Search This thread

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
u5Nmq.jpg


INFO ABOUT THIS STUFF

DISCLAIMER
Code:
[COLOR="Red"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or 
* unfulfilled sexual partners. Please do some research if you have any 
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh. */[/COLOR]
Will try to realease a Nightly every 2nd Day...not really NO! There aren't many changes that come in every day. Only changes from git.cryptomilk.com or from androidarmv6s' GitHub repo. So: I'll definitely release a new build each time something changes respectivelly something is listed under the command "repo sync -c"​

INSTALLATION

FIRST INSTALLATION OF THIS DUDE
Download the latest CM10 build
Download the 4.1.2 stripped GApps
Put both zips into the root directory of your SD Card: /storage/sdcard/0/
Boot into your Custom Recovery
"wipe data/factory reset"
"wipe cache partition"
"advanced" > "wipe battery stats"&"wipe dalvik cache"
"mounts and storage" > format everything except sdcard
Flash both zips with the Recovery with "install zip from sdcard" > "choose zip from sdcard"
Reboot
Enjoy the new flavour of Android 4.2.2 Jelly Bean

OPTIONAL
Eoghan's kernel:
Download Eoghan's kernel
Put the zip into the root of your SD Card: /storage/sdcard0
Flash the ROM
Flash the kernel
(Flash the INT2EXT4+ Script as described below)
Flash the GApps
Reboot into system

INT2EXT4+ Script:
Download the INT2EXT4+ Script
Put the zip into the root of your SD Card: /storage/sdcard0
Flash the ROM
(Flash the kernel as described above)
Flash the INT2EX4+ Script
"mounts and storage" > "format /sd-ext"
Flash the GApps
Reboot into system

UPGRADING
Download the new build
Flash it with "install zip from sdcard" > "choose zip from sdcard"
Also flash the kernel and the INT2EXT4+ (without formatting SD-Ext after) again
Reboot

FIXING PROBLEMS AFTER UPGRADING
"Lost" your Google Account?: Reflash the GApps

FIXING PROBLEMS WITH GAPPS
Use the "Cache GApps" instead

FEATURES

Now Playing
Sound Search for Google Play/Google Ears
Google Play Store v4.0.25
Facebook Home

WHAT WORKS

Camera
Hotspot
Bluetooth Tethering
Google Now
New Clock
WLAN
Mobile Data
USB Thetering (with any 3rd party App)
Wake-Up issue
Electron Beam Animation
Autobrightness

WHAT DOESN'T WORK

Camcorder
Panorama mode
YouTube
Laggy scrolling

CHANGELOG

PREAMABLE
All Nightlies will include the latest CM-Upstream stuff. You can review what has changed here!

16-04-2013
-CM upstream stuff (too much to list like down below)
-Google Play Store v4.0.25 added
-Facebook Home added

09-04-2013
-hardware_qcom_audio
-vendor_cm
-Settings
-Trebuchet
-Added Google Ears v1.1.8
-Added Now Playing

30-03-2013
-Fixed Wake-Up issue
-Fixed Electron Beam Animation
-Fixed Autobrightness

19-03-2013
-android_bionic (WinSuk)
-device_htc_marvel_common (git.cryptomilk.org)

16-03-2013
-Way back to jellybean branch
-CM upstream stuff

02-01-2013
-CM-Upstream Stuff

01-01-2013
-Use jellybean-stable branch now

DOWNLOADS


CREDTIS


All my testers (for bug reporting and supporting)
Jack Underwood (Now Playing)
djolivier+thehacka1 (Bug fixing)
OliverG96+dudeman1996
izi501 (Cache GApps)
Google Drive (hosting)
CyanogenMod
Facebook
Google
 
Last edited:

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
Started working on CyanogenMod 10.1

And another great news is just coming in, this time from Benjamin:

About Jellybean 4.2

As jellybean 4.1 is fairly stable, I should move onto porting this device to jellybean 4.2.

For now, CM has no real features, but they did say in their Google + post that the building scripts are there, so it should build.

FAQ Time! :

Special noob said:
Will super-waffle-data-2-sd-hack (or some other random data2sd hack) work on this rom?
I honestly don't know why so many people ask this question. Go test it, if it works, cool, if not, this ROM isn't for you.

Special noob said:
Where have you been?
Working on Project Llama of course (that and fixing my laptop)


Special noob said:
What phone are you getting/have you got your phone yet
Not yet, I hope to be getting either a HTC One S or a Nexus 4. Please don't PM me telling me to get a certain device, because money-wise, I have none.


Special noob said:
This FAQ has nothing to do with jellybean!
You're not asking any jellybean related questions, how is it my fault?


Special noob said:
When will 4.2 for the Wildfire S be released?
1 second - 75 years.

Special noob said:
How can you build this for us if you don't own the device?
I will probably end up asking Ivan to test private builds (no, don't PM me asking, you'll probably get a reply with very rude ascii art of my finger)


Special noob said:
What about the marvelc?
I forgot all about it, I'll start working again on it soon, but no promises this time.


Special noob said:
What about the icong?
I think I'll leave that project at 4.1, unless I'm up for a challenge.


Special noob said:
Will we see anything above 4.2?
Not from me, no. Sorry!


Special noob said:
Why don't you make 4.1 totally stable first?
Something to do that it would be working backwards on a outdated version of Android and having to recode it because it won't work when we eventually update to a newer version...?


Special noob said:
Will you be posting 4.2 on this thread?
No. Some things might not work with 4.2 that worked with 4.1, so it seems logical to keep them on different threads.


Special noob said:
The current version doesn't fit on our phones properly, how will this version cope?
It will, most likely, be worse. I recommend not using gapps or using a stripped version of gapps instead. This way your /system partition won't flood.


Very Special noob said:
thanx u r be5t devz
I know, but that's not a question.

Will start working on this with him tomorrow. Will also seperate CyanogenMod 10 and CyanogenMod 10.1! :)
 
Last edited:
  • Like
Reactions: willand

dudeman1996

Senior Member
Aug 29, 2010
1,137
1,181
24
London, UK
Posting a thread claiming to have a 4.2 ROM in it, without having a clear download link to a 4.2 ROM was a bad idea. If you don't post a build within the next day or two you're gonna get some angry people on your hands.
 
  • Like
Reactions: omkar9496

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
Posting a thread claiming to have a 4.2 ROM in it, without having a clear download link to a 4.2 ROM was a bad idea. If you don't post a build within the next day or two you're gonna get some angry people on your hands.

I will give them a CM10 build tomorrow if GitHub works again.
Already asked Ben about CM10.1 and as many people just can't expect the first 10.1 build for their WFS, I'll try to only compile from CM's sources and not to add missing files from another device tree or from AOSP, as this may take time. So, these builds won't work properly.

Actually, you promised 2/3/4 nightlies per week and we had to wait 16 days (!!!) for a new build after your 08-11. So 20 days for a new build from you (28-11). That was also the reason why I started to compile and mod ;) I won't make them angry, believe me :)
 
Last edited:
  • Like
Reactions: arydan

arydan

Member
Oct 8, 2011
44
15
Montevideo
github now: Battle station fully operational

03:31 PM PST
All repositories are now available. Our sincere apologies for a rough day. :good:

---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------

i'm already angry:mad: Your threads always ytend to disapoint me.

Sent from my Wildfire S A510e using xda app-developers app

don't be angry with devs dude, they work for you for free, without them your device almost dead

if you don't have anything helpful to say just dont say anything please
 
Last edited:

baluuu

Senior Member
Mar 21, 2012
410
154
github now: Battle station fully operational

03:31 PM PST
All repositories are now available. Our sincere apologies for a rough day. :good:

---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------



don't be angry with devs dude, they work for you for free, without them your device almost dead
Pointing you at your own quote right there. You have no idea what you are talking about.
 

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
Posting a thread claiming to have a 4.2 ROM in it, without having a clear download link to a 4.2 ROM was a bad idea. If you don't post a build within the next day or two you're gonna get some angry people on your hands.

I will give them a CM10 build tomorrow if GitHub works again.
Already asked Ben about CM10.1 and as many people just can't expect the first 10.1 build for their WFS, I'll try to only compile from CM's sources and not to add missing files from another device tree or from AOSP, as this may take time. So, these builds won't work properly.

Actually, you promised 2/3/4 nightlies per week and we had to wait 16 days (!!!) for a new build after your 08-11. So 20 days for a new build from you (28-11). That was also the reason why I started to compile and mod ;) I won't make them angry, believe me :)

i'm already angry:mad: Your threads always ytend to disapoint me.

Sent from my Wildfire S A510e using xda app-developers app

github now: Battle station fully operational

03:31 PM PST
All repositories are now available. Our sincere apologies for a rough day. :good:

---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------



don't be angry with devs dude, they work for you for free, without them your device almost dead


Pointing you at your own quote right there. You have no idea what you are talking about.

This thread is just opened, and the first few posts are a discussion. Can we please stop it now?

I,ll give you the first build around 4PM, if my buildbox is up again!

Show respect and patience! Thanks! ;)
 
Last edited:
  • Like
Reactions: arydan and shaarky

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
Good Luck with that :D

Thanks, but I get repo sync errors again:

Code:
From git://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227 
 * [new branch]      jellybean  -> cryptomilk/jellybean
remote: Total 79895 (delta 46875), reused 79380 (delta 46373)
Receiving objects: 100% (79895/79895), 29.11 MiB | 610 KiB/s, done.
Resolving deltas: 100% (46875/46875), done..65 MiB | 883 KiB/s   
From git://github.com/CyanogenMod/android_libcoreB | 1.21 MiB/s   
 * [new branch]      jellybean  -> github/jellybean
From git://github.com/CyanogenMod/android_libcore
 * [new tag]         cm-7.0.0   -> cm-7.0.0
 * [new tag]         cm-7.0.1   -> cm-7.0.1
 * [new tag]         cm-7.0.2.1 -> cm-7.0.2.1
 * [new tag]         cm-7.0.3   -> cm-7.0.3
remote: Total 613658 (delta 373510), reused 600289 (delta 365706)
Receiving objects: 100% (613658/613658), 950.14 MiB | 810 KiB/s, done.
Resolving deltas: 100% (373510/373510), done.
From git://github.com/CyanogenMod/android_frameworks_base
 * [new branch]      jellybean  -> github/jellybean
Fetching projects:  67% (217/323)  
error: Exited sync due to fetch errors
[email protected]:~/building/cyanogenmod/jellybean$
 
Last edited:

TRuth14

Senior Member
Jul 10, 2012
413
52
Kuala Lumpur
Thanks, but I get compiling errors again:

Code:
From git://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227 
 * [new branch]      jellybean  -> cryptomilk/jellybean
remote: Total 79895 (delta 46875), reused 79380 (delta 46373)
Receiving objects: 100% (79895/79895), 29.11 MiB | 610 KiB/s, done.
Resolving deltas: 100% (46875/46875), done..65 MiB | 883 KiB/s   
From git://github.com/CyanogenMod/android_libcoreB | 1.21 MiB/s   
 * [new branch]      jellybean  -> github/jellybean
From git://github.com/CyanogenMod/android_libcore
 * [new tag]         cm-7.0.0   -> cm-7.0.0
 * [new tag]         cm-7.0.1   -> cm-7.0.1
 * [new tag]         cm-7.0.2.1 -> cm-7.0.2.1
 * [new tag]         cm-7.0.3   -> cm-7.0.3
remote: Total 613658 (delta 373510), reused 600289 (delta 365706)
Receiving objects: 100% (613658/613658), 950.14 MiB | 810 KiB/s, done.
Resolving deltas: 100% (373510/373510), done.
From git://github.com/CyanogenMod/android_frameworks_base
 * [new branch]      jellybean  -> github/jellybean
Fetching projects:  67% (217/323)  
error: Exited sync due to fetch errors
[email protected]:~/building/cyanogenmod/jellybean$

Your Welcome :) Oh mann . No idea how to fix the error ?
 

Eskuero

Recognized Developer
Feb 15, 2012
1,388
2,284
Thanks, but I get compiling errors again:

Code:
From git://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227 
 * [new branch]      jellybean  -> cryptomilk/jellybean
remote: Total 79895 (delta 46875), reused 79380 (delta 46373)
Receiving objects: 100% (79895/79895), 29.11 MiB | 610 KiB/s, done.
Resolving deltas: 100% (46875/46875), done..65 MiB | 883 KiB/s   
From git://github.com/CyanogenMod/android_libcoreB | 1.21 MiB/s   
 * [new branch]      jellybean  -> github/jellybean
From git://github.com/CyanogenMod/android_libcore
 * [new tag]         cm-7.0.0   -> cm-7.0.0
 * [new tag]         cm-7.0.1   -> cm-7.0.1
 * [new tag]         cm-7.0.2.1 -> cm-7.0.2.1
 * [new tag]         cm-7.0.3   -> cm-7.0.3
remote: Total 613658 (delta 373510), reused 600289 (delta 365706)
Receiving objects: 100% (613658/613658), 950.14 MiB | 810 KiB/s, done.
Resolving deltas: 100% (373510/373510), done.
From git://github.com/CyanogenMod/android_frameworks_base
 * [new branch]      jellybean  -> github/jellybean
Fetching projects:  67% (217/323)  
error: Exited sync due to fetch errors
[email protected]:~/building/cyanogenmod/jellybean$

Men, you need to understand that you can post a ROM, that you can't upload because it's not getting built.

That's not an issue while building, just when syncing your repos, for sure, you have wrong on your manifests
 
  • Like
Reactions: TRuth14

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
Men, you need to understand that you can post a ROM, that you can't upload because it's not getting built.

That's not an issue while building, just when syncing your repos, for sure, you have wrong on your manifests

Actually you gave me the manifests :D

You can review them here! ;)

Yeah, I know. Sorry, changed it in the post! Now it says "repo sync errors"
 
Last edited:

Eskuero

Recognized Developer
Feb 15, 2012
1,388
2,284
Actually you gave me the manifests :D

You can review them here! ;)

Yeah, I know. Sorry, changed it in the post! Now it says "repo sync errors"

The output you posted didn't give any important information about the issue, post on pastebin the entire log on repo sync...


I've checked you manifest.xml, replace this line:

<project path="hardware/qcom/display" name="LibertyICS/android_hardware_qcom_display"/>

For this one, and try again:

<project path="hardware/qcom/display" name="WinSuk/android_hardware_qcom_display"/>
 
Last edited:

iH8ra!n

Senior Member
Jul 13, 2012
1,231
1,435
Cologne
The output you posted didn't give any important information about the issue, post on pastebin the entire log on repo sync...


I've checked you manifest.xml, replace this line:

<project path="hardware/qcom/display" name="LibertyICS/android_hardware_qcom_display"/>

For this one, and try again:

<project path="hardware/qcom/display" name="WinSuk/android_hardware_qcom_display"/>

Did it and it's running again but it started with this
Code:
From git://github.com/WinSuk/android_hardware_qcom_display
(the line I've changed) to sync, shouldn't it completely start over or start with the thing which with I got the error earlier
Code:
From git://github.com/CyanogenMod/android_frameworks_base
?
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    u5Nmq.jpg


    INFO ABOUT THIS STUFF

    DISCLAIMER
    Code:
    [COLOR="Red"]/*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, broken hearts,
    * thermonuclear war, you getting fired because the alarm app failed, or 
    * unfulfilled sexual partners. Please do some research if you have any 
    * concerns about features included in this ROM before flashing it! YOU are
    * choosing to make these modifications, and if you point the finger at me
    * for messing up your device, I will point that finger back at you and laugh. */[/COLOR]
    Will try to realease a Nightly every 2nd Day...not really NO! There aren't many changes that come in every day. Only changes from git.cryptomilk.com or from androidarmv6s' GitHub repo. So: I'll definitely release a new build each time something changes respectivelly something is listed under the command "repo sync -c"​

    INSTALLATION

    FIRST INSTALLATION OF THIS DUDE
    Download the latest CM10 build
    Download the 4.1.2 stripped GApps
    Put both zips into the root directory of your SD Card: /storage/sdcard/0/
    Boot into your Custom Recovery
    "wipe data/factory reset"
    "wipe cache partition"
    "advanced" > "wipe battery stats"&"wipe dalvik cache"
    "mounts and storage" > format everything except sdcard
    Flash both zips with the Recovery with "install zip from sdcard" > "choose zip from sdcard"
    Reboot
    Enjoy the new flavour of Android 4.2.2 Jelly Bean

    OPTIONAL
    Eoghan's kernel:
    Download Eoghan's kernel
    Put the zip into the root of your SD Card: /storage/sdcard0
    Flash the ROM
    Flash the kernel
    (Flash the INT2EXT4+ Script as described below)
    Flash the GApps
    Reboot into system

    INT2EXT4+ Script:
    Download the INT2EXT4+ Script
    Put the zip into the root of your SD Card: /storage/sdcard0
    Flash the ROM
    (Flash the kernel as described above)
    Flash the INT2EX4+ Script
    "mounts and storage" > "format /sd-ext"
    Flash the GApps
    Reboot into system

    UPGRADING
    Download the new build
    Flash it with "install zip from sdcard" > "choose zip from sdcard"
    Also flash the kernel and the INT2EXT4+ (without formatting SD-Ext after) again
    Reboot

    FIXING PROBLEMS AFTER UPGRADING
    "Lost" your Google Account?: Reflash the GApps

    FIXING PROBLEMS WITH GAPPS
    Use the "Cache GApps" instead

    FEATURES

    Now Playing
    Sound Search for Google Play/Google Ears
    Google Play Store v4.0.25
    Facebook Home

    WHAT WORKS

    Camera
    Hotspot
    Bluetooth Tethering
    Google Now
    New Clock
    WLAN
    Mobile Data
    USB Thetering (with any 3rd party App)
    Wake-Up issue
    Electron Beam Animation
    Autobrightness

    WHAT DOESN'T WORK

    Camcorder
    Panorama mode
    YouTube
    Laggy scrolling

    CHANGELOG

    PREAMABLE
    All Nightlies will include the latest CM-Upstream stuff. You can review what has changed here!

    16-04-2013
    -CM upstream stuff (too much to list like down below)
    -Google Play Store v4.0.25 added
    -Facebook Home added

    09-04-2013
    -hardware_qcom_audio
    -vendor_cm
    -Settings
    -Trebuchet
    -Added Google Ears v1.1.8
    -Added Now Playing

    30-03-2013
    -Fixed Wake-Up issue
    -Fixed Electron Beam Animation
    -Fixed Autobrightness

    19-03-2013
    -android_bionic (WinSuk)
    -device_htc_marvel_common (git.cryptomilk.org)

    16-03-2013
    -Way back to jellybean branch
    -CM upstream stuff

    02-01-2013
    -CM-Upstream Stuff

    01-01-2013
    -Use jellybean-stable branch now

    DOWNLOADS


    CREDTIS


    All my testers (for bug reporting and supporting)
    Jack Underwood (Now Playing)
    djolivier+thehacka1 (Bug fixing)
    OliverG96+dudeman1996
    izi501 (Cache GApps)
    Google Drive (hosting)
    CyanogenMod
    Facebook
    Google
    4
    I don't care about your physical age man, didn't you understand this ? I'm speaking about your mentality. Explaining you get mad by saying you're a 14 year kid isn't a good way... You should ask your mom on how to be a good guy... Or take a look in Wikipedia about Respect or Intelligence.

    Sent from my Wildfire S A510e using xda app-developers app







    Oh man I am 14 years old. Just shut the phuck up!

    Thanks :)

    I thought, but i could be wrong, that this is thread about ROM. So shut up both if you don't wanna say something interesting.

    Wysyłane z mojego Wildfire S A510e za pomocą Tapatalk 2
    4
    Man, I hate to read post like these. You know you can't change me. If you don't have any important things to say, don't say anything!

    Ok you lost one of your rom user. By acting like a ''boss'' thinking people who don't think like you are noobs wasting their time trying to get some informations they could have found themselves (they may don't know how to use a computer, what's the problem ?), you will get more people getting angry against you ! It's a forum to help other people who are having questions/bugs, not a forum to say that someone sucks so much that he can't do 2+2=4...

    You go mad only because a ''noob'' asks something that have already been asked... Please grow up a bit ! Weren't you a noob before ? Didn't you ask ''why doesn't it work ?'' even if there were a hundred answers ? Were you a perfect guy who knew everything about everything ?! I don't think so. Then think about your agressivity... Be friendly !

    Good luck for your work, you do a great job, but your mentality is so bad that I don't wanna read your posts anymore until you grow up...

    Sent from my Head using my Brainskills...
    4
    First build in 2013

    Made a new build! 01-01-2013 :) I use the "jellybean-stable" branch now, so I removed all old builds from my hostings site and from the changelog. I can only say that it's butter smooth ;)

    Enjoy it! :)

    P.S: I recommend a clean install!
    3
    i'm really sorry but i really feel like saying this.

    iH8ra!n, it doesn't look like you have the skill set to do these. more than half of the messages on this thread is you failing to compile and dudeman/oliver helping you.

    you have like 3 different roms based on modpunks/olivers/dudemans gits, they are mostly all the same stuff with small changes, most of them are more buggy than the original nightlies. you don't offer support nor you have the knowledge to do so.

    we all have access to a computer, we can all install linux on it, read a few tutorials and start compiling, get a few patches of off gerrit, apply them and offer people broken builds and call ourselves developers, but we don't do so.

    i'm sorry if this post seems offensive but it's the truth. you first started with offering a nightly for cm10, saying that the person who's supposed to compile them aren't doing so, it was acceptable to some point (although they weren't compiled properly and had more bugs than the original ones). then you applied a few 4.2 modifications and did the same, and after that, you created a dev thread for an imaginary cm10.1 build.

    modpunk was very strict when he was working on cm9, people were thinking twice when they were asking questions let alone posting a half ass working rom using his code.

    you cant even work with git properly, please quit and stop leading novice users into thinking these are the latest working cm10 builds for our device.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone