[Q] Galaxy SII stuck on bootloader (need help) - Galaxy S II Q&A, Help & Troubleshooting

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:

Related

Phone stuck on Galaxy SII logo in boot

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..

New YP-G70 Owner.. A few questions

Hi Guys
New YP-G70 owner.. love it so far, but I have a few questions:
-Am I right in thinkiing I can do anything with it as i can with a SGS apart from make a phone call, such as mod it, flash it and custom it with EX Launcher, Cyanogen or anything from the Google Market.
- Does anyone know what the latest English language firmware. I found this on SamFirmware,
http://www.sammobile.com/firmware/?p...70&r=1#regiona
but the 2.3.6 are for italy and sweden, when i do a search for UK firmware, the latest one is 2.3.5.. XXKPF, which says France.. can anyone advise.
Thanks
In this thread u can find a file with the update:
http://forum.xda-developers.com/showthread.php?t=1559214&highlight=2+3+6
I booted up odin 1.85, installed the win 7 drivers, and tried to flash the rom, but its now stuck in download mode and it has no removable battery
How do i hard reset it.
Any advice
NightOrchid said:
I booted up odin 1.85, installed the win 7 drivers, and tried to flash the rom, but its now stuck in download mode and it has no removable battery
How do i hard reset it.
Any advice
Click to expand...
Click to collapse
Hold the power button until it restarts.
Sent using Tapatalk
klin1344 said:
Hold the power button until it restarts.
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, i did that.. it now shows me a mini phone, a computer with an orange triangle in the middle of them and pressing the power button just resets to that but it does detect it in windows and odin, it just stops with "ID3 Connection" when i try to flash 236
Ive just got this today.. can anyone help..please
Is it Bricked?. Will leaving it on to drain the battery help?.
Also, is there a recovery file for it. My version is a YP-G70CW, which i believe is the international version.
Any advice
you need to find the stock ROM & use ODIN to install via download mode. All the info you need are in these forums, I did a search for your model & stock rom I got this. Or search the dev forums.
http://forum.xda-developers.com/showthread.php?t=1574207
RMXO said:
you need to find the stock ROM & use ODIN to install via download mode. All the info you need are in these forums, I did a search for your model & stock rom I got this. Or search the dev forums.
http://forum.xda-developers.com/showthread.php?t=1574207
Click to expand...
Click to collapse
It wont go into download mode.. Its stuck on a black screen with a small phone, a small computer and an orange caution triangle inbetween the 2, but it is detected in odin, I get the yellow com3 port up and ID:3 Added, in the main window. When I start it begins the download, but gets stuck at "ID:3 setupconnection
Any advice or am i missing something here
NightOrchid said:
It wont go into download mode.. Its stuck on a black screen with a small phone, a small computer and an orange caution triangle inbetween the 2, but it is detected in odin, I get the yellow com3 port up and ID:3 Added, in the main window. When I start it begins the download, but gets stuck at "ID:3 setupconnection
Any advice or am i missing something here
Click to expand...
Click to collapse
That is download mode. You messed up slightly bad to get that as download mode. which file are you using in ODIN & which option are you using? as in, pitt, pda, etc....
RMXO said:
That is download mode. You messed up slightly bad to get that as download mode. which file are you using in ODIN & which option are you using? as in, pitt, pda, etc....
Click to expand...
Click to collapse
I didnt use a .pit file, I just used the XXKPH file in PDA here:
http://forum.xda-developers.com/showthread.php?t=1574207
then clicked start and it failed, now its just sitting there as mentioned, but i have downloaded the 8gig international..235.pit file, i just havent done anything yet.
What should i do next?
Ok, had a dig around and I need to flash a kernel as well as the KPH file.
http://forum.xda-developers.com/showthread.php?t=1574207
Is there a kernel available for stock KPH and do i need to use the .pit.
Thanks
Thank god.. Its Done.. Yep, its fixed through hard work, reading around, following advice given and much diligence. In the download mode I mentioned, I flashed using rjs Kernel which got it bootlooping, then flashed KPF in ODIN.. had to flash KPF twice, wiped Cache part > Dalvik Cache, fact. reset and reboot.. all done.
Because this has a built in battery, ill not be doing this again through odin.. ill use KIES, even if i have to wait 3 months for the release.
Its now 4.30am and im off to bed.
Thanks
Update... Im now on KPH236
Some questions about that flash:
When the flashing failed and i held holding the power button down for 10 seconds, thats when it booted into the other download mode (phone, triangle, PC), so would i be right in thinking this works like flashing a SGS and what bricks it would be:
- Installing US firmware on my EU player.
- Installing bootloaders for no reason or anything rom-wise from a SGS
- pulling the USB cable out when flashing OR closing down ODIN.
- Geting impatient and pressing/holding down buttons when still in download mode or flashing.
A few other questions:
- Is there anything else that I could do to protect it against a brick.
- As this is not a phone, can I go back to 235 if i want, just use ODIN with XXKPF 235 in PDA.
- If i do go back, Will I have to replace rjs kernel first with stock KPF kernel, then flash KPF ROM or can i just flash the rom and it will overwrite rjs.
- Googles search by voice doesnt work unless its wifi'd, as in finding something in the player like a song, a memo or contacts name, it just "connection problem" .. Is that normal, yet runs fine with wifi on.
The reason Im asking is because Kies keeps telling me there is a connection problem when i plug it in and it wont detect it.. Is this due to rjs kernel or is there another issue, just to put my mind at rest.
Thanks
NightOrchid said:
Update... Im now on KPH236
Some questions about that flash:
When the flashing failed and i held holding the power button down for 10 seconds, thats when it booted into the other download mode (phone, triangle, PC), so would i be right in thinking this works like flashing a SGS and what bricks it would be:
- Installing US firmware on my EU player.
- Installing bootloaders for no reason or anything rom-wise from a SGS
- pulling the USB cable out when flashing OR closing down ODIN.
- Geting impatient and pressing/holding down buttons when still in download mode or flashing.
A few other questions:
- Is there anything else that I could do to protect it against a brick.
- As this is not a phone, can I go back to 235 if i want, just use ODIN with XXKPF 235 in PDA.
- If i do go back, Will I have to replace rjs kernel first with stock KPF kernel, then flash KPF ROM or can i just flash the rom and it will overwrite rjs.
- Googles search by voice doesnt work unless its wifi'd, as in finding something in the player like a song, a memo or contacts name, it just "connection problem" .. Is that normal, yet runs fine with wifi on.
The reason Im asking is because Kies keeps telling me there is a connection problem when i plug it in and it wont detect it.. Is this due to rjs kernel or is there another issue, just to put my mind at rest.
Thanks
Click to expand...
Click to collapse
I will be extra cautious if a ROM has zImage (kernel) and/or bootloader in it. The consequence of a corrupted bootloader is obvious. A corrupted kernel can be problematic because the recovery mode comes with the kernel. If you messed up the kernel, you will loss your recovery mode as well.
Actually I hope more developers will publish their ROM in CWM flashable zip rather than Odin image. Since Odin basically dump the disk image to your device, any mistakes in the process will likely corrupt your device's partitions. In contrast, CWM flashing uses high level operations like file delete and copy to install the ROM (in most cases). It is much less risky than using Odin (if the developer knows what he is doing). Just my 2 cents.
So if i delete the "zimage" in a ROM and flash it, it will only flash the ROM? Also how do i know if it has bootloaders included?
Forgot to quote you but.... Cheers WT Ho, youve put my mind at rest and Im quite happy, that after my problems above, its not the player... rjs is nice and stable and boots really fast, so Im staying on KPH 236 and gonna upgrade through ODIN, not downgrade to KPF.. Have found the issues are with Kies not the kernel being recognised, alot of posts about Kies issues on various sites and forums. SamFirmware.com is my friend.. .
- Googles search by voice doesnt work unless its wifi'd, as in finding something in the player like a song, a memo or contacts name, it just "connection problem" .. Is that normal, yet runs fine with wifi on...
Yes you need a connection, heres why:
http://forum.openetna.com/index.php?topic=537.0
Cheers
Chris4evernoob said:
So if i delete the "zimage" in a ROM and flash it, it will only flash the ROM? Also how do i know if it has bootloaders included?
Click to expand...
Click to collapse
You can open an Odin ROM easily by using 7-zip. If it has md5, you will encounter a warning but that's fine.
For full ROM, you will see
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
Sbl.bin
zImage
Basically most custom ROMs will modify your factoryfs.rfs only. If you need a new kernel, zImage is also needed. All other files are related to boot or data partition (usually not needed). Therefore many ROMs only have zImage and factoryfs.rfs in them.
Although I haven't tried that myself, I think it is possible to just put the factoryfs.rfs in the tar file. That will be similar to the Odin package of rj's kernel, you will only see the zImage in the tar file.

Help- I messed up my phone bad (stuck on exclamation mark)

So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Nick281051 said:
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I checked it out..seems like putting the Stock back on might help me. Just so that I understand this better before I do it, am I installing the UCLE5_Stock_Rooted.tar using ODIN and that is enough to get me through.
Thanks
creepyncrawly said:
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Click to expand...
Click to collapse
Thanks for stopping by. I did not see your post when I posted my reply to the previous poster..I am so worried that I might screw it up more that I wanted to be doubly sure about this. from what I read, I am doing Step 2c as indicated below. Am I correct?
Thanks
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
UPDATE: I did download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package and extracted the file. Double clicked on it with the phone connected and all I see are the words I777- UCKH7 with Root with a lot of empty boxes below. Went to Odin and I see the phone connected (Com has yellow box) but nothing else is ticked off. Clicking Start does not do anything at all.
At my wits end- will not get any sleep tonite if I don't fix it.
Thanks in advance
I had a similar thing happen after trying to make a backup of the stock rom with Rom Manager (Yes, I know now, thanks much.)
If you keep trying new kernels/roms and it never clears up, you're pretty much stuck with wiping data. It won't wipe your sdcard, but more and more apps are sticking their data in the phone's memory rather than on the sdcard, so if you can get a backup at all, you really should.
Source: Was up until 2:30 the other night trying to make my phone work again. The above is a GUESS - it's probable I missed something that creepyncrawly wouldn't.
Ok more progress..turned off the phone and started 'I777UCKH7 OCD With Root.exe". Got the same window with lot of empty boxes. Had turned off the phone by this time and disconnected it. Now, I connected the phone and pressed the volume buttons. Phone goes into Download mode. Now, the Odin3 window has a Com port for the phone. Now I press start and it goes through a bunch of things before it declares "FAIL" in red. What do I do?
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
This stuff makes me so sad seeing these threads............ Thanx for helping him Creepy, ALWAYZ with 100% accurate info!!! Looks like this is the page he got the tar from in the zip on step 3 http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/ Much respect Creepy.....
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
g.kupster said:
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
Click to expand...
Click to collapse
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
creepyncrawly said:
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
Click to expand...
Click to collapse
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
g.kupster said:
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
Click to expand...
Click to collapse
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
creepyncrawly said:
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
Click to expand...
Click to collapse
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
g.kupster said:
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
Click to expand...
Click to collapse
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
creepyncrawly said:
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
Click to expand...
Click to collapse
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
g.kupster said:
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
Click to expand...
Click to collapse
Post the answer when you have your phone in hand and I'll suggest something to try.
creepyncrawly said:
Post the answer when you have your phone in hand and I'll suggest something to try.
Click to expand...
Click to collapse
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
g.kupster said:
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
Click to expand...
Click to collapse
I'm not working from first hand experience, but I'm fairly good at correlating information and making deductions. Something in the sequence of events doesn't add up to me. You're sure you have the I777? You pulled the battery and looked at the label?
At this point any suggestions that I can offer are based on educated speculation. The first thing to try would be to flash an ICS kernel using Odin, but you have already done that. I would suggest that you try that again, but discard the tar you already have and download the tar again, from here. That may be the same place you downloaded it before, not sure. Be sure to use the original USB cable that came with the phone.

[Q] Samsung Galaxy S2 won't boot. Recovery mode not accessible.

Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
marlu873 said:
Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
Click to expand...
Click to collapse
Sounds like the symptoms of a NAND RW corruption. Try this http://forum.xda-developers.com/showthread.php?t=1457458
Hi Marcus,
I had the same problem few days back.
If it's not broken by you trying something fancy, the best solution is to take it to service centre. If you have rooted your device, had installed some custom firmware or are not willing to visit the service centre for some other reason, please read ahead.
All I did was,
Installed USB connectivity drivers through Kies.
Installed ODIN 1.83
Ensured that Kies or any of its processes are not running in background.
Downloaded the official SGS2 firmware
Flashed the firmware through ODIN.
It took around 10 minutes for the full process and I was having my mobile up and running. Using ODIN sounds scary initially if you haven't used it. I have slowly started gaining confidence in it after using it a few times.
Please note that though the process is well proven to be safe, there is still an amount of risk involved.
Sent from my GT-I9100
Download a siyah kernel(like v4.0.1) .tar file and flash through odin.
See if that makes it boot/lets you into recovery.
Adarzannh said:
Sounds like the symptoms of a NAND RW corruption. Try this http://forum.xda-developers.com/showthread.php?t=1457458
Click to expand...
Click to collapse
I appreciate all of your answers!
Adarzannh: I tried the guide but when flashing using odin I get stuck on:
<ID:0/003> NAND Write Start!!
both when trying to flash the recovery package and the kernel. Any clues?
mananbdesai: where do I find the "official SGS2 firmware"?
theunderlining: is it enough just to flash a new kernel or do I afterwards need to flash ROM too?
marlu873 said:
Adarzannh: I tried the guide but when flashing using odin I get stuck on:
NAND Write Start!!
both when trying to flash the recovery package and the kernel. Any clues?
Click to expand...
Click to collapse
A couple of things..ensure KIES is not running on your computer in the background. If possible delete it completely. Also ensure your phone is connected to a USB port directly on the computer and not via a hub or to a USB port on a keyboard or something. Odin is a finicky s/w..so..
Also, try different versions. If v1.85 doesn't work try v3.4
marlu873 said:
mananbdesai: where do I find the "official SGS2 firmware"?
Click to expand...
Click to collapse
Go to sammobile.com or a sticky in the Original Android Development section here..has links to all the stock firmwares.
marlu873 said:
theunderlining: is it enough just to flash a new kernel or do I afterwards need to flash ROM too?
Click to expand...
Click to collapse
Lol at underlining. if you flash a custom kernel like siyah, you'll be rooted and get CWM. Using that you can install a custom ROM.
Sent from my GT-I9100 using xda app-developers app
And youll be safe from the 4.0.4 brickbug if you flash siyah.
You flash a kernel for various reasons like it has emmc cap disabled,you can tweak it etc.
You can flash siyah kernel and stop there.Or you can move onto a custom rom.
Whatever,when its done-backup your efs and make a nand backup.
And yesterday I was downgrading my wifes phone onto 4.0.3.I was using odin and kept getting "failed".After 3 attempts I realised I hadnt put the phone into download mode..........how stupids that......lol
hi there, just wondering, after Flashing the stock firmware through ODIN, do you lose everything in your phone? i need to get all the notes that I have in my phone (notes from the samsung stock apps). I dont have any external sd card in the phone. thanks in advance for the reply.
enquiry
marlu873 said:
Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
Click to expand...
Click to collapse
Hi there sir,
Has the problem solved ? Care to share the solution ?
Thanks.
i had the same exact problem, i tried flashing with odin n stock firmware but stuck in NAND write start, i didnt try flashing with PIT & repartition though, i couldnt be bothered anymore, so i took it to samsung service plaza, they told me the problem is in the main PCB (hardware issue), so all they did was replace that n it got fixed! i didnt pay because it's still under contract/ carrier warranty
Can you get into downloading mode? It's by hold and pressing volume down+home+power
Sent from my GT-I9100 using xda premium
it seems for some strange reason the phone wont turn on now. Wheni plug it in i get the blue flashing dot but its faint. Tried download mode and nothing.
same problem
araz.rozh said:
Can you get into downloading mode? It's by hold and pressing volume down+home+power
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
my phone is stuck at the bootlogo too. but mine is rooted n running on biftor rom (jellybean) pls how do i flash with odin? thanks
help pls.
Pls guys I have the same problem but like I said earlier mine occurred while I waS tRyna backup my ROM. Plss can I get a detailed guide on how to flaSh my samsung galaxy SII GT19100. ItS verion; jelly bean 4.12.Its rooted n runs on a custom ROM( biftor). Plss guys help. Thank you.
tatchero said:
Pls guys I have the same problem but like I said earlier mine occurred while I waS tRyna backup my ROM. Plss can I get a detailed guide on how to flaSh my samsung galaxy SII GT19100. ItS verion; jelly bean 4.12.Its rooted n runs on a custom ROM( biftor). Plss guys help. Thank you.
Click to expand...
Click to collapse
I had a similar problem, stuck at boot with Biftor v12, which happened after I tried to update SuperSU binary through CWM/TWRP. I don't know why it stuck at boot and why it wouldn't reboot to Recovery. Download mode was still working, so I had no choice but to flash new kernel through ODIN and see if it works.
So if your symptoms sound similar to mine, here's what I did to be able to boot again:
I REPEAT, SIMILAR TO MINE. MY SOLUTION MIGHT NOT NECESSARILY APPLY TO YOURS.
1. Download a suitable kernel in tar.md5 format. I used PhilZ-cwm6 v4.93.6 for XWLSN firmware (see OP http://forum.xda-developers.com/showthread.php?t=1877270)
2. Download ODIN, if you don't have it, found here http://forum.xda-developers.com/showthread.php?t=2189539
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
Only do the steps if you are absolutely sure. This worked for me, and I hope it gives some tips for your problem as well.
Flash-IS-Bright said:
I had a similar problem, stuck at boot with Biftor v12, which happened after I tried to update SuperSU binary through CWM/TWRP. I don't know why it stuck at boot and why it wouldn't reboot to Recovery. Download mode was still working, so I had no choice but to flash new kernel through ODIN and see if it works.
So if your symptoms sound similar to mine, here's what I did to be able to boot again:
I REPEAT, SIMILAR TO MINE. MY SOLUTION MIGHT NOT NECESSARILY APPLY TO YOURS.
1. Download a suitable kernel in tar.md5 format. I used PhilZ-cwm6 v4.93.6 for XWLSN firmware (see OP http://forum.xda-developers.com/showthread.php?t=1877270)
2. Download ODIN, if you don't have it, found here http://forum.xda-developers.com/showthread.php?t=2189539
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
Only do the steps if you are absolutely sure. This worked for me, and I hope it gives some tips for your problem as well.
Click to expand...
Click to collapse
Hi Flash-IS-Bright
I have the exact same problem with SuperSU on my rooted Galaxy S2. I updated the SuperSU app, and when I opened it, it recommended me to update the binary, I selected the CWM/TWRP option and then my phone tried to reboot but is now stuck. It can only access download mode.
In doing the process above, you only flashed the kernel? Did this totally work? And all your apps/messages were left intact on your phone?
Any help is appreciated.
peshmann said:
Hi Flash-IS-Bright
I have the exact same problem with SuperSU on my rooted Galaxy S2. I updated the SuperSU app, and when I opened it, it recommended me to update the binary, I selected the CWM/TWRP option and then my phone tried to reboot but is now stuck. It can only access download mode.
In doing the process above, you only flashed the kernel? Did this totally work? And all your apps/messages were left intact on your phone?
Any help is appreciated.
Click to expand...
Click to collapse
when ur updating the binary u should always choose the 'Normal' thing instead of the 'CWM/TWRP' one ma8
if u flash a kernel it will not delete anything on ur phone, all u have to do is to select the right kernel like 'Philz' for example (if ur on a stock JB firmware) and flash the same through 'ODIN' and reboot ur phone
Sun90 said:
when ur updating the binary u should always choose the 'Normal' thing instead of the 'CWM/TWRP' one ma8
if u flash a kernel it will not delete anything on ur phone, all u have to do is to select the right kernel like 'Philz' for example (if ur on a stock JB firmware) and flash the same through 'ODIN' and reboot ur phone
Click to expand...
Click to collapse
Thanks for your help. I've originally had Jeboo 1.2 kernel on my phone and tried to reflash that again through Odin. It passed, however I'm still encountering the same problem of the bootloop.
Would flashing a different kernel help? I'm on stock JB firmware but with a Jeboo kernel. I am happy to try another kernel (if that would not brick my phone)
Do you have any other suggestions to help me solve this?
Again thanks for your help
peshmann said:
Thanks for your help. I've originally had Jeboo 1.2 kernel on my phone and tried to reflash that again through Odin. It passed, however I'm still encountering the same problem of the bootloop.
Would flashing a different kernel help? I'm on stock JB firmware but with a Jeboo kernel. I am happy to try another kernel (if that would not brick my phone)
Do you have any other suggestions to help me solve this?
Again thanks for your help
Click to expand...
Click to collapse
You could try flashing hawkerpaul's kernel wiper first and then install another stock kernel like PhilZ or Apollo, and see if that helps.
Neat Rom lite,suddenly struck in boot loop after 1 month of operation.
Dear All,
I have installed the "I9100XWLSZ_NeatROM_Lite_v5.0.1" custom rom and after 1 month of successful usage, today suddenly the phone was dead.(probably due to autoupdates over wifi) . I tried to reboot, but didnt. Tried to restart but got stuck in the logo screen with yellow triangle.
Tried to enter recovery mode, but no use. Only download mode is possible.
Tried to flash the stock rom using odin, but no use, Nand write failed.
Can somebody help me how to come out of this situation. Shall I install a different kernal and see?
Regards,
Maka11

i9100 won't boot rom or recovery after trying to install a CM nightly

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

Categories

Resources