• 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

Shabbypenguin said:
wow... so umm yea.... rather than going through and quoting all the things that are wrong, ill instead just post here and let yall know i am looking at this thread, if anyone has any questions that i may help with lemme know :)
Click to expand...

Our savior has arrived! But seriously, thank you for your time in helping us out with development.
 
james391 said:
Our savior has arrived! But seriously, thank you for your time in helping us out with development.
Click to expand...

make no istake im not doing anything. we have a foum (interlopwer and i) and our irc channel is on there, you can hop in to talk with us faster and find out what you are doing wrong with cm. obviously its not just a quick fix however, since you guys still havent got a kernel booting yet
 
So apparently the CPU of the Galaxy S+ is the same as the Reverb's. Devs for the S+ looked into the Reverb kernel sources to port the 3.0.8 kernel. The S+ has working custom kernels and roms that support JB.

I don't really have any dev skills so I don't know if this helps but looking into this might help in porting a kernel.

http://forum.xda-developers.com/forumdisplay.php?f=1270

Good luck and hope some gonts will pick this project back up.
 
ebonywinn said:
So apparently the CPU of the Galaxy S+ is the same as the Reverb's. Devs for the S+ looked into the Reverb kernel sources to port the 3.0.8 kernel. The S+ has working custom kernels and roms that support JB.

I don't really have any dev skills so I don't know if this helps but looking into this might help in porting a kernel.

http://forum.xda-developers.com/forumdisplay.php?f=1270

Good luck and hope some gonts will pick this project back up.
Click to expand...

I changed the updater scripts for one of the s+ Roms and flashed...installed just fine but wouldn't boot just like this rom
 
Shabbypenguin said:
wow... so umm yea.... rather than going through and quoting all the things that are wrong, ill instead just post here and let yall know i am looking at this thread, if anyone has any questions that i may help with lemme know :)
Click to expand...

I do apologize, pretty much every angry post i've had is out of sheer frustration with not getting this to work. If you guys are willing to help me through getting a working kernel then I'll be happy to continue my work. I can't keep doing this on my own though, because we're getting nowhere.

I took a voltmeter to my battery and found that it's reading at about 3.2v (compared to the 3.8+ it should be), so I have a feeling it's just dead and needs to be manually charged. I had the same problem with my Optimus V at one time so this is nothing new to me. I'm going to try to get ahold of a battery charger on Friday and see if I can get it booting again - if I can, great, this phone isn't as easily brickable as I thought and we'll be able to get back on track.

Once again, sorry to mislead you guys, I didn't have a working phone and I was kind of freaking out! Now that I've got my old Optimus working (it's so slow... :() I don't have to worry too much about breaking the Samsung.

Update: Battery is now at 3.9v (I got a charger today) and still not booting. I bought a USB jig and it'll be here Thursday. If it still doesn't boot then I'm not going to be doing any testing myself again!

Update Update: Jig did nothing. No boot. :(
 
You should try making a jig yourself, I did that for my Captivate and it worked reasonably well. Also the pins that force it into download mode may be different than what the Jig you have sits on. But then again, it also sounds like the first bootloader may be destroyed in which case it would take a JTAG to get a good bootloader flashed.
 
titan87 said:
You should try making a jig yourself, I did that for my Captivate and it worked reasonably well. Also the pins that force it into download mode may be different than what the Jig you have sits on. But then again, it also sounds like the first bootloader may be destroyed in which case it would take a JTAG to get a good bootloader flashed.
Click to expand...

The pins seem to be the same across devices, so I don't think that's the issue. It looks like I'd need to do the JTAG method, and that's not worth my time.

Virgin still hasn't sent me a new phone. It's kind of annoying me because they say it's because they're out of stock, but that's bull, because you can buy one right now from their website. They're probably out of USED ones to give me -_-

I e-mailed them asking for an ETA and they just made a support case...

Edit: I called them today and they were like "Oh, uh, yeah it's in stock, I don't know why we didn't ship it to you" and I finally got an e-mail saying it was shipped. Woot. Should be back in business soon.
 
So I have a working reverb again. Yay! I should be able to start working on things again this weekend, but it's going to be a little slow since college is back in full swing for me. I'll do my best.
 
Jimmy422 said:
So I have a working reverb again. Yay! I should be able to start working on things again this weekend, but it's going to be a little slow since college is back in full swing for me. I'll do my best.
Click to expand...


Let me know if there's anything I can do to help. I'm not much of a programmer but I can compile from source, and also troubleshoot.
 
titan87 said:
Let me know if there's anything I can do to help. I'm not much of a programmer but I can compile from source, and also troubleshoot.
Click to expand...

Will do.

I know that our problem lies in the ramdisk. If somebody is knowledgeable enough, we need to unpack the ramdisk from the boot.img in the original zip. My ubuntu environment got corrupted somehow, so I don't have the tools right now to do so.
 
Jimmy422 said:
Will do.

I know that our problem lies in the ramdisk. If somebody is knowledgeable enough, we need to unpack the ramdisk from the boot.img in the original zip. My ubuntu environment got corrupted somehow, so I don't have the tools right now to do so.
Click to expand...


Ok, i'll try and unpack the Ramdisk. If successful i'll upload it so you can take a look at it.
 
I was so glad to find this thread, I've been searching the internet since I got my Reverb in anticipation for someone to at least get started on porting CM to it. We all appreciate the hard work, I know it's not an easy task. I am a novice programmer myself, but I really doubt I'll be of any use, I've never written an app for Android, but I'm going to look into the code and see if I can possibly be of any help, but I can't make any promises.

Keep up the hard work :D
 
Have you posted what you've been working on anywhere? Not only the compiled rom, but the source? I can't find it anywhere in this thread, the initial post from 2012 is all I can find.
 
KoRnKloWn said:
Have you posted what you've been working on anywhere? Not only the compiled rom, but the source? I can't find it anywhere in this thread, the initial post from 2012 is all I can find.
Click to expand...

I have no idea how to post the source. My original code is gone too, so I'd have to spend some time and re-compile everything to get back to that point.
 
Slayer72 said:
Hey Jimmy I've been converting the Reverb roms to work on the Rush lately and have been wondering does this cm10 JB rom boot yet or what??
Click to expand...

Nope. I apparently missed a few files when compiling and that's what's butchered the rom. I don't have any time right now to look into it but I know that it's going to be a while.

cobretti said:
Go here for OEM and LK2 update:Samsung Open Source Release Center
Search for SPH-M950, there you go.
Click to expand...

I'm referring to the device tree source for CyanogenMod, not the kernel source. I wish it was that easy!
 
Trying my hand at porting CM10, so far it will start to compile but errors out in the kernel compile. I also am trying to change a Galaxy S+ Device tree over to work with the Reverb, no guarentees but so far its somewhat promising.
 
You must log in or register to reply here.
Back
Top Bottom