I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
gadgetcraze said:
I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
Click to expand...
Click to collapse
You did do a full wipe after flashing the new roms right?
wangdaning said:
You did do a full wipe after flashing the new roms right?
Click to expand...
Click to collapse
In stock recovery yes (data and cache). From cwm (data cache and dalvik) also. Let me try that again
what file did you flash?
does the recovery show any errors?
gadgetcraze said:
I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
Click to expand...
Click to collapse
Once you flash a stock ROM, factory reset the phone from stock recovery. That'll solve the issue of reboot loop. :good:
Be warned, you'll lose all data in the internal SD card.
Glebun said:
what file did you flash?
does the recovery show any errors?
Click to expand...
Click to collapse
Stock Firmware for my country downloaded from sammobile.
When the phone boots into Recovery, there is a dead green bot and an exclamation mark.
It says
manual mode
Appling Multi-CSC
Applied the CSC code BTU
Successfully applied multi CSC
Oomahey said:
Once you flash a stock ROM, factory reset the phone from stock recovery. That'll solve the issue of reboot loop. :good:
Be warned, you'll lose all data in the internal SD card.
Click to expand...
Click to collapse
Did not work
are you sure the file you flashed is for your model?
Glebun said:
are you sure the file you flashed is for your model?
Click to expand...
Click to collapse
I am. It was not the latest one though. I will download the latest one and give it another shot. Maybe. But if this was a firmware problem, the phone would get stuck at the samsung logo. Would'nt it? Instead the samsung logo never comes on and I just see that battery sign.
And as I mentioned, I had this problem where the phone would not switch off even if I select power off. Even after a battery pull it would boot up on its own. Even now, as I put in the battery, it starts showing the battery symbol with a circle in it. I suspect the two problems may be interconnected and may be related to a hardware failure.
I had a working phone before. Just to fix the power off thing, I might have bricked my phone.
gadgetcraze said:
I am. It was not the latest one though. I will download the latest one and give it another shot. Maybe. But if this was a firmware problem, the phone would get stuck at the samsung logo. Would'nt it? Instead the samsung logo never comes on and I just see that battery sign.
And as I mentioned, I had this problem where the phone would not switch off even if I select power off. Even after a battery pull it would boot up on its own. Even now, as I put in the battery, it starts showing the battery symbol with a circle in it. I suspect the two problems may be interconnected and may be related to a hardware failure.
I had a working phone before. Just to fix the power off thing, I might have bricked my phone.
Click to expand...
Click to collapse
Have you got a backup of your efs, if not pull it from your device while you can. Use ADB from recovery to do it.
Something else on you device is causing the power button issue. Could be some mod, or just some corruption. Are you getting other signs when booting?
Last resort, use Kies. Follow the guide posted on here. Don't plug in your device, select emegency (firmware) recovery, give the info (serial number) and plug in when prompted. Back up your efs first if you can. ADB pull the efs is /dev/block/mmcblk0p3.
wangdaning said:
Have you got a backup of your efs, if not pull it from your device while you can. Use ADB from recovery to do it.
Something else on you device is causing the power button issue. Could be some mod, or just some corruption. Are you getting other signs when booting?
Last resort, use Kies. Follow the guide posted on here. Don't plug in your device, select emegency (firmware) recovery, give the info (serial number) and plug in when prompted. Back up your efs first if you can. ADB pull the efs is /dev/block/mmcblk0p3.
Click to expand...
Click to collapse
I did backup my efs folder when I rooted my phone first. Hope that suffices. Can you point me to the guide for emergency recovery? I could locate this. http://forum.xda-developers.com/showthread.php?t=1984717
That guide would be correct, but make sure you use your model number. For international, I believe it is GT-I9300, and has to be written that way.
wangdaning said:
That guide would be correct, but make sure you use your model number. For international, I believe it is GT-I9300, and has to be written that way.
Click to expand...
Click to collapse
Worked partially. Now wont reboot. At least I was able to set the counters to 0 before it went dead again. Thanks for the help.
After working for a while, on resetting the phone, it went completely dead. I took the phone to the service center and it turned out to a case of defective mini usb jack. Maybe the reasons it was booting up in between on change of softwares was just a matter of chance.
Thanks for the help.
Related
So today I was running my Galaxy 2 like any other regular phone. I had pulled it out of my pocket and was listening to some music whilst playing some game that I recently downloaded from the Android Market. Before I started playing it I recall my battery was at 18%.
Then all of a sudden.
My screen turned off.
I thought hmm. Maybe it just turned off. Attempted to turn it back on. Nothing.
I started to worry.
So I tried to boot my device in download mode or recovery mode.
Nothing
Even more worringly I attempted to charge my phone to see if the charging thing would pop up.
Nothing at all.
So I'm wondering if my GalaxyS2 has died?
At the time I was running CM7.1 Nightly 81 with Siyahs 2.0 beta 6.
any chance of claiming it on warranty as they can't check the actual phone for flashes, or a possible solution?
Hey, sounds ugly.
Did you leave the phone plugged in for some time? because I think the phone needs some juice, when it was down to zero battery, before it will show anything on the screen.
For your warranty, You know I would first try everything to get it back by yourself and if nothing is going to work then I would guess the sammy guys can't do much either. So if you send it back then and you get a new one be happy, if not yeah you know hope that it will not cost too much. Good luck dude.
Try to pull out the battery and put it back in and plug in the charger and let it be for som time.
Well **** me sideways....
On the way back home from the vendor to get the charger my phone turned on.
Like... What the actual hell???
Its currently charging in my USB.
I just tried flashing an old backup I had and that didn't work for some strange reason.
I'm going to try and flash a stock rom from the USB and see what happens. Not willing to turn it off though.
giga502 said:
Well **** me sideways....
On the way back home from the vendor to get the charger my phone turned on.
Like... What the actual hell???
Its currently charging in my USB.
I just tried flashing an old backup I had and that didn't work for some strange reason.
I'm going to try and flash a stock rom from the USB and see what happens. Not willing to turn it off though.
Click to expand...
Click to collapse
Ah great news....is it still on ?
But I would recommend using stock for a while to see if this problem comes up again.
But as you are using a CM nightly that might be the reason for the problem.
brunobanane said:
Ah great news....is it still on ?
But I would recommend using stock for a while to see if this problem comes up again.
But as you are using a CM nightly that might be the reason for the problem.
Click to expand...
Click to collapse
Well. I'm trying to flash a stock rom.
But whenever I go to the recovery menu some error pops up
can't access to system csc kor system
and it gives me a very limited recovery menu...
hmmm
giga502 said:
Well. I'm trying to flash a stock rom.
But whenever I go to the recovery menu some error pops up
What has the recovery menu got to do with flashing a stock rom ???
can't access to system csc kor system
Why
and it gives me a very limited recovery menu...
Its a non CWM recovery then probably 3e Samsung Recovery .
CWM or recovery is not used to flash stock rom .
jje
Click to expand...
Click to collapse
JJEgan said:
giga502 said:
Well. I'm trying to flash a stock rom.
But whenever I go to the recovery menu some error pops up
What has the recovery menu got to do with flashing a stock rom ???
can't access to system csc kor system
Why
and it gives me a very limited recovery menu...
Its a non CWM recovery then probably 3e Samsung Recovery .
CWM or recovery is not used to flash stock rom .
jje
Click to expand...
Click to collapse
ahh yes that is the one. Thankyou!
I'm now using Odin to flash litnin rom 6.1
if I can get into download mode....
Click to expand...
Click to collapse
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 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:
I'm having real issues trying to get a stock ROM on my Virgin Mobile S3 (GT-I9300) and I'm hoping you guys can help me. I've looked absolutely everywhere for a solution but so far nothing has worked.
OK so a little history about the problem:
Using phone as normal, and then randomly turns off. Turn it back on and I get the two Samsung splash screens loop booting constantly. I boot into recovery mode and do a factory reset - same problem. Clear the cache - same problem. Send phone back to Virgin and they tell me I've rooted and installed a custom ROM which I absolutely have not but they have a screenshot with the custom counter showing '1'.
I've no idea how this is possible, but I would have remembered if I'd installed a custom ROM. Anyway, they send it back because I'm not going to fork out £100 for them to flash it.
So...lots of research later, I download the latest Odin (3.09), find the most likely stock ROM that will work with my phone (Carrier is Virgin Mobile UK). I find this ROM on SamMobile: I9300XXUGMK6_I9300OXAGMK6_BTU. Cannot for the life of me find an actual Virgin rom so this apparently should be fine as it's a generic EU build.
Fine, so I apply it using the AP selection in Odin, connect phone, it goes through and applies fine "PASS" etc.. and phone reboots automatically.
Now, it just sits at the Samsung splash screen (the static white text) and doesn't go any further. I've left it upwards of 10 minutes but no dice. So look online and find threads that suggest booting to recovery and doing a factory reset will do the trick. So try that (Power+volume up+home) and same problem - static splash screen. Balls.
So now I don't know what to do. I either need to try an actual Virgin ROM which doesn't seem to exist(?!) or my phone is truely bricked and I'll finally have a good reason to destroy the thing.
Can anyone let me know what the next steps should be? I would be eternally grateful.
Thanks in advance.
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
shivadow said:
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
When you say 'wipe' do you mean factory reset via recovery mode? Because I'm not able to access that. All I can get to is Download Manager to use with Odin...
I thought you said you could access recovery and you had cleared cache. In that case you are buggered. If it goes through the flashing phase and reboots but you still cannot get into recovery then you have 3 options..
1. Flash another rom but no lower than 4.3. Carrier shouldn't matter.
2. Full on flash with pit file (dangerous and can perma brick).
3. Return the phone under warranty and state that the flash counter also clocks official flashes too, samsung should know this as they make the phone.. staff need training if they say otherwise.
Sent from my GT-I9300 using Tapatalk
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
It sounds like nand failure, so it's possible that you won't be able to fix it.
Sent from my GT-I9300 using Tapatalk
I thought you said you could access recovery and you had cleared cache.
Click to expand...
Click to collapse
Apologies for not being clearer, before sending it back to Virgin for the warranty repair I could access the recovery mode fine, when I got it back I couldn't - whether that was caused by the flashing of the firmware or something Virgin did I don't know unfortunately.
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
Click to expand...
Click to collapse
Thanks for the tip - I've flashed the stock recovery and I can now get into recovery mode! Looks slightly different but I can now access the factory reset/wipe cache options so that's some improvement.
I'm just downloading the stock international ROM as per this thread http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847 but it's going to take a few hours. Thanks so much for your advice so far i'll report back once the download completes.
No joy
I can however get into download mode and recovery mode now. Is there anything else I can try? Is it possible I can get a custom recovery image on there and flash it with something other than the stock rom?
I've got a feeling you're correct and it could be a hardware fault. Virgin say I can pay £100 to get it fixed, if they have to replace the entire phone that would prove it wasn't 'tampering' that caused it so I could potentially get my money back I guess, if I complained. I think that might be my only option now.
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
crispin85 said:
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
Click to expand...
Click to collapse
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
ag4751 said:
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
Click to expand...
Click to collapse
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
crispin85 said:
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
Click to expand...
Click to collapse
Make sure you are using the USB cable supplied with the phone and it is connected direct to your PC USB port, ideally the ones on the back but don't connect through any multi USB port connectors.
The USB cables and how you connect can make a difference
Hi all,
I was driving home using gps and clicked on a message as it popped up, the phone itself went black and the Samsung logo appeared.
Now I tried the obvious holding the power button but nothing happened, then tried holding volume down and power which replicates a battery pull, which reset the phone but it was still frozen at the Samsung logo.
Upon getting home I tried going into recovery mode multiple times by resetting the phone then holding down, power, vol+ and home but however, I tried I couldn't get it to boot into recovery.
I was able to get it into Odin mode, downloaded the latest firmware 7.0 for SM-G920I xsa Australia which was installed previously before bricking itself.
The phone was never rooted or played with in anyway til this point.
Anyway, Odin successfully flashed the firmware without hassle but the phone still froze at the Samsung's logo and I am still unable to go into recovery.
I tried using a phone doctor to fix it using a fix for a similar SM-G920F which brought up red writing and was possibly the point in which Knox warranty void: 1 (0x0500) I can't be sure as I never really took in what was displayed before.
I reflashed back the 7.0 which got rid of the red writing error and tried using smart switch emergency recovery which successfully downloaded and installed the correct firmware but I was still stuck at the Samsung logo after a restart.
I was onto Samsung and apparently, my phone is from Singapore originally so I downloaded the stock rom for Singapore but Odin wouldn't flash it.
I have installed all drivers but the phone only connects to the PC during Odin mode, adb/fast boot can't see the device.
I've tried TWRP recovery but I still cant boot into recovery mode to wipe cache or anything so any Idea I explore seems to hit a dead end.
Usually, I get things working again but this one is really puzzling me I've already ordered a new phone.
It's a 128gb version less than 2 years old, seems such a waste.
Anyway, does anyone have any ideas?
Thanks in advance
Aubra said:
Hi all,
I was driving home using gps and clicked on a message as it popped up, the phone itself went black and the Samsung logo appeared.
Now I tried the obvious holding the power button but nothing happened, then tried holding volume down and power which replicates a battery pull, which reset the phone but it was still frozen at the Samsung logo.
Upon getting home I tried going into recovery mode multiple times by resetting the phone then holding down, power, vol+ and home but however, I tried I couldn't get it to boot into recovery.
I was able to get it into Odin mode, downloaded the latest firmware 7.0 for SM-G920I xsa Australia which was installed previously before bricking itself.
The phone was never rooted or played with in anyway til this point.
Anyway, Odin successfully flashed the firmware without hassle but the phone still froze at the Samsung's logo and I am still unable to go into recovery.
I tried using a phone doctor to fix it using a fix for a similar SM-G920F which brought up red writing and was possibly the point in which Knox warranty void: 1 (0x0500) I can't be sure as I never really took in what was displayed before.
I reflashed back the 7.0 which got rid of the red writing error and tried using smart switch emergency recovery which successfully downloaded and installed the correct firmware but I was still stuck at the Samsung logo after a restart.
I was onto Samsung and apparently, my phone is from Singapore originally so I downloaded the stock rom for Singapore but Odin wouldn't flash it.
I have installed all drivers but the phone only connects to the PC during Odin mode, adb/fast boot can't see the device.
I've tried TWRP recovery but I still cant boot into recovery mode to wipe cache or anything so any Idea I explore seems to hit a dead end.
Usually, I get things working again but this one is really puzzling me I've already ordered a new phone.
It's a 128gb version less than 2 years old, seems such a waste.
Anyway, does anyone have any ideas?
Thanks in advance
Click to expand...
Click to collapse
I don't have this device, but with most Samsung devices recovery is hold vol+, home, and power. Once the splash screen appears let off of power but keep the other two buttons pressed.
Sent from my XT1609 using Tapatalk
I remember having this exact same problem about a year ago.. Now I'm not sure if this'll work for you since I was on MM at the time, but try downloading arters version of twrp, (my S6 would never boot to recovery with the official twrp) flashing via Odin and try booting into recovery. Flash a custom rom or restore a backup of you have one. Then from there you can try restoring to stock rom.
Link to arters twrp http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
RealWelder said:
I don't have this device, but with most Samsung devices recovery is hold vol+, home, and power. Once the splash screen appears let off of power but keep the other two buttons pressed.
Sent from my XT1609 using Tapatalk
Click to expand...
Click to collapse
Yea tried that, thanks for the different combination..
Kiid said:
I remember having this exact same problem about a year ago.. Now I'm not sure if this'll work for you since I was on MM at the time, but try downloading arters version of twrp, (my S6 would never boot to recovery with the official twrp) flashing via Odin and try booting into recovery. Flash a custom rom or restore a backup of you have one. Then from there you can try restoring to stock rom.
Link to arters twrp
Yea doesn't seem to work on nougat all I get is "Recovery Is not Seandroid Enforcing" in red. I was able to flash back to 7.0 to remove the warning.
Click to expand...
Click to collapse
Aubra said:
Kiid said:
I remember having this exact same problem about a year ago.. Now I'm not sure if this'll work for you since I was on MM at the time, but try downloading arters version of twrp, (my S6 would never boot to recovery with the official twrp) flashing via Odin and try booting into recovery. Flash a custom rom or restore a backup of you have one. Then from there you can try restoring to stock rom.
Link to arters twrp
Yea doesn't seem to work on nougat all I get is "Recovery Is not Seandroid Enforcing" in red. I was able to flash back to 7.0 to remove the warning.
Click to expand...
Click to collapse
I'm not 100 percent sure since it was a long time ago but I believe the red warning didn't impact the recovery and I think it was just to let you know that recovery wasn't stock. And on first boot to twrp it could take about 5 minutes, right after flashing I mean. Good luck any ways mate. Cheers
Click to expand...
Click to collapse
Kiid said:
I remember having this exact same problem about a year ago.. Now I'm not sure if this'll work for you since I was on MM at the time, but try downloading arters version of twrp, (my S6 would never boot to recovery with the official twrp) flashing via Odin and try booting into recovery. Flash a custom rom or restore a backup of you have one. Then from there you can try restoring to stock rom.
Link to arters twrp http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Click to expand...
Click to collapse
Kiid said:
Aubra said:
I'm not 100 percent sure since it was a long time ago but I believe the red warning didn't impact the recovery and I think it was just to let you know that recovery wasn't stock. And on first boot to twrp it could take about 5 minutes, right after flashing I mean. Good luck any ways mate. Cheers
Click to expand...
Click to collapse
It still just hangs at the Samsung logo.. Do you mean I should hold the 3 buttons for 5 minutes?
Click to expand...
Click to collapse
Possibly your emmc went bad... happens from time to time.
Sent from my XT1609 using Tapatalk
RealWelder said:
Possibly your emmc went bad... happens from time to time.
Sent from my XT1609 using Tapatalk
Click to expand...
Click to collapse
Dropped it down to the local phone fix shop, they couldn't fix the software problem either so they're going to try replacing the battery.
Aubra said:
Dropped it down to the local phone fix shop, they couldn't fix the software problem either so they're going to try replacing the battery.
Click to expand...
Click to collapse
Seems like its a hardware issue, if I replace the whole motherboard off eBay with the same model g920I unlocked will that do the trick or will I have to start flashing networks, bootloaders, pit files and whatever else it needs to get moving?
It is possible to flash ONLY a recovery using ODIN by making your own custom tar.md5. If you leave the pit files and userdata images alone, it shouldn't overwrite your personal data. You could reinstall the entire OS, boot sections, and even stock recovery.
Note: Do your own fair share of diligence, I am not responsible for any mishaps.