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

Root SyndicateROM Frozen

I believe the concern is boot looping. If at the higher frequencies errors start occurring it will reboot and do that over and over again. I hear some have the option of switching back to standard settings if an improper shutdown is detected to help prevent this issue. Not sure if set cpu does this.
 
Slow5Ohh said:
What does this do? I have it checked and am running at 100/1300 with some profiles enabled on srf 1.1. Just curious
Click to expand...

Stringyquark said:
I believe the concern is boot looping. If at the higher frequencies errors start occurring it will reboot and do that over and over again. I hear some have the option of switching back to standard settings if an improper shutdown is detected to help prevent this issue. Not sure if set cpu does this.
Click to expand...

Bingo. Some Epics simply won't handle certain settings, and if yours is one of them and it's set that way on boot, you're in a world of hurt. Once you find something stable your phone can handle, then setting it on boot (which literally means when your phone boots up) is fine and dandy.

However, if your Epic is one of the ones that cannot handle 1.3 (which is sounds like it can) if you have it set to do that on boot, then you've kind of hosed yourself. So when testing certain limits, make sure to uncheck that box. When you find what you're happy with and what it can handle, than just run it that way all the time.
 
Stringyquark said:
I believe the concern is boot looping. If at the higher frequencies errors start occurring it will reboot and do that over and over again. I hear some have the option of switching back to standard settings if an improper shutdown is detected to help prevent this issue. Not sure if set cpu does this.
Click to expand...

In my experience I was at standard 1000/100 and it went into endless reboot.
It could be the "set on a boot" SETCPU thing, but that would imply a flaw with Syndicates ROM as Bonsai is stable with this option set.

I think 1.1 is not quite finished.
 
Andrzey said:
In my experience I was at standard 1000/100 and it went into endless reboot.
It could be the "set on a boot" SETCPU thing, but that would imply a flaw with Syndicates ROM as Bonsai is stable with this option set.

I think 1.1 is not quite finished.
Click to expand...

No, that would be more of a kernal thing, not a ROM thing. Bonsai uses (I believe) a different kernal.

However, if this was the first time you flashed a ROM, especially your first EXT4 ROM, then the majority of people have problems their first flash, regardless of what ROM they're on.

So you may have flashed SRF, boot looped, then flashed Bonsai and it was fine. However, had you flashed SRF again, I bet it would've worked out. If you're up for it, try flashing SRF again and see what happens.
 
I am on 2.2.1 EB13 & flashed the EC05 modem & the latest version of this ROM. Everything seems to be working fine...is there any reason why I should Odin to EC05 & do this all over again?

I just want to make sure I'm not missing out on anything!
 
New user here... though I've lurked for a quite a while now. There's is a lot of great information here and it seems the community is very friendly and helpful.

I have a few questions about the entire process of root to syndicate frozen rom and I haven't seen them addressed in other threads.

1. Does converting file system to EXT4 automatically erase/format the storage on the phone to convert?

2. The instructions mention doing a 3x wipe (data/cache/delvik or whatever), however settings for some apps I use are obviously stored in data. Is it possible to backup those settings to the SD card first (using root explorer), then do the wipes, then copy the settings back after reinstalling the apps? Is it even possible to copy files that were created on the RFS file system onto the EXT4 file system? Is this recommended? Or, will it cause problems?
 
Mith22 said:
2. The instructions mention doing a 3x wipe (data/cache/delvik or whatever), however settings for some apps I use are obviously stored in data. Is it possible to backup those settings to the SD card first (using root explorer), then do the wipes, then copy the settings back after reinstalling the apps? Is it even possible to copy files that were created on the RFS file system onto the EXT4 file system? Is this recommended? Or, will it cause problems?
Click to expand...

I back up settings within the individual apps to the SD card, then I use My Backup to backup all apps to the SD card. Then I do all those things, flash the ROM, restore the apps then restore the settings. That has never been a source of trouble for me.
 
Mith22 said:
New user here... though I've lurked for a quite a while now. There's is a lot of great information here and it seems the community is very friendly and helpful.

I have a few questions about the entire process of root to syndicate frozen rom and I haven't seen them addressed in other threads.

1. Does converting file system to EXT4 automatically erase/format the storage on the phone to convert?

2. The instructions mention doing a 3x wipe (data/cache/delvik or whatever), however settings for some apps I use are obviously stored in data. Is it possible to backup those settings to the SD card first (using root explorer), then do the wipes, then copy the settings back after reinstalling the apps? Is it even possible to copy files that were created on the RFS file system onto the EXT4 file system? Is this recommended? Or, will it cause problems?
Click to expand...

1. Yes, all data will be wiped from the phone, so anything you want to keep, make sure you save it to the SD card.
2. Yes, the saves from your games and such will also be gone.

droid newb said:
I back up settings within the individual apps to the SD card, then I use My Backup to backup all apps to the SD card. Then I do all those things, flash the ROM, restore the apps then restore the settings. That has never been a source of trouble for me.
Click to expand...

From what I've seen and read, restoring data isn't the best idea. While it may work, it has also been known to cause quite a few problems too. My suggestion? Back up all the apps + data and when you're fresh on a new ROM, reload the apps back in and then one by one, reload the data. I believe MyBackup Root allows you to do this...
 
I need some help PLEASE. I followed instructions on the XDA site (via the video) to a T (except I skipped the one click root because I already did it).

Everything worked fine until reboot. It gets stuck on the Samsung screen. I did a battery pull and did everything all over again, and same thing.

I did also tell it to fix permissions.

Does anyone know why it says:

E:Can't open /cache/recovery/log ??? it's showing this in the log after just about every thing I do.
 
sounds like a kernel panic, what kenel are you using? you might want to download and try vision kernel (its posted it here as well)
 
I don't see the link for it, just a mention of it being up. I guess I'm using whatever came with the rom. My phone was stock, except the one click root, which has been almost flawless for about a week.

Last night, i downloaded the rom onto my desktop. This morning I put it on my SD card, etc, according to the video.

I can't do anything with my phone right now except access the clockwork recovery.
 
I'm working on downloading all the files to odin back to stock. Then I'll one click root again. Then leave it the hell alone. It's making me mad that others had zero issues, and I bricked my damn phone. I have had no phone for 4 hours now.
 
forddna said:
I'm working on downloading all the files to odin back to stock. Then I'll one click root again. Then leave it the hell alone. It's making me mad that others had zero issues, and I bricked my damn phone. I have had no phone for 4 hours now.
Click to expand...

Which version of one click did you do? Was it the 3.xxxx version that converts over to EXT4?

Also, before you flashed the ROM, did you do the 3x wipe on Data, Cache, and Dalvik cache?

Did you verify the download of the ROM.zip file was not corrupted?

Sometimes things gets corrupted one way or another. It took me a few tries to get it working properly. I have yet to try the 1.1.0 version though.
 
he may have done everything properly, just happens that the kernel i believe sets 1.2ghz on boot, some devices cant handle it
 
She.

Yes, 3x wipe of all three things, per the video. I literally held my phone in my hand while watching the video and did exactly what it said to do.

Sorry, I did the one click root in the WIP thread.

BTW, 5 hours later, I got my phone working, thanks to Odin. I may try it again when things are more stable, now that I have all the things needed to rescue my phone. I'm just too frustrated with it for right now.
 
forddna said:
She.

Yes, 3x wipe of all three things, per the video. I literally held my phone in my hand while watching the video and did exactly what it said to do.

Sorry, I did the one click root in the WIP thread.

BTW, 5 hours later, I got my phone working, thanks to Odin. I may try it again when things are more stable, now that I have all the things needed to rescue my phone. I'm just too frustrated with it for right now.
Click to expand...


It's an EXT4 based rom, so the file system is a different format then the method you used to originally root. A bit later in the WIP it discusses how to convert to EXT4.

At least it's a mistake that makes sense! :)

And you learned how to use Odin as well... That's a helpful bit of information!
 
forddna said:
She.

Yes, 3x wipe of all three things, per the video. I literally held my phone in my hand while watching the video and did exactly what it said to do.

Sorry, I did the one click root in the WIP thread.

BTW, 5 hours later, I got my phone working, thanks to Odin. I may try it again when things are more stable, now that I have all the things needed to rescue my phone. I'm just too frustrated with it for right now.
Click to expand...

Mine did the exact same thing, did the 3x wipe and re-flashed the ROM and visionkernal and it has been flawless since.
 
Kelmar said:
It's an EXT4 based rom, so the file system is a different format then the method you used to originally root. A bit later in the WIP it discusses how to convert to EXT4.

At least it's a mistake that makes sense! :)

And you learned how to use Odin as well... That's a helpful bit of information!
Click to expand...


For some reason, I was thinking the rom would change the file system for me. I dunno why I thought that, but I did. :)
 
I can flash the vision kernal without a rom, correct? I was thinking of doing it anyway for overclocking capability.
 
You must log in or register to reply here.
Back
Top Bottom