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

Root [ROM] CTMod 3.80 (04/06/13)

UncleBud said:
I'm on CTMod 3.75, ff19 baseband, 8GB class 10 sd card with 7GB fat and 1GB ext4. I go into kouma setting and select data, it prompts to reboot, I reboot and it just hangs at the kouma kernal 2.5 splash screen. Same deal after reflashing the rom and formatting sd-ext4. Any suggestions much appreciated.
Click to expand...

Try it without reflashing.

Flash rom
Switch to data mode
Boot into recovery
Go into mounts and storage
Format sdext
Reboot
 
OK after the last splash screen freeze, rebooted to CWM, formatted sd-ext4, rebooted, same deal froze on splash screen.
Reflashed, immediately on first boot set to data, rebooted to recovery, formated ext4, reboot, froze. Beginning to think my phone just does not want me on CTMod for some reason.
 
Just wanted to let people know that there is nothing wrong with the voltage control system app...turns out that when you hot boot (or when it lags out and hot boots on you) the voltage control settings dont load properly just fyi for anyone that switched or was having problems
 
Slayer72 said:
I wonder why some people have to do that and some don't, I'm one of the ones that didn't have to do that, all I did was perform a wipe data/factory reset, wipe cache and dalvik-cache and then installed CT3.75 then when it booted afterwards I went into CT Settings, then Kernel Settings and switched it to data then rebooted, when it came back up it showed I had 0.88 GB free of the 1 GB partition that I have created on my MicroSD Card already... Hmmm, strange... And that was from the 1 GB partition that I created when I was back on CTMod 3.68... :p
Click to expand...

What you will see happen when you change from one mode to the other without formatting is a lot of space used up duplicating files in the sd-ext that end up serving no useful purpose.

to elaborate, in ssm mode, the /sd-ext folder would contain everything that would be in /data/data. This is a series of folders that are all named with the internal name of all your apps, system and user, (i.e. com.android.camera, com.android.certinstaller, etc) those folders contain the databases, libraries and preferences for every app on your system. i.e. your text messages, contacts, ringtone settings, security features, etc

when you then change to Data mode, /sd-ext becomes /data and all of those folders have effectively been moved up a level. So, when the phone reboots, and that new mounting location takes effect, there now is no longer a /data/data folder and it makes a new one and starts filling it with default settings for all your system apps. It also makes a new /data/app folder, since there isn't one anymore because that data was on the internal storage and is no longer mounted. So now all your installed apps are 'gone'.

going the other way presents even more possible issues. because now /data would become /data/data and all your datafiles from data mode would appear to be settings that android would need to interpret. It would think it should be able to find an app called dalvik-cache, or an app named app, that has sub-settings all named after all the apps you had installed before. This can potentially lead to a serious phone WTF moment.

It can also just lead to you having a big chunk of your sd-ext wasted with files that you can't use and should just get rid of to save space.
 
Thank you Slayer and LV for the help, but all for nought I guess, no matter what I try this phone just refuses to cooperate with kouma kernel. The rom did seem somewhat smoother, but also comes with that annoying bleebloop noise whenever my signal comes and goes. I'm one of the unfortunates with almost 0 signal here on the homefront, and have to use grooveip thru my wifi. Somehow JoyOS doesn't give me that annoying noise on signal loss, and I have my extended memory as it uses kato so I guess it's back to Joy.

Thanks again for the help :)
 
i did have debugging on but i tried after and and still no go all drivers are installed and tried a different port. I tried my wife's prevail with my sdcard and had no issues. any other suggestions? thanks
 
jack52482 said:
i did have debugging on but i tried after and and still no go all drivers are installed and tried a different port. I tried my wife's prevail with my sdcard and had no issues. any other suggestions? thanks
Click to expand...

That is weird, if her phone works and yours doesn't, drivers are good then. Might be something wrong with usb port on phone:confused:, Does it charge plugged into pc? When did this start to happen? How long have you been running the rom? Maybe someone else knows and answer to this and if all fails just reflash rom, but wait to see if someone can help first!
 
UncleBud said:
Can ANYbody toss me a bone here please? All I want is the extended internal memory from my 1024MB ext4 partition, don't give a rat's ass about swappiness and all that. This was always totally painless with other roms, never had to bother with apps2sd and all that crap, just flashed the rom and bam, 1GB+ of internal ram.

I'm on CTMod 3.75, ff19 baseband, 8GB class 10 sd card with 7GB fat and 1GB ext4. I go into kouma setting and select data, it prompts to reboot, I reboot and it just hangs at the kouma kernal 2.5 splash screen. Same deal after reflashing the rom and formatting sd-ext4. Any suggestions much appreciated.
Click to expand...


I've had the same exact problem!! I've tried pretty much everything that was suggested...even as far as upgrading my sd card to a 32gb class 10 with a 2gb partition. I had CTMod up and running for about 2hrs...thought things were straightened out..had to do a reboot and bam STUCK on the splash screen again:questionmark::questionmark::banghead::shot:.....so if you or anyone comes up with a solution please do pass on. I am at a standstill after reading, and reading, and reading, and researching, and researching............
 
monticello said:
wonder if i should use twrp instead of cwm
Click to expand...

The download was pulled because there were some problems with it.

Hroark just said on the xda thread regarding twrp that he bricked his prevail, and isn't sure if it was caused by using twrp or not. But since he no longer has a working prevail, he isn't going to continue doing dev work for it. So cwm is what we got.
 
Slayer72 said:
I'm currently reinstalling CT3.75 in TWRP, just an FYI for those that are using TWRP like me, after you switch to DATA mode and reboot once in TWRP don't go to Mounts and Storage go to the Wipe button and there you will find the SD-EXT button that's where you wipe it, I guess as far as TWRP is concerned wiping and formatting are considered the same thing... :p

EDIT: Ok got CT3.75 reinstalled, switched to DATA, rebooted to TWRP, went to Wipe Menu, tapped the SD-EXT button, it formatted sd-ext, rebooted back into system, checked Settings>Applications>Manage Applications and it shows I have 60 MB used out of 0.88 GB free from my 1 GB partition, so everything is working properly as far as I can see... :D This is also with nothing installed...
Click to expand...

Hey slayer would mind if i ask you to share twrp file?
 
Well, I LIKE both responses, from LV as well as from Slayer..........

TWRP runs great for most of us, but heyyyyyyyyyyy, we all know there was something "buggy" going on with TWRP according to Hroark..... So I think it's everyone's OWN RESPONSIBILITY to either run the safe CWM or risk putting TWRP on it !! :)

So if someone gets a download link and bricks his phone, don't complain !!
 
Slayer72 said:
Well since he wasn't sure if TWRP was the cause of it then TWRP can't be directly blamed for it, I'm using TWRP along with other people in this forum and it's working perfectly fine, if anyone wants a DL link for it just PM me...
Click to expand...

Well I'm glad you're confident enough to release his firmware... because he sure felt a need to pull the links
 
Slayer72 said:
Well since he wasn't sure if TWRP was the cause of it then TWRP can't be directly blamed for it, I'm using TWRP along with other people in this forum and it's working perfectly fine, if anyone wants a DL link for it just PM me...
Click to expand...

I thought with Odin that it's impossible to fully brick?:confused:

That also reminds me of something else I want to ask, since there are some guru's watching this thread.
Since there are possibilities of bricking, and other massive screw-ups, it would make sense to me to have a safer way to test out kernels, ROMs, etc.

The best way that could be done would be to have an option to boot up kernel, etc from SD card, leaving all of the on-phone NAND alone. I realize that this would need a custom boot loader that could give you the option to do this, but don't we already use a custom one now? :confused:

If this could be done, installing a new ROM could be as simple as using 'dd' on Linux to an SD card. No need for CWM flashing, and complicated instructions etc etc etc... Just have the boot loader check the SD card for kernel magic (easy to do, just like the 'file' utility), and have the boot go there, instead of NAND. If you end up liking the ROM, _THEN_ you could flash it. If you didn't, no harm done to your old set up, no backup required, it's still all there untouched.

Why this has not been done yet for any device, at least as far as I am aware of, is a complete mystery to me. In my honest opinion, it would have been the most logical thing to do from the start. :confused:
 
ajkII said:
I thought with Odin that it's impossible to fully brick?:confused:

That also reminds me of something else I want to ask, since there are some guru's watching this thread.
Since there are possibilities of bricking, and other massive screw-ups, it would make sense to me to have a safer way to test out kernels, ROMs, etc.

The best way that could be done would be to have an option to boot up kernel, etc from SD card, leaving all of the on-phone NAND alone. I realize that this would need a custom boot loader that could give you the option to do this, but don't we already use a custom one now? :confused:

If this could be done, installing a new ROM could be as simple as using 'dd' on Linux to an SD card. No need for CWM flashing, and complicated instructions etc etc etc... Just have the boot loader check the SD card for kernel magic (easy to do, just like the 'file' utility), and have the boot go there, instead of NAND. If you end up liking the ROM, _THEN_ you could flash it. If you didn't, no harm done to your old set up, no backup required, it's still all there untouched.

Why this has not been done yet for any device, at least as far as I am aware of, is a complete mystery to me. In my honest opinion, it would have been the most logical thing to do from the start. :confused:
Click to expand...

Hardware failure can cause a hard brick that even the all mighty Odin can't save you from. That is what happens if you use Rom manager on the prevail.
 
Soooo I have A question, my phone's signal jumps around all over the place, most of the times my signal and the 3g sign would both be light Grey (instead of white than the battery life and clock and sometimes nearly when I get the best signal it would appear to be white the same colors say the clock and battery and much problem appears to be when it's light Grey it would get difficult to get data signal

Anybody getting a problem somewhat the same?
 
lettucefez said:
Soooo I have A question, my phone's signal jumps around all over the place, most of the times my signal and the 3g sign would both be light Grey (instead of white than the battery life and clock and sometimes nearly when I get the best signal it would appear to be white the same colors say the clock and battery and much problem appears to be when it's light Grey it would get difficult to get data signal

Anybody getting a problem somewhat the same?
Click to expand...

only when the weather is crap and takes out towers in my area.
it;s not the ROM, it's where you are. Try going someplace else
:smokingsomb:
 
You must log in or register to reply here.
Back
Top Bottom