Just this morning i rooted my sgs3 i9305 adn all went fine.
Then after that my phone couldn't connect to the mobile network anymore, so i thought maybe a custom rom would change anything.
After installing a custom rom my phone wouldn't boot anymore.
I could still access cmw recovery and download mode.
I then flashed the stock rom for the i9305 through odin 1.85.
After that my samsung galaxy s3 logo comes up agaain when booting but after that just a black screen with the blue led slowly flashing.
Have i done soemthing wrong?
you need to wipe data from recovery when switching roms
Now i managed to flash the custom rom called; [ROM][16 Apr][UBBMC1][JB 4.1.2][rXTREME.v8.0] (stable, smooth & fast)), and my phone is wroking again.
But my phone still can't connect to the mobile network.
I did cut my sim card to a micro sim card and it worked before i started flashing but now it can't connect to my network?
What does your IMEI say in Settings, About phone, Status?
It did say nothing...
But already found the soultion at the end of the first post on this page;
http://forum.xda-developers.com/showthread.php?t=1946915
Thnx for anyone who helped me out! :good:
Related
Hi All,
I was try to change the stock animation on Infinitum when after restarting I wasn't abble to sign in. There was a msg saying something baout "Report" "Ok"..." Settings.
I shut down the SGS and made a nandroid restore, the device restarted but it shows the Samsung logo blinking evry six seconds and a can't go to recovery anymore only downloading.
What should I do?
Thank you all in advance.
what program did you use to root your phone?
broncosfan007 said:
what program did you use to root your phone?
Click to expand...
Click to collapse
I think was "OneClick Root"...
I'm trying to find .tar files to recover using Odin but I can't find... Old SGS + Froyo + Portuguese TMN (carrier)... Any help would be apreciated.
Heeeeeelpppp
Now things are getting very strange. I got the original firmware and flashed the Galaxy S with Odin. All went well without errors. But now, when restarting, the device makes the carrier original sound and is swapping between the carrier logo and galaxy logo, endlessly....
I can use the pseudo-CWM menu with the options Install from sdcard, Wipe Factory and Wipe.
Any help or idea to follow?
(I love this mobile )
Definitus said:
Now things are getting very strange. I got the original firmware and flashed the Galaxy S with Odin. All went well without errors. But now, when restarting, the device makes the carrier original sound and is swapping between the carrier logo and galaxy logo, endlessly....
I can use the pseudo-CWM menu with the options Install from sdcard, Wipe Factory and Wipe.
Any help or idea to follow?
(I love this mobile )
Click to expand...
Click to collapse
Hmm..when i screw something up with my SGS, I just go download, and make myself a stock ginger trough ODIN.
Try the steps for installing andy 2.3 as a preperation for CM7
Hey guys, I'm really in a bad spot here.
So I installed CM10 on a GT-i9000, worked fine except for the hardware buttons not working. So from there, I decided to install SlimBean (A foolish mistake that I thought was foolproof). And boom, now I am here, stuck in a CWM bootloop, and I've tried factory resetting and all, still boots the same.
I've tried installing other roms, sometimes it reboots during installation and doesn't complete, and even if it does complete, same problem, it boots into CWM. And I've noticed a new Samsung AnyCall Boot logo every since I tried SlimBean.
I've tried updating the kernel, no luck. I bought a download mode jig, but windows does not detect the Galaxy S in download mode with Kies installed. (I think I disabled USB Debugging in CM10)
Any suggestions? This is really stressing me out. I'm prepared to use odin, but download mode is not recognized on my PC.
slicer91 said:
Hey guys, I'm really in a bad spot here.
So I installed CM10 on a GT-i9000, worked fine except for the hardware buttons not working. So from there, I decided to install SlimBean (A foolish mistake that I thought was foolproof). And boom, now I am here, stuck in a CWM bootloop, and I've tried factory resetting and all, still boots the same.
I've tried installing other roms, sometimes it reboots during installation and doesn't complete, and even if it does complete, same problem, it boots into CWM. And I've noticed a new Samsung AnyCall Boot logo every since I tried SlimBean.
I've tried updating the kernel, no luck. I bought a download mode jig, but windows does not detect the Galaxy S in download mode with Kies installed. (I think I disabled USB Debugging in CM10)
Any suggestions? This is really stressing me out. I'm prepared to use odin, but download mode is not recognized on my PC.
Click to expand...
Click to collapse
You will hadware buttons failure when you flash a i9000 ROM on an Anycall M110S ( Korean Galaxy S) , so I am curious are you sure your phone is not an Anycall M110S? since you also getting Anycall boot screen...sounds odd, that i9000 will do that.
For USB connection problems , just try link on Quick Fixes and Solutions link below
slicer91 said:
Hey guys, I'm really in a bad spot here.
So I installed CM10 on a GT-i9000, worked fine except for the hardware buttons not working. So from there, I decided to install SlimBean (A foolish mistake that I thought was foolproof). And boom, now I am here, stuck in a CWM bootloop, and I've tried factory resetting and all, still boots the same.
I've tried installing other roms, sometimes it reboots during installation and doesn't complete, and even if it does complete, same problem, it boots into CWM. And I've noticed a new Samsung AnyCall Boot logo every since I tried SlimBean.
I've tried updating the kernel, no luck. I bought a download mode jig, but windows does not detect the Galaxy S in download mode with Kies installed. (I think I disabled USB Debugging in CM10)
Any suggestions? This is really stressing me out. I'm prepared to use odin, but download mode is not recognized on my PC.
Click to expand...
Click to collapse
Go back your original firmware...
Any updates to this?
I am having a similar situation. I tried flashing ICS ROM to my Anycall Samsung Galaxy S GT-I9000. It is now stuck in recovery mode. I tried doing factory reset and wiping the cache and dalvik cache and tried reflashing. Everything goes fine but gets stuck in the recovery mode - more correctly in download mode but the download mode logo flashes twices and enters to recovery mode.
Any possible solutions to get me out of this mess?
Thanks,
Sid
your problem will be solved with this post:
http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Edit : above url is for S+ your device is S , sorry .
Thanks, but anything similar for Galaxy S? And remember my download mode does not stay, if flashes twice and runs into recovery mode. So if your solution is something to do in recovery mode it will be helpful (or if your solution is to first make me stay on download mode and then flash something using odin I will be thankful)
Regards,
Sid
sidswami said:
I tried flashing ICS ROM to my Anycall Samsung Galaxy S GT-I9000.
Click to expand...
Click to collapse
Check your Model, Anycal does not make GT I9000, it makes only M110S and firmwares / solutions for them vary.
If you have Anycal M110S visit PIT STOP link below to solve your problems
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
worked for me
Hi..also had the boot loop...
fixed that easily by removing the accu..
removing external SD !!
Thats it !
Worked for me !
Later on I inserted the SD again..and everythings fine
beben3 said:
Hi..also had the boot loop...
fixed that easily by removing the accu..
removing external SD !!
Thats it !
Worked for me !
Later on I inserted the SD again..and everythings fine
Click to expand...
Click to collapse
Glad that worked for you, but I for some reason can't be so lucky. I tried to also flash CWM 10 but after the home key not working I decided to flash Slim Bean and now I am stuck. My phone isn't even recognized by Odin any more and I have tried different USB ports and even my laptop with Heimdall. I don't know what to do at this point, but any kind of suggestions would be great. Usually when I get stuck I just flash back to Stock and start all over with a new ROM or kernel but I have no idea where to go from this point.
Hi everyone. I have a rooted Galaxy Note 1. I accidentally tried to update something (the phone said there was an Android update or something) and now my phone in stuck in a bootloop showing the Android logo. When I try to reset it (volume+home+power buttons) it goes to an Odin "Downloading..." screen and gets stuck on that.
I've seen some stuff about unbricking the phone using Odin to return to the original stock rom. But from what I can tell, there are different stock roms available depending on your Country Sales Code (CSC). So apparently I need to look in Kies for my CSC to know which rom to download, but Kies doesn't recognise the phone, I guess because it's bricked. I know the phone is from the UK, but I don't know what network it came from (I bought it second hand). All I know is that it is unlocked now.
I have CWM.zip, CWM-SuperSU-v0.87.zip, and franco.Kernel-r5.zip on the micro SD card from when I was rooting it ages ago. Do these have anything to do with fixing it?
Any ideas on where I go from here? Thanks for your help.
Which volume button did you press ? You need volume up + home + power to get into recovery.
You can flash any rom from any region using odin.
Same problem
Hey,
Thanks for helping me in advance...
I used the Custom ROM (( http://forum.xda-developers.com/showthread.php?t=1970626 )) Ultimate N7000 for a long time. However this build became more and more unstable the longer I used my phone.
So I decided to go back to STOCK.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1424997
And everything went well (Odin didnt give any errors)
However after reboot... the problem began... I cant turn my phone on anymore.... It seems to be stuck in a bootloop....
How can I fix this?? please help me
Which rom did you flash? If you flashed JB, boot into recovery and wipe data. Then reboot.
hi everyone
I have a samsung cappy ATT with CM10 before and it was not detecting my sim card so i decided to flash it back to stock so i can use it with sim.
I was so noob and went to CWM and wipe out everything (whatever i see on the menu that i see i can delete, i deleted them). Then now my phone it stucks in ATT logo when i turn on and my pc wont detect even in download mode. I am not able to boot to CWM so I can't flash with zip file. I did some research here and tried 3 different USB cable and 3 different desktop(XP and vista) and none of them detect my phone :crying:.
Just want to see if any expert here know the solution and help me out. My model is 1007 so i dont need a JIG to go download mode. I love my cappy and really it to back to life.
Please help
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Gregg1100 said:
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Click to expand...
Click to collapse
Hi,
You should use ODIN v3.09 and flash a i9305 official firmware (4.1.2, 4.3 or 4.4.4). You can search on samsung-updates.com or sammobile.com.
IMPORTANT : If you don't want KNOX BL because of warranty purpose, don't flash official 4.3 or 4.4.4 via ODIN.
Don't forget to install Samsung usb drivers on your computer.
For instance, you can follow that guide from MaHo_66 : http://forum.xda-developers.com/gala...sions-t2694249
Gregg1100 said:
I have just purchased this Samsung GTi 9305 LTE from a mate. I found out then that it was rooted, but not correctly. I used Rootchecker to tell me. The Security manager kept telling me also that it was blocking Supersu.
Oops. Just done a factory reset on this S3 Gti9305 (LTE) and all I am getting now is the blue notification light on and the Samsung logo just going light and dark blue.
I tried to then do a recovery, with all the buttons held down, it starts with a green warning;
A custom OS can cause critical problems in phone and installed applications. ( Yeah, just found out)
If you want to download a custom OS, press vol up key, if not, vol down and restart. ( which it doesn't).
I remember disabling Supersu, and unticking the security manager warning box. I put in the correct sim card, factory reset, and since then it will not start.
Phone was on Uk EE, but was unlocked for previous owner. The replacement sim is GiffGaff- running on UK O2 lines.
When hooked up to pc and Kies 3, the phone was not recognized and I was notified that the usb device is not working. When usb lead is in phone, it shows that it is charging, so lead looks to be ok.
Is this what you call a brick? Or just in a bootloop mode ??
I rooted my S3 GTi9300 ok and put on Omnirom v5.
Any help would be appreciated, so I can throw the phone back at mate.
Thank you.
Click to expand...
Click to collapse
just flash a stock firmware via odin..
I had the exact same problem after some unsuccessful attemts to root my s3 lte!
Sent from my GT-I9305 using XDA Free mobile app
Non start up after factory reset. Bricked ??
Thanks for help. All sorted.
If your phone stuck on boot after flash stock via odin, go to recovery and make a full vipe and factory reset. Some devices unable to boot first after reflash stock.
you can watch here how to install rom via odin.
https://youtu.be/32TQ6DG0JZ8