Here is my port thus far:
X Disclaimor - Rom does not boot meaning this is not working yet X
I think since sense 4 was obtainable I'd like to think Sense 3.6 is too.
Now, i'd like to ask for a little help if anyone is available.
Plus, I know developers because I am one; we have an insatiable palette for a good project.
I've discovered two things that have made me feel like i'm stuck:
4/12/2013
1) I am not sure what else I can remove from the system dir to decrease the size to what is needed ~ 272524902.4 bytes (259.9Mb)
The Roms system dir is ~274083573.9bytes (261.4Mb); I basically need to know what else I can get rid of that equal up to 1558671.5 bytes (1.5Mb)
Here's the catch- I already took out the weather from media and apps and have symlinked them from the data partition.
2) I am not sure if I have correctly made the kernel.
I have a boot.img from the sense 3.6 rom i used to port. And I added the bootclasspath from the base kernel.
I also have renamed the proper files that needed to be renamed with inc.
Update: 4/13/2013
I've shrunk the system/usr dir down and now the port is under the size limit.
I have also tinkered with the boot.img more. Can someone check it to make sure that I have done is okay..
`Link in my sig:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So far I've symlinked system/media/weather to data/system.weather and the system/app dir to data/system.app.
This is what i'm using:
symlink("/data/system.app", "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.app");
symlink("/data/system.weather", "/system/media/weather");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.weather");
Do you think i could do the same with the system/vendor dir?
Edit: Don't need to worry now that the current port's system partition,which is now uploading, will be under the size limit.
*Bumpdated*
v1_1 Upload
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
ChemicalSymphony said:
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
Click to expand...
Click to collapse
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
tiny4579 said:
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
Click to expand...
Click to collapse
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Tribulattifather said:
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Click to expand...
Click to collapse
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
zachf714 said:
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
Click to expand...
Click to collapse
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
zachf714 said:
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
How about the latest evervolv ICS release. That's what pure pulled from I believe.
@zachf714:
I will look also. If I find any, i'll upload them to the working folder i created for the project.
And if you guys find any, link me here and i'll download and do the same thing.
@tiny4579:
On the Luxe Rom we worked.. I don't have any of the files anymore. Do you happen to have a rom.zip of the project?
@project Community:
I've uploaded the Rom I used to port with to the dev host - droid in working folder.
I'm about to upload the other Rom I used.
Both the base and port rom I used to make the WIP are uploaded now.
Cm9 http://goo.im/devs/invisiblek/dinc/.../dinc-CM9-invisiblek-KANG-09-03-2012-1608.zip
This was actually the most stable ICS ROM I ran
Sent from my Nexus 7 using Tapatalk HD
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
zachf714 said:
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
Click to expand...
Click to collapse
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not until I just forked it and yeah you did
Damn. Wish I wasn't in bed already.
I'd compile pures git and see if his kernel does anything with the WIP.
My kid gets on the bus at 7:50a (est) and will Dev a bit before I get going for the day.
But if someone tries before then let us know the outcome.
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Tribulattifather said:
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Click to expand...
Click to collapse
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
zachf714 said:
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
That is exactly what I thought so took care of that hahaha.
Right now, imo, I'm thinking it's a lib problem from my recent logcat.
I'll hop on in a few minutes and take another logcat and upload it.
(I deleted the one I had because I hadn't realized that you all might want to take a look too)
Related
Hello all. Jdfroyo is a free community based distro of HTC Sense ROMs for the Droid Incredible. My Main goal was to bring the community a fast, yet very polished rom based off HTC Leaks and official releases for the EVO and Incredible.
This ROM is based off of the Official OTA for the Inc. It is deodexed, zipaligned, and all bloat is removed, yet the rom still features the very handsome Sense-UI interface by HTC.
Sense Version includes:
1. Deodexed
2. Zialigned
3. Most bloat removed
4. VERY FAST!!!!!
5. Can be stably overclocked to 1.2 ghz !!!!
6. Can be used with HYdra or KING Kernels.
Bloat Removed:
Mode 10 and Magic smoke livewallpaper
VZNav
Footprints
MyVerizon
Footprints Widget
VisualVoicemail
Amazon MP3
Vanilla Version:
All Sense Bloat removed- including weather, clockwidget, and Rosie!
Themed vanilla
General Changelog:
9/7 update- added buildprop edit so wifi scans every 2 mins, removed oj wake
RC3- fixed boot.img problem and temed vanilla ROM
v2.5- inital revival of jdfroyo
Link: Downloads - MOD Edit: Links Removed
FAQ:
Q. Why should I flash your ROM? There are others just as good.
A. The jdfroyo project aims to provide a very customized rom that most usere will like. It is stble, fast and not buggy.
Q. You had some boot.img bugs in previous bugs. Is that dangerous?
A. The boot.img contains the kernel and ramdisc, so the boot.img bug did cause severe overheating, and couldnt mount emmc, but that bug was cleared up in RC3, so no worries (actuaslly i replaced the whole boot.img)
Q. Does this give me root?
A. If you flash a coustom recovery after flashing the RUU (and have S_off) Then it gives you SU perms again, but not for anyone who wasnt previously rooted before.
Q. Are there any specific risks in flashing this
A. THere are potential risks in flashing ANY rom (even the ruu). This rom was tested and proven that it is ok for day to day use and will not brick.
Q. What is this based off?
A. The newer versions (2.5 and up) are based on the offical 2.2 release, and versions before v2.5 is based on the old 7/27 leak.
Q. Why dont you have screen shots up? We have only been asking you for weeks.
A. I am putting up some screens tonight. They will be here and on my site.
Q. What is your site?
A. check my sig (and no i am not trying to website spam)
Q. What is required before flashing this ROM?
A. S_OFF, custom recovery (Clockwork or AMON_RA) the 2.15 radio and 92hboot.
Q. Where can i find the things you mentioned in the previous answer?
A. 1.SOFF: www.unrevoked.com/forever
2. Closkwork or Amon ra: Clockwork can be found on unrevoked.com/forever , Amon can be found floating around on XDA
3. 92 hboot and 2.15 radio: can be found on adrynalyne's site
PLEASE eNJOY MY ROM!!!!!!!!!!!!!!!!!!!!!!
Isn't this the same thing as before?
Sent from my HTC Incredible
no it has various fixes, mostly the wifi fix....and for the sense version, i ixed the buildprop whaer ot said jdfroyo vanilla....it is very different from the version that i posted here last eek, but if you followed me on AF, then this is a bit similar
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others before I try this.
Hehe
Sent from my ADR6300 using XDA App
Lcsglvr said:
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others. Hehe
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Its hard to stay away
Link isn't working.
try it now
I don't think anybody likes you
Sent from my ADR6300 using XDA App
theguitarguy58 said:
I don't think anybody likes you
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
its not about liking me, its about liking my rom
jdkoreclipse said:
its not about liking me, its about liking my rom
Click to expand...
Click to collapse
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Touche...let's get back in topic
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Is it just me, or do you always come out with a new version of *cough* a rom with almost the same name and number as skyraider. I guess it's like"the distinguished gentleman", if you have a familiar name, people will vote. At least make some attempt to be different so no one accidentally downloads this crap. How about POS ROM VERSION, oh hell, does it really matter?
And you use the same bull**** op almost every time. "Sorry no screens or info, just check my website, but I'm not spamming my website, and if it doesn't work, use other peoples fixes who I'll give no credit to ever never, but my rom is prefect and full of awesome." Give it a rest bud.
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
He's gotta be a relative or something right?
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
screenshots are in the first post!!!!!!!!!111
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I don't know the story since I just joined a few weeks ago but that made me laugh, thanks ! great wit sir!
Sent from my ADR6300 using XDA App
jdkoreclipse said:
screenshots are in the first post!!!!!!!!!111
Click to expand...
Click to collapse
I have to tell skyraider that my pinch to zoom isn't working with his rom, cuz those screens must be hella small.
Rather than continuing to have to discuss what is obvious to us all, let's try the objective approach with this. I downloaded jdfroyo Sense (for comedic value, honestly) and opened up the updater-script.
Going through this in sequence (I did not change the ordering):
So far so good.
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
Deleting files on a freshly formatted filesystem. What's supposed to be there?
Code:
delete_recursive("/system/etc/init.d");
delete("/system/xbin/a2sd");
delete("/system/xbin/apps2sd");
delete("/system/xbin/e2fsck");
Data isn't mounted, but delete operations are running, on /data.
Code:
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache/");
delete_recursive("/data/a2sd/");
delete("/data/.dalvikcache");
delete("/data/dta2sd.log");
Runs a script against /data, which still isn't mounted. Then extracts the contents of his zip to it. Into the void.
Code:
run_program("check_data_app");
package_extract_dir("data", "/data");
set_perm(0, 0, 0777, "/data/dalvik-cache");
Deleting more files on a newly formatted volume.
Code:
delete("/system/xbin/busybox");
delete_recursive("/system/xbin");
Oh, now we'll put some files on system. Since we've formatted it and deleted files which weren't there.
Code:
package_extract_dir("system", "/system");
I could go on but I think the point is clear. He's either not reading his updater-script, doesn't understand any of it or both. I'm going with both. So yeah, download at your own risk.
Still using evo framework?
Hey does anyone know what the artifact is in the middle of the 3rd screenshot?
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]
On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2
where the hell is the ramdisk
Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.
Maybe I should give it a try.
How about paste bin a logcat?
Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium
Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted
PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Upload!!!! Lol
Sent from my Droid Incredible using xda premium
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium
Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!
Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?
Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
I see progress! I will download your port right now and see what I can help you with.
tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2
Fully working Cyanogenmod 9 for the HTC Vivid calling, sms, data work.
And before you ask, yes its based on some of the HTC Frameworks, but i dont think anyone cares that much lol. When certain issues are fixed, i will pull out the htc stuff..
Issues:
-Apps randomly crash when downloading from google play.
-Certain options in settings cause device to crash.
-data randomly disconnects
-sometimes signal bars are inaccurate
LINK:
v0.1bhttp://q.gs/2Yy7E (dead zip)
v0.2 http://j.gs/1fJM (fixed zip but added problems
Sent from my HTC PH39100 using xda app-developers app
"Thanks/credits:
-Sensation CM9 devs for the base of this rom
-My mom for making me cookies this morning
-MG2195 for telling me to make this list
-Big thanks to theslam08 for fixing the ZIP
-Anyone else who I have forgotten
wow, pretty exciting news man!
cant wait for the link to test it...
Dude link!
Sent from my De-Sensed HTC Vivid using xda premium
What great timing... WildChild just banned me from his forum
Sent from my HTC PH39100 using Tapatalk 2
The skeptic in me wonders why it's based on 4.0.3...
altanimi said:
The skeptic in me wonders why it's based on 4.0.3...
Click to expand...
Click to collapse
its 4.0.4 i believe i screwed up some of the build.prop last night and thats what came out lol
and lmao @rignfool i hate that he did to me for "spamming"
Nice work...personally not a fan of HTC based aosp...as to me its not real aosp....but as you stated most people won't mind
Sent from my SGH-I997 using Tapatalk 2
I can't believe that I'm going to ask such a noob question, but what is the advantage of this build over wajee's de-sensed ROM?
Sent from my Nexus 7 using xda app-developers app
I hate to be a jerk but...
Link link link
Sent from my HTC PH39100 using Tapatalk 2
gotzaDroid said:
I can't believe that I'm going to ask such a noob question, but what is the advantage of this build over wajee's de-sensed ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
cyanogenmod is based of aosp (basically what descended is) but with added features and tweaks...including easy theming, and much more customization abilities
rignfool said:
I hate to be a jerk but...
Link link link
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
If you look at the op he edited it saying 17 hours remaining....
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
Nice work...personally not a fan of HTC based aosp...as to me its not real aosp....but as you stated most people won't mind
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
haha thanks man.. same here but its a usable rom so hey, who cares lol
Ok everyone, having some trouble with the zip not flashing, will upload now because i dont have time to fix it now, have a soccer game, if anyone can fix it for me and send it back so i can upload it again thanks.
XxSHaDoWxSLaYeRxX said:
Ok everyone, having some trouble with the zip not flashing, will upload now because i dont have time to fix it now, have a soccer game, if anyone can fix it for me and send it back so i can upload it again thanks.
Click to expand...
Click to collapse
Any weird reason why half the app files are com.android.xyz.apk, com.google.android.xyz.apk and com.htc.xyz.apk?
The updater script appears with no problems though its a universal script for a few phones so will keep looking.
EDIT: Seems was something wrong with the first few lines of the script (using recovery.log). Removed those, did some other tweaking to it and now its installing. Will report back how it goes.
UPDATE: Well it boots, for some reason the bootlogo goes white after a few seconds of seeing the CM9 logo. Though it is booting. Anyway, will play around with it, seems nice and fast so far...will report
UPDATE2: Ok, its nice, but it is very buggy (OP is on point). If you are on virtuous, stay. Not much of the CM works, many settings crash (settings>display even crashes). I cant really stay on this to test more as I need a semi-working phone. But if the bugs could be fixed it would be a nice ROM. BTW it is only 4.0.3, same as others.
Thanks man and im not rly sure i think it screwed itself up when uploading to dropbox, il check when i get home
Also, make sure to install kernel from compuyer even if s-off had some problems with that
Sent from my HTC PH39100 using xda app-developers app
theslam08 said:
Any weird reason why half the app files are com.android.xyz.apk, com.google.android.xyz.apk and com.htc.xyz.apk?
The updater script appears with no problems though its a universal script for a few phones so will keep looking.
EDIT: Seems was something wrong with the first few lines of the script (using recovery.log). Removed those, did some other tweaking to it and now its installing. Will report back how it goes.
UPDATE: Well it boots, for some reason the bootlogo goes white after a few seconds of seeing the CM9 logo. Though it is booting. Anyway, will play around with it, seems nice and fast so far...will report
UPDATE2: Ok, its nice, but it is very buggy (OP is on point). If you are on virtuous, stay. Not much of the CM works, many settings crash (settings>display even crashes). I cant really stay on this to test more as I need a semi-working phone. But if the bugs could be fixed it would be a nice ROM. BTW it is only 4.0.4, same as others.
Click to expand...
Click to collapse
hey man could you upload the update-script. and thats wierd it works for me other than thememanager and themechooser crashing every 20 min lol
EDIT: nvm i could have sworn it was working last night..
XxSHaDoWxSLaYeRxX said:
hey man could you upload the update-script. and thats wierd it works for me other than thememanager and themechooser crashing every 20 min lol
EDIT: nvm i could have sworn it was working last night..
Click to expand...
Click to collapse
I cant actually upload mine because I changed alot, I reworked the folders so the holiday folder for the 'device' was just already in the system folder, where it ends up going anyways. Then I just left the simple extract /system line, so it does that. Also removed all the sdcard folder as I dont use any of those files anyway (except a few which I could download from GP if I needed it (ie. gmail)). So removed those lines and such. Also changed the boot line/folder so its on the main dir of the ROM, then using this line:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
instead I think makes things easier. I also changed the updater binary with another working rom.
Anyway, point is, not exactly where in all that it fixed it lol. But, 1 certain thing I can say is no matter what I did it said Status 6 on the zip install error. Doing report logs or something similar, go to the SD card and you will have a recovery.log file, open it and go to the end, it should say something like
Code:
line 1 col 14: syntax error, unexpected BAD
1 parse errors
E:Error in /sdcard/cm9-holiday-20121111.zip
(Status 6)
which is this:
Code:
ui_print("");
Which...is fine I thought, but idk. I removed down to line 14, removing the device lines too as I removed the device named folders, starting with the ui print formatting. Needless to say, it installed from there. So, just try removing that top part of your script and re-sign try again. Also, try the recovery.log process, that will point more to your problem.
theslam08 said:
I cant actually upload mine because I changed alot, I reworked the folders so the holiday folder for the 'device' was just already in the system folder, where it ends up going anyways. Then I just left the simple extract /system line, so it does that. Also removed all the sdcard folder as I dont use any of those files anyway (except a few which I could download from GP if I needed it (ie. gmail)). So removed those lines and such. Also changed the boot line/folder so its on the main dir of the ROM, then using this line:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
instead I think makes things easier. I also changed the updater binary with another working rom.
Anyway, point is, not exactly where in all that it fixed it lol. But, 1 certain thing I can say is no matter what I did it said Status 6 on the zip install error. Doing report logs or something similar, go to the SD card and you will have a recovery.log file, open it and go to the end, it should say something like
Code:
line 1 col 14: syntax error, unexpected BAD
1 parse errors
E:Error in /sdcard/cm9-holiday-20121111.zip
(Status 6)
which is this:
Code:
ui_print("");
Which...is fine I thought, but idk. I removed down to line 14, removing the device lines too as I removed the device named folders, starting with the ui print formatting. Needless to say, it installed from there. So, just try removing that top part of your script and re-sign try again. Also, try the recovery.log process, that will point more to your problem.
Click to expand...
Click to collapse
i checked it and changed something and instead of saying col 10 or something, it said col 17 >.< so im gonna go see if i can fix it again now.. thanks man
Wait...sounds like you included gapps (gmail was referenced above)
Be careful, there is a reason cyanigenmod doesn't include gapps be default
A while ago cyanogenmod used to include gapps by default until basically one day they got a nice letter from Google telling them they can not include there apps and if they did they would be sued. So since then gapps have been kept separate for legal issues...now the chances of you getting sued are unlikely as this is unofficial and not that big of a phone plus its not like your some huge software team...but you never know...just a warning keep em if you want (many do and to this day I don't think anyone has actually faced legal charges) but I always say better safe then sorry...
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
Wait...sounds like you included gapps (gmail was referenced above)
Be careful, there is a reason cyanigenmod doesn't include gapps be default
A while ago cyanogenmod used to include gapps by default until basically one day they got a nice letter from Google telling them they can not include there apps and if they did they would be sued. So since then gapps have been kept separate for legal issues...now the chances of you getting sued are unlikely as this is unofficial and not that big of a phone plus its not like your some huge software team...but you never know...just a warning keep em if you want (many do and to this day I don't think anyone has actually faced legal charges) but I always say better safe then sorry...
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
thanks man.. il pull 'em out when i get back to my computer..
wait is this just de-sensed with cm9 apks?
So I started this build, and it finished without any errors. Keep in mind that this is my first EVER Rom build. And I have not been able to test it because I'm away from my workstation and Tab. But didn't want to wait till I got home to see if it works.
If there are any brave souls out there that want to try it, I have linked the package............. Please be kind
Tested and Failed!!!
Continuing my efforts
Zidkijah said:
So I started this build, and it finished without any errors. Keep in mind that this is my first EVER Rom build. And I have not been able to test it because I'm away from my workstation and Tab. But didn't want to wait till I got home to see if it works.
If there are any brave souls out there that want to try it, I have linked the package............. Please be kind
UnTested!!!!!
CM10.1 Unofficial: http://www.androidfilehost.com/?fid=23159073880933175
Click to expand...
Click to collapse
downloading now
i will test and report back
updater binary failed i'll see if i can fix and get it to boot.
wranglerray said:
downloading now
i will test and report back
updater binary failed i'll see if i can fix and get it to boot.
Click to expand...
Click to collapse
Let me know if you can get this booting. would love to take a look at it.
Might be worth a try using the update binary from my stock deodexed Rom.
Sent from my DROID RAZR MAXX HD
gr8nole said:
Might be worth a try using the update binary from my stock deodexed Rom.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
i tried that and also jamisons,
replacing boot.img with stock just to check
still getting the same error.
build.prop says its 4.2.2. I got rid of the build.prop assert in updater and still having errors. i would like to take a look at the op's device tree he compiled this from
I may need to tweak some of these files, and rebuild it. I'm surprised it completed without errors....lol
I took parts from the Tab 2 wifi and followed http://wiki.cyanogenmod.org/w/Doc:_porting_intro
I think it has something to do with when I pulled the blobs from my device............... "generate-blob-lists.sh" I had to edit that and I'm thinking that it didn't get everything that it should have needed.
I have ssh running so I'm able to get into my Ubuntu box remotely....... Time to play.
I'll see if I can get the tree pushed to git....... never done that either...... but hey, that's what learning is all about........right
If you need help with github - My how to. Do you have the propriety files?
i've been working on a device tree also. i believe this github may provide a great deal of info on what may be lacking for us to build cm.
https://github.com/ohanar/android_device_samsung_smdk4210-tab
during my research the exnoys chipset was used in the gsII and according to marvell pxa988 and smdk4210 are synonmous. AFAIK the prop blobs should mostly be in /system/lib/hw the major workload maybe just resizing for our display
Nice to see this get going I just finished setting up Ubuntu. Now I need to setup the build stuff and then I can try.my luck as well. I ll also setup git then, so that everyone, who is interested can follow and join in hope I get it done by tonight
Sent from my LG-P760 using xda app-developers app
this is great news planning to get my tab by this weekend ..
N00BY0815 said:
Nice to see this get going I just finished setting up Ubuntu. Now I need to setup the build stuff and then I can try.my luck as well. I ll also setup git then, so that everyone, who is interested can follow and join in hope I get it done by tonight
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
thats 3 of us that are planning to port cyanogenmod, why dont we hookup on hang outs and share notes. Afterall 3 minds are better than one
also once we get a working cm 10 base i have the paranoid android and aokp repo's all synced for my ONE. We could port that too
Forget what I sayed I ll party hard tonight I ll try my luck tomorrow
Sent from my LG-P760 using xda app-developers app
Jamison904 said:
If you need help with github - My how to. Do you have the propriety files?
Click to expand...
Click to collapse
I think that's where my problem is, when I went to pull the blobs I got some errors. I'll take a look at your how to......... The more reference points the better......right.
Zidkijah said:
I think that's where my problem is, when I went to pull the blobs I got some errors. I'll take a look at your how to......... The more reference points the better......right.
Click to expand...
Click to collapse
You use the extract-files.sh or pull files yourself?
The issue is the extract-files.sh are board dependant. There isn't a universal extract-files.sh file. The cyanogen mod wiki says to create your own.
Sent from my HTCONE using Xparent BlueTapatalk 2
The issue is you can only run that file when your device is running cm10. Otherwise you have to pull it all out yourself.
Crap....... that's where I went wrong then......
Sent from my SM-T210R using XDA Premium 4 mobile app
I ll try to build cm 10.2 btw repo is still syncing... takes more than 12 hours already I guess thats the disadvantage, of living on the countryside :/ will keep you guys posted, as soon, as I have got anything new good luck for the rest who is trying as well :thumbup:
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
I ll try to build cm 10.2 btw repo is still syncing... takes more than 12 hours already I guess thats the disadvantage, of living on the countryside :/ will keep you guys posted, as soon, as I have got anything new good luck for the rest who is trying as well :thumbup:
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I've got a fairly good connection and could do a build for you. I'm building PA nightlies for mako but I also keep my cm sources synced. So I'd just need your local_manifest (including your device trees repo) to do a build for you. Would take around 2 1/2 hours I guess...
fabi280 said:
I've got a fairly good connection and could do a build for you. I'm building PA nightlies for mako but I also keep my cm sources synced. So I'd just need your local_manifest (including your device trees repo) to do a build for you. Would take around 2 1/2 hours I guess...
Click to expand...
Click to collapse
Thanks for the offer, I really appreciate it, but I am @ work currently... I ll see, if it already finished syncing after work and if it did, I ll try my luck. As soon, as I have all the stuff needed, I ll get a git setup, so everyone can join in and also try his luck I gotta confess, I am also still a noob concerning this whole cm build thing. So dont get your hopes up too high. But I am still convinced, that we can get it done together
Sent from my LG-P760 using xda app-developers app