• 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

Jump to latest Follow Reply
Sort by date Sort by votes
xInterlopeRx

xInterlopeRx

Android Enthusiast
Apr 5, 2012
509
280
Hudspeth County, Texas
#1
MAKE A BACKUP FIRST!
Ok, since the other thread had a misleading title, and because we all have something to tell the grandkids about I went ahead and started a thread for the Samsung Galaxy Reverb.

[rant]This thread should be for you, the user, to ask questions concerning the development of CM-10 for YOUR phone. This is a development thread, so please try to focus the comments on bugs, reports, logs, etc. There is a thread in the general section for other discussion about the device. I don't want to be a forum moderator but I also don't want to be swimming through extraneous posts trying to find important information.[/rant]

That being said Jimmy422 has started a github for the device and that is right here.

MAKE A BACKUP FIRST!

I also have a github for the device and that link is in my signature, as is a link to use webchat and connect with me personally. Jimmy422 does enter the chat, but seldom stays long. Any message with the name 'interloper' in it will alert me and I will get the message. Please, don't be shy. Ask what you want to ask. As long as you don't want to date either of us, it'll be ok.

Lets start off with a file created today by bully the buildbot, AKA, my computer:

I was told this file failed to flash, but I don't know why yet. Maybe someone can figure it out for us before I can get to it.

Wait, Martinez is on the other thread so I gotta cut this short, bye!

Hey, here is the test build for the day. By downloading this you agree that I will not be held responsible for anything happening to your device. MAKE A BACKUP FIRST! Then, you mush also agree to read how to use adb logcat and adb shell to provide logs on what is happening so I can make the changes for tomorrows' build.
 
  • Like
Reactions: MTdude, Slayer72, bkttk2 and 1 other person
#3
We do not yet have a booting cm-10. It should be booting in the next few days, then on to fixing everything that inevitably needs fixing. so, if the dev cycle was a clock, we're just past midnight...

I'll be posting a link in a few minutes that will (should) flash and hopefully we can start collecting logs and last_kmsg from the kernel.
 
Upvote 0
#4
xInterlopeRx said:
We do not yet have a booting cm-10. It should be booting in the next few days, then on to fixing everything that inevitably needs fixing. so, if the dev cycle was a clock, we're just past midnight...

I'll be posting a link in a few minutes that will (should) flash and hopefully we can start collecting logs and last_kmsg from the kernel.
Click to expand...

If it flashes I can help you out with logs and what not
 
Upvote 0
#8
Did either of you try ABD perchance? I have a partially boot Galaxy Victory that behaves like a sucking chest wound but it gives me a logcat for a few seconds and I can at least get some clues as to the internal injuries. Please try to give me as much information as possible about the experience and the device, because without it I can't do much but guess. Also, I need a stock boot.img for the ramdisk. It can be done with ADB OR I think you can get it from a backup.
 
Upvote 0
#9
xInterlopeRx said:
Did either of you try ABD perchance? I have a partially boot Galaxy Victory that behaves like a sucking chest wound but it gives me a logcat for a few seconds and I can at least get some clues as to the internal injuries. Please try to give me as much information as possible about the experience and the device, because without it I can't do much but guess. Also, I need a stock boot.img for the ramdisk. It can be done with ADB OR I think you can get it from a backup.
Click to expand...

Here's the boot image:

boot.img

Also I think you're using an incorrect defconfig file for the kernel. The icon00 is something else, because if you compare it with the one on the phone it's completely different. I'll recompile with the one pulled from the phone and see if that makes a difference.
 
  • Like
Reactions: xInterlopeRx
Upvote 0
#10
xInterlopeRx said:
Did either of you try ABD perchance? I have a partially boot Galaxy Victory that behaves like a sucking chest wound but it gives me a logcat for a few seconds and I can at least get some clues as to the internal injuries. Please try to give me as much information as possible about the experience and the device, because without it I can't do much but guess. Also, I need a stock boot.img for the ramdisk. It can be done with ADB OR I think you can get it from a backup.
Click to expand...

I did not...I current currently am out of a computer because I left it in my girl's car...whoops!
 
Upvote 0
#11
Good news guys! With PlayfulGod's help we got ADB working! I have no idea what to make of it, but it's definite progress. It's showing a (corrupted) initlogo.rle and bootlooping.

Here's the results of adb logcat

Code: 
--------- beginning of /dev/log/main
F/libc    (  122): Fatal signal 11 (SIGSEGV) at 0x0007d9d0 (code=1)
I/logwrapper(  121): /system/xbin/run-parts terminated by signal 11
F/libc    (  128): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  131): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  130): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  133): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  136): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  140): Fatal signal 11 (SIGSEGV) at 0x0007d9d0 (code=1)
F/libc    (  150): Fatal signal 11 (SIGSEGV) at 0x0007d9d0 (code=1)
E/ThermalDaemon(  157): Thermal daemon started
I/rmt_storage(  156): rmt_storage user app start.. ignoring cmd line parameters
I/rmt_storage(  156): rmt_storage open success
E/ThermalDaemon(  157): Threshold 0 Action[0] : none
E/ThermalDaemon(  157): Threshold 1 Action[0] : none
E/ThermalDaemon(  157): Threshold 2 Action[0] : none
E/ThermalDaemon(  157): Threshold 0 Action Info[0] : 768000.000000
E/ThermalDaemon(  157): Threshold 1 Action Info[0] : 368640.000000
E/ThermalDaemon(  157): Threshold 2 Action Info[0] : 245760.000000
E/ThermalDaemon(  157): Number of cpus :1
I/rmt_storage(  156): 3 supported partitions found
E/ThermalDaemon(  157): No rules to monitor sensor 'XO_THERM' disabled: 0 num_thresholds: 0
E/ThermalDaemon(  157): No rules to monitor sensor 'XO_THERM_GPS' disabled: 0 num_thresholds: 0
E/ThermalDaemon(  157): No rules to monitor sensor 'POP_MEM_TZ' disabled: 0 num_thresholds: 0
F/libc    (  171): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  168): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  172): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  169): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  166): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  180): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  181): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  178): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  177): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  175): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  189): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  190): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  186): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  187): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  184): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  200): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  198): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  201): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  197): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  195): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  209): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  210): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  206): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  204): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  218): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  219): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  216): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  215): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  213): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  227): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  225): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  228): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  224): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  222): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  237): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  234): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  233): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  231): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  243): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  245): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  246): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  242): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  240): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  254): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  252): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  255): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  251): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  249): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  263): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  264): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  261): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  260): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  258): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  272): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  273): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  270): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  269): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  267): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  281): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  279): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  282): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  278): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  276): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  290): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  288): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  291): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  285): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  287): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  300): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  297): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  299): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  296): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  294): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  308): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  309): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  306): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  305): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  303): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
I/rmt_storage(  156): rmt_storage open event: handle=1
I/rmt_storage(  156): Opened /boot/modem_fs1
I/rmt_storage(  156): rmt_storage events processing done
I/rmt_storage(  156): rmt_storage send user data event
I/rmt_storage(  156): rmt_storage events processing done
I/rmt_storage(  156): rmt_storage client thread started 
I/rmt_storage(  156): rmt_storage open event: handle=2
I/rmt_storage(  156): Opened /boot/modem_fs2
I/rmt_storage(  156): rmt_storage events processing done
I/rmt_storage(  156): rmt_storage send user data event
I/rmt_storage(  156): rmt_storage events processing done
I/rmt_storage(  156): rmt_storage client thread started 
I/rmt_storage(  156): rmt_storage write event
I/rmt_storage(  156): rmt_storage events processing done
I/rmt_storage(  156): unblock rmt_storage client thread
I/rmt_storage(  156): rmt_storage fop(1): bytes transferred = 3145216
I/rmt_storage(  156): rmt_storage fop(1): bytes transferred = 512
F/libc    (  317): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  320): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  316): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  314): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  328): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  326): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  329): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  325): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  323): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  337): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  338): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  334): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  335): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  332): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  346): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  344): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  347): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  343): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  341): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  355): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  352): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  353): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  356): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  350): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  364): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  362): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  365): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  361): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  359): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  373): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  371): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  374): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  370): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  368): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  382): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  380): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  383): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  379): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  377): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  391): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  389): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  392): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  388): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  386): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  400): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  401): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  398): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  397): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  395): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
F/libc    (  409): Fatal signal 11 (SIGSEGV) at 0x00001e84 (code=1)
F/libc    (  407): Fatal signal 11 (SIGSEGV) at 0x00002e50 (code=1)
F/libc    (  410): Fatal signal 11 (SIGSEGV) at 0x00003dec (code=1)
F/libc    (  406): Fatal signal 11 (SIGSEGV) at 0x00001ea0 (code=1)
F/libc    (  404): Fatal signal 11 (SIGSEGV) at 0x00005db0 (code=1)
 
Upvote 0
#12
I did a quick Google search on fatal signal 11 and SIGSEGV. Apparently it is called a segmentation fault. The cpu is trying to access memory it can't address. I saw one instance on stack overflow that was caused by allocating too much memory or the process ran out of memory to use. Don't know what that means for this case though.
 
Upvote 0
#13
Okay, I fixed that error. Now here's where it's getting stuck:

Code: 
I/cm      (  126): Welcome to Android 4.1.2 / CyanogenMod-10-20130316-UNOFFICIAL-iconvmu 
I/cm      (  127):                                                 _  
I/cm      (  128):  __ __ _ ___  _ _  __  ___  __ _ _  _  _  __  __)) 
I/cm      (  129): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(  
I/cm      (  130):      ))                 _)) 
I/cm      (  131):   
I/rmt_storage(  171): rmt_storage user app start.. ignoring cmd line parameters
I/rmt_storage(  171): rmt_storage open success
E/ThermalDaemon(  172): Thermal daemon started
E/ThermalDaemon(  172): Threshold 0 Action[0] : none
E/ThermalDaemon(  172): Threshold 1 Action[0] : none
E/ThermalDaemon(  172): Threshold 2 Action[0] : none
E/ThermalDaemon(  172): Threshold 0 Action Info[0] : 768000.000000
E/ThermalDaemon(  172): Threshold 1 Action Info[0] : 368640.000000
E/ThermalDaemon(  172): Threshold 2 Action Info[0] : 245760.000000
E/ThermalDaemon(  172): Number of cpus :1
I/rmt_storage(  171): 3 supported partitions found
E/ThermalDaemon(  172): No rules to monitor sensor 'XO_THERM' disabled: 0 num_thresholds: 0
E/ThermalDaemon(  172): No rules to monitor sensor 'XO_THERM_GPS' disabled: 0 num_thresholds: 0
E/ThermalDaemon(  172): No rules to monitor sensor 'POP_MEM_TZ' disabled: 0 num_thresholds: 0
I/rmt_storage(  171): rmt_storage open event: handle=1
I/rmt_storage(  171): Opened /boot/modem_fs1
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage send user data event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage client thread started 
I/rmt_storage(  171): rmt_storage open event: handle=2
I/rmt_storage(  171): Opened /boot/modem_fs2
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage send user data event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage write event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage client thread started 
I/rmt_storage(  171): rmt_storage fop(1): bytes transferred = 3145216
I/rmt_storage(  171): rmt_storage fop(1): bytes transferred = 512
 
Upvote 0
#15
Upvote 0
#17
Jimmy422 said:
Here's the boot image:

boot.img

Also I think you're using an incorrect defconfig file for the kernel. The icon00 is something else, because if you compare it with the one on the phone it's completely different. I'll recompile with the one pulled from the phone and see if that makes a difference.
Click to expand...

No the icon00 defconfig is correct kernel config for the Reverb. Its in the README-Kernel file from the official Samsung source fyi. I use that config to compile the reverb kernel.
 
Upvote 0
#20
Unfortunately I'm going back to college today, so my free time will likely be nonexistant yet again.

However, we've made a ton of progress. We now have a (almost) booting ROM and a github, so others can definitely pick up where I left off.

The updated repos can be found at

https://github.com/Jimmyk422/android_device_samsung_iconvmu_jb

and

https://github.com/Jimmyk422/android_vendor_samsung_iconvmu_jb

What I know so far:

It's not giving me a dmesg (which is probably the next step). I get

Code: 
klogctl: Operation not permitted
When I try to run it. I can't find how to fix that, but I think once it's fixed we can start finding out why it's getting stuck.

Here's the last logcat I got

Code: 
I/cm      (  126): Welcome to Android 4.1.2 / CyanogenMod-10-20130317-UNOFFICIAL-iconvmu 
I/cm      (  127):                                                 _  
I/cm      (  128):  __ __ _ ___  _ _  __  ___  __ _ _  _  _  __  __)) 
I/cm      (  129): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(  
I/cm      (  130):      ))                 _)) 
I/cm      (  131):   
I/rmt_storage(  171): rmt_storage user app start.. ignoring cmd line parameters
I/rmt_storage(  171): rmt_storage open success
I/rmt_storage(  171): 3 supported partitions found
I/rmt_storage(  171): rmt_storage open event: handle=1
I/rmt_storage(  171): Opened /boot/modem_fs1
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage send user data event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage client thread started 
I/rmt_storage(  171): rmt_storage open event: handle=2
I/rmt_storage(  171): Opened /boot/modem_fs2
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage send user data event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage write event
I/rmt_storage(  171): rmt_storage events processing done
I/rmt_storage(  171): rmt_storage client thread started 
I/rmt_storage(  171): rmt_storage fop(1): bytes transferred = 3145216
I/rmt_storage(  171): rmt_storage fop(1): bytes transferred = 512

It's stopping at rmt_storage. I have no idea why.

That's all I know. Hopefully Interloper can explore a little bit if he has some free time.
 
Upvote 0
You must log in or register to reply here.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones

Best Android Phones

See All
  1. Google Pixel 8 Pro Check Price
  2. Samsung Galaxy S23 Ultra Check Price
  3. Samsung Galaxy Z Fold5 Check Price
  4. Google Pixel 8 Check Price
  5. Samsung Galaxy S23 Check Price

Upcoming

See All
  1. Samsung Galaxy S24 Early Access

Best iPhones

See All
  1. Apple iPhone 15 Pro Max Check Price
  2. Apple iPhone 15 Pro Check Price
  3. Apple iPhone 15 Plus Check Price
  4. Apple iPhone 15 Check Price
  5. Apple iPhone SE (2022) Check Price

Upcoming

See All
  1. Apple iPhone 16 Early Access

Tablets

Best Tablets

See All
  1. Samsung Galaxy Tab S9 Ultra Check Price
  2. Apple iPad Pro (2022) Check Price
  3. Apple iPad Air (2022) Check Price
  4. Apple iPad Mini (2021) Check Price
  5. Microsoft Surface Pro 9 Check Price

Upcoming

See All
  1. Apple iPad Air 6 Early Access
  2. Apple iPad Fold Early Access

Laptops

Best Laptops

See All
  1. Apple Macbook Pro Check Price
  2. Apple Macbook Air (2023) Check Price
  3. Dell XPS 13 Check Price
  4. Acer Chromebook Spin 714 Check Price
  5. Dell Alienware m18 (2022) Check Price

Upcoming

See All
  1. Microsoft Surface Laptop 6 Early Access
  2. Microsoft Surface Pro 10 Early Access

Televisions

Best TVs

See All
  1. Samsung The Frame TV Check Price
  2. Samsung Neo QLED 4K QN90C Check Price
  3. LG G3 OLED Check Price
  4. LG A2 OLED Check Price
  5. ROKU Plus Series Check Price
  6. Samsung S90C OLED Check Price
  7. SunBriteTV Veranda 3 Check Price

Upcoming

See All
  1. Hisense 110UX ULED X TV Early Access

Game Consoles

Best Game Consoles

See All
  1. Nintendo Switch OLED Check Price
  2. Microsoft XBOX Series X Check Price
  3. Sony Playstation 5 Check Price
  4. Microsoft XBOX Series S Check Price
  5. Nintendo Switch Lite Check Price

Upcoming

See All
  1. Nintendo Switch 2 Early Access

Wearables

Best Wearables

See All
  1. Oura Ring 3 Check Price
  2. Apple Watch Series 9 Check Price
  3. Google Pixel Watch 2 Check Price
  4. Samsung Galaxy Watch 6 Classic Check Price
  5. Fitbit Inspire 3 Check Price
  6. Amazfit Amazfit Band 7 Check Price
  7. Apple Watch SE Check Price
  8. Apple Watch Ultra 2 Check Price

Upcoming

See All
  1. Samsung Galaxy Watch 7 Early Access

Smart Home

Smart Home Tech

See All
  1. Amazon Echo (4th Gen) Check Price
  2. Schlage Encode Smart Lock Check Price
  3. Amazon Blink Smart Cameras Check Price
  4. Google Nest Thermostat Check Price
  5. Phillips Hue Smart Lights Check Price

Upcoming

See All
  1. Apple Homepod Vision Early Access

Similar threads

Upvote 0
Samsung
  • Suggestion
Samsung Introduces New Intelligent Connectivity Features on Galaxy Book4 Series in Collaboration with Microsoft
Replies
0
Views
144
Breaking News
Samsung
Samsung
Upvote 0
Samsung
  • Suggestion
[Galaxy Unpacked 2024] Highlights From Galaxy Unpacked: The Promise of a New Beginning With Galaxy AI
Replies
1
Views
174
Breaking News
The_Chief
The_Chief
S
Help (Help)How to transfer entire Groups of Albums to PC(SamsungNote 10+/Android)
Replies
3
Views
2K
Ask a question
Dannydet
Dannydet
Upvote 0
Samsung
  • Suggestion
Travel Just Got a Whole Lot Smarter, Thanks to Samsung Galaxy S24
Replies
0
Views
146
Breaking News
Samsung
Samsung
Upvote 0
Samsung
  • Suggestion
[Editorial] Welcome to the Era of Mobile AI
Replies
0
Views
127
Breaking News
Samsung
Samsung
Top Bottom
Back
Jump to latest Follow Reply
Jump to latest Follow Reply