WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
Related
Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.
*** WORKING ***
RIL (calls/sms/3g data)
WiFi
GPS
sdcard and USB mass storage
rotation and proximity sensors
screen on/off animation
haptic feedback
*** NOT WORKING ***
Camera/Camcorder
MMS
BT
most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
Voodoo lagfix conversions
There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.
PLEASE READ
It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.
If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
THANKS FOR READING
The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.
ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!
Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.
If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me
***** Update 4/26 - ALPHA2 *****
fixed USB mass storage
fixed haptic feedback
fixed TiBu 'whoami' bug
update to 3.x ClockworkMod recovery
sync'd with latest CM code
updated to latest Market
stubbed the camera (yes, I know it takes pictures of nothing but a green android )
** package still includes gapps and kernel **
** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
** Make sure to wipe data even if coming from the previous alpha! **
***** Update 5/11 - ALPHA3 *****
updated to latest CM7 code (7.0.3)
enabled recent CM code to prevent "ring only once" bug (lightly tested)
made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
fixed some memory settings in kernel - should fix the lag experienced when using previous versions
added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
unstubbed camera (no more pics of a green android )
cleaned up my build tree a bit for a smaller download for people building themselves
removed gapps from ROM package, download from link below (kernel still included in ROM package)
ROM package will no longer flash a recovery
switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)
Instructions:
flash with Clockwordmod recovery
flash ROM first then flash gapps package
WIPE DATA! if coming from ANY other ROM
Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs
ALPHA3
http://www.mediafire.com/?ziawa7ot8dhdq4k
GAPPS
http://www.mediafire.com/?ogylu5w024148lt
Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
You work pretty quickly for someone who gets bored.
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
dw77x said:
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
Click to expand...
Click to collapse
any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log
I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:
adb logcat > logcat.txt
will dump the main log
adb logcat -b radio > radio.txt
will dump the radio log
thank you for your concern
Hey JT, I was talking to you on twitter today (@ScottColeBCS). I sent my email addy, I don't know if you got it. Let me know if you figure out a way for me to do that for you. Thanks Bro.
EDIT: Nevermind bro. I'm stupid. I just checked my email and saw that you sent the info I needed. Be expecting it.
I need to clean my keyboard...great job jt!!
Sent from my SCH-I500 using XDA Premium App
Thank you JT. You are a boon to this community. Have a beer on me.
Thanks Jt....good stuff
Sent from my SCH-I500 using Tapatalk
Sweet. So what are the chances this will bebe compatible with the Mesmerize eventually? I assume it is not currently.
Sent from my MIUI SCH-i500
What's the difference between this and the one you released on Twitter last night?
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
running great
Sent from my SCH-I500 using XDA App
kidserious said:
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
Click to expand...
Click to collapse
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
You are the man, man! Thank you so much that you do for us. You guys are awesome! Thank you again!
Sent from my SCH-I500 using XDA Premium App
jt1134 said:
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
Click to expand...
Click to collapse
Ok, Well I will take that as there is a definite possibility you will be able to fix some of the non-camera bugs. It lets me know that fixes for these issues are not out of the realm of possibility with current sources. JT, your new name is Mr. Fascinate (with a thunderbolt) Lol. Keep doing what you do brother, you're making a lot of people happy.
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
What will be different between This rom and the Kaoscinate?
Sent from my SCH-I500 using XDA App
deaffob said:
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
Click to expand...
Click to collapse
Apparently kaos has been MIA for quite a while now.
kallell said:
Apparently kaos has been MIA for quite a while now.
Click to expand...
Click to collapse
maybe he just likes the thunderbolt people better
Works damn good for an alpha.
*** This thread is now outdated ***
Please follow this link for a much better solution - Also, be sure to hit the Thanks! button to show your support for DizzyDen's excellent work!
********************************************************************************
I have removed all the files from this post and I encourage everyone to migrate to DizzyDen's superior solution. If for some reason you are unable to use Dizzy's tool you can PM DizzyDen or myself (Martian21) and one of us should be able to get you want you need.
********************************************************************************
[Original Thread]
I have seen several threads regarding this topic and thought I'd try to consolidate as much as I can in one place.
Credit for the original IMEI work goes to mthe0ry His original thread is here.
Because the NOOK Color is not a phone it does not have an IMEI number. This is why some apps that check for an IMEI number do not work on the NOOK.
Thanks to the work of mthe0ry and now DizzyDen it is possible to modify the framework.jar file in order to create a fake IMEI number on the NOOK Color. Doing so will allow programs such as Swype Beta, the free version of the XDA app, HBO GO, and the Xfinity app to work on the NOOK Color.
Unfortunately you need to have a framework.jar file that matches the ROM you are running as changes to the framework between ROMs can (and probably will) cause problems.
[See DizzyDen's thread for the IMEI generator tool]
*** This is mostly obsolete now that Dizzy's tool handles replacing the framework.jar file and backs up your original file - but I will leave it here just in case it is still useful to someone. ***
Installation:
You will need a file manager with Root access such as Root Explorer.
Download the framework.jar file for your Rom.
Unzip the file and transfer the framework.jar file to your NOOK Color.
Navigate to /System/framework using Root Explorer.
Mount the /System/framework folder R/W.
Rename the original framework.jar to framework.jar.bak.
Using Root Explorer, copy the new framwork.jar file.
Paste the modified framework.jar into /System/framework.
Long press the newly copied framework.jar and select "Permissions".
Change the permissions to match framework.jar.bak [rw-r--r--].
Mount the /System/framework folder R/O.
I recommend you reboot your NOOK although resetting the launcher may be enough.
For those that used my original files or the ones from mthe0ry, the original IMEI used in those files is "12-34567-89012-45". If you wish to continue using this IMEI number [NOT RECOMMENDED] you can manually enter it into Dizzy's tool.
Martian21
Request pls
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
I did a total wipe, stock 1.2 install, then a second total wipe before n82. I then added the modded framework and HBO GO worked really well! But, after adding Dal's 5/13 OC, I then got the spinning circle problem you describe.
I tried re-flashing just n83 to fix it (without Dal's OC), and re-installing the modded framework, but the spinning circle problem remains.
I can't say for sure that the OC kernel broke it -- it could be one of a dozen apps I installed? -- but it's certainly the leading culprit in my case. The 5/13 OC kernel also appeared to break a few of my other apps as well (360 Live failed too, but started working again after I returned to vanilla n83).
I'm going to start the entire process over again tonight to try and narrow down the problem...
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Didn't work for me -- still stuck on spinning circle after intro clip plays.
I used TiBu to wipe data, uninstall, then install app. Did you reboot in between, or take any other steps?
martian21 said:
I am using the same IMEI of "12-34567-89012-45" that mthe0ry used.
Click to expand...
Click to collapse
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
nemith said:
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
Click to expand...
Click to collapse
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
paleh0rse said:
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
Click to expand...
Click to collapse
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
You're a good man, thank you!
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
This is great news!!!
I will cease and desist as soon as it it completed. Obviously the best thing would be for people to follow mthe0ry's instructions and do this themselves (it's really not that hard) using their own unique IMEI number. That said I'm happy to continue the "hack" method for those who don't wish to do it themselves.
Yes, having multiple devices with the same IMEI could become problematic but so far it's worked for the apps people want. I do appreciate the warning as I probably wasn't as clear about the "hack" nature of this in the OP as I should have been.
Martian21
jzibit17 said:
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Click to expand...
Click to collapse
Attached:
enjoy
slide it
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
smiley1960 said:
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
Click to expand...
Click to collapse
Many of us use this hack for HBO GO, not just Swype...
First zip file is for which Rom?
Sent from my NookColor using Tapatalk
RASTAVIPER said:
First zip file is for which Rom?
Click to expand...
Click to collapse
Opps - Typo. It is for CM7 Stable 7.03
I added a note to the first post. I'll try to fix the file name when I get home tonight. I'm sure there will be 1 or two more nightly builds as well.
paleh0rse said:
Many of us use this hack for HBO GO, not just Swype...
Click to expand...
Click to collapse
It's also needed for a number of Gameloft titles.
Rodney
Concerns about unique devices make me wonder... I have a broken HTC Kaiser sitting on a shelf above my desk. It will never again be a functional device, but yet it has it's own unique IMEI.
Does the IMEI alone tell apps anything about what sort of device belongs to the number? If not, then it seems that I could use the IMEI from that Kaiser or the broken G1 I have.
It doesn't seem like these apps know anything about the device from the IMEI alone, given that people have been implementing this fix with no repercussions. That means apps probably don't check any hypothetical IMEI-device info against what's recorded in the build.prop, so this seems like a safe, workable solution for those of us with defective devices on our shelves.
Is there a way to make this work on a ManualNootered nook with 1.2, or does it only work if you have a custom rom.
Thanks
integrate in CM7
could you not ask the maintainers of CyanogenMod to integrate this in the future nightlies?
they would probably welcome the added functionality
This thread is now for bug reports/development only. Do not post in this thread any more until you have fully read the first four posts of this thread, and the first two posts of the Q&A Thread. If you post in this thread and it is clear that you have not read the posts indicated above, your post will be reported. For other discussion and "Is this a bug?" type questions, go to the Q&A Thread
Heeeeere we go! As LinuxBozo, one of the most talented developers in the Infuse community said, "Welcome to a new and sick, twisted world!"
Over in the Infuse community, we had an oddball device that had little in common with anything else. As a result, it was not easy to port ROMs from the I9000/Captivate. However, after LOTS of work, LinuxBozo pulled it off and came up with an automatic porting package that could get most I9000/Captivate ROMs running on the Infuse. As a result, it opened the Infuse community up to a massive variety of ROMs.
For the month since the I777 came out, people keep asking about I9100 ROMs. In general, the answer has been, "It should be possible, but no one other than designgears has done it yet." - I didn't have the time as I had too much kernel work to do. However, as the kernel is at a fairly mature and stable state, when someone asked for SensatioN to be ported, I figured it was time for a challenge.
I was successful, but encountered a few glitches. Tethering was broken, fortunately the Infuse community had the same issue and the same fix worked. Mic in calls was broken, just like CM7 - I finally got atinm's list of the blobs to swap out. As a result, nearly all of the challenges in porting an I9100 ROM to the I777 have been identified.
This is a package that should automatically port most I9100 ROMs to the I777. It has been tested by myself as follows:
SensatioN 1.8 by Crysis21 has been manually "Hellraised", and was the basis on which this package was developed. Do note that the author of this ROM tends to be unresponsive to porters. I asked for permission to release a ported ROM but never heard back.
VillainROM 3.0 was the first ROM to be tested with the attached package - it seems to work, if there are any problems, it is likely because I missed something in the permissions settings of the updater script. - Also, I have tested JKay's Deluxe Themes on VillainROM successfully - his thread is at http://forum.xda-developers.com/showthread.php?t=1154278 - You need to use the XXKI3 theme packages.
In general, XXKI3-based ROMs work. XXKI4-based ROMs may have issues with WiFi (see Known Issues below). I am working on compiling a more complete list in the Q&A Thread.
Please don't report bugs with ROMs to the upstream author of the ROM in the event that the bug was caused by Hellraising - unfortunately, it is going to be very difficult to identify when Hellraising caused a bug and when the ROM itself has a bug.
Instructions for the package:
Download an I9100 ROM to be Hellraised - must be CWM-flashable Gingerbread (ICS will NOT happen until after kernel source code becomes available, and if you spam me with 10000 "did you see this" links when it does I'll just go watch some TV. You have been warned.), and must be Samsung-derived (not CM7/MIUI/AOSP-based), ROMs distributed as Odin .tar files like Litening won't work. (I've tried...)
Download the package above
Unzip the ROM, check to make sure it does not have bootloaders. If it has Sbl.bin or param.lfs in it, RUN AWAY. No ROM developer should EVER include a bootloader without explicit warnings of this, if a ROM includes a bootloader it's a sign that it'll be **** in almost all cases. Similarly, param.lfs corruption can lead to a device that won't boot and I believe it can even break download mode. ROMs shouldn't be messing with this either without warning users.
Once you've done your safety check, put the ROM zip and the Hellraiser zip onto your SD card
Enter CWM
You should probably do a Nandroid backup here...
Wipe Data/Factory Reset - Some ROMs write apps to /data and you'll lose these if you wipe afterwards
Flash the ROM, DO NOT REBOOT, STAY IN CWM
Flash the Hellraiser package
Reboot and enjoy!
Known issues:
NFC files are included, but enabling NFC requires smali modifications to Settings.apk on some ROMs. (Starting to look like this is only for I777 stock-derived ROMs - VillainROM doesn't actually need any smali.)
Touching an NFC tag containing NDEF data will cause the NFC service to crash due to being unable to obtain STOP_APP_SWITCH permissions
Wifi tethering settings are not persistent and keep resetting themselves (At least on SensatioN and VillainROM) - Workaround for now: Enable tethering, THEN set the SSID and password, OR see http://forum.xda-developers.com/showthread.php?t=1335377&page=24
When initially setting up the ROM, it claims that network time is not available, and takes you to Settings - where you can check it to enable it and it works fine... Infuse Hellraiser had the same issue. Happens only once per flash so it's a very low priority.
When flashing other ROMs that do device compatibility checks (such as CM7), they will think you have an I9100 instead of I777. You need to flash an I777 ROM first.
Download links have been moved to the ChangeLog post (Post #2 below)!
Alpha 0.3.1 Release, 12/3/2011:
Download: http://www.multiupload.com/NUV8KDF9OZ or http://dev-host.org/4up if MultiUpload never comes back
Changes:
Only one - actually include Daily Driver 12/1/2011. People who flashed 0.3.0 only need to reflash Daily Driver from my kernel thread, no need for a full flash of Hellraiser.
Alpha 0.3.0 Release, 12/1/2011:
Download: PULLED, BAD RELEASE: Use 0.3.1 instead. If you already flashed 0.3.0, flash the 12/1 release of Daily Driver
Changes:
Update to some random kernel pulled from the wrong location on my hard drive
Overwrite /system/etc/apns-conf.xml with a "known good" one
Overwrite the CSC with a "known good" one
Home button haptic fix, courtesy of LinuxBozo of Infuse Hellraiser. Thanks to amtrakcn for pointing out that LinuxBozo's fix works on our device
Alpha 0.2.2 Release, 11/10/2011:
Download: http://www.multiupload.com/C1W5S6XW0R
Changes: Update to Daily Driver 11/10/2011 kernel (disables autoroot which broke root for a bunch of people), tiny installer script cleanups.
If root is working well for you, it is not worth flashing this
If root is broken for you, I recommend installing Daily Driver 11/10 and flashing ChainsDD's latest su package (linked from the DD thread's first post now). If you flash this it will remain broken, this only fixes new installs
Alpha 0.2.1 Release, 11/08/2011:
Download http://www.multiupload.com/ORQESFHVBT
Changes: Only one, replace Nfc.apk with the correct one. Fixes NFC service force closes.
Alpha 0.2 Release, 11/07/2011:
Download - PULLED due to excessive fail. Use 0.2.1 instead!
Changes:
Should now flash without the mount workaround trick after ROMs that unmount /system
Added NFC files from the I777 and one permissions XML - These combined with a small mod to Settings.apk will allow NFC to work. Will post details for ROM devs on making these mods soon. NOTE: Right now this only supports reading tags! Google Wallet support requires a LOT more work, if even possible! (Edit: I'm fairly certain it'll only be possible in CM7 - but I think I also know what's needed for the CM7 guys to get the rest of the way there.
Initial release, 11/06/2011:
Version - Alpha 0.1
Download - http://www.multiupload.com/9RJKKSBFZ0
How it works
Here's the details of how this package works.
1) This package replaces the modem with a known good I777 modem
2) It also replaces the kernel with an I777 kernel (Right now, Daily Driver 11/03 release) - This is half of the keymap fix. Also, DD 11/3 contains a fix that allows wifi tethering to work on both I777-derived ROMs and I9100-derived ROMs
3) It replaces two of the keymap files in /system/usr/keylayout/ - see http://forum.xda-developers.com/showthread.php?t=1313050&page=56 for details - thanks to MikeyMike01 and Dungeon47 for this one
4) It replaces most of the audio library files to fix the issue with outgoing mic audio in calls - this is the same fix used by Cyanogenmod 7 - see https://github.com/koush/proprietar...12f711197665edeb28522386a77a62da24bab#diff-28 for details, thank atinm for this one
Attached:
Hacked settings APK for VillainROM 3.0 - This, along with Alpha 0.2.1, should allow you to turn on NFC. May work on other XXKI3-based ROMs
For ROM Authors:
To get NFC to show in Settings, baksmali the Settings APK and open WirelessSettings.smali
Look for the line below:
Code:
invoke-static {p0}, Landroid/nfc/NfcAdapter;->getDefaultAdapter(Landroid/content/Context;)Landroid/nfc/NfcAdapter;
Delete the next two instances of lines that contain the word removePreference
NFC should then show in Wireless settings
Great work! I can't wait to try this out when I have some free time.
well aren't you awesome bro. Thanks a lot. This opens the door to a lot of good things.
this looks awesome i have to find a rom i want to try from their forums though since lite'ening doesnt work
Dude you freaking rock! Thanks so much for this! What is your donate link?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
What is your donate link?
Click to expand...
Click to collapse
Under his Thanks Meter.
THANKS!!!
about to test it out with the sensation rom! Really appreciate the effort you have been putting in lately!
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Awesome, just awesome entropy
Let the flashing and testing begin! You are a genius sir.
Sent from my SAMSUNG-SGH-I777 using XDA App
jgrimberg1979 said:
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
CWM is in the kernel, and this replaces the kernel.
Entropy512 said:
CWM is in the kernel, and this replaces the kernel.
Click to expand...
Click to collapse
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Thank you Entropy, can I use this with i9100 MIUI rom as well?
Sent from my SGH-I777 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You need to map the keys correctly...
Sent from my GT-I9100 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Still not workin
Edit; to clarify audio issue on the sensation rom is still there
Sent from my GT-I9100 using xda premium
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
I think it might be the kernel because i know certain issues from older versions of the skyhigh kernel for the sgs+ wich occured the errors u are stating in here....
so take into consideration to check the kernel
thats all i know about this topic
Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.
TDJ512 said:
Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.
Click to expand...
Click to collapse
yea...im not a kernel pro too but i think i know a method to find out..
go to this thread and check the kernel sources on github
the kernel has one version wich is called 1.4 and one called 1.4d check the changelog in the thread cus the author stated that he fixed the issues in the 1.4d version so i think if you compare the sources of the 2 kernel u might find out whats wrong with yours
http://forum.xda-developers.com/showthread.php?t=1555431
heres the thread
TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
A little more information would be helpful. What does the logs tell you? Either udev does not recognise the sdcard device, or vold does not like it. Do you get the device nodes? Does vold log anything? Is the sdcard properly initialised? Does it mount in a unmodified phone? Can you mount it manually? Does it contain more the four partitions (vold handles no more by default)?
The SD Card mounts fine on builds originally intended for the Shift. Its just with cross ports from Desire Z/G2 these issues are arising. When I attempt to initialize the USB the charge feature activates, but the PCSC.apk (I believe) doesn't pop up with the options to charge/mount, it couldn't mount the SD Card anyhow if that feature would initialize because its not reading that there's anything to mount. I'm thinking this issue is more along the lines of file issues then a kernel issue. Give or take I follow the principles of this guide http://forum.xda-developers.com/showthread.php?t=1222746 with a bit of common sense there after. What could I be missing? See, I also thought maybe it was a kernel issue initially. So I ported a few more ROM's from the Desire Z/G2, builds ranging from Gingerbread 2.3.5 (CM7/Sense 3.5) to 4.0.4 (CM9/Sense 4.0), of course while using proper kernel's intended to boot the builds that are proven to function accurately on the Shift & all of them came back with a usb/sd card mount issue.
(Click on image above to go to the Aberration website)
This is a continuation of my previous ShishirROM series of ROMS that started out on Gingerbread 2.3.4, and have evolved and expanded to today, where the latest version of ShishirROM is based off of XWLPG 4.0.3. Aberration is built completely independent of those and the only resemblance to my old ROMs is the dialer, which was an original creation anyways, but at it's heart, it's the next step. The ROM focuses on speed and smoothness and battery life. It incorporates common-sense fixes and ground-breaking features as well as third-party applications that bring something new to the table every time you use them. The ROM was inspired by the old Samsung gingerbread ROMS -- they were stable, fast, and just worked. This ROM manages to bring the same sort of feel back to the table while maintaining an updated look similar to the Galaxy S3 series of phones, and Android's resident Holo design. The Aberration Settings application is an extension of this ROM that lets you change some deeper settings, such as using Lidroid's beautiful 14 Notification Widget Mod instead of the default themed widgets, as well as provide an easier way for users to update to the latest version of Aberration, no matter which model of the Galaxy S2 they're running. This ROM aims to be the ONE ROM that supports every Galaxy S2 phone, and brings them on par with the super-phones coming out later this year. It's an update away from giving your phone four cores, two gigs of RAM, and a 4.8" SAMOLED HD display.
Features:
ODEXED (for smoothness)
Based on XWLPM
Siyah
Aberration Settings app
Lidroid 14 Quick Toggles
AROMA Installer
Google Now
Lux Auto-brightness
Opensource Sensors library (more accurate and faster)
Holo/Jellybean inspired styling
Apex/GS3/GS2 Launcher
GS2/GS3 Music application
Easy-Update
Samsung Dive
Complete development cycle
Directions:
Install i9100 zip in CWM
Wipe Data
Configure installation & install ROM
Reboot
Set-up ROM, download apps, etc.
Reboot again to settle everything
Download Link on the Aberration website. Click on the picture above.
FM Radio if you want it: Here
Wrong section, Should be in Development, not original development. However can you explain the features of this ROM and perhaps a link to the original.
Sent from my GT-I9100 using xda premium
uppon2 said:
Wrong section, Should be in Development, not original development. However can you explain the features of this ROM and perhaps a link to the original.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I built this ROM directly from XXLPM stock, not ported it from another unrelated device, sorry if that was unclear. The Galaxy S2 i777 and Galaxy S2 i9100 are EXTREMELY alike, so alike in fact that about five files hold the changes between them. No actual porting was done.
And I can't provide a link to the original since I made this, and this is the original lol. It's just a Stock Samsung ROM based off of 4.0.4 LPM with a few tweaks and fixes thrown in.
EDIT: Let me try and be more clear: this ROM was built off of XXLPM. It was initially tested on the i777 because that happens to be the device I have, but the development of the ROM was exactly the same for both versions. The i777 and i9100 versions are very different. Different modems, kernels, libs, etc. This ROM truly was built for both devices in mind, therefore it isn't a port.
EDIT2: Moved
shishir95 said:
I built this ROM directly from XXLPM stock, not ported it from another unrelated device, sorry if that was unclear. The Galaxy S2 i777 and Galaxy S2 i9100 are EXTREMELY alike, so alike in fact that about five files hold the changes between them. No actual porting was done.
And I can't provide a link to the original since I made this, and this is the original lol. It's just a Stock Samsung ROM based off of 4.0.4 LPM with a few tweaks and fixes thrown in.
EDIT: Let me try and be more clear: this ROM was built off of XXLPM. It was initially tested on the i777 because that happens to be the device I have, but the development of the ROM was exactly the same for both versions. The i777 and i9100 versions are very different. Different modems, kernels, libs, etc. This ROM truly was built for both devices in mind, therefore it isn't a port.
Click to expand...
Click to collapse
What he means is that what special features or original features does the rom have in order for it to stay in the original development for example paranoidandroid, it has the capability of changing per app dpi, from phone ui to a tablet ui etc. Jkay framework which can customize almost everything from the lockscreen to the notification bar. Because if it is just a cooked rom with some features that has been gotten from other devs, it should belong to android development. But i may be wrong, maybe you have something special in the settings you mention on the OP. Good luck on your rom bdw.
Cheers!
Sent from my GT-I9100 using xda premium
EDIT: Moved
Also, on a somewhat related note, pictures are uploaded to the ROM site.
//FM Radio attached.
Please comment with your experiences with Aberration! It'll help me build a better version for the i9100!
It's fantastic, thanks man.
Sweet looks like it works Removing all beta tags right now.
Can I use touchUX and lkewise aosp mms posted in nexus thread? Can I flash them?
download now and flash later... but where i can see the SS of this ROM guys??
allaboutarif said:
download now and flash later... but where i can see the SS of this ROM guys??
Click to expand...
Click to collapse
Everything's on the website. Click on the picture in the OP.
legola said:
Can I use touchUX and lkewise aosp mms posted in nexus thread? Can I flash them?
Click to expand...
Click to collapse
Depends specifically which zip. Go for it and if it messes up, just flash this ROM again to go back to default
Hello,
I wanted to try your rom, so i downloaded the i9100 zip and followed the installation steps and i got installation completed without any problems.
Then i choosed to reboot. The screen showed the Siyah logo, then the phone gave me a sound... and then nothing. Black screen. I have tried again and again but the same result. Maybe i am doing something wrong.
Thanks
too much bloatware dude.. maybe make a slim version
same issue. after siyah bootanimation a sound and then the screen blanks out.
uppon2 said:
Wrong section, Should be in Development, not original development. However can you explain the features of this ROM and perhaps a link to the original.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
What kind of a rude person are you ? This is no way to post something on a thread
Anybody else facing this issue. Any suggestions for this issue.
For everyone facing the black screen issue, first make sure you're running the i9100 version, and confirm that you wiped data before installing, then try flashing another i9100 kernel before you boot up for the first time. It sounds like the kernel didn't get flashed for some reason. I'll have to do some more digging. If anyone can grab a logcat then i'd appreciate it, although I don't know if the Log service got started after the Siyah screen.
If it still doesn't work, it may not have gotten installed properly. Try going into mounts/storage in CWM and wipe /system, manually do a factory reset/wipe data, and wipe cache as well. That should get everything.
EDIT: If you're getting the sound after boot, that just means the boot animation isn't showing for some reason. Give it five minutes and see if the phone boots up. If so then I'll upload a fix for this when someone confirms that's the issue.
shishir95 said:
EDIT: If you're getting the sound after boot, that just means the boot animation isn't showing for some reason. Give it five minutes and see if the phone boots up. If so then I'll upload a fix for this when someone confirms that's the issue.
Click to expand...
Click to collapse
I left the phone on black screen after sound nearly for 25 minutes, but the phone didn't boot up
bervin said:
too much bloatware dude.. maybe make a slim version
Click to expand...
Click to collapse
I don't quite understand what you mean by bloatware, since I allowed you to pick if you wanted to install most of it, and I allowed you to remove bloatware post-install anyways. Can you list some apps that you'd want an option to remove?
xscreations said:
I left the phone on black screen after sound nearly for 25 minutes, but the phone didn't boot up
Click to expand...
Click to collapse
:/ Try a different kernel. or any of the other solutions I outlined.
shishir95 said:
:/ Try a different kernel. or any of the other solutions I outlined.
Click to expand...
Click to collapse
Sorry none of the solutions worked...