Device: AT&T Galaxy S III (SGH-I747) Rooted
ROM: Cyanogenmod 11
I have had my phone rooted and running a custom ROM for a few months now and I have decided that I no longer want to run a custom ROM. I looked up how to go back to stock ROM and everything said to: wipe cache and do a factory reset, download latest stock ROM off of Samsung's firmware website and flash the ROM from Odin. Every time that I did this, it would always fail even if i tried to install from recovery mode. I tried a few more times and it still didn't work. One post said that it was because TWRP, i downloaded and installed the stock recovery (which was the only successful install) and the other installs still didn't work through odin or recovery mode.
Is there anything that I am doing wrong, am I leaving a step out, or is something just flat out wrong with my device?
Assistance would be greatly appreciated!
Related
While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).
Hello everyone,
I had CM11 installed on my Samsung galaxy S3 I9300. But I wanted to trade my phone with my dads and he wanted the simple stock rom (Android 4.3). I tried flashing the stock rom on it which went good until the last step when it should reboot itself. But i'm stuck at the samsung logo, I tried everything (pulling out battery, rebooting it, install stock rom again,...).
And I even can't get in recovery mode. The only possible mode in can get in is download mode. What can the problem be? Have I done something wrong? Should I try to install another stock rom from another country? Is there another way to get in recovery mode? I am from Belgium and I can't find the "Belgian stock rom", so I tried installing it from the Netherlands, is that the problem?
Thanks already.
What is the filename of the stock ROM you flashed and which options did you select in Odin?
hamzah.bhatti34 said:
Hello everyone,
I had CM11 installed on my Samsung galaxy S3 I9300. But I wanted to trade my phone with my dads and he wanted the simple stock rom (Android 4.3). I tried flashing the stock rom on it which went good until the last step when it should reboot itself. But i'm stuck at the samsung logo, I tried everything (pulling out battery, rebooting it, install stock rom again,...).
And I even can't get in recovery mode. The only possible mode in can get in is download mode. What can the problem be? Have I done something wrong? Should I try to install another stock rom from another country? Is there another way to get in recovery mode? I am from Belgium and I can't find the "Belgian stock rom", so I tried installing it from the Netherlands, is that the problem?
Thanks already.
Click to expand...
Click to collapse
First thing you should always do after flashing stock rom or any rom that causes a boot loop is to boot into recovery and factory reset then wipe cache this solves 90% of bootloops. Now I know you said you can't get into recovery so try flashing a custom recovery with odin then try booting into that and then factory reset.
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
Hi, recently I just rooted my phone, everything going fine back there. Then I try to download cwm touch recovery and everything fine.Then I download "http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574/page333" this rom and wipe data/factory reset >>> flash it with cwm, it said Installation Abort Stage 7 something like that, I found something that said my cwm version is not compatible with the rom. So I now stuck at cwm, I tried to flash to stock rom and the big PROBLEM is, I dont know my software version. here http://samsung-updates.com/device/?id=GT-I9300
Then can anyone help me get out of this cwm, flash to stock rom, and get my s3 back?
It's 3am and I still didn't sleep.