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.
Related
Hi,
I think i have forgot to turn on debbuging mode while flashing stock firmware and now i stuck at bootscreen.I have also turned off F. Reset Time in odin.Any help how i can make my phone alive or is it bricked?Btw i can get into system recovery and download mode
Flash any on click file with odin in download mode
manojcitc said:
Flash any on click file with odin in download mode
Click to expand...
Click to collapse
Hmm.. I I tried but no luck I stuck at boot logo
Sent from my GT-I9300 using xda premium
Should I flash cf root kernel and go into recovery and flash Rom, or send it to Samsung because there is no triangle?
Sent from my GT-I9300 using xda premium
Should I flash cf root kernel and go into recovery and flash Rom, or send it to Samsung because there is no triangle? <br />
<br />
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
If there is no yellow triangle, and your custom binary counter is zero, then just send it to Samsung.
Good luck
Swyped from Samsung Galaxy SII
Try that and after vo into recobery and wipe data,clear cache and flash new rom...
I had faced this problem in for so many times,i always use one click cm9 rom and flash with odin,and make sure that you dont touch any option in odin...
manojcitc said:
Try that and after vo into recobery and wipe data,clear cache and flash new rom...
I had faced this problem in for so many times,i always use one click cm9 rom and flash with odin,and make sure that you dont touch any option in odin...
Click to expand...
Click to collapse
I also had bootloop long time ago, but that was because I didn't made I factory reset. When I need to flash kernel via odin, I need debbuging on. I think I have to send it to Samsung. I am also such a dimbass to forgot to turn debbuging on:sly:
Sent from my GT-I9300 using xda premium
Can I turn on debugging while I can't access my phone. If yes, how?
Sent from my GT-I9300 using xda premium
Problem solved by factory reset in system recovery
Sent from my GT-I9300 using xda premium
I had a boot loop on my galaxy s 2 .. out of nowhere didnt do anything.
It was too weird. I spent time reading lots of forums about this and saw different techniques.
What i did was i flashed back to 2.3.6. Did factory reset. then flashed back to ICS.
I think it happened because of some cache bull****. Just thought i should share.
Boot Loop Solved
I don't know where to post this so I'm posting it here. I have been scouring the internet for HOURS trying to figure how others got out of boot loop so I could get my phone out of it. I have a samsung galaxy s2 i9100g. I was in the process of unrooting it and while rebooting after installing the stock rom BOOM- boot loop to the samsung logo. I tried everything; battery out, in, pushing all combinations of volume(s)+home+power= nothing worked. Finally after a lot of trial and error one thing worked. I unplugged my USB and took the battery out, then while holding the three buttons I put it back in- and suddenly after hours(of trying to get something to happen) I got the download screen. (My phone wouldn't turn off or go into recovery as other suggested). So I downloaded a different stock rom and tried reinstalling via odin a few times but the problem persisted- still boot loop, still only download mode. Then I tried something different. When in download mode I decided to see what would happen if I pushed the volume down to 'reboot'. To my amazement my phone started up and went past the samsung logo for the first time in FOUR HOURS. It went into recovery mode! Then I factory reset it, and restarted it. So keep at if you think your phone is soft bricked or boot looped. I appreciate everyone else's questions/answers that kept me going while trying to figure out something that worked for me. So I'll break it down into steps.
1)unplug USB, take out battery. Hold down volume (holding down the 'down' volume worked for me), home and power button then quickly slide the battery in(while still holding down till the screen comes up). It may take a few times but the 'download mode' screen should come right up.
2)using odin install the stock ROM for your phone
3)when re installation is complete follow step 1 to get into download mode
4)instead of clicking the volume up for download, click down to restart and recovery mode should come up
5)factory reset your phone and reboot
I genuinely hope this helps someone. Nothing worse than rendering your phone useless.
tried it
I'm having the same issue but your trick didn't help. i'm exasperated.
SirenumDev said:
I'm having the same issue but your trick didn't help. i'm exasperated.
Click to expand...
Click to collapse
Same issue how to fix this?
SirenumDev said:
tried it
I'm having the same issue but your trick didn't help. i'm exasperated.
Click to expand...
Click to collapse
yes, same here...my phone is back to the initial screen 'samsung galaxy sII' , with sign at bottom
Me too...
I think we need to flash stock rom as pointed in those guides:
[INDEX] Samsung Galaxy S2 - ROMs, Kernels, MODs, GUIDES
Samsung Galaxy S2 [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need for your device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you"...
forum.xda-developers.com
The problem is I don't find a ODIN that works... links seem to be broken.
I have even risked to download a couple (4) different odin versions and some windows drivers / stock roms from the wild internet (who knows what crap those executables and files may come with), but I had no success with it...
I don't know how we can find trustable files that are required, or at least verify checksums somewhere to be sure that we don't get any unrequested present instead....
Will create or post in there asking for some help I think...
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.
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,
My S2 was working perfectly and I put it on charge. About 15mins later I walked past and noticed it was displaying just the very first screen ie the one you see as soon as it starts and says Galaxy S2. Tried all the usual things like removing battery etc. I thought I might have a corrupted ROM so I have re-flashed it with Odin and whilst that was successful it is still at the same screen. I flashed it with the Australian XSA ROM. I can get it into flash mode but nothing else.
Anyone have any further thoughts?
JohnYW
JohnYW said:
Hi,
My S2 was working perfectly and I put it on charge. About 15mins later I walked past and noticed it was displaying just the very first screen ie the one you see as soon as it starts and says Galaxy S2. Tried all the usual things like removing battery etc. I thought I might have a corrupted ROM so I have re-flashed it with Odin and whilst that was successful it is still at the same screen. I flashed it with the Australian XSA ROM. I can get it into flash mode but nothing else.
Anyone have any further thoughts?
JohnYW
Click to expand...
Click to collapse
Try going to stock recovery and doing a factory reset
noppy22 said:
Try going to stock recovery and doing a factory reset
Click to expand...
Click to collapse
OK thanks for the quick reply. Tried to get there but what happens is the android appears with his whirling blue bit....then it goes to black and the samsung galaxy s 2 screen again appears and thats where it stays. The only mode it will go into is the flash rom mode. In other words vol up plus power and home buttons does the above whereas vol down plus home and power gets me successfully to the rom flash screen.
John
JohnYW said:
OK thanks for the quick reply. Tried to get there but what happens is the android appears with his whirling blue bit....then it goes to black and the samsung galaxy s 2 screen again appears and thats where it stays. The only mode it will go into is the flash rom mode. In other words vol up plus power and home buttons does the above whereas vol down plus home and power gets me successfully to the rom flash screen.
John
Click to expand...
Click to collapse
The only other thing I can think of is to flash a .tar recovery from download mode(vol down+home+power).
Try the modified kernel from philz HERE You will need to match the kernel to the rom version, read carefully particularly the 2nd and 3rd posts
Just untick reboot on finish in odin and once you succesfully flash the kernel try to enter recovery from power off. Good luck
Another question
noppy22 said:
The only other thing I can think of is to flash a .tar recovery from download mode(vol down+home+power).
Try the modified kernel from philz HERE You will need to match the kernel to the rom version, read carefully particularly the 2nd and 3rd posts
Just untick reboot on finish in odin and once you succesfully flash the kernel try to enter recovery from power off. Good luck
Click to expand...
Click to collapse
Just getting back to it ....Thanks for that and all makes sense ...but maybe its a dumb question but how do I determine what Kernel I need ...I can't boot the phone up to get any of that information....the only thing I see on the inside cover is the Model - GT-I9100 and an SSN (whatever that is) of -I9100GSMH. Any other clues?
John
JohnYW said:
Just getting back to it ....Thanks for that and all makes sense ...but maybe its a dumb question but how do I determine what Kernel I need ...I can't boot the phone up to get any of that information....the only thing I see on the inside cover is the Model - GT-I9100 and an SSN (whatever that is) of -I9100GSMH. Any other clues?
John
Click to expand...
Click to collapse
Do you still have the stock rom file that you used with odin? If not you might be able to identify the rom from the website you got it from.
noppy22 said:
Do you still have the stock rom file that you used with odin? If not you might be able to identify the rom from the website you got it from.
Click to expand...
Click to collapse
Yes ...I do but again, when I repalced the ROM I didnt know which of the files to try (SamMobile)...the phone originally had an Optus ROM on it before all this happened soI couldnt readily identify which of the 4 files I found were correct to use so in the end I thought I would load the XSA file ...which had the latest date.... hoping that would work....so thats what I went with.... it was I9100XWLSH ...ahh now the penny has dropped... I need the XWLSH Kernel dont I ...butwhat does fixed for bootloop mean? Sorry if these are dumb questions but thanks for your patience
John
JohnYW said:
Yes ...I do but again, when I repalced the ROM I didnt know which of the files to try (SamMobile)...the phone originally had an Optus ROM on it before all this happened soI couldnt readily identify which of the 4 files I found were correct to use so in the end I thought I would load the XSA file ...which had the latest date.... hoping that would work....so thats what I went with.... it was I9100XWLSH ...ahh now the penny has dropped... I need the XWLSH Kernel dont I ...butwhat does fixed for bootloop mean? Sorry if these are dumb questions but thanks for your patience
John
Click to expand...
Click to collapse
Yes, thats the kernel you need. Just get the .tar version of the kernel and flash in download mode(vol down, home, power). I'm hoping you can get a working recovery to give you a few more options. It may not work, as I suspect you have filesystem corruptions or something, but try that anyway
OK ...will try that in a few days ...again, thanks for the help
John
im using cm12 archidroid 3.5.14 and decided to update to 3.5.15 version last night. but the update didnt went well, something went wrong and i got 'recursive' error, and it started to boot loops.
i tried so many solutions, i odin this and that and nothing worked. i downloaded cwm 6.0.0.47 i think, and managed to install the AD rom, but now im stuck at languange selection, i cant select anything because screen support isnt working
what do i do now?
Samsung S3 i9300
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Hawaiihemd said:
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Click to expand...
Click to collapse
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
I would try to flash latest AD again but with a proper up-to-date recovery
Click to expand...
Click to collapse
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
ricvai7 said:
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
Click to expand...
Click to collapse
Well then, if you already flashed stock rom via odin, your data is already gone. Make sure your phone is working on stock first now. Please be aware that the first boot after each rom flash might take up to 15 min or so because the cache has to be built at first boot!
You can find the link to TWRP recovery in my signature (see My Gadgets). I suggest your read the tutorials that are linked there also for more information.
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
ricvai7 said:
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
Click to expand...
Click to collapse
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
ricvai7 said:
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
Click to expand...
Click to collapse
i havent solved the problem with touch screen. can anybody help?