[Q] Can't get past boot animation on custom ROM - Android Q&A, Help & Troubleshooting

Lets play a game.
Hypothetically, if someone were to compile a ROM based on CM10; what would make that ROM go into a never-ending boot animation on a clean flash (wipe data/cache/dalvik), yet boot up without a problem when dirty flashed over a CM9 variant. One might think that since a dirty flash over CM9 works, what about dirty flashing over a CM10 variant? What if it acts just like performing a clean flash and never gets past the boot animation?
Lets compound this by adding that once a successful boot-up after the dirty CM9 flash has occured; if one goes into recovery and wipes data/cache/dalvik, the ROM goes back into a never-ending boot animation.
Sounds fun, right? Any ideas?

---

I have played your game it sux try switching out libandroid_runtime.so in lib folder
In system/etc/permission try platform.xml
Handheld _core_hardware.xml from the rom made for your phone with the rom your installing see if that gets you out of the bootloop cycle
Sent from my R800x using xda premium

---

darkharbinger81 said:
I have played your game it sux try switching out libandroid_runtime.so in lib folder
In system/etc/permission try platform.xml
Handheld _core_hardware.xml from the rom made for your phone with the rom your installing see if that gets you out of the bootloop cycle
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Thank you. I will try that.
Also, any clue as to why the rom I compiled doesn't have root privileges? I mean, I know WHY, because the su binary is nowhere to be found; but why would that be? I'm searching and will possibly find the answer before I get a response, but I figured I'd toss that little bit out there too.
Also, could the fact that I don't have su capabilities be negatively impacting my boot sequence?

---

Did the rom u were compilimg from have root? And are yoh using a custom kernel? A lot of kernals in my forum mostly all I use any hiw auto root the phone try a different kernal if possible
Sent from my R800x using xda premium
---------- Post added at 04:11 AM ---------- Previous post was at 04:08 AM ----------
The subinary is actually kind of easy to fix bro lol update the su if its installed on the ROM I had thag issue on a ROM made me mad no root=no use then I updated the superuser and I had root so try that let me kno what happens if u need further help PM. me
Sent from my R800x using xda premium

---

darkharbinger81 said:
Did the rom u were compilimg from have root? And are yoh using a custom kernel? A lot of kernals in my forum mostly all I use any hiw auto root the phone try a different kernal if possible
Sent from my R800x using xda premium
---------- Post added at 04:11 AM ---------- Previous post was at 04:08 AM ----------
The subinary is actually kind of easy to fix bro lol update the su if its installed on the ROM I had thag issue on a ROM made me mad no root=no use then I updated the superuser and I had root so try that let me kno what happens if u need further help PM. me
Sent from my R800x using xda premium
Click to expand...
Click to collapse
The thing is, I'm trying to build a ROM from source for a device that isn't officially supported by them. I'm not so much planning on releasing it, more as trying to jump in head first and force myself to learn. I'm about as green as can be.
I have compiled CM10 previously as a test of my build environment... you know, test something that you know should work as a control; and it has root capabilities. The ROM I'm trying to get working now SHOULD have it; why else would superuser.apk be a part of the build? I am using the CM kernel, mostly because of the control idea, don't want to introduce something that itself might have problems; then maybe move into something else.
I'm pretty sure the su binary isn't installed on this rom because it's not in the out directory in any of the places it should be; eg. /symbols/system/xbin, /system/xbin. If I could figure out which file governs the creation of that file I would be one step closer to figuring this out, but I'm getting no clues searching either my source folder or the internet as a whole. Also, updating superuser does nothing as far as root privs go. I've tried both superuser and supersu. Supersu tells me I dont' have root privs and shuts down while superuser tells me I need to update my su binary. When I attempt the update through superuser, it goes on for a few seconds then fails.

---

Can you gain access tonthe android market place on the rom yur compiling?
Sent from my R800x using xda premium

---

darkharbinger81 said:
Can you gain access tonthe android market place on the rom yur compiling?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Yes.

---

And still csnt update su on the market ?
Sent from my R800x using xda premium

---

darkharbinger81 said:
And still csnt update su on the market ?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
If you mean update the su binaries, no. If you mean update the superuser app, then yes. But even doing it that way, updating the su binary through the app fails.
Also, swapping out libandroid_runtime.so, platform.xml, and handheld_core_hardware.xml had no effect on the boot process.
After a good bit of research I found that the su source is located in /system and /external/busybox/loginutil in CM. The rom I'm working on doesn't have su in /system, but it WAS in /external/busybox/loginutil. I synced those files into my current rom's /system and built. The output zip has the su binary in /system/xbin as it's supposed to, but the ROM still tells me that the su binary isn't installed when I try to update the su binary.
I have downloaded a couple "root checker" programs from the market and they all say my device is rooted, yet in a terminal emulater, typing "su" gives me "permission denied" I tried using a market app to install busybox, it tells me my phone is rooted; but fails to install busybox. The Gmail app from the market tells me "Your device isn't compatible with this version", same with superuser now for some reason... My baseband also shows as "unknown" yet I have full phone/wifi capabilities. I'm thinking I've got something mixed up in the code somewhere.

---

Ok try this from the rom ur basing your port on the rom made for your phone take the framework.res.apk and framework.jar put them in your port
Sent from my R800X using xda premium

---

darkharbinger81 said:
Ok try this from the rom ur basing your port on the rom made for your phone take the framework.res.apk and framework.jar put them in your port
Sent from my R800X using xda premium
Click to expand...
Click to collapse
Tried this too, no luck.
Here is a better question that might help me track down what is going wrong... when dirty flashing over another ROM, what part of /data, /cache, or dalvik is essential to this ROM booting up successfully? There has got to be something in those dirs that allows the rom to boot because just a simple wipe of those 3 areas (or a clean flash like every other rom in existence) renders it unable to move past the boot animation. Is there any kind of log that might be generated showing me what part of the boot sequence it is hanging on?
Also, I downloaded a CWM flashable su binary/superuser.apk and I now have full root privs, yet the su binary/superuser.apk that is built into this ROM fail to give me root access.

---

Have yoh pulled the battery for a ffew minutez let it sit reinsert the battery do a full wipe and reboot? Also is the kernal your using made for the rom is it stock kernal or custom kernal?
Sent from my R800x using xda premium

---

darkharbinger81 said:
Have yoh pulled the battery for a ffew minutez let it sit reinsert the battery do a full wipe and reboot? Also is the kernal your using made for the rom is it stock kernal or custom kernal?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
I've tried holding the power button until it resets, it still hangs. I've pulled the battery and let it sit, it still hangs.
I'm gonna go through and resync the repo; start from scratch so I can make sure when I'm making the modifications to my device/kernel from CM that I'm not leaving anything out. I might even try to use a device that is officially supported by both this rom's developers and CM10, maybe try to see if there are changes between CM's device tree and this one to see if I'm forgetting something, need to add something, etc... Also, I'm going to keep a log of my changes (like I should have done to begin with) so I can know exactly where I started, what I changed, and the result of those changes. I had modified some of this roms files but don't remember exactly which ones I changed, where I changed them, or what I did. Basically I was destined to fail before I even started.
I do appreciate your help, but judging from how long it's gonna take me to re-sync this repo on my horrible connection, I'll give you at least the weekend off from racking your brain with me

---

Just pm if yoh need help bud
Sent from my R800x using xda premium

---

darkharbinger81 said:
Just pm if yoh need help bud
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Thank you, I appreciate it.

---

Any time
Sent from my R800x using xda premium