Hello all
I have been playing with a variety of 4.1.2 ROMS via CWM
at times in between I have wanted to flash a ROM via Odin (the carrier brand that originally came with the phone) to sort of get back to a start point
however even though odin seems to indicate it installed the ROM after reboot I get stuck on the samsung splash screen
if I then go for another CWM ROM all seems to work.
what might I be doing incorrectly?
After... Or before... Flashing with Odin, wipe data and cache in recovery. Be sure if youre doing it on stock recovery to avoid superbrick bug kernels.
Or... Flash with 512 pit. Will do the trick. Cheers!
Sent from my GT-I9100 using Tapatalk 2
superbrick bug?
This isn't development
This thread is in the wrong section, please move it
Related
First, I want to say sorry because this question has been asked many times. Though I have done searches on the Internet and came across some solutions, I still don't understand how to solve it.
Anyway, here's the story: my brother just bought a galaxy S2 (I9100) and decided to root it via ODIN. However, he mistakenly flashed his phone with a firmware for I9100G. He then tried to flash again with a custom kernel for I9100, but the phone always freezes at the startup screen (with that yellow triangle). So that's 2 custom kernel at the same time.Then I tried to flash the phone with a stock kernel. This time, there is no yellow triangle at the startup screen, but the phone still freezes there. I can still access to the Recovery and Download mode, but have no idea what to do next. Please help me. Thank you
If you can access Recovery, try to wipe data/cache and Dalvik cache. And try flashing a custom kernel after that with the compatible zip file through recovery. I recommend Siyah.
But don't do this with 4.0.4 stock recovery, cause then you will be bricked.
Cheers.
WardenBerret said:
If you can access Recovery, try to wipe data/cache and Dalvik cache. And try flashing a custom kernel after that with the compatible zip file through recovery. I recommend Siyah.
But don't do this with 4.0.4 stock recovery, cause then you will be bricked.
Cheers.
Click to expand...
Click to collapse
Wait, if I recall correctly, then the phone's version is 4.0.4 before the rooting attempt. So what you mean is that I shouldn't wipe cache with the version 4.0.4 or I shouldn't flash kernel with that version ? Because if it is the latter problem, I can go around and flash through download mode. Anyway, thanks for the advice
boiboi12345 said:
Wait, if I recall correctly, then the phone's version is 4.0.4 before the rooting attempt. So what you mean is that I shouldn't wipe cache with the version 4.0.4 or I shouldn't flash kernel with that version ? Because if it is the latter problem, I can go around and flash through download mode. Anyway, thanks for the advice
Click to expand...
Click to collapse
You've managed to flash the right official firmware with Odin? Just make sure you don't perform any wipe with stock kernel (in stock recovery) from 4.0.4, all other kernels will be safe.
Sent from the Matrix
Donnie Sins said:
You've managed to flash the right official firmware with Odin? Just make sure you don't perform any wipe with stock kernel (in stock recovery) from 4.0.4, all other kernels will be safe.
Sent from the Matrix
Click to expand...
Click to collapse
Yes, I managed to flash the official kernel with ODIN after flashing the 2 custom kernels mentioned.
So, now if I want to wipe, I'll have to re-flash my S2 with a custom kernel right ? assume that works and everything is wiped, will the S2 be able to work again ? Or do I have to do something else ?
Did ur bro make a backup before flashing ?
I had a stuck on logo prob and the only way I could fix it was by loading my backup. wipes or flashing other kernels would not fix for me.
I have read others with similar or boot loop issues caused by kernel and fixed the same way.
if u don't have a backup I don't know, maybe research soft brick fixes. good luck.
peace
Just flash official firmware through Odin. No need to restore back ups or flashing other kernels.
Afterwards root it again and flash a custom rom.
Sent from the Matrix
[Solved]
I am unable to flash any roms through cwm, and can only do it through odin. Flashing through cwm results in the phone not loading past the boot logo.
I formatted sd card in cwm, thinking it would only restore to factory settings, not knowing it would completely wipe everything.
From then i was unable to even see the boot logo or recovery mode, but luckily download mode still worked.
So i flashed the stock rom through odin, but it still plays up. Now the battery doesn't last more than 1 day, and constantly freezes.
Now whenever i install anything in cwm, as soon as i reboot, it goes to the bootscreen and freezes. I have tried at least 5 different roms and the same story each time, So each time i have to reflash stock rom with odin.
So any ideas to why this is? any help is appreciated. I have tried ultimate kernel wipe cleaner , or whatever it is called as well.
[Solved]
I just reflashed stock ICS in odin, and ticked the 're-partition' box. the repartition file is called " u1_02_20110310_emmc_EXT4.pit ". Now it works good as new and I'm currently running PACman rom on 4.3. gg guys.
Just to check, but you have factory reset after flashing the new ROM from CWM right?
Try these steps :
1. Flash ROMNuke script by hawkerpaul. (it's a ROM nuke, not just a kernel nuke)
2. Flash ROM in CWM.
3. Boot.
I know it sounds simple, but that's got me out of a few odd bootloop /failed flash situations. Give it a go.
Then, if that doesn't work, re-download the ROM which you're attempting to flash & try again.
One more thing, what kernel are you trying to flash the ROM from in CWM? Try a different one, say siyah. I've sometimes seen where a particular kernel won't flash but another will for no apparent reason.
Sent from a galaxy far, far away
Hopper8 said:
Just to check, but you have factory reset after flashing the new ROM from CWM right?
Try these steps :
1. Flash ROMNuke script by hawkerpaul. (it's a ROM nuke, not just a kernel nuke)
2. Flash ROM in CWM.
3. Boot.
I know it sounds simple, but that's got me out of a few odd bootloop /failed flash situations. Give it a go.
Then, if that doesn't work, re-download the ROM which you're attempting to flash & try again.
One more thing, what kernel are you trying to flash the ROM from in CWM? Try a different one, say siyah. I've sometimes seen where a particular kernel won't flash but another will for no apparent reason.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
it was stock ics cwm i think?, also another thing when I install a new rom, when it shows the progress bar, it goes up to 3 quarters then it skips the rest and says update completed (I just tried Romnuke and same story). I have also tried siyah kernel and it just freezes at the siyah kernel instead. Im currently stuck on stock ICS 4.0.2
Not sure what you mean by 'stock ICS CWM'?
And just to make sure, you definitely have an i9100 right? Not a variant, i9100g etc? Just asking as 4.0.2 was never released for i9100, only 4.0.3 and 4.0.4 (stay away from that one)
So now, re-download the ROM which you're attempting to flash, and try again after the ROMNuke script. Does the script run successfully? Or does it have errors /messages which indicate it didn't run successfully?
Sent from a galaxy far, far away
Hopper8 said:
Not sure what you mean by 'stock ICS CWM'?
And just to make sure, you definitely have an i9100 right? Not a variant, i9100g etc? Just asking as 4.0.2 was never released for i9100, only 4.0.3 and 4.0.4 (stay away from that one)
So now, re-download the ROM which you're attempting to flash, and try again after the ROMNuke script. Does the script run successfully? Or does it have errors /messages which indicate it didn't run successfully?
Sent from a galaxy far, far away
Click to expand...
Click to collapse
my bad it is 4.0.3, it is definitely only gt-i9100, and in recover mode it says CWM-based Recover v5.0.2.7
kobe24lebron23jordan said:
my bad it is 4.0.3, it is definitely only gt-i9100, and in recover mode it says CWM-based Recover v5.0.2.7
Click to expand...
Click to collapse
All good. And also good that you have an i9100.
Ok, so have you tried the things I said?
1. Try flashing from a different kernel (your choice, try one other than Siyah)
2. Re-download the ROM & reflash with Nuke script then ROM.
[Solved]
5 months later I found the answer when messing with odin. What you do is tick the 're-partition' box, and then in the 'pit' sections you need the partition file i guess, for the i9100 its called u1_02_20110310_emmc_EXT4.pit . hope this helps anyone else who may have this problem
Hi,
I have a Galaxy S3 I9300.
I tried to flash a stock rom a couple of days ago and something went wrong.
Now my touch screen doesn't respond, it's the weirdest thing, I guess I flashed a corrupted file with Odin.
Anyway, I couldn't enter recovery mode (the phone kept roobting when I tried), I managed to flash the CWM recovery and now I can enter recovery mode.
I could flash a rom via external SD card, but still no luck, now I have paranoid, but still the only buttons that work are the home and shutdown (physical buttons) the touch screen just doesn't respond...
What can I do ???
edocoh said:
Hi,
I have a Galaxy S3 I9300.
I tried to flash a stock rom a couple of days ago and something went wrong.
Now my touch screen doesn't respond, it's the weirdest thing, I guess I flashed a corrupted file with Odin.
Anyway, I couldn't enter recovery mode (the phone kept roobting when I tried), I managed to flash the CWM recovery and now I can enter recovery mode.
I could flash a rom via external SD card, but still no luck, now I have paranoid, but still the only buttons that work are the home and shutdown (physical buttons) the touch screen just doesn't respond...
What can I do ???
Click to expand...
Click to collapse
which stock rom did you flash a couple of days ago?
If you can get back to recovery now then try download mode too and reflash your countrys/carriers original firmware to what it was before.Then re-root and flash philz recovery and then a custom ROM from the internalSD.
sriram231092 said:
which stock rom did you flash a couple of days ago?
Click to expand...
Click to collapse
I've tried so many ROM's to repair that I'm not sure regarding which one is the corrupted one...
I'm almost sure it was downloaded from the link in http://forum.xda-developers.com/showthread.php?t=2187081
Before flashing a new ROM boot to recovery and manually wipe cache partition and dalvik and format data/system/cache from mounts and storage.After that the phone wont reboot so pull the battery and put it back in and boot to download mode then flash via Odin.Also try Odin v1.85 too.Ive used both v1.85 and v3.07 and sometimes had issues with the newer one.
try this with a different firmware than the first one you used.
the WEIRDEST thing ever
cooza said:
Before flashing a new ROM boot to recovery and manually wipe cache partition and dalvik and format data/system/cache from mounts and storage.After that the phone wont reboot so pull the battery and put it back in and boot to download mode then flash via Odin.Also try Odin v1.85 too.Ive used both v1.85 and v3.07 and sometimes had issues with the newer one.
try this with a different firmware than the first one you used.
Click to expand...
Click to collapse
So, I have done what you suggested.
And now, the left bottom 'menu' button work!
it's not a physical button, and It didn't work before.
I know it sound crazy, but this is the situation.
I've tried doing it a few times more, and nada, still the same..
I've tried more roms, but nothing seems to help...
Any ideas anyone ?
Sounds like damage to the hardware from flashing a rom not for this phone .
Good point from JJEgan mate.What was the ROM you flashed to your phone and is your phone an i9300 or i9305?.Maybe another varient..?.Makes a big difference.
cooza said:
Good point from JJEgan mate.What was the ROM you flashed to your phone and is your phone an i9300 or i9305?.Maybe another varient..?.Makes a big difference.
Click to expand...
Click to collapse
I have the international I9300.
All the stock rom's that I tried contained '9300' in their name...
the custom roms that I tried were Paranoid and Cyanogenmod.. I was pretty careful regarding the exact model type.
I think maybe at one time I accidentally plugged out the phone while odin was in the reset stage and didn't get to PASS yet.
Can this explain the symptoms ?
If indeed there is a hardware problem, is it fixable or should I begin grieving ?
Flash stock rom via Odin .
Post at what point it fails .
If you unplug your phone in Odin mode you could kill it.Atleast it was at the end.You said you have formatted and reflashed again and I guess that about all you can do but do it a couple more times with your countrys firmware just to make sure.Keep an eye on the flash bar on Odin an watch to see if anything doesnt flash or skips.
I hope you didn't flash a note 2 rom (i and some other users flashed the kernel of note2 and the digitizer was dead), you can read in one of my posts and I'm sure there are other users. Not so many but still.
I tried to put custom recovery for i9100 via odin. http://forum.xda-developers.com/showthread.php?t=1118693
I wanted to flash unofficial CM11 to replace official 4.1.2
Flashed .tar.md5 now phone won't boot, but it can enter recovery and download mode. (Options ticked were Auto-reboot and F. Reset Time)
Then I downloaded stock firmware 4.1.2 and tried to flash. It stucks at NAND write start.
Then I tried to flash another kernel http://forum.xda-developers.com/showthread.php?t=1877270
Same thing. In recovery I did wipe data/cache, same thing, display remains blank on power on.
Please help. Thanks in advance.
You need to get a successful Odin flash of stock to give you a 'clean slate' to start again (with flashing a custom rom/whatever) from. Find Hopper8's 'Odin troubleshooting' thread & try the stuff in it, you should be able to get it done with the suggestions in the thread.
Thanks, it was phone from friend and it scared me to death
I flashed earlier Gio and realized I can flash kernel in zip, so that phone is now running CM11, but this info might come in handy when he wants to get back to stock. Also, I'm getting this phone next week, so it's good to know workaround if I run into a problem.
Yep knowing how to recover is a must before you start flashing stuff. If you're getting an S2, download at least one stock rom for your carrier/country from Samfirmware & keep it on your PC w/Odin in case you ever need it.
^+1.......and also make sure you have a working (official Samsung) USB lead......(or even more than one)
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
And make sure you have backed up your efs folder too. Something like ktool is good for this. Get it from playstore. And a good working nandroid is a must.
I was just preparing to update to new ROM when this happened
I just installed the newest CWM (non-touch) 4.0.4.6 and from ROM Manager i booted into recovery. Now when i start up my phone it displays the normal Samsung logo with red dot on topleft of the screen and after that CWM flashes real quick like one second (without menus) and then the cycle continues.
Is there anything i can do to my phone at this point?
Follow the guide in general forum sticky thread to flash a full stock firmware, or just a recovery if you want to try, with odin.
ROM manager is best avoided for the s3.
Sent from my GT-I9300 using Tapatalk
Go to download mode and flash a new recovery by downloading .tar file on your PC and flash that via Odin..
Sent from my GT-I9300
Okay, thanks for this guys! Should search more threads before getting all worked up if something like this happens again.