• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [On Hold] JellyBean CM10.1

Wow. At the beginning of the compile it neglected to tell me in a bigger font that it compiled without the kernel. That's why it didn't boot -____________________-

I'm having a little trouble finding out which *_defconfig file to use, but I think I found the right one. Re-compiling now with the kernel so (HOPEFULLY!) it should boot.
 
Sorry guys, flashed the ROM and got a black screen, just as the old one. What's weird is the file size didn't change on the new .zip even though it (supposedly) has the kernel. I don't know if that's normal or not, but something to note. I'll do more testing tomorrow, but for now I'm going to sleep.
 
Jimmy422 said:
Sorry guys, flashed the ROM and got a black screen, just as the old one. What's weird is the file size didn't change on the new .zip even though it (supposedly) has the kernel. I don't know if that's normal or not, but something to note. I'll do more testing tomorrow, but for now I'm going to sleep.
Click to expand...

The old one also has the kernel. The problem is the kernel itself. The stock kernel was made to boot up the stock rom. We need a custom kernel to boot up cm10. Try this link, it might be useful.

Doc: integrated kernel building - CyanogenMod

siyangqiu said:
martinez, could you upload the wallpaper please? when I entered my Google account, it replaced the stock one my old one from the touchwiz times. I'd greatly appreciate it.
Click to expand...

http://2.bp.blogspot.com/-EHceUmDO0sA/T_f2MRh608I/AAAAAAAAApY/oGBsxjKunw4/s1600/wallpaper_03.jpg
 
martinez41613 said:
The old one also has the kernel. The problem is the kernel itself. The stock kernel was made to boot up the stock rom. We need a custom kernel to boot up cm10. Try this link, it might be useful.

Doc: integrated kernel building - CyanogenMod
Click to expand...

I guess the old one was using the pre-built kernel. Huh.

That guide only seems to be useful if you have a device officially supported by CM, which we don't.

I looked into building my own kernel but it seems the one CM is using is somewhat out of date (2.6x and we're on 3.x according to Samsung's kernel files). I can't get it to compile with the device's config. It doesn't even give me an error, it just...stops halfway through the compile. I don't even know. Compiling with the Samsung-provided kernel worked fine, so I don't know what the problem is.
 
I'm a developer by trade, although admittedly I have very little linux experience, and I haven't delved much in to operating systems. And the whole mobile thing in general is foreign territory.

But I love tinkering with things and adding to my skillsets. This looks like one heck of a science project, but I'm willing to take a stab over the weekend ... just to see how frustrated I can make myself. If I get anywhere with it, then I'm happy to share any findings.

Getting started building custom ROM and Kernels:
http://forum.xda-developers.com/showthread.php?t=1789341

To Jimmy or Martinez: Does that link look like it contains most of what I would need to get up and running? Or am I just embarking on a suicide mission?
 
Online Forum said:
Try porting a 3.x.x. kernel to an existing handset that is about 12-18 months old; Not a snowball's chance in hell would it work, that's because, of the differing factors, the 3.x.x sources is vastly different to the 2.6.x source and would take a lot of hacking to get it working - I should know, have tried porting 2.6.38.6 source for the Zte Blade and failed.


Likewise, the latest kernel release 3.0.1 - when working on the ics4blade project over on Modaco, have made numerous attempts to port it but that's down to the simple fact that Zte made a very bad mess of the source which rendered porting nigh on impossible.
Click to expand...


I know that's not for a Samsung device but that doesn't sound very good at getting the kernel ported back to 2.6x, which is what the CM one is apparently.


I've done a little digging and found that the ramdisk may be to blame. I'm going to attempt to figure out how to merge it into the boot image and see if that solves the problem.
 
I did a quick search and apparently a bunch of people are using the kt747 kernel based on 3.0.57 something for CM10. We don't have to use their official CM kernel, just one that supports aosp ROMs. BTW, would our stock ROM be considered an aosp ROM like CM10?
 
Replacing the ramdisk hard-bricked my phone. It won't turn on now. If anyone has any advice, it would be great. If not, welp, i'm out of a phone. And a little pissed.
 
I can't get it to even power on. Tried download mode, tried recovery mode, tried holding on the power button with no battery...nothing.
 
Yes!!! I finally got my camera/gallery app bug fixed! Definitely a pain though... I had to search the interwebs to find another Samsung gallery... I got the note 2 gallery and it worked but has bugs because it is for jellybean... But then I took our stock gallery and moved it into system app and it replaced the note gallery... I don't know why,I tried before to move the gallery to system but it wouldn't work until I did this
 
superboy4444 said:
Yes!!! I finally got my camera/gallery app bug fixed! Definitely a pain though... I had to search the interwebs to find another Samsung gallery... I got the note 2 gallery and it worked but has bugs because it is for jellybean... But then I took our stock gallery and moved it into system app and it replaced the note gallery... I don't know why,I tried before to move the gallery to system but it wouldn't work until I did this
Click to expand...

Glad you got it fixed. Just a heads up, have you tried any of the system apps from the JB Rom in this thread? I have, and can verify that they work. Just thinking out loud. Maybe that camera is better I don't know.
 
So VM is sending me a new phone, they were like "We don't care how it broke, no questions asked we're going to send you a new phone". That's pretty cool.

But I'm not doing this again. Maybe I'll try to work on getting CM9 working, because that should be a lot easier. But this? No. There's something wrong with the ramdisk file because CM10's compiler has an issue with building a correct one. I can't find out how to fix it. Building CM is some weird closed-off process that absolutely nobody wants to help you with (Aside from xInterlopeRx! Thanks bud!) and I obviously don't have the knowledge that every other CM developer seems to have.

Sorry to disappoint everyone. I'm more than happy to help some willing person to get to the point that I got to though! Just let me know if you want help and I'll walk you through getting to where I got.
 
Jimmy422 said:
So VM is sending me a new phone, they were like "We don't care how it broke, no questions asked we're going to send you a new phone". That's pretty cool.

But I'm not doing this again. Maybe I'll try to work on getting CM9 working, because that should be a lot easier. But this? No. There's something wrong with the ramdisk file because CM10's compiler has an issue with building a correct one. I can't find out how to fix it. Building CM is some weird closed-off process that absolutely nobody wants to help you with (Aside from xInterlopeRx! Thanks bud!) and I obviously don't have the knowledge that every other CM developer seems to have.

Sorry to disappoint everyone. I'm more than happy to help some willing person to get to the point that I got to though! Just let me know if you want help and I'll walk you through getting to where I got.
Click to expand...
I would watch out, they might charge you full price after realizing that it has been rooted and modded.
But anyways, Ill take cm9, still way better than stock and most other roms. Thanks for the work!
 
james391 said:
I would watch out, they might charge you full price after realizing that it has been rooted and modded.
But anyways, Ill take cm9, still way better than stock and most other roms. Thanks for the work!
Click to expand...

Considering I couldn't even get it to boot using a jig I doubt they'll be able to get it to turn on. I just told them I dropped it and it wouldn't turn on anymore, so :P
 
Has anyone every hard bricked a computer before? How come computers aren't nearly as susceptible to hard bricking compared to phones?
 
siyangqiu said:
Has anyone every hard bricked a computer before? How come computers aren't nearly as susceptible to hard bricking compared to phones?
Click to expand...

Offtopic but it's because when you're putting an operating system like Linux or anything else on your computer you are only modifying files on the hard drive as opposed to modifying firmware. The only way you could really brick a computer if you somehow mess up a BIOS/UEFI firmware update which almost never happens.

Anyways back on topic, I'd love to see any version of CM on this phone, even if it is CM9. Plus once you have that figured out, I'm sure porting CM10 would be easier. So good luck and I'll be trying out whatever you come up with.
 
You must log in or register to reply here.
Back
Top Bottom