Related
Hey guys!!!
New galaxy S2 owner. I have done some searching in these forums and the threads answered many of my questions. However, I still have some newbie questions that I found unanswered. Please excuse me if my questions have been answered before but I got tired of searching
Here is the deal:
Yesterday, I flashed a CF Root with Odin3. Then used CWM to flash a wanamlite firmware. The firmware was great but I didn't like that it still had TW. So I dl'ed another firmware to the internal SD card and flashed again using CWM. I then flashed a couple of other ROMS and I noticed that after the first wanamlite flash, the new ROMs were unstable with many error messages that some OS processes have stopped etc.
I got back home, flashed to stock with Odin3 and the phone got stuck at the second samsung logo. I followed some community steps (thanks XDA) like disabling all kies processes from TM, wiping data/cache, then boot in DL mode and flash the stock ROM using Odin3 which worked.
I then Flashed a CF Root again and used CWM to flash a Spike Pure ICS ROM v5 which was great but I get occasional error messages like 'gallery stopped' or some other error message when I try to set contact photos. It just lags, blackscreen then comes back with the 'Unfortunately, the process had stopped'.
My questions: is this because of the previously flashed firmware that this is happening or is it that those ICS ROMs have these issues commonly? Did anyone have this experience before? What do you advice before flashing to a new ROM going back to stock or going straight from the current? Doesn't Odin3 technically wipe everything back to stock?
WIPE WIPE WIPE.
Go into recovery. Data/factory reset.
Advanced, Wipe dalvic cache. Mounts and storage, format system. Its a standard procedure going from one OS to another OS. You can then either flash a firmware zip from recovery or an .tar file from Odin.
Then to be on the safe side factory reset once again.
Sent from my GT-I9100 using Tapatalk 2
Wich fw do you have?
Make a deep clean with odin an flash on the latest ics version (lp9 is a good one)..then flash (if you want) a custom rom..
My experience with custom roms: one of the best rom samsung based (ics 4.0.3) is the foxhound greyfox v2..if you want a pure ics rom flash the omega aokp rom (ics 4.0.4)..
Try then to change kernel..siyah is the best for both roms..
P.s. sorry for my bad english
Sent from my GT-I9100 using Tapatalk 2
After LP7 should be staple enough for daily use .However you are using custom roms and you should read carefully each roms thread before flashing .
You are probably suffering from flashing multiple roms and leaving bits behind as well = clean wipe .
jje.
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
I currently have Spike Pure ICS v 5.
What do you mean by Odin3 'deep clean'?
OJ77 said:
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
Click to expand...
Click to collapse
Read my last post..
Sent from my GT-I9100 using Tapatalk 2
so:
1. Recovery mode > format user data > wipe cache > clear dalvik > format system (from moutns and storage)
2. Download mode > flash stock ROM using odin 3
Did I get it right? Was there something i didn't wipe?
Before you flash a new rom, make sure you answer the requirements.Some ICS roms need to be flashed in specific way.
The way of doing a full wipe is you go in Clockwork mode, wipe data/factory reset, you wipe cache partition, then go to advanced wipe Dalvik and Battery stats, then go in mounts and storage ( i think ) and you wipe the cache from there, but nothing else in mounts and storage.If you wipe anything else there's a high percent of bricking your phone.If this doesnt help you, I doubt that anyone could give you any clearer instructions.
Good luck.
DONT FORMAT SYSTEM.
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Followed by root and custom rom if you so wish .
jje
OK im confused now... do I format system directory in mounts and storage or no?
OJ77 said:
OK im confused now... do I format system directory in mounts and storage or no?
Click to expand...
Click to collapse
i always do personally.
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card.. I get errors and 'installation aborted' if i try to do it from CWM... does that mean formatting those 3 means Odin3 is the only way? Cus I'm not home and I don't have odin3 on me.... LOL!
OJ77 said:
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card..
Did you format sd card and totally wipe the lot = nothing on the phone .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
At this point you have no OS on the phone nor kernel rooted nor CWM .
Hence
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
skimminstones said:
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
Click to expand...
Click to collapse
Agree must try better .
Habit from replying to emails i guess .
jje
Thanks...
I did a 'full wipe' by doing t his:
1. Boot into CWM: wipe data, wipe cache, wipe dalvik, wipe battery stats, wipe system/data/cache from mounts.
2. Reboot into DL mode, flash stock ROM using Odin3.
3. Repeat step 1
4. flashed spike ICS v 7.3 using CWM. Stable so far.
Thank you!
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
budi.hermawan said:
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
Click to expand...
Click to collapse
I agree! I don't like ICS because is still unstable! My battery lasts very short with ICS and the phone overheats.
Moreover I hate the browser! I mean, The Galax S2 with GB still has the smoother browser of all the smartphones out there, and Samsung with ICS update messed it up! Now is laggy with micro stutters! Don't understand why!
OJ77 said:
The firmware was great but I didn't like that it still had TW.
Click to expand...
Click to collapse
You didn't need to go through all that trouble just because you didn't want TW (which I also hate, btw).
You could simply have installed another launcher (such as Go Launcher EX, ADW, etc) from Play Store and, since you were already rooted, uninstalled TW using Titanium Backup afterwards. It has to be in that sequence (install new then uninstall old).
this way you can have whatever ROM + kernel combination you like, and still use whatever launcher you prefer.
So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
LSGio said:
So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
Click to expand...
Click to collapse
hey ma8, try wiping data/factory reset after installing CM7 not before, then reboot phone and see
przemcio510 said:
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
Click to expand...
Click to collapse
i tried cm9 and 10 but i just mis the old day you know!
cause i haad sgs1 and i flashed any rom with no problam but i dont wanna go back to my sgs1 i just want to have cm7 on my sgs2.
Sun90 said:
hey ma8, try wiping data/factory reset after installing CM7 not before, then reboot phone and see
Click to expand...
Click to collapse
i tried to wipe after and it didn't work but i appriciate the advice
przemcio510 said:
If you would have corrupted nand rw, you couldn't flash stock firmware with success.
Why don't you try CM9/10?
Click to expand...
Click to collapse
can the problem be envolved with that fact that im flashing the rom from the internal sd card?
cause i saw some videos that people were installing cm 7 onto thier devices from the external sd and it worked for them.
LSGio said:
So I bought my new galaxy s2 (i9100 int'l version) and i flashed a stock rom that matches my carrier and country (israel) and then i rooted it
by using CF-Root kernel, now i have it for over a month and i flashed many roms with success and then when i tried to flash cm 7 from stock i got into an endless bootloop.
now if you need to know how i flashed it so here you go:
flash stock rom (2.3.5) with ODIN
flash CF-Root kernel that matches my rom (KJ1)
move the official cm 7 (cm-7.2.0-galaxys2.zip) install file onto my internal memory
reboot into cwm recovery with 3 button combo
wipe data/factory reset
wipe cache partition
wipe delvik cache
install zip from internal SD TWICE just to be sure
and then when i reboot with the "reboot device" option i get stuck on the galaxy sii screen
note: after i flashed the zip twice i also tried to reboot straight into cwm from the advanced tab and it still got stuck in the bootloop.
also when im in the bootloop i cant get into cwm with 3 button combo but i can get into download mode and i have been reading that when a thing like this happens it means its a NAND rw corruption
so does it mean i can never acomplish successfull installation of cm 7 on my device?
Click to expand...
Click to collapse
Are you sure you have I9100 or do you have I9100G? Try flashing CM9 or CM10 and report if you face similar issues.
atulalvenkar said:
Are you sure you have I9100 or do you have I9100G? Try flashing CM9 or CM10 and report if you face similar issues.
Click to expand...
Click to collapse
i flashed cm9 and 10 with no problem and i know for sure i have i9100 cause all the roms i flash are for i9100 and i flash them successfully.
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
SynGates said:
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
Click to expand...
Click to collapse
Follow this:
-boot to CWM recovery
-wipe data /factory reset
-wipe dalvik cache (under advanced)
-format /system (under mount and storage)
-flash ROM
-flash Gapps (for jelly bean)
-fix permissions
-reboot phone
Done
Swyped from my Samsung Galaxy SII
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
Nope
Swyped from my Samsung Galaxy SII
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
which kernel u were into while flashing the JB rom?
Use siyah or dorimanx kernel it works fine for me must be your kernel
Sun90 said:
which kernel u were into while flashing the JB rom?
Click to expand...
Click to collapse
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
SynGates said:
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
Click to expand...
Click to collapse
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Sun90 said:
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Click to expand...
Click to collapse
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
SynGates said:
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
Click to expand...
Click to collapse
Use a newer version of siyah or dorimanx, they should work fine
Sent from my GT-I9100 using xda app-developers app
I have tried three versions of syiah, including 4.1.4 but I will try dorimanx and report with the results.
edit: dorimax kernel is the same.
One thing I noticed tough is whenever I wipe dalvik cache the system reports "unknown volume for /ext-sd blablabla" - maybe this is connected to my problem?
I am at a complete stop...
No JB kernels seem to work whatsoever. Is there any wit to flash the bootloader? Or is that even possible?
I really would like to get JB working on my device.
There must be something about the previous state of my phone, some files or folders that are in the way or are missing or somewhat. Is there any way to completely reset the phone? Not just factory resetting it since that is not working.
edit: Progress! These are my steps:
- Downloaded fresh stock Samsung ROM and another version of CF-root.
- Flashed stock ROM and then CF-root kernel.
- Booted into recovery and did the whole wipe.
- Flashed .zip twice (don't know if that did the trick or what)
- Wipe dalvik cache and fix permissions.
After that the phone booted normally and I'm now running ResurrectionRemix with Android 4.1.1, hoping it wil be awesome as ****.
how to factory reset stock 4.0.4 and keep root?
hi am quite new to the s2, after rooting with Siyah 4.1.5 i am getting constant crashes and freezes, i wanted a quick step to stop guide on how to factory reset the firmware.
i don't mind loosing all apps and data as i can use titanium also all my main data is on my external sd card. thanks
You are asking to do to different things a factory reset will wipe user data only nothing else , you will still be rooted.
go into recovery and clean cache, daavik cache and then do a factory reset. It will store your phone to default settings for what ever stock rom you are on.
If you format the internal storage, you will lose the rom, root and all data on the internal card. You will then have use cwm or odin to flash a new rom and apps.
Don factory reset jus download philz kernel an flash it via odin or cwm
sent from I9100 XXLSJ Official JB
hussy22 said:
Don factory reset jus download philz kernel an flash it via odin or cwm
sent from I9100 XXLSJ Official JB
Click to expand...
Click to collapse
Don't know what you make of his question, but this is definitly not the answer.
Sent from the Matrix
Cosmic Blue said:
You are asking to do to different things a factory reset will wipe user data only nothing else , you will still be rooted.
go into recovery and clean cache, daavik cache and then do a factory reset. It will store your phone to default settings for what ever stock rom you are on.
If you format the internal storage, you will lose the rom, root and all data on the internal card. You will then have use cwm or odin to flash a new rom and apps.
Click to expand...
Click to collapse
if i do a factory reset through recovery, will the brick bug effect me in any way, also is it advisable to update my Siyah 4.1.5 to the latest one. thanks
kuljit55 said:
if i do a factory reset through recovery, will the brick bug effect me in any way, also is it advisable to update my Siyah 4.1.5 to the latest one. thanks
Click to expand...
Click to collapse
Someone posted this very succinct summary of the brickbug yesterday in the I9100 General section.
I installed 4.1.2 on my s2 gt i9100 no brand but will not start, crashes on startup with the samsung logo. Why?
I now have the phone down, I think I have to replace the 4.0.3
this is the tread http://forum.xda-developers.com/showthread.php?t=1544487
Did you use CWM recovery wipe? Maybe it's emmc brick bug?
It can't be a brick as it is turning on
And it's flashable with Odin, not CWM.
Sent from the Matrix
mar10o said:
Did you use CWM recovery wipe? Maybe it's emmc brick bug?
Click to expand...
Click to collapse
CWM doesn't have the emmc bug, Its a bug in the stock 4.0.4 recovery.
Conte94 said:
I installed 4.1.2 on my s2 gt i9100 no brand but will not start, crashes on startup with the samsung logo. Why?
I now have the phone down, I think I have to replace the 4.0.3
this is the tread http://forum.xda-developers.com/showthread.php?t=1544487
Click to expand...
Click to collapse
This is most likely because you have just flashed 4.1.2 without wiping old rom data. Its advised on just about every single rom thread to wipe before flash. If you dont want to lose apps/appdata then use Titanium Backup Pro.
TheATHEiST said:
CWM doesn't have the emmc bug, Its a bug in the stock 4.0.4 recovery.
This is most likely because you have just flashed 4.1.2 without wiping old rom data. Its advised on just about every single rom thread to wipe before flash. If you dont want to lose apps/appdata then use Titanium Backup Pro.
Click to expand...
Click to collapse
you have made a backup of the app + system data with titanium. also save photos, music and video
I did not think to flash a firmware I had to clean everything, I thought it was enough to download the file, put the phone in download mode with odin and startare
now how do I proceed? I wipe the 3 as I did for the rom?
Conte94 said:
you have made a backup of the app + system data with titanium. also save photos, music and video
I did not think to flash a firmware I had to clean everything, I thought it was enough to download the file, put the phone in download mode with odin and startare
now how do I proceed? I wipe the 3 as I did for the rom?
Click to expand...
Click to collapse
1) Put ur phone into dwnld mode and flash a stock ICS 4.0.3 firmware using ODIN to make ur phone up and running.
2) after that root ur phone by flashing the tar file of Siyah kernel v5.0.1 vide ODIN.
3) then reboot to siyah kernel recovery and wipe Data/factory reset and the wipe cache partition.
4)Dwnld the stock JB firmware from that link u provided and flash the same using ODIN
that way u will have a clean install of stock JB on ur phone
but if by dalal recovery without installing the 4.0.3 and do the wipe, and then install the 4.1.2 is not good?
Conte94 said:
but if by dalal recovery without installing the 4.0.3 and do the wipe, and then install the 4.1.2 is not good?
Click to expand...
Click to collapse
u can give it a try that way and post ur Success/Failure feed back over here
IMO the best bet is what i stated in my earlier post
Sun90 said:
u can give it a try that way and post ur Success/Failure feed back over here
IMO the best bet is what i stated in my earlier post
Click to expand...
Click to collapse
He has no need to do what you said and install rom twice. All he needs to do is flash kernel like Siyah v6 beta4, reboot into download mode, wipe data and then flash his stock rom via download. No need to install 4.0.3 first its just waste of time.
and where can I download the file of Siyah kernel v5.0.1?you say the kernel?
I installed the 4.1.2 doing the wipe, and everything went ok.
so every time I install a new firmware should I do the wipe right?
and then I do not have siyah kernel but everything went well from recovery
Conte94 said:
I installed the 4.1.2 doing the wipe, and everything went ok.
so every time I install a new firmware should I do the wipe right?
and then I do not have siyah kernel but everything went well from recovery
Click to expand...
Click to collapse
Good:good:
Yes, its always better to do the wipes first for a clean install, as u can see in ur case itself
Enjoy the rom for now and no need to worry about siyah kernel for now
ok
however, once I had siyah then I removed
thank you very much for your help, I did not know I had to do so for the firmware
thank you very much