Just had a really strange problem with S3...I've installed the 1st OTA update, than my phone restarted & ended up in a bootloop. Atm I'm downloading a stock rom & gonna make a hard reset with Odin, but anyway I think it was kinda strange. Did the update just after I got the phone from the box, so it was in completely stock configuration. Any1 else experienced or heard of this kind of situation? Rom baseband: i9300XXALF2
cardrigar said:
Just had a really strange problem with S3...I've installed the 1st OTA update, than my phone restarted & ended up in a bootloop. Atm I'm downloading a stock rom & gonna make a hard reset with Odin, but anyway I think it was kinda strange. Did the update just after I got the phone from the box, so it was in completely stock configuration. Any1 else experienced or heard of this kind of situation? Rom baseband: i9300XXALF2
Click to expand...
Click to collapse
Try force restarting it by pressing volume up+power. It fixes bootloop sometimes.
else just flash a stock ROM using Odin.
Try to restore factory settings in recovery mode.
I presume you still can get there with volume up+home+power buttons pressed simultaneously when the phone is off?
Sent from my GT-I9300 using xda premium
Related
Hi Guys
I flashed the leaked ICS but hate it. Can I flash to stock GB via Odin? What about the baseband versions etc.., would it matter?
Sorry, I read another thread but it's unclear and I want to avoid bricking. Thanks
As far as what I've read you can flash stock from Odin or even use CWM to a previous nandroid of gingerbread.
Sent from my SAMSUNG-SGH-I717 using XDA
If you got your Note from AT&T, simply flash this stock ODIN:
http://forum.xda-developers.com/showthread.php?t=1506330
I went from ICS back to Gb cause I missed the tethering and it was easy. Just make sure you clear the caches and all should be well.
Thanks.. I was worried of the different baseband would have any adverse effect, but it doesn't sound like it will. I'll give it a try.
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Mines fine..only baseband is different, phone works.
Before I Odin to stock, I booted into recovery, factory reset and wiped cache. Odin, then booted into recovery and performed another factory reset and wiped cache again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
beall49 said:
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Click to expand...
Click to collapse
Try factory wipe/format usb from within GB..it may help.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
beall49 said:
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Click to expand...
Click to collapse
figured it out. My post is below.
lindenhurst said:
You get it figured out? I did the same thing. . My old apps still there. I can tell it is gingerbread, but nothing works now. I hope you got your figured out!!
When I boot into recovery I get the screen that tells me to use the up and down keys and when I choose factory wipe, and press power button, nothing happebs. If I hold it down eventually the phone shuts off. When i restart it, nothing changed.
Click to expand...
Click to collapse
I had to revert from ICS to GB yesterday and, even tho I am on Telus, I had success by flashing the pda-odin-att-stock.rar image
I can't post links .. I'm too new. But literally.. google what's bolded above and you will find the hotfile link.
It replaced everything (including the recovery) ... FULL system image. Solved everything and brought me back to 100% stock.
So yes, I lost my root and my CWM recovery software.. but it got my phone working again.. I can reflash CWM and re-root as I need.
After the install, wipe cache, factory reset etc.
I too flashed the stock ATT rom but like the previous poster, it gave me a phone which started up but wouldn't work. When I tried to get into recovery mode, it went to a screen with the recovery mode stuff at the top, but with a yellow warning sign in the middle and some words about manual mode, and it would not let me do a wipe or reset.
Here is what I just did that did work.
I flashed the recovery-i717-cwm-b4.tar file with odin. This worked and allowed me to get into the "proper" recovery mode to do a wipe and factory reset, as well as a cache wipe. I then reflashed tieh the stock ATT rom, and my phone now is back to stock.
menu and back button isn't responding nor working,
flash back cf-root, tried another kernel nothing works,
i flashed back to DXLP7 with pit file, wipe everything. and still nothing works.
So you never thought of wiping and flashing the ROM your phone came with to check whether it was a phone problem, a firmware problem or some app causing problems?
fred_up said:
So you never thought of wiping and flashing the ROM your phone came with to check whether it was a phone problem, a firmware problem or some app causing problems?
Click to expand...
Click to collapse
the firmware i flashed it working before.
tried everything and googling doesn't help.
Im running 2.3.5 on a rogers phone in canada and my phone says there is an update. When I click on download and install, it does its thing and when it boots back up it says updated failed. Not sure what im doing wrong. I searched everywhere and could not find anything that will help
You have probably changed your system somehow. You can try flashing a nandroid backup to restore all missing bloats. You can also flash brasilizian 2.3.6 gb, wich is pretty much the same as rogers one.
Sent from my XT910 using Tapatalk 2
I just tried to flash brasilizian 2.3.6 gb and right away I got flash failure and now I cant get out of fastboot
edit. I got out of it. Cant understand why its failing to flash
ottawadad34 said:
I just tried to flash brasilizian 2.3.6 gb and right away I got flash failure and now I cant get out of fastboot
edit. I got out of it. Cant understand why its failing to flash
Click to expand...
Click to collapse
Try disabling any anti virus you may have installed. Also, do a factory reset/ wipe user data and cache before flashing the brazilian 2.3.6
Think my phone is messed up. everything time I reboot, It goes to flashmode. I have to hold power and both volume buttons and when it goes blank I let go of the power it goes to fastboot and I have the option to power up in normal.
Try an wipe Data in Moto Recovery. For me it was the solution when I had this problem first time...
flash this empty_radio.zip
Thanks, I got my phone back up
Hi Guys,
Last night for some reason my GT-19100T running CM9.1.0 wouldn't lock by pressing the power button, the button itself seems to be working. I can press the button down but nothing happens. I left it for the night and came into work this morning, I thought it might be a bug with the rom, i managed to boot into recovery via the "Rom Manager" app and was going to flash to CM10. My problem is now that i am in recovery, I can't select anything as the power button is not working. I can scroll through the recovery menu with the volume buttons but cant select anything, and now soon as the phone turns on after removing the battery, it goes straight to recovery mode and i cant get around it.
I have tried leaving the battery out for about 3 hours and same thing. I can boot into download mode, But at the moment that doesn't help me.
Any suggestions on what i can do? I'm not worried about warranty so i may pull the phone apart and clean it tonight. Thanks in advance.
Update:
After much playing around with the button i can get it work, it is very temperamental and requires to be pushed in the right way. Was able to flash with Touch recovery and am now updating to CM10 nightlies. Thanks all for your help on my first post.
SirBigBird said:
Hi Guys,
Last night for some reason my GT-19100T running CM9.1.0 wouldn't lock by pressing the power button, the button itself seems to be working. I can press the button down but nothing happens. I left it for the night and came into work this morning, I thought it might be a bug with the rom, i managed to boot into recovery via the "Rom Manager" app and was going to flash to CM10. My problem is now that i am in recovery, I can't select anything as the power button is not working. I can scroll through the recovery menu with the volume buttons but cant select anything, and now soon as the phone turns on after removing the battery, it goes straight to recovery mode and i cant get around it.
I have tried leaving the battery out for about 3 hours and same thing. I can boot into download mode, But at the moment that doesn't help me.
Any suggestions on what i can do? I'm not worried about warranty so i may pull the phone apart and clean it tonight. Thanks in advance.
Click to expand...
Click to collapse
Hi!
First, have you tried flashing a stock firmware? If that does not help, you can try cleaning your hardware.. it may be dusty or something.. be careful! I hope you get this sorted out.
Also, i hope my suggestion will help you out, cheers!!
Sent from my GT-I9100 using xda premium
First, have you tried flashing a stock firmware?
I am currently flashing back to xxlpq via odin and see if that changes anything. Will post back with results.
Thanks.
SirBigBird said:
First, have you tried flashing a stock firmware?
I am currently flashing back to xxlpq via odin and see if that changes anything. Will post back with results.
Thanks.
Click to expand...
Click to collapse
Okay, will wait for your feedback
Sent from my GT-I9100 using xda premium
Okay, Flashed back to stock ICS rom, Got a little bit further but still no go. It gets the "S" loading screen and stays there, Still cant do factory reset via Android Recovery as it also needs the power button to select. Someone suggested installing CWM touch recovery but i cant find a .tar version of "recovery-clockwork-touch-5.8.1.5-galaxys2" downloaded from CWM website. Any suggestions on how i can install this without using recovery? Thanks.
SirBigBird said:
Okay, Flashed back to stock ICS rom, Got a little bit further but still no go. It gets the "S" loading screen and stays there, Still cant do factory reset via Android Recovery as it also needs the power button to select. Someone suggested installing CWM touch recovery but i cant find a .tar version of "recovery-clockwork-touch-5.8.1.5-galaxys2" downloaded from CWM website. Any suggestions on how i can install this without using recovery? Thanks.
Click to expand...
Click to collapse
I guess you have to flash them with odin..
1. Flash a stock firmware to get you out of bootloop
2. Flash the latest siyah kernel cause it's a touch recovery via odin as well
Do you want me to post the links or will you find it yourself?
I hope this helps, cheers!
Sent from my GT-I9100 using xda premium
I recently tried converting back to stock firmware(xdlj4). Did it many time but this time Odin failed and I didnt know what to do. So I turned off Odin and rebooted back my phone. And got a message saying my firmware has failed and download via kies. Well I didn't and I just rebooted into download mode and tried flashing it again. It was successful but now I when I try to call out or have some one call me. I cant hear anything in the speakers or on speaker phone. Any help would be appreciated. Thanks
reflash with auto reset disabled
power off
power on into android stock recovery or cwm
wipe data / factory reset
profit?
Thanks but no luck at all.. anyone else??
Sent from my GT-I9300 using xda premium
DEEBS808 said:
Thanks but no luck at all.. anyone else??
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
First of all when you use odin you need to have everything that is related to kies turned off.So before you try to flash again via odin, go to process monitor, kill everything that has to do with kies and try again. You tried factory reset and nothing happened? Can u be more specific? I mean your speaker had that problem after the factory reset?Or you flashed again and then you found out the problem?
(Keep in mind that it might be a hardware problem.)