Develop Bugs

Confusion about recovery

So I'm kinda new to Samsung community. Just came over from the shift. Basically I installed ROM manager and now I have 2 recoveries. If I turn the phone off then hold volume up and power I get this rogue recovery. If I reboot in to recovery from room manager I have the standard clock work mod recovery. Is this normal? Thanks ahead of time for any answers!
Sent from my SPH-D710 using xda premium

Only portions of ROM manager work on this phone. Recovery is only "fake-flashed" so it isn't permanent.
I would actually suggest you don't use it on this phone due to issues people have had, but it is up to you.

The kernel included with whatever ROM you're running was repacked with Rogue recovery. Rogue is a modified version of CWM. It has all the same tools, but has modified the menus and made other changes. In a nutshell, Rogue is basically CWM, as it's built from the same source.
As sfhub said, it's probably best to avoid ROM Manager on this phone. It's unnecessary and it has the potential to cause problems.
Regarding the kernel, Samsung phones don't use a recovery partition, but rather some kind of RAMDISK on the kernel partition (or something along those lines). As a result, recovery is packed into the intramfs in the kernel. So whenever you flash a kernel, you will also be flashing whatever recovery is included with it. Keep this in mind in your future flashing.

makes perfect sense! Thanks! One more thing...since clock work is temporary can I just uninstall ROM manager and that recovery will go away? I'm using blazer ROM 4.1 if it matters
Sent from my SPH-D710 using xda premium

Yes. I would uninstall it anyway. It doesn't work well for this phone
Sent from my SPH-D710 using Tapatalk 2

ICS safe?

Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium

If you want to go back to gingerbread use el29 restore get recovery then flash CyanogenMod 9 it is better than most roms based off leaks.

Here is the latest stock ICS.
http://forum.xda-developers.com/showthread.php?t=1694695
Give the devs a little time and you can flash a kernel with the recovery you want.

harley1rocker said:
Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
They are safe to flash if you follow OP directions. Always flash from el26 cwm recovery and you're good. If you cant live without recovery, flash a touchwiz rom and use agat63s repack recovery.

SFhub just released an updated FF02+CWM repack built on GB code to avoid the eMMC lockup bug. However, you need to check the ROM and see if update-binary is corrected or not.
Please look for his post on this here:
http://forum.xda-developers.com/showthread.php?t=1694695&page=7
The other safe solution is the one that has been known - go back to EL26 and flash away from there. (GB doesn't have the offending code that causes the bug to be triggered.)

I've been using Calkulin's E4GT 2 v1.6 ICS rom since version 1.6 came out (FE22) and I haven't had a single crash or FC, and I've been getting good battery life.. I never even get close to dying and thats even with a couple hours of screen on time (games, facebook, lots of texting, ~1hour talk time).
I'd say go for it =) Just make sure you follow all instructions carefully! This ROM was very easy to flash.. I had been using Calkulin's GB rom (el29) and all I had to do was wipe my caches and flash his .zip file in CWM.. bam, ICS ^_^

When you say safe what is it you really mean... cuz its all SAFE if you know what you are doing..

Well nothing is ever 100% safe. There is always a small chance you could screw things up somehow (the eg31 deal back when the phone was first released, the emmc bug, etc). There are always possible unknown side effects that don't become obvious until down the line.
That said, if you are careful, the odds of doing something irreversible are extremely small on a phone that has been out for a few months or more.
Sent from my SPH-D710 using Tapatalk 2

[Q] Will someone update the multiboot fuction to work with CM10?

I am running CM10 nightly 24. When I try using the cm9 utility it wont flash in CWM, it errors. Will someone please make a new version that will boot the Epic from SD on CM10? If not, does anyone know how to make the cm9 version to work?
CM9 Multiboot Utility:
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html

At the risk of raising your ire, are you sure you're doing it right? I don't think the utility cares which CM version you're running (unless the repartitioning that's part of CM10 interferes with it??).
You need to download and untar the utility tarball onto your PC first, then copy the boot_FC09.zip from your PC to your SD card's /sdcard/multiboot/FC09 directory.
Al

arschend said:
At the risk of raising your ire, are you sure you're doing it right? I don't think the utility cares which CM version you're running (unless the repartitioning that's part of CM10 interferes with it??).
You need to download and untar the utility tarball onto your PC first, then copy the boot_FC09.zip from your PC to your SD card's /sdcard/multiboot/FC09 directory.
Al
Click to expand...
Click to collapse
No, he's correct. The current multiboot utility won't work from CM10 due to some undetermined incompatibility between the kernels. I intend to post a workaround soon, which basically has you flash a 2.6 kernel so the multiboot will work, then flash back your proper CM10 kernel after you're done. Bit of pain with the extra steps, but it's faster than restoring all the way back to CM9.
Sent from my SPH-D700 using xda app-developers app

bbelos said:
No, he's correct. The current multiboot utility won't work from CM10 due to some undetermined incompatibility between the kernels. I intend to post a workaround soon, which basically has you flash a 2.6 kernel so the multiboot will work, then flash back your proper CM10 kernel after you're done. Bit of pain with the extra steps, but it's faster than restoring all the way back to CM9.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
thanks for the info, now i dont have to odin to switch prls again.

bbelos said:
I intend to post a workaround soon, which basically has you flash a 2.6 kernel so the multiboot will work, then flash back your proper CM10 kernel after you're done.
Click to expand...
Click to collapse
Are saying all i need to do is flash 2.6 kernel and it'll work
Sent from my SPH-D700 using xda premium

pctech101 said:
Are saying all i need to do is flash 2.6 kernel and it'll work
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
You can try that yes.
1. Boot into recovery.
2. Do a backup, if you don't already have one with your current kernel.
3. Flash a 2.6 kernel (I tested with a CM9 kernel)
4. Reboot to recovery (since you won't be able to boot CM10)
5. Flash the boot_FC09.zip
6. Do whatever you need to do
7. Boot back into recovery
8. Advanced restore -> boot (or reflash CM10, reflash your CM10 kernel of choice, full restore, etc.)
How you restore your proper CM10 kernel is up to you. Advanced restore seems like the easiest way if you remember to backup first, although I haven't tested that method yet.

thanks. i used cleangb kernel and then multiboot worked.
Sent from my SPH-D700 using xda premium

I have a proper fix for using the multiboot from CM10. Stay tuned.

sense port issues

Tried to use logcat to figure out why rom wasn't booting but adb daemon wasn't starting which led me to believe that the kernel hadn't loaded. So I pulled the recovery log from when I installed the rom zip. It seems that for some reason the install process skips over the kernel for some reason. here is the recovery log and both updater-scripts. I cut out a lot of crap on the recovery where it was extracting apps and stuff so you can see where it skips. I get no errors or anything that I can tell. it just doesnt install the kernel.
Recovery Log
updater-script sense port
updater-script base s3
any advice?
EDIT finally got the kernel to install. I was told that all you needed to do to get it to at least boot was copy the bootclasspath from the sense kernel to the base kernel and it would (should) boot up enough for me to run logcat and figure out where to go from there. However ive swapped out the bootclasspath and left it stock. ive even left the kernel completely stock (base cm9 kernel) or installed the pure sense kernel (sense port is evo 4g lte stock rom) and I get the EXACT same boot loop. it makes it to the second boot logo (Samsung Galaxy S III) then right before the boot animation it boot loops. Ive compared all the .rc's in the ramdisk and all are the same save for the init.rc. i tried merging the base init.rc and the sense init.rc and nothing appears to change. when i install cm9 with the same base kernel i used in the port it installs fine no issues. this is driving me bananas! i cant imagine what could be present in both separate kernels that is preventing it from booting.
I even took a guess that it wasnt the kernel and tried swapping .so files and .ko's but same thing. idk what else to do. there are sense ports for the S3 i9300 and Xperia Neo that are booting, not completely functional but booting up. ive studied the kernel of both and nothing that I can tell is different besides the obvious differences in mount points and such. what all can prevent a rom from making to the boot animation (at that point i can run logcat)? is there a list? lol
I dont have a logcat for obvious reasons and recovery.log shows no errors or anything out of the ordinary. it HAS to be something with the ROM itself. maybe a file(s) im missing or something?
Sent from my SPH-L710 using xda app-developers app

GRock84 said:
Tried to use logcat to figure out why rom wasn't booting but adb daemon wasn't starting which led me to believe that the kernel hadn't loaded. So I pulled the recovery log from when I installed the rom zip. It seems that for some reason the install process skips over the kernel for some reason. here is the recovery log and both updater-scripts. I cut out a lot of crap on the recovery where it was extracting apps and stuff so you can see where it skips. I get no errors or anything that I can tell. it just doesnt install the kernel.
Recovery Log
updater-script sense port
updater-script base s3
any advice?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF?

honest1212 said:
Are you S-OFF?
Click to expand...
Click to collapse
Ah see that's the trick lol this is a sense port to the S3 from the Evo 4G LTE. I can't get the darn thing booted to troubleshoot because the kernel never gets installed. I only make it to the second samsung boot logo then boot loop.
Sent from my SPH-L710 using xda app-developers app

[Q] Kernel Question

I'm not sure if its just my phone, had this problem for a while now, but when it occurs, i usually just flash another rom, but basically, when it comes to my rom and flashing a rom that comes with a custom kernel, its a no go what so ever, its force close central, and boot loops and all that, no idea why, but my phone just simply doesn't play nice with any custom kernels at all, started with Jellybomb, use to love it, worked perfect, no problems, then when it updated to i believe 10, 11, not precise on what version, and he used a custom kernel, then bam, tried everything, no luck, and couldnt use that rom with my phone anymore, or any other rom that comes with custom kernels, and still cant, and i guess its time to mention it to verify if this happens to anyone else.

Parkourkid93 said:
I'm not sure if its just my phone, had this problem for a while now, but when it occurs, i usually just flash another rom, but basically, when it comes to my rom and flashing a rom that comes with a custom kernel, its a no go what so ever, its force close central, and boot loops and all that, no idea why, but my phone just simply doesn't play nice with any custom kernels at all, started with Jellybomb, use to love it, worked perfect, no problems, then when it updated to i believe 10, 11, not precise on what version, and he used a custom kernel, then bam, tried everything, no luck, and couldnt use that rom with my phone anymore, or any other rom that comes with custom kernels, and still cant, and i guess its time to mention it to verify if this happens to anyone else.
Click to expand...
Click to collapse
Try kernel cleaner
Sent from my SPH-L710 using xda premium

xblackvalorx said:
Try kernel cleaner
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
where would i find that?, and what specifically does it do?

i dont want to hijack a thread but also dont want to start a new one since there is this one. has any cspire s3 users flashed a different kernel and had success with it. im on the latest pacman rom and want a diff kernel. ive flashed one before and got a softbrick. just curious.

@ IonIcone, Keep the thread to the user that's asking the question.
Search the whole forum first / search it online, if it's a no go on both parts, then start a question
thread of your owns.
@ ParkourKid93
KernelCleaner can be downloaded here.
http://forum.xda-developers.com/attachment.php?attachmentid=1319515&d=1347395869
scripted by mattrb, you can thank him for that file.
When using kernels make sure it's for the right version
JB or AOSP. and also make sure its for the right version
4.1.x or 4.2.x
Usually when you're also installing a rom with a dif kernel ( and you CAME from a rom with STOCK kernel )
you'll need to wipe cache and dalvik cache, and re-set permissions via Custom Recovery.
If those don't work, search the original ROM thread for a [Q] of the same as yours and see if there was a fix / reply for that.
If all else fails, contact the dev of the rom with your specific issue.
I've been switching between kernels and JB versions and i've never ran into this issue. Anthrax, K747, Agat's and Stock Optimized.
Have you tried odin flash restore to stock LJ7 and re-installing the rom as well?

ionicone said:
i dont want to hijack a thread but also dont want to start a new one since there is this one. has any cspire s3 users flashed a different kernel and had success with it. im on the latest pacman rom and want a diff kernel. ive flashed one before and got a softbrick. just curious.
Click to expand...
Click to collapse
No problem bro, does sound like you flashed a wrong kernel for your phone, but like spark said, look around, their is a lot of topics on soft bricked phone, you will deffinatly find something on it
Sent from my SPH-L710 using xda premium

Spark91 said:
@ IonIcone, Keep the thread to the user that's asking the question.
Search the whole forum first / search it online, if it's a no go on both parts, then start a question
thread of your owns.
@ ParkourKid93
KernelCleaner can be downloaded here.
http://forum.xda-developers.com/attachment.php?attachmentid=1319515&d=1347395869
scripted by mattrb, you can thank him for that file.
When using kernels make sure it's for the right version
JB or AOSP. and also make sure its for the right version
4.1.x or 4.2.x
Usually when you're also installing a rom with a dif kernel ( and you CAME from a rom with STOCK kernel )
you'll need to wipe cache and dalvik cache, and re-set permissions via Custom Recovery.
If those don't work, search the original ROM thread for a [Q] of the same as yours and see if there was a fix / reply for that.
If all else fails, contact the dev of the rom with your specific issue.
I've been switching between kernels and JB versions and i've never ran into this issue. Anthrax, K747, Agat's and Stock Optimized.
Have you tried odin flash restore to stock LJ7 and re-installing the rom as well?
Click to expand...
Click to collapse
I actually tried that same exact kernel cleaner this morning, I searched and found it, had no luck with it though, and for the 'choosing the right kernel', it comes built in with the ROM, its the jelly bomb 14 ROM I'm referring to, also did wipe both caches and fixed permission, still no luck, I want to believe its my phone itself though, because I know it wouldn't be the ROM, I deff trust the ROM and developer obviously, and used his work before, but that's when he didn't use a custom kernel, but when he included the custom kernel built in, I believe jellybomb 10, or 11, then it was the last time I could of flashed any of his Roms, I do remember having similar problems with other Roms that uses custom kernels also, the only kernel my phone plays great with, is the stock optimized, and the cyanogenmon kernels, but ktoons and agats, and even anthrax (when I was using freeza fregs3, just went no go on my device
Sent from my SPH-L710 using xda premium