Update: So, the bootloop problem is now solved, thanks to @MistahBungle guiding me at Troubleshoot a failed Odin flash and did the Another option in i9100 step. But, access to Recovery Mode is still unsolved... So here's the phone problem's history:
Okay. Long-story short, after I downgraded-flashed my friend's S2 to Stock GB (which is I think a corrupted file, my bad) via Mobile Odin, the phone starts to bootloop. Here are the factors:
1. Main problem is the phone won't go Recovery Mode. (Vol UP + Power only leads to a reboot).
▬ Thinking it's a kernel issue, I flashed a Stock JB Firmware XWMS1 via Odin (which is a success), then flashed Philz Kernel for XWMS1 (flashable via Odin, which also is a success). But sadly, the phone still won't go to Recovery Mode.
▬ Before I flashed the GB, to ensure the phone can go to Recovery, I tested the Volume keys, and they are working, so a faulty/broken Volume UP key is excluded in reasoning.
2. I can access Download Mode, can successfully flash stock firmwares via Odin (tried officials 4.0.3/2.3.x/4.1.2), but the result are the same = Bootloops and cannot access Recovery Mode, again. Each and every one of them.
What I think: Since it's a bad firmware, I think wiping system/data/cache/boot.img will do the trick, but I can't access Recovery Mode for it. Is there a possible procedure like via Odin? Like flashing some files to wipe those filesystems and such?
Thanks for noticing, and a much of a thanks for helping! :good:
Flash the 3 part firmware linked in Hopper8's 'Odin troubleshooting' thread stickied in General which will wipe the phone & hopefully get rid of whatever is causing the problem. From there, re-root your phone & restore nandroid or reinstall custom rom/kernel/whatever.
MistahBungle said:
Flash the 3 part firmware linked in Hopper8's 'Odin troubleshooting' thread stickied in General which will wipe the phone & hopefully get rid of whatever is causing the problem. From there, re-root your phone & restore nandroid or reinstall custom rom/kernel/whatever.
Click to expand...
Click to collapse
I guess that's my last bet. How does that work? Just curious.
As it's a 3 part firmware, the separate CSC wipes the phone. And as I said, hopefully this gets rid of whatever is causing the problem. Either that will fix it, or something really small/obvious is being missed here, which can be very very difficult for other people to figure out from the other side of the world (not there watching you/etc, etc).
If you can't get a successful flash, go through the troubleshooting stuff in Hopper's thread until you do.
MistahBungle said:
As it's a 3 part firmware, the separate CSC wipes the phone. And as I said, hopefully this gets rid of whatever is causing the problem. Either that will fix it, or something really small/obvious is being missed here, which can be very very difficult for other people to figure out from the other side of the world (not there watching you/etc, etc).
If you can't get a successful flash, go through the troubleshooting stuff in Hopper's thread until you do.
Click to expand...
Click to collapse
OK... The good news is the S2 is now usable (currently using), and a big thanks for you to that!
But the bad news is Recovery Mode is still unaccessible. When I do the Volume UP + Power, it just reboots.
Is it related to Bootloader? Or something?
souler456 said:
OK... The good news is the S2 is now usable (currently using), and a big thanks for you to that!
But the bad news is Recovery Mode is still unaccessible. When I do the Volume UP + Power, it just reboots.
Is it related to Bootloader? Or something?
Click to expand...
Click to collapse
Use some other third party applications for booting into recovery move
( just to make sure your keys are faulty or not)
Sent from my Nexus 5 using Tapatalk 2
Vivek_Neel said:
Use some other third party applications for booting into recovery move
( just to make sure your keys are faulty or not)
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Volume Keys are working fine. I can volume up and down the sounds and some media stuff. It's just that there's some kind of a problem "blocking" me to access Recovery Mode. It always ends to the Boot Logo then Reboot when I do the Volume UP + Power combo.
As of now, I cannot do the "Other Third Party Applications" thing, cause it's not rooted (Stock Firmware XXLSJ freshly squeezed by Odin). And I can't root it cause I can't access the Recovery Mode, so... Yeah...
I was thinking of getting a Philz Kernel (Odin Flashable) for the ROM, but it will trigger the accursed "Yellow Triangle", which I'm trying my best to avoid. So, any root procedure that doesn't require me to access Recovery Mode is pretty much a helpful info for me as of now... Do you know such a thing like that?
souler456 said:
Volume Keys are working fine. I can volume up and down the sounds and some media stuff. It's just that there's some kind of a problem "blocking" me to access Recovery Mode. It always ends to the Boot Logo then Reboot when I do the Volume UP + Power combo.
As of now, I cannot do the "Other Third Party Applications" thing, cause it's not rooted (Stock Firmware XXLSJ freshly squeezed by Odin). And I can't root it cause I can't access the Recovery Mode, so... Yeah...
I was thinking of getting a Philz Kernel (Odin Flashable) for the ROM, but it will trigger the accursed "Yellow Triangle", which I'm trying my best to avoid. So, any root procedure that doesn't require me to access Recovery Mode is pretty much a helpful info for me as of now... Do you know such a thing like that?
Click to expand...
Click to collapse
You can flash tar version of philz via Odin.
Read philz thread.
Sent from my Nexus 5 using Tapatalk 2
Related
I know this question was asked, but however the solution's do not work for me. I have google search, XDA searched, and tried things on my own to figure this out and to fix it...but can not. I re-flashed (using Odin) to STOCK ICS - Worked like a charm. Until, one time, I did this again - And Odin shows that it was successful, and I get the Stock boot up screen (Rethink Possible) and it just stays there. I have tried to rethink possible but cant get a solution. I have read somewhere that putting the phone into recovery to do a wipe/data clear - Would solve this issue - but problem is, I cant get into recovery. And yes, I have had the phone completely off, held Volume Down + Power ... I even tried both Volumes + Power = NOTHING. I dont think I ever tried doing this way back when, before I even rooted...but I know for a fact, after I rooted, I was never able to get into CWM by doing the button combos...I always had to reboot into recovery.
Things I have done, was re root with ODIN. Flash back to complete bone stock. I tried flashing Kernels with Odin etc etc, and never did Odin say it failed...but I can not get my phone to pass the Rethink Possible Screen...the closest I got - was a looping boot up screen. But now, its just frozen there, and never moves forward. Any ideas?
My idea is post http://forum.xda-developers.com/forumdisplay.php?f=1372 next time. This isn't development. Also the EMMC "superbrick" bug is confirmed to affect the UCLE5 STOCK KERNEL. So I hope that you didn't flash stock UCLE5 with the stock kernel. Read more info here http://forum.xda-developers.com/showthread.php?t=1746181. Hopefully you didn't use the odin file from there and if you did and flashed anyways without changing the kernel and wiped data/factory reset you more than likely got the emmc "superbrick" bug.
I had the same exact problem when I flashed back to stock ICS and on first boot got stuck at rethink possible screen. The trick is to go into stock Recovery and wipe data. I hope this works for you.
Sent from my SGH-I777 using xda app-developers app
Reported.
Thanks for playing "That's not dev!"
Raise yer mizzenmast and swab 'er poop deck!
These dev projects get better and better
Sent from Team Pirate's Transmitter Thingy
mpkothari said:
I had the same exact problem when I flashed back to stock ICS and on first boot got stuck at rethink possible screen. The trick is to go into stock Recovery and wipe data. I hope this works for you.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Lets try and help someone brick a phone if they already haven't. Great Idea.
To the others, yes it is posted in the wrong forum and needs to be moved. That doesn't mean you have to report useless posts to a misplaced thread and continue to fill it with uselessness.
mpkothari said:
I had the same exact problem when I flashed back to stock ICS and on first boot got stuck at rethink possible screen. The trick is to go into stock Recovery and wipe data. I hope this works for you.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Not to sound rude, because I am not, But I get yelled to "Read" and I guess...that if I get told to, others should too.
I can not get into stock recovery. I put that in my OP
JimiGEE said:
I know for a fact, after I rooted, I was never able to get into CWM by doing the button combos...I always had to reboot into recovery.
Click to expand...
Click to collapse
This sounds like whatever you used to root the phone also installed a secondary bootloader for a different device.
You need to provide more detailed information so we can troubleshoot, or...
enter download mode and flash the stock Gingerbread UCKH7 full distribution from the Download Repository that includes bootloaders and param.lfs. Then use the three button method to enter 3e recovery and perform a wipe data/factory reset. Then you can root, flash a custom kernel, and install whatever firmware you want.
creepyncrawly said:
This sounds like whatever you used to root the phone also installed a secondary bootloader for a different device.
You need to provide more detailed information so we can troubleshoot, or...
enter download mode and flash the stock Gingerbread UCKH7 full distribution from the Download Repository that includes bootloaders and param.lfs. Then use the three button method to enter 3e recovery and perform a wipe data/factory reset. Then you can root, flash a custom kernel, and install whatever firmware you want.
Click to expand...
Click to collapse
You sir, are Jesus. I have been to the links in your signature before, and you helped me out (without knowing you did) and this time, you came through again! I flashed a few things with Odin with no avail, and no recovery still. But I have this little problem with taking "no" or "not going to work" as my answer...So i kept pulling the battery, doing three button combo...FINALLY got into recovery...and I seriously could not be happier right now! I am back to complete bone stock Gingerbread - Thank you
creepyncrawly said:
This sounds like whatever you used to root the phone also installed a secondary bootloader for a different device.
You need to provide more detailed information so we can troubleshoot, or...
enter download mode and flash the stock Gingerbread UCKH7 full distribution from the Download Repository that includes bootloaders and param.lfs. Then use the three button method to enter 3e recovery and perform a wipe data/factory reset. Then you can root, flash a custom kernel, and install whatever firmware you want.
Click to expand...
Click to collapse
JimiGEE said:
You sir, are Jesus. I have been to the links in your signature before, and you helped me out (without knowing you did) and this time, you came through again! I flashed a few things with Odin with no avail, and no recovery still. But I have this little problem with taking "no" or "not going to work" as my answer...So i kept pulling the battery, doing three button combo...FINALLY got into recovery...and I seriously could not be happier right now! I am back to complete bone stock Gingerbread - Thank you
Click to expand...
Click to collapse
Was hoping I was in the clear...I can get into CWM using button combo, but however, selecting an option doesnt work. It just removes all text, until I push the power button to replace the text. It weird. So if I were to go to reboot system....and use power button to select, everything disappears besides the CWM logo in the background...So i can not flash any roms, etc via CWM - any idea?
JimiGEE said:
Was hoping I was in the clear...I can get into CWM using button combo, but however, selecting an option doesnt work. It just removes all text, until I push the power button to replace the text. It weird. So if I were to go to reboot system....and use power button to select, everything disappears besides the CWM logo in the background...So i can not flash any roms, etc via CWM - any idea?
Click to expand...
Click to collapse
Ignore me, I need to use the home key!
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
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
Not paying attention while updating supersu has led to my s2(i777) not being usable. Updated binary selecting wrong option and and phone would not boot past the splash screen. At this point I used creepyncrawly's I777UCKH7-CL5038881-No-Bl.exe to return to factory settings. Was able to do this using battery pulls to turn off and on and enter download mode. Appeared all was going to work but now phone will not boot past initial setup screen. Can get into recovery but unable to enter selection as power button not working at this point even though I use it to get into factory recovery. About to flash stock sbl.tar (downloaded from repository) using Odin but decided I should probably get some feedback first.Phone was running Semi_v18 and Siyah 3.3.3d and working well B/4 I messed things up.
I have no idea what gets changed or corrupted when you have a problem updating supersu. Maybe you could go to chainfire's supersu thread and see if you can get an idea what it might be.
Your thinking may be right though, because the sbl seems to be the place that controls power and volume button actions.
creepyncrawly said:
I have no idea what gets changed or corrupted when you have a problem updating supersu. Maybe you could go to chainfire's supersu thread and see if you can get an idea what it might be.
Your thinking may be right though, because the sbl seems to be the place that controls power and volume button actions.
Click to expand...
Click to collapse
Thanks Creepy, been to the other thread nothing helpful from reading responses to others posting wih the same problem. I'm just going to flash sbl.tar with Odin unless you think it may just cause a bigger problem.
It should be no problem to flash it as long as the flash doesn't get interrupted. If the sbl is not damaged, it won't do any harm to re-flash it.
creepyncrawly said:
It should be no problem to flash it as long as the flash doesn't get interrupted. If the sbl is not damaged, it won't do any harm to re-flash it.
Click to expand...
Click to collapse
Thanks, flash went fine but no go on getting power button to work in recovery. Not sure what to try next but maybe flashing rom and kernel from odin. Any way thanks again.
GJMX said:
Thanks, flash went fine but no go on getting power button to work in recovery. Not sure what to try next but maybe flashing rom and kernel from odin. Any way thanks again.
Click to expand...
Click to collapse
Just wanted to let you know what happened with S2. Took a long shot and called at&t cs.
After 2 calls to at&t and 2 to Samsung tech support I got lucky on the third cal to at&t and the rep set up a
free appointment at a nearby device support center. Guy there said all he could do was to wipe the phone and
install ICS 4.0.4. Phone works now but seems the power button stopped working at the same time I messed up the update.
Need a new power button, rom and a kernel with cwmr and I will be set.
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: