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

Root [OUDHS] CM-10 for Galaxy Reverb from Jimmy422 and Interloper

Here's the terminal output. Still don't see it.

Because it's not mounted which means:
1. It's not mounted
2. The device only mounts it for specific reasons, like to find encryption keys on boot for radio processes, then it umounts.
3. Aliens have taken the partition, but left us a clue.
4. You can dd the partition and find out what on it, unless you already have/know.
 
Because it's not mounted which means:
1. It's not mounted
2. The device only mounts it for specific reasons, like to find encryption keys on boot for radio processes, then it umounts.
3. Aliens have taken the partition, but left us a clue.
4. You can dd the partition and find out what on it, unless you already have/know.

Hmm. I'll have to see.


In the meantime, i've modded ani's kernel to fix what was wrong. Since my card reader decided to explode and the USB connection to my phone doesn't like linux, if somebody could kindly flash the following zips, try these two commands and paste the result into pastebin on both of them, that would be awesome.

Flash this first: cm-10-20130319-UNOFFICIAL-iconvmu-20130320-17:04-signed.zip

Then this right after flashing the first. OCkernel2_MB3-SPH-M950-20130320-17:31-signed.zip

adb logcat

and

adb shell
dmesg

are what you need to do in a terminal.
 
Just downloaded both files and flashed them. adb logcat & adb shell work but adb dmesg didn't work for me. logcat is attached.

EDIT: Nevermind I'm about to get you the dmesg
 

Attachments

I see no show stopping errors. What the heck.

I'm gonna push some kernel changes later today that got me past some video errors on boot. I still don't have full video, but I am getting some flickering and the "optimizing apps' dialogue window. The error would not be on the dmesg because the kernel was doing what it was supposed to do, but I needed it to do something else. Are you learning anything yet?
 
Neither dmesg nor logcat have errors, so I'm not sure why it's not working. Haven't learned anything from that!
 
Well crap. I checked out the vendor folder and there's a ton of files that aren't being told to be copied, especially qcom binaries, which control booting. Along with Kies files and thermal configs. I'll fix that, and that should help. Derp.
 
So it turns out the files that didn't look like they were being copied were actually being copied. Still not booting. I can not figure this out at all. There's no errors. It just sits at that darn rmt_storage and refuses to continue.
 
So it turns out the files that didn't look like they were being copied were actually being copied. Still not booting. I can not figure this out at all. There's no errors. It just sits at that darn rmt_storage and refuses to continue.

So maybe it is a boot animation error, like the boot animation loads wrong so it just shows black and then loops
 
So maybe it is a boot animation error, like the boot animation loads wrong so it just shows black and then loops

It's showing the initlogo.rle but won't move on to loading the boot animation. I've checked in the logs and it doesn't even attempt to start the boot logo service.

I found this while doing a bit of googling. It might help, but I have to go do work. Somebody check it out!

https://www.codeaurora.org/gitweb/q...ads/jb_mr1_rb1.22;hb=refs/heads/jb_mr1_rb1.22
 
I've been having a problem with the init binary in the ramdisk, not to be confused with the updater-binary. I thought it was a ramdisk issue, but I tagged all the files, they went to the right places and I could repack the files with the ramdisk/zImage from the android build, sans that specific init binary, and I would get farther. This is the one I'm using:

www.waywardpilgrim.net/android/samsung/sph-l300/stock/init

replace it in the ramdisk. Once I get a fix for the one built with android, I'll post here again.
 
I've been having a problem with the init binary in the ramdisk, not to be confused with the updater-binary. I thought it was a ramdisk issue, but I tagged all the files, they went to the right places and I could repack the files with the ramdisk/zImage from the android build, sans that specific init binary, and I would get farther. This is the one I'm using:

www.waywardpilgrim.net/android/samsung/sph-l300/stock/init

replace it in the ramdisk. Once I get a fix for the one built with android, I'll post here again.

I just tried it with your init binary, no dice. I get a black screen and I can't even run logcat.
 
Interloper, if you'd like, I'd be happy to sell you my Reverb for $100. Sprint coverage up here is awful (especially 3G, which is a big deal) and I'm considering switching to T-Mobile and the Nexus 4.

I've still got the box and everything and it's only got a few minor scratches from being in my pocket.
 
Interloper, if you'd like, I'd be happy to sell you my Reverb for $100. Sprint coverage up here is awful (especially 3G, which is a big deal) and I'm considering switching to T-Mobile and the Nexus 4.

I've still got the box and everything and it's only got a few minor scratches from being in my pocket.

Lets do it. All I have is paypal, and I have to see if animania will still give me $50. If that works out, I'm game.
 
We do have a section here for selling our unwanted tech goodies. Please see Classifieds for more info. I understand you want to give first shot to those you know will appreciate it the most but it's not the proper place. Thanks for your understanding!
 
Back
Top Bottom