Related
Ok so I now own a Samsung Galaxy S 4G, and like everyone else the internal memory is nearly full out of the box.
The solution.......... root your phone and install a custom ROM right!
Phone is rooted and ready, but now I have some questions in regards to installing the custom ROM.
1. How do I back everything up in case I need to roll my phone back to the original settings?
2. I have seen things that say ODIN does not work well for flashing at this point and time and may brick your phone, please confirm if this true.
3. I'm currently thinking about Darky's custom ROM, good distro or not? If its not please recommend a better one.
4. To anybody that has installed a custom ROM how much application space did you gain by this change?
Thanks in advance for the help
Backup the original ROM with ROM Manager.
I do not have a Galaxy 4G so i don't know how much memory it has, but i'm using MIUI on my Desire HD and i got some extra space after flashing it.
The original Sense ROM is about 260 MB, while MIUI is 65MB. So if you want extra space i recommend a CM7 based ROM. (MIUI is based on CM7 btw)
Sent from my HTC Desire HD using XDA Premium App
galaxy s 4g rooted
in regards to freeing more memory, when i ran out of memory i decided to root my phone and then got instructions on replacing fota files in the /data/data directory. Immediately I got about 300 meg extra memory on the phone, cause 2 fota files were 125 meg each. After that I was trying to install OCLF 2.2 but it would not work, period! And I can not find the older OCLF anywhere. Than again, I heard that older OCLF comes with root software and I am already rooted. So i froze all the bloatware using bloat freeze app, and unroot, factory reset and root it again. Now, for some reason I have 416 med available out of 514 total. Probably erased all bloatware that was frozen - really don't care about it tho. So if your phone is rooted, here is your answer! I read on XDA that the custom ROMs are on a way to the public but i don't think they are there yet. I am a noob but I would not flash my galaxy s 4g with vibrant ROM. To me it looks like sure brick, someone correct me if I am wrong
Hi Devs, just to start off I am not a dev and there am not able to solve the question below.
I am a proud owner of the Galaxy S2 4G i9210t the Australia Telstra version, we are able to flash all gingerbread roms from the i727 and they run perfect except for one little problem when we flash the gingerbread rom from i727 we lose our capacative button it completely stops to function so to get it back to work we have to restore the original boot.img from our nandroid backup and then the rom starts to function perfectly.
So I decided to try your ics roms from the i727, so obviously it has the same problem everything works except of the capacative buttons so the problem is we have to restore the boot.img from the nandroid backup, but the boot.img is from a gingerbread roms so the rom does not boot.
So the ics roms work perfectly except for that one problem and I believe the problem is somewhere in the boot.img. I hope someone can help.
you're SOL (sh1t outta luck). U need an ICS kernel for your device, and until u get one (from an ICS release) or source drops for our device and someone ports it, its not gonna happen.
so basically, no. Sorry bud.
icenight89 said:
you're SOL (sh1t outta luck). U need an ICS kernel for your device, and until u get one (from an ICS release) or source drops for our device and someone ports it, its not gonna happen.
so basically, no. Sorry bud.
Click to expand...
Click to collapse
thanks buddy, what about for the gingerbread kernel can anything be done with it so that we don't have to restore original boot.img every time we flash a gingerbread rom to get the capacitive buttons working?
madshabz said:
problem everything works except of the capacative buttons so the problem is we have to restore the boot.img from the nandroid backup
Click to expand...
Click to collapse
Hi,
I just stumbled across this thread as I was looking for ROMs for an I9210 that I need to repair, just something that sprung to mind and that was a similar situation between the Samsung Galaxy S, Samsung Vibrant and Samsung Captivate. Although the Vibrant and Captivate were running Cortex-A8 core and the Galaxy S was running S5PC110 and yes the boot.img files were completely different, I found that the ROMs were essentially the same except for the same issue you were having. As a work around I figured out that the key mappings could be switched around to allow the back button to function correctly
I know that this is dead thread and I am necro-bumping like a zombie, however if you run into this issue in the future it might be something to consider? Especially considering ROMs for I9210 stop at ICS now and I would assume that the i727 has gone on to Jellybean due to it's popularity in the US?
In the Vibrant the keys were found in /system/usr/keylayout/
The other things that were different between them were the modules them selves, in the S1 they were located in /system/lib/modules although I am fairly certain this is a symlink not an actual location but it will give you or someone else something to consider when thinking of porting any roms over in the future.
Edit: If you want to port ROMs, you need to go back to the closest possible denominator and work backwards. What I mean is that you download two standard firmware packages for I727 and I9210 both in Gingerbread 2.3.6 and then diff the both packages against each other. From the files that differ, if you cannot simply trade them in/out because of significant changes in Android versions then you can resort to decompiling the files that differ from each device and then proceed to diff the decompiled code. It's not impossible it's just very difficult and time consuming. I have managed to port ROMs from I9100(Galaxy S2) to I9000(Galaxy S), I9020(Nexus S) to I9000(Galaxy S), I897(Captivate) to I9000(Galaxy S) and T959(Vibrant) to I9000(Galaxy S).
James
Hi,
i have seen many people got problem after installing a new firmware or Rom.
Even though the next update might fix the error, but it feels annoying right?
So do you prefer to stay on stock rom or update if there is a new update?(not custom rom, official one.)
I prefer leaving stock. But i have an SE phone, and they don't do a good job imho of updating/supporting their products. It's a safe answer, but go with what works for you. Our devs are really good, though.
Sent from my rooted tomato using xda app
cascabel said:
I prefer leaving stock. But i have an SE phone, and they don't do a good job imho of updating/supporting their products. It's a safe answer, but go with what works for you. Our devs are really good, though.
Sent from my rooted tomato using xda app
Click to expand...
Click to collapse
Thank you
But i afraid if i update and have a problem, and have to change back to previous rom it might affect my warranty, since i still have my phone's warranty i will not root and install custom rom, i afraid it might be affected even though it can still back to stock rom.
I say go ahead and update to a new firmware / rom . It usually shouldn't cause any problems if you follow the steps closely . Also you can always reinstall stock rom and then un root your phone to get your warranty back
I would like to use custom ROM for my HTC to enable Bluetooth file sharing, but it seems like very complicated process.
On my previous smartphone (Blackberry) I always used hybrids.
im abcd said:
I say go ahead and update to a new firmware / rom . It usually shouldn't cause any problems if you follow the steps closely . Also you can always reinstall stock rom and then un root your phone to get your warranty back
Click to expand...
Click to collapse
I did install a custom rom before to my previous rom and ever heard about getting warranty back by reinstall to stock rom, but i didn't have a chance to do it, so i am not really sure.
maya79 said:
I would like to use custom ROM for my HTC to enable Bluetooth file sharing, but it seems like very complicated process.
On my previous smartphone (Blackberry) I always used hybrids.
Click to expand...
Click to collapse
I had a LG before, and did try some custom rom. It was not so complicated.
But maybe other phone procedure might be a little different.
I've never left any of my Android phones alone ever. When I got my Motorola Droid (my first android OS phone) I rooted it a few hours after activation, a new ROM a few hours later while at work then put it all back to stock and got it replaced with a HTC Droid Incredible with the 30 day swap thing VZW does.
Flashing a custom ROM or staying stock is the whole reason XDA-Developers exists. Stock firmware are solid builds, but they are also very, very limited in what they allow you to do. I say allow because that is exactly what your carrier/manufacturer is doing with their firmware. With a custom ROM, you open the door to so many more possibilities, (ie tethering, mobile hotspot, Superuser access apps,...)
Now whether to stay on a stock FW or go custom, that is going to be up to you and what you want to get out of your device. My wife and I each have a phone and a tablet. All are Rooted. My Phone (Samsung Vibrant) is running a custom ROM by me, her phone (Motorola XT720) is running a custom ROM, her tablet (Nook Color) is running CyanogenMod 7.2, but my tablet (Asus Transformer) is running stock ROM but custom kernel.
Personally, I do not like Touchwiz from Samsung or Motoblur from Motorola, hate the bloat that both manufacturers put in there that I do not use. I also bought my wife a tablet that was Barnes&Noble branded android based FW, but I completley scrubbed it off and put a custom ROM on there for her. So now she has a full on tablet instead of a simple reader. See where I am going with this?
My tablet is fast, has all I need on it and since I am considered a power-user, I tinker with it but at this point I am satisfied with it as stock. Now, that is not to say that I have not altered it. I put a custom kernel on it and frozen some of the bloat that Asus provided. It came out with Honeycomb and then updated to ICS. Since I have had it on HC, it has seen 6 FW updates and every one of the ICS ROMs were terrible and left most users with a useless piece of machinery. Myself, I was able to keep it from de-evolving into that and have been happy with it ever since.
Hopefully this shows you that there are plenty of options for why to use a custom ROM but also to stick to stock firmware. It really just depends on you and what you want. Flashing is easy. Just read the OPs, search and read some more and above all, learn to make a Nandroid Backup.
Personally, I prefer to stay as close as possible to AOSP, with custom ROMs like Cyanogen. You don´t feel bounded by the locks imposed by the manufacturers or, even worse, the carriers.
In my experience, they are not as stable as stock ROMs (currently, I´m having some random reboots with cyanogen 9 in my Galaxy Note) so, if you don´t feel adventurous, stay stock.
Regards,
It's coming from China so I imagine there will be a few annoying icons but nothing major.
I want to root the phone.
Then install a CFWM & Backup Original Stock Rom
I don't plan on using anything other than the orginal stock rom however one day if I fancy a play and mess it up I can roll back.
The main thing I carer about is the root feature.
Anyone suggest any tutorials I cant find any specific for this phone just copys of roms from need rom, I need to know how to root and instal CFWM first!
Also can I chose what rom to boot when powering on, almost like running it dualm boot, one for work and one for play?
Thanks
No longer own this phone, and no longer have a copy of the rom so this is no longer being developed.
Thanks to @shifattk and @FitAmp for the overclock
Thanks to @Restl3ss, who is working on a rooted and overclocked, otherwise bone stock ROM
Thanks to @atmu5fear, who made the first flashable rom for the S730M, I based my Rom off your original release.
changes I made from the stock 4.04 image
Rooted
BusyBox
Overclocked to 1000mhz
Nova Launcher
Default Ringtone: Crank
Disabled power on and power off boot sounds
Bloat Removed
Theme Changes
Zipaligned
Replaced Samsung keyboard with the google keyboard (much better IMHO)
Stable
Working and tested. Tested on a S730M as well as a S730G
Flashing instructions:
1. Use CWM 6.0.3.1 Get it here https://docs.google.com/file/d/0B1BxFtN0QItNUExLMHBWT1loQjg/edit?usp=sharing, flash with Odin)
2. Make a backup, if things go wrong for you, you cause use the backup to restore your phone's original firmware.
3. WIPE DATA/CACHE
4. Flash
5. Wipe Dalvik.
6. Reboot
NOTE: I can not and will not be responsible for any damage this rom could potentially cause on your phone, http://en.wikipedia.org/wiki/Caveat_emptor
Download Version 1.0 here
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
FitAmp said:
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It's a nifty little phone. I personally think it's better than a Nexus S but just suffers from the typical Samsung pump and dump routine where they sold all their inventory to the carriers then stopped supporting it with any updates.
Good job! I have 3 versions of the stock ROM available for this device as well, may have been more appropriate for a base, there's stock, stock + root + Busybox, stock + root + Busybox + overclock. Find them here
http://forum.xda-developers.com/showthread.php?t=2677332
Sent from my SGH-T989D using XDA Premium 4 mobile app
r740c
Will these ROMS work with the Cricket version?
kadeleblanc said:
Will these ROMS work with the Cricket version?
Click to expand...
Click to collapse
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
CDMA
doctor_evil said:
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
Click to expand...
Click to collapse
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
kadeleblanc said:
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
Click to expand...
Click to collapse
You may be able to use the same CWM recovery on that model,
you should be able to probably use the same kernel to overclock your model too, and you can probably use the kitchen app we used to cook these different version roms for the 730M and 730G models to do your own custom rom, just remember before you start working, to do a full nandroid backup of the current rom so you can restore it back to the original (mostly stock except for the cwm recovery) firmware if you need to later on.
By any chance this will unlock it or do you know a way for me to get the unlock using hex?
Thanks to doctor evil for this ROM I was able to flash my phone but not before removing more apps (bell apps and oothers ).
I was wondering if anyone was successful in unlocking the tethering? Tried a few things out there and the best I could get was Bluetooth tethering with foxfi.
And it works!
@doctor_evil: I flashed your set after having played with @atmu5fear's version (http://forum.xda-developers.com/showthread.php?t=2673097). I like them both very much and am still looking which one I will keep. I have not wiped data/cache (i.e. Factory Reset) before overlaying your version over @atmu5fear's one, and it did not hurt. I noticed the following:
Flashing your ROM did not again trip the ROM counter after applying the triangleaway script after @atmu5fear's ROM load (it did go off then).
When having a SIM in the S730M and after putting in the phone unlock password, the keyboard stays on top (this does not happen when no SIM is present)
My Battery-drain problem when having the phone powered fully off with a SIM installed is still there. Probably need to await a cooked custom ROM for this to be solved
The triangleaway script for the S730M can be found at http://forum.xda-developers.com/showthread.php?t=2420184
The Battery-Drain S730M issue has been noticed by quite a few people (TELUS and BELL, both in Canada), and is unexplainable. When the phone is on (with SIM installed), power usage is normal, but when you power off the phone (with SIM still installed) the power-drain goes up dramatically (draining the battery completely within a few hours). When the SIM is removed, or when the battery is removed there is no abnormal drain perceived. The other thing is, that, when the device, with SIM and battery installed, is powered off, both the battery area and the SIM area get warm (not really hot), indicating SIM activity WHILE THE DEVICE IS OFF... Very odd. I am hoping that a new KK custom ROM would fix this issue as both 'custom' 4.0.4 ROMS I have tried now show the same issue, indicating it is either a hardware or a 4.0.4 implementation issue...
I am sorry I never responded back to you. I had my Cygwin install with my kitchen build environment running on a SSD hard drive with my OS and the drive crapped out on me and had to be sent in for a RMA. I had a easus todo workstation backup of my drive I was able to restore, but the backup wasn't current so I lost my kitchen environment. I never tried to set it up again as I had hoped that someone would have ported Cyanogenmod to the phone.
I may give it a try again as I just setup a vmware ESX host server here at home and I can allocate multiple cores and plenty of ram to the linux Virtual Machine I created on it once I figure out the best build environment and how to actually go about building CM successfully. Anyone know of a porting cyanogenmod for dummies guide I can use? LOL