Hi All
I am currently running stock Android 2.3.3 on my SGS and I have 16 GB internal storage and 16 GB microSD storage.
I want to install Cyanogenmod or DarkyROM and I also want to format the disk using a faster filesytem e.g RS or ext4.
Could you please point me in the right direction? I am not completely noob, I have flashed my HTC HD2 with TyphooN Cyanogenmod v3.5.4 successfully but I am very new to the scene.
Thanks
Mike
If you like a bit more speed, theme manager, and more custom options flash cyanogenmod. But it uses a bit more battery than stock roms and videoplayback is not fully working for some file formats, there are problems with hd videorecording and tv out is not working and also occasional bugs that the device won't wake up and so on...
When flashing a modified Samsung Stockrom you won't have this problems
For filesystem Samsung RFS and ext4 are relatively on par with speed. You won't notice any difference with the bare eye. The only problem with rfs is that it is fat based so it gets fragmented over the time and after a few months of usage the phone is getting a bit slower.
If you want a all in one package I would probably go for darky or any other rom.
If you want a small barebon like system that you can expand with the things you really need I would go for surface .
For flashing there isn't really much to do. Put the zip file with your rom on the internal sd card. Turn the phone off. Go into recovery with pressing volup+home+power and then letting go when phone turns on.
In menu choose select zip from sdcard, choose the rom and install it. Reboot and it should be done
You are very kind chainer1, I was looking at http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide and I cannot see where I could format the partition where Android will install, to ext4.
Yes I am worried about file system errors in my current SGS because I think I have ejected it without safely removing it; so I want to format both internal and external SD cards and start fresh.
Q: Can I have Hardcore's SpeedMod kernel with ClockworkMod Recovery installed as per http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide in my SGS and continue to run with my stock Androind 2.3.3?
internal and external sd card are just user space it has nothing to do with the partitions the systemfiles are on. the internal and external sdcards are fat, you cant do anything about that. when you install a stock rom through odin or kies, partitions like system, data, dbdata, cache are formatted in rfs. generally if you are flashing a roms, things on internal or external sdcard remain untouched. after you have flashed a custom rom with custom kernel you can do filesystem conversion to ext4. on kernels based of chainfire's you have to do it via chainfires ext4 app. on speedmod via recoverymode i think. but be aware that cm and samsung rom have differrnt kernels. you cant use speedmod for cm7 only for samsung roms.
and yes that should work that you can run speedmod while staying on stock.
and you dont have cwm recovery if you dont flash a custom kernel via odin before. check if there is a tar version of speedmod and flash it as pda via odin. after that it should be done.
Sent from my GT-I9000 using Tapatalk
This is great. One last question, can I format partitions like system, data, dbdata, cache using ClockworkMod Recovery? I am asking this because I can't test ClockworkMod Recovery anymore in my HD2 because I "without knowing" installed ROM Manager and updated CWM which has prevented me from using Recovery. It says "Invalid boot image".
you can format them. but you likely cant change the filesystem. i guess you can enable ext4 on speedmod in cwm, but i dont know exactly cause i havent used speedmod for ages on gingerbread
Sent from my GT-I9000 using Tapatalk
If you go to a cm rom like insanity, you get yaffs file system, which imho is miles ahead in terms of speed
Sent from my GT-I9000 using XDA Premium App
I had Samsung Android 2.3.4 and I followed http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide to the word and after
"Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically."
It it stuck at the boot where it says
Galaxy S
GT-I9000
SAMSUNG
Please help
Edit 1: Okay I installed http://forum.xda-developers.com/showthread.php?t=1106075 and now it loads that kernal.
chainer1 said:
and yes that should work that you can run speedmod while staying on stock.
and you dont have cwm recovery if you dont flash a custom kernel via odin before. check if there is a tar version of speedmod and flash it as pda via odin. after that it should be done.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Warning for new users of Samsung Galaxy S (SGS) with Gingerbread... flashing SpeedMod as per http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide will make your phone not boot! When that guide says "This guide assumes the Samsung Galaxy S already has Android 2.2 installed on it. If the Samsung Galaxy S is already rooted & has ClockworkMod Recovery installed, skip this section." it really does mean that.
Now as for my situation, I have ended up in a rather weird state:
https://lh4.googleusercontent.com/-7pw7B9B0glM/TkRh2hXHcLI/AAAAAAAACQo/WZuadkg7W44/s800/11+-+1
I have a SGS with Samsung Android 2.3.4 and TalonDEV 0.4.3 kernel installed.
My goal is to install Cyanogenmod latest Nightly.
What are my options? Thanks guys.
Related
Scenario:
- I'm running Phoenix 4 ROM
- I want to try another ROM
- I have a copy of the JH7_OTA-1.zip
Can I just use ClockworkMod Recovery to flash the JH7_OTA ROM, then do a master clear from the phone and then apply any ROM I want?
Would that not accomplish the same thing as putting the phone in download mode and doing a stock restore via ODIN, followed by a Master Clear, and then flashing any ROM?
Can someone clear this up for me because it seems that both methods accomplish the same thing. They restore your phone to factory stock ROM as it's suggested by majority of the ROM before applying them.
Thanks
You can go from one rom to another without flashing stock.
I just went from doc jpy base to andromeda armani base. All I did was disable lag fix and kernel tweaks then flashed
I did so knowing I had odin just in case
What mcord11758 said except you don't actually need to disable anything. Just flash.
So that's the confusing part because:
Cognition ROM used to saynow there is just a DL link)
"flash back to I897UCJF6 (Recommended)"
and
How to flash PHOENIX Roms:
"1. BACK UP!!!
2. Use Odin One click to Flash Stock
2a. Wait for it to reboot and then re-enable debugging, hook phone back up to pc and Master Clear"
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
I would love to hear from one of the developers but I couldn't ask this question in the Dev Forum due too my n00b posting status.
Thanks for anyone who takes the time to provide some insight.
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Vezee said:
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
Click to expand...
Click to collapse
The partitions get formatted either way (unless it's now wipe, in which case I guess data and datadb don't). If are running ext4 and your new kernel supports ext4 then why disable it?
mcord11758 said:
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Click to expand...
Click to collapse
Thanks, that was the answer I was looking form I didn't exactly understand that the restriction was the recovery rom. It makes sense.
I was out today, minding my own business.
In the middle, my phone just shut off. Restarting it, it would not boot past the kernel boot screen, not even into CWM. When I got home, I oneclicked it to stock in an attempt to return to my nandroid CM7 from right before the full-9 package was released. I encountered an issue.
CWM3 said "Error: Can't mount /sdcard". Booted the phone up in JF6, and the storage menu shows both my External and internals reading with total and available space as "Unavailable", and both the mount and format options on both are greyed out. Internal phone storage is normal, however, and reads 1.73GB.
Don't ask me to flash Froyo or something. Standard 2e recovery does not allow me to use a ROM Manager flashable CWM2, thus I cannot flash Froyo or CM7's package. CM7's initial kernel returns the "Can't mount /sdcard" error, so that's also inadequate.
So, anyone have any idea what I'm dealing with here? How would I be able to go about fixing it? If it helps, my IMEI number and all that jazz is still present.
EDIT: I just realised a perplexing quality. The phone will ONLY boot with an external SD in it... Doesn't matter if I remove it after, it just needs an external in it to boot. Once the phone boots, it's dead weight. Funny, as I always flash without it in there...
EDIT2: Found some info from Supercurio on the Bell Vibrant while searching, I wonder if this is relevant...
supercurio said:
On #project-voodoo IRC I helped a user who had issues with his SDcard on a Bell I9000M
Turns out that his internal SD MoviNAND chip was dead!
The system automatically used his external SD as a backup for /data, as the "mmcblk1" device become "mmcblk0".
The internal SD was so dead that the Linux Kernel didn't detected any existence of it anymore.
The symptom that the phone was working (using the external SD) but he couldn't mount his SD card anywhere.
Eventually he had a replacement from Bell in a few days.
What killed the sdcard ? An old Ext2 lagfix when creating the giant 1GB+ loop files.
But it wasn't the lagfix fault. It just acted as accelerator.
Click to expand...
Click to collapse
But I've never used that lagfix. I've been on Speedmod then CM7 the entire time.
Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.
emcnelly said:
Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.
Click to expand...
Click to collapse
Already said, CWM returns "Can't mount /sdcard" in CM7's CWM3 from the initial kernel... I can't flash Froyo, so Speedmod is out of the question.
Thread moved.
I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.
studacris said:
I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.
Click to expand...
Click to collapse
Did not work; tried flashing JH7, KB1 and JF6, all 3 do not boot past the kernel screen. Only OCD JF6 gets the phone in a working way. I found some other threads, but it's looking worse and worse by the second.
ATT is probably getting a call tomorrow...
Same happened to me, I managed to get JI6 working somewhat. Flash the one click ODIN JI6, wait till bootanimation ends, ROM will not boot up completely so go back into download mode, then flashed speedmod with three button ODIN, let boot up complete then go into recovery and delete user data, wipe cache and dalvik cache.
Still don't have an mnt/sdcard but at least I can make a phone call.
Also, I lost data connection so I had to manually enter APN in settings, wireless and networks, mobile networks, Access point names and create a new APN, I just googled AT&T APN for the values.
Hope it works out as I'm probably going to contact AT&T as well.
I had that happen kinda with "cognadian bacon" it fried my sd card and I flashed odin one click then master cleared in odin. After that I booted up and got my format option back ..... If that doesn't work you could probably hook it to computer (windows) and go under device management and format from there but don't know if will support fat32.. Just a suggestion though.... That what I did for my external sd when it wouldn't recognize it
Sent from my GT-I9000 using XDA Premium App
Hey forum, pretty much a noob (not even 10 posts) I would like to get off my stock AT&T Gingerbread rom (KK4 2.3.5) and I keep looking through the posts for a lil explanation, can't find any. So I'm hesitant to flash roms without properly knowing what is actually going on within. Essentially I would just like to test the water first by rooting so I could get rid of the AT&T crap, and possibly progress to a full-on custom rom. If there are any devs, or passers-by that could assist, I would be more than grateful.
I suppose comparing it to regular PC terms would help best, as i feel I am somewhat savvy with PC's.
Root can be acquired through the [APP]SuperOneClick, or gained through [MOD] FuguRoot: root _any_ stock SGS ROM safely (froyo, GB) or by means of Flashing a Custom Rom (all have Root). See this 【Guide】How To flash Captivate ROMs from Stock (inc. Gingerbread ROMs) or U could flash a Developer's Kernel that has the CWM Recovery baked in and the option to install Root through said recovery (Corn Kernel is one that is based on KK4. I recommend v6.03 because it is very stable).
And be sure to read the Stickied Threads View attachment 868387 in the Captivate General, Q & A, and Delelopment Forums. That will prove to be most helpful.
Very cool. Now i suppose I'm being a pansy about this, but you seem pretty knowledgeable; if (rather when) I take the plunge to a new rom, will that wipe the whole card (which is where I'm assuming that the system is mounted), including any apps that I have gotten, and/or erase the SIM card (I hope not)?
Yes it wipes apps, although those aren't stored in /system they're in /data but a full wipe ROM will clear data. Use titanium backup to backup your apps, move contacts to Sim card or backup to your gmail.
It will not touch your Sim card.
When I attempt to root using SOC it locks up at step 7 (shell root), it freezes. Of any assistance, I look at my task panel, it runs 2 instances of adb.
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the FuguRoot method or just use Odin3 v1.83 to flash the .tar v6.03 of Corn Kernel. The .tar file goes in the PDA slot of the Odin.
Open Odin 1st, Select the PDA tab, Navigate to the .tar kernel (that u sould have downloaded) Connect ur phone to ur pc in Download mode and once Odin recognizes it, select Start. Kernel will get installed and phone will reboot. Afterwards use button combo to get into CWM Recovery (hold volume up and volume down and power button at the same time until u see the att splash screen then release the buttons). U r now in cwm recovery and can install root from there. Look under Reformatting, tweaks and more. There u will find the option to install root.
Sent by XDA Premium App
4-2ndtwin, I would like to verbally thank you, in addition to the "digital" thanks given already, I'm running the Corn Kernel right now, and from what I can see, it's a re-packaged KK4 with CwM to allow installation of root from the Bootloader menu. Now what I'm wondering, is what is the difference between the available kernel's for i897 (Captivate), more specifically those running the 2.3.5 kernel, e.g. corn kernel is re-packaged and does not have VooDoo sound, in PC terms could that be equated to a specific driver for the sound processor vice a generic driver included in the kernel?
Secondarily, just prior to appying root, I backed up everything using Nandroid, is that essentially a 1-to-1 image of what's on the rom?
Third(arily) , does Ti Backup save apps in such a state that I can move the .apk's to my pc desktop, install a custom ROM w/wipe, and re-install the apps as if they were there the entire time?
I appreciate any help.
Voodoo sounds is kinda like that, its a module compiled in the kernel that allows the tweaking of audio levels by the user with an app called voodoo control.
A nandroid is a system image yes, but it is not 1 for 1. They do not contain kernels or modems. Just the firmware and user settings and stuff. So, if you were to flash a different ROM, you would have to flash back to what the backup was made on, then restore the nandroid and it'll be like you never flashed anything.
Tibu backs up the apps and their data top a folder in your sdcard called "titanium backup" just move that whole folder back and forth and it'll work fine. Hell you can even put that folder in a different phone and restore those backups
The reason I was inquiring about Voodoo sound is (call me crazy) the volume reference has gone up a few notches since Froyo i.e. the lowest earpiece volume is twice what it was with Froyo. It's too bad there isn't a "Patchable" kernel that one could add that into.
I hate to admit this, but I always get confused at the term SD Card, as i usually think of dynamic storage that can be removed, not a static, soldered-to-mainboard storage that it is. So if I got a ROM that wiped the entire static storage, wouldn't I also lose the backups that Nandroid made?
Sdcard reffers to the /sdcard partition on the internal sdcard.
A ROM does not wipe this partition, that's where they are flAshed from, it can't wipe itself from existence and still continue the flash.
Update: Solved
Thank you for everyone's reply and help.
What worked for me:
Downloaded Mobile ODIN v3.10
Downloaded Goku v1.5-10 TAR (Kernel-Goku-V1.5-10.tar)
Flashed firmware with Mobile Odin with MD5 signature check
Can now boot into recovery
Currently on:
CM9 Version 9-20120515-Nightly-n7000
Build date Tue May 15 23:06:26
Kernel version 3.0.30-CM-q6804ca8
I cant seem to get into recovery while using any of the ICS roms. I've tried several CM9 bulds, Kindgroid, Stunner and a few others. I doesn't matter if i try to access it through the hardware keys (press and hold the Volume UP+Home+Power) or through one of the software options (reboot into recovery). After the samsung logo apears the screen will turn black. I'll have to restart the phone with the power key.
Everything else seems to be fine. I can get into download mode just fine. I have no problems downgrading to a gingerbread rom from pc odin or mobile odin. Also theirs no problem for me getting into recovery from any of the gingerbread roms I've tried.
I first noticed this while I was on ICS stunner. It was the build with the affected kernel. Everything was running smooth for me. Recovery and everything else seemed to be working fine but when i started reading posts about the brick scare i became afraid of doing anything else on that kernel.
I followed Entropy512's advise:
If you are running an affected kernel:
STOP USING IT IMMEDIATELY. FLASH A SAFE KERNEL USING ODIN/HEIMDALL.
DO NOT wipe in recovery
DO NOT flash anything else in recovery
In general, DO NOT use recovery at all
I flashed his DAFUQ releas using mobile odin while still on stunner. Everything seemed to go smooth. After flashing I checked under setting -> about phone -> kernal version and his kernel was properly displayed. I tried going into recovery but the screen would turn black after the samsung logo.
I've must of done something wrong while flashing Entropy512's kernel because ever since I flashed his kernel I havent been able to get into recovery while running an ICS rom.
TL;DR
Cant access recovery from ICS roms but recovery works fine while on gingerbread roms
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
jonpaslim said:
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
Click to expand...
Click to collapse
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
runnin4mayor said:
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
Click to expand...
Click to collapse
How about 4 wipes including format/system and also use jbroid even though your not installing a kernel but rom still use it.
Flash stock GB rom. Reroot it and then check everything is working fine? If yes then flash ICS rom.
Sent from my GT-N7000 using XDA Premium App
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
jonpaslim said:
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
Click to expand...
Click to collapse
Yes.. I've tried that before installing my current ICS rom. Actually I formatted both the internal and external SD while still on GB. I'm still wondering if the recovery stored in the same partition space in both GB and ICS. I can't understand why I can access CWM recovery on GB but not while I'm on ICS.
i too have the same problem even though i can access cwm manually cant install any zip file but if i use abyssnote kernell everything works fine the problem started when switched over to ics from gb
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
Wiping more than once is pointless... I don't know where people get silly ideas like "wipe 3 times".
When you switched to something else, did you flash it using CWM or Odin?
Try flashing a different kernel using Odin. I have seen that in rare cases on some devices, doing something like the following:
Flash one kernel from a recovery
Reboot directly to recovery using CWM's Advanced menu
At this point, the device will be stuck either always booting to recovery or never booting to recovery
Flashing a kernel with Odin/Heimdall - NOT "Mobile Odin" (I hate that name because it's completely different from Odin) or CWM often breaks these loops.
problem accessing recovery
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Thank you sir for your swift action.
deepalakshmidas said:
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Click to expand...
Click to collapse
How did you flash abyssnote kernel without being able to enter recovery?
Edit: Solved my problem. Updated 1st post
Hey there Xda,
I'm having an issue with my phone, whenever i install a Jelly Bean Rom(coming from CM9), 1) the lock screen is completely gone(it is checked on) 2) no notications come 3) no recent menu pops open.
I am running GB boot-loader (from KF1) and someone suggested to update to the latest.
So i would like to format everything on my cellphone (manual internal sdcard format using mount and PC) as well as formatting the /boot from CWR.
Before i go ahead and do that, i would like to make sure that it is still possible to go into download mode.
My plan is to format everything and /boot, then Odin one click to KK4 (i don't know the differences between KK4 and the others; the good or bad, does anyone know?)
Do i have to odin back to jf6 then kies it to kk4 ????
Then root the phone using something, i haven't found a simple method of rooting and installing CWR (if you know one, let me know)
Then from there flash a jelly bean kernel, reboot into recovery and flash a ROM.
What do yall think, good? bad? ugly?
any help would be appreciated.
Try flashing UCKK4 (download from the master stock collection thread) and then corn kernel. It has cwm recovery built-in. Then you should be able to flash a JB rom. If it doesn't work, first flash CM9 and then a JB rom.