Hi there, I'm panicking right now.
I just rooted my phone using a tutorial online and it was no problem and everything worked fine after that.
Then I used another tutorial to flash my ROM to CM7 and that's when I started to have problems.
I booted into ClockworkMod Recovery (holding volume up + home + power) and wiped data and chache partition, then I select "Install zip from sdcard" and chose CM7 zip file which I had put on to my sd card, I get a message that installation was successful.
But now I can't access my phone, it's stuck at the Samsung Galaxy SII logo.
I have wiped data again and used Odin to flash a stock ROM on to my phone but it doesn't work.
I need help guys.
EDIT: This post doesn't matter now, there is a new reply at page 3 with new problems.
Did you use a .pit file a repartition when you flashed a stock ROM with ODIN again? What do you mean the phone doesn't work? Does it bootloop or still stuck on the startup logo?
Prasad007 said:
Did you use a .pit file a repartition when you flashed a stock ROM with ODIN again? What do you mean the phone doesn't work? Does it bootloop or still stuck on the startup logo?
Click to expand...
Click to collapse
Well the phone did bootloop at one time and I fixed that by flashing a stock ROM on the phone with Odin, did not use a PIT file.
Now the phone is just stuck on the white Galaxy SII logo and I was hoping that flashing the phone again with stock ROM would also fix that.
I did not use a PIT file for that either.
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Prasad007 said:
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Click to expand...
Click to collapse
Yep!
@OP Download this package : http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
And then, in ODIN, put :
.PIT -> PIT
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
Toggle repartition, and those 2 standard ticks. DO NOT TICK ANYTHING ELSE.
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Prasad007 said:
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Click to expand...
Click to collapse
Could you link to a ROM with a .pit file, have not found any. Thanks!
Also, I tried flashing to CM7 again with ClockworkMod Recovery and it now said:
E:Error in /sdcard/cmgs.zip
(Status 7)
Installation aborted
Is that bad?
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
oinkylicious said:
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
Click to expand...
Click to collapse
I have an I9100 and I got the CyanogenMod from the official website where I chose my device.
The first flash was pretty fast yes.
oinkylicious said:
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
Click to expand...
Click to collapse
Wrong.
10 chars.
Phistachio said:
Yep!
@OP Download this package :
And then, in ODIN, put :
.PIT -> PIT
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
Toggle repartition, and those 2 standard ticks. DO NOT TICK ANYTHING ELSE.
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Click to expand...
Click to collapse
Thanks man! You saved me!
I was seriously going to stay up all night trying to fix this and skip school tomorrow...
But I still want a custom ROM
Is there a better way than booting into ClockworkMod Recovery and installing zip file from sd card?
Also, any idea about why all this would happen to me? I got all the tutorials on an Icelandic forum where a person with the same phone did exactly what I was going to do and it worked perfectly for him, and I have gone over the steps many times, I did not screw up.
How to flash CM7
1) Flash a kernel with CWM, CF-root will do
2) Download CM7 zip and put it in your internalSD card
3) Boot into CWM
4) Flash CM7 zip
5) Reboot into CWM
6) Flash CM7 zip again
7) wipe cache/data/dalvik cache
6) reboot and wait for upto 10min for it to boot.
You HAVE to flash the CM7 zip twice.
Also you NEVER need to use the .pit, also never tick repartition, a bad flash with repartition ticked is a one way street to hardbrick land.
himmip said:
Thanks man! You saved me!
I was seriously going to stay up all night trying to fix this and skip school tomorrow...
But I still want a custom ROM
Is there a better way than booting into ClockworkMod Recovery and installing zip file from sd card?
Also, any idea about why all this would happen to me? I got all the tutorials on an Icelandic forum where a person with the same phone did exactly what I was going to do and it worked perfectly for him, and I have gone over the steps many times, I did not screw up.
Click to expand...
Click to collapse
Ideally, you:
1. Flash a stock ROM via ODIN
2. Flash CF-Root via ODIN
3. Flash a custom ROM such as CM9 via CWM Recovery
Ok thanks guys!
And just to be sure, I went here: http://www.cyanogenmod.com/devices/samsung-galaxy-s2 and was going to download nightly, or is their anything else you would recommend more?
himmip said:
Ok thanks guys!
And just to be sure, I went here: http://www.cyanogenmod.com/devices/samsung-galaxy-s2 and was going to download nightly, or is their anything else you would recommend more?
Click to expand...
Click to collapse
Only this: http://forum.xda-developers.com/showthread.php?t=1410400
Prasad007 said:
Only this: http://forum.xda-developers.com/showthread.php?t=1410400
Click to expand...
Click to collapse
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
himmip said:
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
Click to expand...
Click to collapse
The stable build is much older and actually less stable than the newest nightly.
Also you can restore user apps with titanium backup, just not system apps.
himmip said:
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
Click to expand...
Click to collapse
You can restore non-system apps, just not their data.
Prasad007 said:
Ideally, you:
1. Flash a stock ROM via ODIN
2. Flash CF-Root via ODIN
3. Flash a custom ROM such as CM9 via CWM Recovery
Click to expand...
Click to collapse
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
EDIT: Never mind guys, finally got it to work Thanks for your help!
himmip said:
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
Click to expand...
Click to collapse
If the Home button doesn't work for you, try selecting with the power button once inside CWM Recovery..
Phistachio said:
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Click to expand...
Click to collapse
seconded...
Don't panic dude, it happens sometimes Keeping cool is the key to fixing your phone without making it worse than it already is... I can't count the times this has happened to me already, and there ain't nuffin like a good 'ole repartitioning to set things straight (and show the damn contraption who's boss around these here parts.. I hate those stupid machines to whom nobody has ever taught that Man's genius INVARIABLY always triumphs over dumb and inert matter.. )
(although I almost never flash the whole ROM back on : most times flashing the .PIT file and rebooting the device does the trick -unless it's an installed app which caused the trouble in the first place, in which case you're better off starting over from scratch than wasting time trying to debug the problem)
N.B : don't forget to flash the "old bootloader" too, AFTER you've flashed the PIT and rebooted the device (or at least rebooted the recovvery, to check that it boots off a valid partition), I've noticed the new one can give a lot of weird and unpredictable behaviors when used in conjunction with root and a CMx ROM.
---------- Post added at 01:36 PM ---------- Previous post was at 01:28 PM ----------
himmip said:
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
EDIT: Never mind guys, finally got it to work Thanks for your help!
Click to expand...
Click to collapse
I was going to ask : have you flashed the CM rom twice, and flashed the google apps pack BEFORE even rebooting the phone ? It's almost always mandatory to do this precise sequence, the installation routine of the CM ROM is not quite perfect -far from it, actually..
Related
I've basically soft bricked my phone and haven't got a clue how to fix it. I've read everything and tried everything and still can't get it working with my knowledge.
I tried to flash resurrection v1.0 but phone just hung on the GSII startup screen and froze. I've tried different kernels so that i can flash from external SD card but whenever i try this, it always says bad file (no matter what file i try use to flash). When i try flash from the internal SD card, it says its all successful (for the resurrection 1.0) but i'm back to where i started.
I think i need to flash the firmware using odin but i can't find the right files. Anyone got any ideas how to fix this issue? I've been playing around with it for 10 hours roughly now.
The original kernel i used when i flashed to resurrection 9.4 was for XWKI4.
Thanks.
Nelinski said:
I've basically soft bricked my phone and haven't got a clue how to fix it. I've read everything and tried everything and still can't get it working with my knowledge.
I tried to flash resurrection v1.0 but phone just hung on the GSII startup screen and froze. I've tried different kernels so that i can flash from external SD card but whenever i try this, it always says bad file (no matter what file i try use to flash). When i try flash from the internal SD card, it says its all successful (for the resurrection 1.0) but i'm back to where i started.
I think i need to flash the firmware using odin but i can't find the right files. Anyone got any ideas how to fix this issue? I've been playing around with it for 10 hours roughly now.
The original kernel i used when i flashed to resurrection 9.4 was for XWKI4.
Thanks.
Click to expand...
Click to collapse
Am sure you didnt search before posting but i recommend this
download this and extract, you get three files
load pda, modem and csc
also load pit in the pit tab, uncheck repartition and flash with odin 1.85
goodluck.
http://hotfile.com/dl/123612065/a85a23d/I9100JPKF3.rar.html
http://hotfile.com/dl/139350663/9ba2e55/u1_02_20110310_emmc_EXT4.pit.rar.html
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
here is odin incase you are too lazy to search
http://www.4shared.com/rar/dHnCINEN/odin_185.html
put phone in download mode by pressing volume - +home+power
connect.
If this help and i am sure only flash siyahs kernel... Start CWM and Clear Cache Data and and and all with Clear.. Than flash again.... I had the same prob 3 times because i always flshed over and forgot to cler data;cache;dalvik-cache...
Sent from my GT-I9100 using xda premium
How to flash with Odin Hold Volume UP + Home button + Power button...
Sent from my GT-I9100 using xda premium
Thanks for the help but had one last attempt and got it working. Thanks everyone who helped.
Kaffee4Eck said:
How to flash with Odin Hold Volume UP + Home button + Power button...
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thats wrong .
Down not up .
jje
JJEgan said:
Thats wrong .
Down not up .
jje
Click to expand...
Click to collapse
I'm not sure that guy (Kaffee4Eck) knows what he's talking about anyways. In another thread, he also suggested an I9100G user to flash Siyah kernel.
Right i've got it back working with 2.3.4 i think it is, however i still don't want to give in to getting resurrection 1.0.
Are there any steps i'm missing which causes it to hang on GSII startup then restart into the stock kernel? Tried flashing the old bootloader as well which didn't help.
Nelinski said:
Right i've got it back working with 2.3.4 i think it is, however i still don't want to give in to getting resurrection 1.0.
Are there any steps i'm missing which causes it to hang on GSII startup then restart into the stock kernel? Tried flashing the old bootloader as well which didn't help.
Click to expand...
Click to collapse
If you're having trouble flashing a custom ROM, first place to start would be the thread for that particular custom ROM.
All custom ROMs should have detailed installation instructions. Make sure you are following them to the letter.
If you are flashing kernels, you must make sure you flash a kernel meant for your phone, and meant for your build. Hang on boot screen usually means you have a file not compatible with your build of Android. Could be kernel, but could also be another system file.
I have been searching, its what im currently doing now but everyone seems to have got it working or have completely different problems to me.
http://forum.xda-developers.com/showthread.php?t=1436854
Literally followed it step for step, there isn't much to it. When i did 9.4 it had the same steps and that all worked fine, so i must be missing something pretty damn important here.
So when you say:
Nelinski said:
Are there any steps i'm missing which causes it to hang on GSII startup then restart into the stock kernel? Tried flashing the old bootloader as well which didn't help.
Click to expand...
Click to collapse
what do you mean by restart into the stock kernel? This part of the sentence doesn't make sense.
Are you saying it is hanging on the boot logo for a very long time, then it boots normally, but you are not on the new ROM?
Sorry, what i was trying to say was the galaxy s 2 logo shows for about 5 seconds then the phone restarts itself into recovery mode (which is the new kernel included with the resurrection 1.0 flash).
Nelinski said:
Sorry, what i was trying to say was the galaxy s 2 logo shows for about 5 seconds then the phone restarts itself into recovery mode (which is the new kernel included with the resurrection 1.0 flash).
Click to expand...
Click to collapse
And now this sentence doesn't make sense.
So when it restarts into recovery, it is stock recovery instead of CWM recovery? Is that what you mean?
Stock recovery will only have like 4 or 5 line entries, with no options to back up/restore. CWM recovery will have substantially more options.
EDIT to add: BTW - did you see under the "Rom Installation (please don`t miss any step! )" section... there is text that says: "NOTE: İF YOU WANT FLASH SOMETHİNG FROM CWM RECOVERY FİRST YOU MUST İNSTALL CWM.ZİP FROM STOCK RECOVERY MOD(APPLY UPDATE FROM EXTERNAL STORAGE AND CHOOSE CWM.ZİP AND İNSTALL)
AND NOW TOUCH RECOVERY MODE WİLL APPEAR THAN YOU CAN FLASH ZİP FİLES"
---------- Post added at 03:23 PM ---------- Previous post was at 03:11 PM ----------
Also, you seem to be mixing up the terms kernel and recovery. They are NOT the same. You should read up on what those two terms actually mean.
"So when it restarts into recovery, it is stock recovery instead of CWM recovery? Is that what you mean?"
Yeah thats what i meant sorry, been a long day lol. I don't really get what the last bit means..
"NOTE: İF YOU WANT FLASH SOMETHİNG FROM CWM RECOVERY FİRST YOU MUST İNSTALL CWM.ZİP FROM STOCK RECOVERY MOD(APPLY UPDATE FROM EXTERNAL STORAGE AND CHOOSE CWM.ZİP AND İNSTALL)
AND NOW TOUCH RECOVERY MODE WİLL APPEAR THAN YOU CAN FLASH ZİP FİLES"
I've got cwm and can flash roms if thats what it means? Sorry for sounding like such a noob..
Nelinski said:
"So when it restarts into recovery, it is stock recovery instead of CWM recovery? Is that what you mean?"
Yeah thats what i meant sorry, been a long day lol. I don't really get what the last bit means..
"NOTE: İF YOU WANT FLASH SOMETHİNG FROM CWM RECOVERY FİRST YOU MUST İNSTALL CWM.ZİP FROM STOCK RECOVERY MOD(APPLY UPDATE FROM EXTERNAL STORAGE AND CHOOSE CWM.ZİP AND İNSTALL)
AND NOW TOUCH RECOVERY MODE WİLL APPEAR THAN YOU CAN FLASH ZİP FİLES"
I've got cwm and can flash roms if thats what it means? Sorry for sounding like such a noob..
Click to expand...
Click to collapse
So... You know there's also a video guide on installation in that thread too, right? I've never installed this ROM, so I've about reached the limit of how far I can help you if you don't understand that last bit, as you say.
Indeed, i've watched it several times. Thats what i don't get. Everything looks the same, yet i'm the one with the problem lol.
I basically go into custom recovery, install the 3 things (rom, and both gapps), clear the cache and dalvik cache yet it goes freezes on logo then restarts into stock recovery.
Nelinski said:
Indeed, i've watched it several times. Thats what i don't get. Everything looks the same, yet i'm the one with the problem lol.
I basically go into custom recovery, install the 3 things (rom, and both gapps), clear the cache and dalvik cache yet it goes freezes on logo then restarts into stock recovery.
Click to expand...
Click to collapse
Well, only 2 more posts, and you can post in the actual ROM thread to ask for help. Maybe the ROM chef can help you more.
Yeah, thanks for all the help mate, i appreciate your time.
gsmxpert said:
Am sure you didnt search before posting but i recommend this
download this and extract, you get three files
load pda, modem and csc
also load pit in the pit tab, uncheck repartition and flash with odin 1.85
goodluck.
http://hotfile.com/dl/123612065/a85a23d/I9100JPKF3.rar.html
http://hotfile.com/dl/139350663/9ba2e55/u1_02_20110310_emmc_EXT4.pit.rar.html
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
here is odin incase you are too lazy to search
http://www.4shared.com/rar/dHnCINEN/odin_185.html
put phone in download mode by pressing volume - +home+power
connect.
Click to expand...
Click to collapse
Thanks man found this thread and it solved my problem in minutes. Phone no longer has yellow triangle and is back to normal.
Sent from my GT-I9100 using xda premium
I recently updated my phone from 2.3.3 to Cyanogenmod 7.1 I believe and went to overclock the phone, Unfortunately, I overclocked it too much and now it is stuck in an endless loop on the boot screen..
Phone is obviously a Galaxy Ace, Network carrier is Vodafone UK.
I have been trying for the last two hours to look for answer's on how to fix this and I haven't found anything, So I thought the best idea was to come to here.. Any help would be appreciated, I have also tried to install other ROM's on to the phone to correct it but it look's like the CPU is still at the overclocked setting and because of that, Won't boot up.
thanks.
Dan.
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
madman_amit said:
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
Click to expand...
Click to collapse
I tried wiping everything before but will give ODIN a try. Thank you. I really like the phone and am trying my best to get it working again. lol
So, I downloaded ODIN and I have absolutely no idea what I am doing.. I don't want to risk breaking the phone anymore.. The only tut on how to use ODIN is for the Galaxy 3..
I have never done anything like this before so it's all new to me.. :/
Ok, I used ODIN and I have the original ROM that came with the phone, But still in an endless loop on the Samsung boot screen.. :/ I am totally stuck now.. I have tried all I know to get it to work
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Th3GrimRipp3r said:
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Click to expand...
Click to collapse
Excellent work having a backup on your laptop. First thing now do a full backup on your phone before you think about further experiment. If overclocking make sure "set at boot" is not ticked. Finally read up a little on xda before you do anything - a good place to start is "Tutorial" on top of dev section and the "q & a " thread here.
I hope this works for You.
You've a one packege STOCK Rom?
so open ODIN 4.38
Untick Reset Time
Choose your one package file.
choose OPS; attatched here.
press start.
to sum up: you have this ticked only:One package, auto reboot, protect OPS
if doesnot work go to recovery and try factory reset& cache wipe.
if doesnot work, try flshing CWM and install any backed up rom, if you want one. just PM and i will upload backed up stock rom.
I really hope it helps because I got the same issue after flshing a stock from ODIN, but been removed from wipe data& factory reset.
_________________________________________________
If I've helped you in any way, Press THANKS
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Hi All,
I got a problem
This what caused the problem:
- I installed Revolt Rom after factory reset/wiping Dalvik cache.
- It asked for Kernels, Gapps etc.
- I chose DorimanX kernel and got done with it then it asked me for a reboot.
- After reboot the phone got stuck showing DorimanX kernel and its logo. Nothing happened for 2 hours.
- After that I downloaded a safe kernel and installed using Odin 3.07.
This is what is happening now.
- Even after installing a new kernel It is stuck at boot. Shows "Samsung Galaxy SII I9100" with a "Yellow Triangle".
- I can not go into recovery mode. There was a CWM installed before.
I just have EFS backup folder.
I have just started flashing new ROMs so I am sort of a noob.
Please consider this and help me to fix it.
Thanks in advance.
Go to Samfirmware. Get a stock rom for your carrier (or for your country if there isn't one; or any stock rom if there isn't one for your country). Flash it with Odin. This gets covered here all the time - search for how to.
MistahBungle said:
Go to Samfirmware. Get a stock rom for your carrier (or for your country if there isn't one; or any stock rom if there isn't one for your country). Flash it with Odin. This gets covered here all the time - search for how to.
Click to expand...
Click to collapse
I am gonna do this now. Do I need to install CWM again after I am done flashing stock ROM?
Once you've got your phone working normally (forget about anything else for now; this should be your priority), yes; then you can re-root your phone/flash a custom rom/whatever.
MistahBungle said:
Once you've got your phone working normally (forget about anything else for now; this should be your priority), yes; then you can re-root your phone/flash a custom rom/whatever.
Click to expand...
Click to collapse
I got a problem now
I flashed stock firmware and Flashed using Odin. Everything went normally and Odin said "PASS" also.
But now when I try to turn my phone on it shows Samsung logo with device model number(without yellow triangle) and it crashes after that.
What firmware did you flash; what Android version is it ?
Edit - As long as it isn't 4.0.4, boot into recovery mode; switch phone off, hold home/volume up/power. Then do a wipe/factory reset. If you flashed 4.0.4, get another rom that isn't 4.0.4 & flash that. If you end up with bootloop again, do the reset as above.
MistahBungle said:
What firmware did you flash; what Android version is it ?
Edit - As long as it isn't 4.0.4, boot into recovery mode; switch phone off, hold home/volume up/power. Then do a wipe/factory reset. If you flashed 4.0.4, get another rom that isn't 4.0.4 & flash that. If you end up with bootloop again, do the reset as above.
Click to expand...
Click to collapse
I flashed jellybean (4.1.2).
I am not able to access recovery mode.
Sticker on the phone chassis under the battery; what does it say ?
MistahBungle said:
Sticker on the phone chassis under the battery; what does it say ?
Click to expand...
Click to collapse
Sticker says:
Model - GT-I9100
SSN - I9100GSMH
Rated - ...
FCC ID - A3LGTI9100
And then I have IMEI and S/N.
I have flashed "I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5".
When you say 'the phone crashes', does it actually bootloop (show the boot screen over & over) or does it automatically shutdown at this point ? (Shutdown could be caused by some kind of power issue).
MistahBungle said:
When you say 'the phone crashes', does it actually bootloop (show the boot screen over & over) or does it automatically shutdown at this point ? (Shutdown could be caused by some kind of power issue).
Click to expand...
Click to collapse
It actually shuts down. But it was fine before(before flashing it was showing boot screen over and over).
MistahBungle said:
When you say 'the phone crashes', does it actually bootloop (show the boot screen over & over) or does it automatically shutdown at this point ? (Shutdown could be caused by some kind of power issue).
Click to expand...
Click to collapse
I actually shuts down. But it was fine(was stuck at boot screen before flash).
Check the md5 sum on the rom package you downloaded. If you can't do that, get 7Zip & 'test' the package (in Windoze Explorer, R click on the tar.md5 & choose 7Zip/test archive), If the md5 sum check or 'test' fails, bad download. Download again, and if it keeps happening, download with a different internet connection (I had this problem once; every rom package I downloaded from home that time ended up corrupted).
If that checks out OK, put the phone on charge & leave it for as long as it normally takes to get a full charge from almost empty (couple of hrs) & see if you can get into recovery mode.
If you can't try another stock rom from Samfirmware (not 4.0.4; doesn't necessarily have to be for your country/carrier given you're probably going to root your phone & go back to a custom rom when you fix it).
MistahBungle said:
Check the md5 sum on the rom package you downloaded. If you can't do that, get 7Zip & 'test' the package (in Windoze Explorer, R click on the tar.md5 & choose 7Zip/test archive), If the md5 sum check or 'test' fails, bad download. Download again, and if it keeps happening, download with a different internet connection (I had this problem once; every rom package I downloaded from home that time ended up corrupted).
If that checks out OK, put the phone on charge & leave it for as long as it normally takes to get a full charge from almost empty (couple of hrs) & see if you can get into recovery mode.
If you can't try another stock rom from Samfirmware (not 4.0.4; doesn't necessarily have to be for your country/carrier given you're probably going to root your phone & go back to a custom rom when you fix it).
Click to expand...
Click to collapse
I tested the md5 sum with 7zip. It was ok.
After charging the phone also I am not able to get into recovery mode(It gets stuck at android image)..
So going to try another stockroom.
Also try flashing the Odin version of whatever Siyah build is compatible with the Android version you flashed (I forget which, check the Siyah thread; should be on the first page) & see if that boots the phone normally or allows you to get into recovery mode (Again, and I can't stress this enough, don't flash a 4.0.4 rom if you do intend to flash Siyah, if you do a wipe from recovery chances are you'll brick your phone).
MistahBungle said:
Also try flashing the Odin version of whatever Siyah build is compatible with the Android version you flashed (I forget which, check the Siyah thread; should be on the first page) & see if that boots the phone normally or allows you to get into recovery mode (Again, and I can't stress this enough, don't flash a 4.0.4 rom if you do intend to flash Siyah, if you do a wipe from recovery chances are you'll brick your phone).
Click to expand...
Click to collapse
I will not flash 4.0.4 at all.
How do I flash Siyah using Odin because I downloaded TAR but it has zImage file which is not recognized by Odin. I understand that .zip has to be flashed using CWM.
Searched google as well but no help.
MistahBungle said:
Also try flashing the Odin version of whatever Siyah build is compatible with the Android version you flashed (I forget which, check the Siyah thread; should be on the first page) & see if that boots the phone normally or allows you to get into recovery mode (Again, and I can't stress this enough, don't flash a 4.0.4 rom if you do intend to flash Siyah, if you do a wipe from recovery chances are you'll brick your phone).
Click to expand...
Click to collapse
Oh I am sorry. I have flashed Siyah build(Previously did not try to add the zip file).
But even that does not help.(now phone has stuck on siyah logo).
OK. Either your phone is busted or something really obvious is being missed here. Given what you've done, your phone should work unless it's borked (or unless something really obvious isn't being done).
I recommend you keep trying to get into recovery mode so you can do a reset, or perhaps try this thread, it's an oldie, but it's saved a lot of people.
If I had to wager tho, we're missing something really obvious (And given the 'issues' you had trying to flash Siyah, that makes me think even more you're not doing something/not doing it right).
MistahBungle said:
OK. Either your phone is busted or something really obvious is being missed here. Given what you've done, your phone should work unless it's borked (or unless something really obvious isn't being done).
I recommend you keep trying to get into recovery mode so you can do a reset, or perhaps try this thread, it's an oldie, but it's saved a lot of people.
If I had to wager tho, we're missing something really obvious (And given the 'issues' you had trying to flash Siyah, that makes me think even more you're not doing something/not doing it right).
Click to expand...
Click to collapse
I did exactly what you told me to. Meanwhile I was searching I found this thread http://forum.xda-developers.com/showthread.php?t=1457458
Has my phone got a corrupted NAND rw (read/write) function?
And one more question
Do you suggest me to flash CWM and try going to recovery mode after that?
I'll keep trying though.
MistahBungle said:
OK. Either your phone is busted or something really obvious is being missed here. Given what you've done, your phone should work unless it's borked (or unless something really obvious isn't being done).
I recommend you keep trying to get into recovery mode so you can do a reset, or perhaps try this thread, it's an oldie, but it's saved a lot of people.
If I had to wager tho, we're missing something really obvious (And given the 'issues' you had trying to flash Siyah, that makes me think even more you're not doing something/not doing it right).
Click to expand...
Click to collapse
Woowwwwwww.
Thanks man. When I tried flashing another stock rom. It got fixed.
Thanks a ton man. You were really helpful.:laugh::laugh:
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
the donkey said:
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
Click to expand...
Click to collapse
Do you mean you can't even get into recovery? If it can, I would think a data wipe might get the ROM to be able to boot.
the donkey said:
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
Click to expand...
Click to collapse
You might want to double check if you are using the right version of recovery that kernel is fully supported with your ROM. For example, if you are trying to install a KK ROM using an old version of CWM you will end up in error 7 or end up in a boot loop screen. My words are pretty mess up but I hope you get what I mean. So make sure you have the right version that match each other (recovery, kernel, ROM).
Hope that helps.
im new to all of this. when i hold the home button the power button and the vol down button i get a screen telling me installing a custom os could be bad press up to continue i do this and install even the official software but when it reboots it keeps looping on the samsung logo
cglegion said:
You might want to double check if you are using the right version of recovery that kernel is fully supported with your ROM. For example, if you are trying to install a KK ROM using an old version of CWM you will end up in error 7 or end up in a boot loop screen. My words are pretty mess up but I hope you get what I mean. So make sure you have the right version that match each other (recovery, kernel, ROM).
Hope that helps.
Click to expand...
Click to collapse
i cant access the phone to see what kernal was on it so i am just trying to get it back to normal
the donkey said:
i cant access the phone to see what kernal was on it so i am just trying to get it back to normal
Click to expand...
Click to collapse
I suggest you flash a working recovery via odin first. Look for TWRP, it's the best newbie-friendly recovery or try CWM if you are looking for more advanced options. After that, flash a stock or custom ROM to get your phone back working. Make sure they are compatible with each other. Why didn't it work when you try flashing the stock firmware via odin? Make sure the zip file is downloaded properly.
Hope that helps.
cglegion said:
I suggest you flash a working recovery via odin first. Look for TWRP, it's the best newbie-friendly recovery or try CWM if you are looking for more advanced options. After that, flash a stock or custom ROM to get your phone back working. Make sure they are compatible with each other. Why didn't it work when you try flashing the stock firmware via odin? Make sure the zip file is downloaded properly.
Hope that helps.
Click to expand...
Click to collapse
that sounds excellent but being new and a bit thick what is a twrp and where would i get one?
still no joy
ok so now i have tried 3 official samsung roms h3g o2 and t mobile the h3g installs but just keeps looping the boot screen the o2 failed and the t mobile installes but all i get is a blck screen but it showes the batter the clock and the usb conection i can also go into it through my computer but it wont boot up properly. is it possible to get a samsung rom thats not network based?
the donkey said:
ok so now i have tried 3 official samsung roms h3g o2 and t mobile the h3g installs but just keeps looping the boot screen the o2 failed and the t mobile installes but all i get is a blck screen but it showes the batter the clock and the usb conection i can also go into it through my computer but it wont boot up properly. is it possible to get a samsung rom thats not network based?
Click to expand...
Click to collapse
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
il give it a go
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
il try that just now cheers
ahhh my heed
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
ok so i downloaded the romnuke and the neatrom the instructions say... Boot into Recovery
- Install RomNuke (Does all clean & backup your android folder as well) - Thanks to Hawkerpaul
- Install ROM
- Reboot & Enjoy
but when i unzip the files i cant see any way of gettong romnuke to work i tried odin but it doesnt pick it up is there some other download i need??
still no joy
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
ok so i put the zip files on an sd card and put it in the phone. but when i try and install them it says ignature verification failed also if i try and wipe the date and retore it says faild to mount/efs invalid argument. when i manage to get the t mobile rom to load the screen is black but i can get the swipe down screen to turn on blue tooth or wifi
the donkey said:
ok so i put the zip files on an sd card and put it in the phone. but when i try and install them it says ignature verification failed also if i try and wipe the date and retore it says faild to mount/efs invalid argument. when i manage to get the t mobile rom to load the screen is black but i can get the swipe down screen to turn on blue tooth or wifi
Click to expand...
Click to collapse
This error is most probably because you don't have the right Rom for the right model or not compatible hence the verification error. Are you doing this in recovery mode? Make sure you follow the installation instructions properly and download the right one for your phone model. Just try cyanogenmod for starter. Installation is easy to understand.
still no joy
cglegion said:
This error is most probably because you don't have the right Rom for the right model or not compatible hence the verification error. Are you doing this in recovery mode? Make sure you follow the installation instructions properly and download the right one for your phone model. Just try cyanogenmod for starter. Installation is easy to understand.
Click to expand...
Click to collapse
ok so i went to cyanogenmod downloaded the newest file for the s2 when i did unzip i get 2 folder meta-inf and system plus a boot.img file. i burned the boot file to a disc but when i check it the disk is empty even though i can see its burned. also when i go to sammobile to get firmare it says no files available...therte must be some way of getting this to work H E L PPPPPPPPPPP
Dude, you're not supposed to be burning anything to discs. The zip file is what the recovery uses to install from. It should include the custom kernal too.
Copy the zipped ROM file to your SD card, put it in your phone and boot into recovery. Assuming you've already flashed the latest custom recovery CWM or TWRP (I prefer TWRP)
From here, to be safe, do a full wipe (That's everything except sd-card: system, data, cache, dalvik-cache)
Now you install/flash the zip file via recovery. Hopefully that completes without error. After that clear cache and dalvik-cache again just to be sure (I do this out of habit)
Reboot.
Hope this helps. I saw you mention something about "efs" and that gives me a bad feeling, read something about needing to back that up before bad things happen. But anyway, good luck :good: