• 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

xInterlopeRx said:
Wow, I feel like a real ass. I thought I was posting in the Galaxy Victory forum. I have that device in hand so decided to give it a shot. Honestly guys things have just kinda gotten out of hand with trying to support too many devices. But, since it was my mistake I'll make this group a deal. Two things: I just noticed my inbox with a request to fix CWMR. If I can get a tester to join me tomorrow night we'll get it done. Second, if this device is on JB I'll try for cm10 if not it'll have to be cm9 but I'll need some details from a working device. I have a buildbox now that cuts build times down a lot so upload is the biggest delay. if you can help leave me a message on irc.
Click to expand...
Our device is currently stuck on 4.0.4 so I guess that means cm9?
 
Yeah. It would take more kernel hacking than I could possibly do for a higher version without updated proprietary files.
 
Hey, at least no one donated...

I'm not sure how closely you follow the scene as a whole, but some of the best devs worked on the Sprint Galaxy Nexus for weeks before a release, and it was a mostly supported device to begin with. Most devices take months and some longer. The CM development double-edged sword is that higher CM versions have more support for a broader range of devices provided the dev has the props to match. So, CM-9 will work with what this devices has, but stuff thats supported better in say cm-10.1, like RIL and WIFI, will be harder to get working. It'll take time to get working than you may think. I'm already working on three other devices but getting more used to the workflow and I have a machine that can build JB in 15 minutes (that is a huge help). Please, try to be patient as we all do all we can.
 
What is the download file there? & from what I've read they're pretty similar. I'm no dev myself though. :/ is there anyway I could aid or help?
 
I don't know that it is. I re-based my local repo to reflect the actual device codename, but otherwise, it's been so long since I worked on this I am just using this as a starting point to fix whatever's broken. If you flash it, try all the things then pull the recovery_log if you can and let me know whats broken. If I can get this perfect I will submit for official acceptance by the god-droids that be and it will update through rommanager.
 
So those if us who have the rush, which is VERY similar to this phone, try and flash this it won't work correct? Any really good thorough instructions on how to port it over to the rush?
 
Gendo420 said:
So those if us who have the rush, which is VERY similar to this phone, try and flash this it won't work correct? Any really good thorough instructions on how to port it over to the rush?
Click to expand...

Since I didn't work on both devices I can't say it's safe. If there are problems with your recovery contact Shabbypenguin. There are no instructions detailed enough to do any of this perfectly right the first time between devices. You have to know about the devices' memory, the location the kernel and ramdisk need to be in once loaded, the boot order of the chip, etc. With that in mind, I know the devices are very similar and it's very likely to work, but I can promise nothing and warn you not to try unless you can replace your device tomorrow, without any hassles and for free.
 
I'm working on getting this done again now that I'm going on spring break shortly. There were a ton of files I missed from the ramdisk that control booting. Lucky enough, Samsung uses the same naming conventions for their files as they do for their other newer phones (SIII, for example) so I know which ones I need. Hopefully I'll have a build out by the end of the week. And hopefully it'll boot with the added files.
 
Jimmy422 said:
I'm working on getting this done again now that I'm going on spring break shortly. There were a ton of files I missed from the ramdisk that control booting. Lucky enough, Samsung uses the same naming conventions for their files as they do for their other newer phones (SIII, for example) so I know which ones I need. Hopefully I'll have a build out by the end of the week. And hopefully it'll boot with the added files.
Click to expand...
So we might be able to have an experimental build by the weekend?
 
Thatwhitelion said:
So we might be able to have an experimental build by the weekend?
Click to expand...

Hopefully, although what xInterlopeRx said about kernel hacking kinda worries me, because I haven't seen anything about that. As long as I can get it booting though then the rest should be easy (Relatively speaking, its a matter of getting updated binaries for jellybean from what I've gathered).

Also I've updated the repository to CM 10.1, so there's that.
 
Jimmy422 said:
Hopefully, although what xInterlopeRx said about kernel hacking kinda worries me, because I haven't seen anything about that. As long as I can get it booting though then the rest should be easy (Relatively speaking, its a matter of getting updated binaries for jellybean from what I've gathered).

Also I've updated the repository to CM 10.1, so there's that.
Click to expand...
True, well hopefully something good happens soon and our phones get cm 10.1. Thanks for your hard work. I know it must be tiring and stressing.
 
Well, after a ton of work I got all the libraries pulled off the device. 95% of them had the same name as on the SIII, which makes me really happy. Anything that the SIII had and the Reverb didn't was obviously features we don't have (I remember one being a send-to-tv or something of the nature...weird.)

Also good news, the graphics chipset is an Adreno 200, which just happens to have official Android Jellybean support! This is great news in the event we need updated drivers (which, from what it sounds like, we will)

I'm building a new build as we speak with all the ramdisk stuff included. Should have it uploaded by the end of today if the build goes through. And this time, it's got a good chance of doing...something. If it doesn't work, I now have a github with all my work so that others can help us out.
 
Jimmy422 said:
Well, after a ton of work I got all the libraries pulled off the device. 95% of them had the same name as on the SIII, which makes me really happy. Anything that the SIII had and the Reverb didn't was obviously features we don't have (I remember one being a send-to-tv or something of the nature...weird.)

Also good news, the graphics chipset is an Adreno 200, which just happens to have official Android Jellybean support! This is great news in the event we need updated drivers (which, from what it sounds like, we will)

I'm building a new build as we speak with all the ramdisk stuff included. Should have it uploaded by the end of today if the build goes through. And this time, it's got a good chance of doing...something. If it doesn't work, I now have a github with all my work so that others can help us out.
Click to expand...
That sounds awesome :D can't wait to test it out. Good work Jimmy.
 
Jimmy422 said:
Well, after a ton of work I got all the libraries pulled off the device. 95% of them had the same name as on the SIII, which makes me really happy. Anything that the SIII had and the Reverb didn't was obviously features we don't have (I remember one being a send-to-tv or something of the nature...weird.)

Also good news, the graphics chipset is an Adreno 200, which just happens to have official Android Jellybean support! This is great news in the event we need updated drivers (which, from what it sounds like, we will)

I'm building a new build as we speak with all the ramdisk stuff included. Should have it uploaded by the end of today if the build goes through. And this time, it's got a good chance of doing...something. If it doesn't work, I now have a github with all my work so that others can help us out.
Click to expand...

Adreno 205
 
Jimmy422 said:
Really? Everything internally pointed to 200. Hmm.

Anywho, here's a build! I have no idea if this will flash correctly or not. Please, please, please test this for me and let me know what happens. You might need the desktop.zip a couple of pages back to get it to work. I don't know.

cm-10.1-20130306-UNOFFICIAL-iconvmu.zip download - 2shared
Click to expand...

Hey, so I looked into the zip here and it's missing the files in system/framework/. The libs/bins look a little short also. A typical cm-10 build is about 150-175mb. Aside from the meager criticism I can help you setup the files a bit once I clone your stuff. I do the most LATE at night so it'll be later tonight.
 
xInterlopeRx said:
Hey, so I looked into the zip here and it's missing the files in system/framework/. The libs/bins look a little short also. A typical cm-10 build is about 150-175mb. Aside from the meager criticism I can help you setup the files a bit once I clone your stuff. I do the most LATE at night so it'll be later tonight.
Click to expand...

Any idea why that might be? And any help would be greatly appreciated.
 
You must log in or register to reply here.
Back
Top Bottom