I tried searching in the Captivate forums and I couldn't find anything about it. I already installed the Unleash The Beast ROM, and then a little bit afterwards, I put in the ROM with the circle battery in it, and everything from the Unleash the Beast ROM seemed to still be there afterwards.
My question now is this: would putting in another ROM undo anything else that was put into the phone?
everything you have done is not a ROM, they are a mods.
A ROM will completely reinstall the operating system of your phone.
the update.zip's you have been using arent roms, they just patch or add files into the system, so as long as your not using 2 mods/updates that change the same files then they will not replace eachother
Curious as well.
If my phone is rooted, and I want to change the rom, could I do it without restoring everything to the way i bought it? And do you recommend just going back to everything he way it was when I bought it and just doing one of these mods and patches on the forums?
Related
im hoping to generate a consensus from this post. i see some ppl like to sbf before each new rom install and other not. is it necessary and why>?
From my understanding of the ROM development for the android platforms that still have to have proprietary frameworks, ie: Motoblur (droid2/X) and Touch Wiz (Galaxy S) you are not wiping and installing a whole new operating system like you do when you flash a HTC phone. So youre really just adding onto what you already have as a base. So it would be like taking a car and taking out stock parts and swapping for performance parts like exhaust, intake, etc.
This is just my understanding, it could be wrong. But my opinion and preference is when you change development teams like team defuse to say Jrummy16 roms, I like to SBF to stock to have a clean base. Sure its a PITA, but it keeps things from going horribly wrong.
gammaxgoblin said:
im hoping to generate a consensus from this post. i see some ppl like to sbf before each new rom install and other not. is it necessary and why>?
Click to expand...
Click to collapse
SBFing before installing a new ROM is something I would recommend. I have had slight problems such as the clock keeping the color from the ROM before it, and just minor stuff like that. I really don't think its needed but I would say if you plan on keeping the new ROM for a long amount of time it would be better to SBF first just so you know that everything is going to be okay.
I would also advice to sbf back to stock, reroot and then insstall the new custom rom you want to run.
the only reason is since the roms are all diffrent then one another and have to generall base (besides stock) then flashing (sbf) to stock is a good idea to have the rom running at the fastest most stable potential.
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
I looked and found nothing I even tryed copying other roms but nothing I added everything i thought should make the rom rooted but nothing. I have my own rom and want to make it pre rooted. its the only thing i seem to not get i have everything else going but this.
What ROM do you have? If it's from a stock base, then you could syslink the SU files or run gingerbreak and all of the files will be linked already.
If you have a CM7 based ROM, it's rooted from the source. Other GB ROMs would need someone else to chime in, but I would think gingerbread would work.
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