I want to try to port AOSP to my Samsung Infuse, but I need a little help. I heard that in order to port ROMs like this, you basically start by getting the source, building it, then putting it on your phone. Then try to boot into it and see what's broken and fix it(I realize fixing what's broken is going to be where majority of the work will be at.).
I downloaded the source to AOSP from Google and was able to build it, then I tried putting it on my phone but I'm unable to boot into it. How do you figure out why it won't boot? I tried running logcat on my computer when booting but it just says waiting for device and nothing else ever comes up.
Any help regarding helping me get it booting or any other general porting advice would be greatly appreciated!
Related
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
nerdman said:
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
I think there were two other devs in this thread trying to get ICS up and running as well. They could probably help.
http://forum.xda-developers.com/showthread.php?t=1309620&page=3
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
nerdman said:
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
Click to expand...
Click to collapse
We have 3 people working on it... your assistance would be of great help
Okay, so I tested the idea of changing the bootclasspath in init.rc, and it didn't seem to be helping much. In fact, it may have hindered things. Before the modifications, the phone would finish going through the two lg splash screens. Now, it hangs on the second. Suspect bad merge of ramdisk and kernel. But as for now, sleep is calling. I will work on it more tomorrow.
And I'm glad I can be of help. If you would like, I could throw what I have on megaupload, see if what I have is valuable.
You don't have ICS built device drivers and the kernel needs to be built for ICS. If you do not get it to boot nothing will work except maybe the touchscreen if you are lucky.
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
nerdman said:
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
Click to expand...
Click to collapse
This is sounding a lot like the Hackintosh driver hacks, which I've done, to get the Mac OS to run on PC hardware of various kinds. In that world, drivers from previous iterations and versions of the Mac OS are merged into the Mac OS to enable various PC hardware which Apple didn't support in the new OS version. One example is the video drivers which Apple supplies for very few video cards but have been hacked to run other, non-supported video cards. As well, Apple is notorious because it orphans perfectly useable and upgradeable Apple Mac hardware by not providing video drivers for it in new releases of the Mac OS. When Mac OS 10.7 was released some people used the Mac OS 10.6 hacked and/or unhacked video drivers and hacked video drivers for OS 10.7 to keep their PC display hardware working. Keep trying.
Got the kernel source. I'll start messing around with it today.
Hello, I'm porting Cyanogenmod to my phone, it boots of course many functions don't work, but I can't diagnose anything as logcat fails. http://pastebin.com/r39RsiUM Is what I get....I googled and haven't found anything to fix this. Logcat works just fine stock. Could anyone offer advice? If this is in the wrong place please move it! Need to get this cat out of the way to move on to fixing everything else!
Hello forum,
I have recently been able to build the source of the teameos rom for our s3. For those who don't know, team-eos is a team of developers that make great, and clean ROMs for a variety of Google-Nexus and Nexus-like devices (Including the Xoom- If you own a xoom, there is no way you haven't heard of Team EOS) and the Asus Transformer and Transformer Prime.
Anyways, I guess that is enough with the background.
So I have been able to build the rom successfully using CyanogenMod's device tree for the VZ SGSIII... I am able to get an otapackage that I can flash. All is well except for when I reboot and try to boot the ROM. When I reboot, I see the Samsung logo (It goes away fast now, because of the unlocked bootloader), but then I never see the "Samsung Galaxy SIII" that normally follows it. Instead, the phone vibrates once after a bit, and then reboots. It keeps doing that for a while but doesn't get anywhere, even after a couple reboots...
So my question is, has anyone run into something like this when building AOSP? Or does anyone have any idea what is going on?
Any help is much appreciated.
Thanks in Advance
go to development forum and PM any of the developers there. most of tHE people here are clueless about that sort of thing.
DROID3R said:
go to development forum and PM any of the developers there. most of tHE people here are clueless about that sort of thing.
Click to expand...
Click to collapse
Ok thanks! I appreciate the heads up. I'll do just that and see what happens.
can you still get in recovery just fine?
i am assuming so?
Hey guys, I was trying to port a ROM called the Nexus Beam 5.0.0 from the Nexus S. Its an ICS CM9 based ROM. However, when I installed it, i got a bootloop, so I decided to copy the libandroid_runtime.so, libandroid_servers.so, libmedia_jni.so from the Ported ROM to the base ROM. Now it doesn't even get past the Team Kick Ass bootimage. (I used your kernel Erik XD) Do you have any ideas what could be wrong?
Why would you port it when we already have a ported one?
If you can access the recovery flash this:
http://forum.xda-developers.com/showthread.php?t=1794413
If not then flash back to stock:
http://forum.xda-developers.com/showthread.php?t=1358498
I also don't suggest following any porting guides because they are sometimes incorrect and sometimes mislead you. I learned that, now I'm waiting for XDA-University to go online. Also don't ask people on how to port stuff, they'll just reply with google this, learn by yourself, typically they're not going to give you a clue on how to start on the right foot. I bet XDA-University will fix that
You should check what the bootloop is about with adb logcat
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
SedentaryDev said:
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
Click to expand...
Click to collapse
did you installed cm from here http://getcm.thebronasium.com/?device=u8833?
303
I didn't install it at all. This is just how I got the phone. I can tell you that it's CyanogenMod version 11-20141114-NIGHTLY-u8833
That could be the problem. You never know what the previous owner did or what they flashed could be a bad download, the wrong firmware, etc. Best to get back to stock and start over so you know exactly what has been done.
Hmm... probably. Right now going back to the stock ROM would be an improvement. Could I get some help with that, then? I haven't been able to find clear steps to do that with my specific phone, and when I went to Huawei's web site, I couldn't find the ROM for the Y300-151 and wasn't confident the Y300-100 was suitable.
I've used CM11, but I'm not familiar with that phone, so unfortunately I can't help with that specifically. There should be plenty of help on XDA. Just search for that specific model. Sometimes it takes a while to find what you need, but I'm sure its there. If it's done right CM11 has never let me down.
I'm sure CM11 works fine for most people, but my instincts tell me that my phone is underpowered for it. Ok, I'll look elsewhere or start a new thread about getting back to the factory ROM.
Yes, first thing to do is get back to stock. But don't give up on CM11. It should work fine on underpowered phones. It's just a slightly modified version of vanilla android which is a fairly light ROM.
I hope you figure it out.
Good luck!
If what you say is true, then I expect I'll be right back here again. I doubt that the wrong binary was used--I dunno, maybe something was wrong w/the installation procedure, but I'm sure the right binary was downloaded. In which case, maybe I should be attacking these problems directly, since I'm having trouble getting support for installing the factory ROM.