I was running the latest Carbon nightlies on my Rogers GS3 and I wanted to return the phone back to stock. I downloaded the latest Rogers Firmware and flashed the .tar file through Odin. Everything worked but when the phone rebooted, it got stuck in a bootloop on the samsung logo. My TWRP got replaced by stock recovery so I cannot restore any backups. What should I do???
There could be several causes to this issue. Some that come to mind are:
-You have old files in your cache, system partition, or internal memory that are interfering with the stock ROM
-You downloaded the wrong ROM for your phone
-The ROM file you flashed was corrupted
-Something went wrong in the flashing process
-Something else
I think the simplest way to try and get back to stock is to just install Samsung Kies on your computer, and run the emergency firmware recovery.
It will ask for your model and serial number, and from that will find the exact firmware for your phone. You put your phone into download mode, plug it in, and Kies will do the rest.
bobyum said:
I was running the latest Carbon nightlies on my Rogers GS3 and I wanted to return the phone back to stock. I downloaded the latest Rogers Firmware and flashed the .tar file through Odin. Everything worked but when the phone rebooted, it got stuck in a bootloop on the samsung logo. My TWRP got replaced by stock recovery so I cannot restore any backups. What should I do???
Click to expand...
Click to collapse
Hopefully you have set TWRP to backup to external SD card because you will likely need to do a factory reset/full wipe in order to get the phone past boot loop. There are lingering OS settings remaining from Carbon that prevent you from booting stock. A factory reset will fix this and you will boot stock just fine. Hopefully you have backed up what you need before this though because factory reset will wipe your internal memory at the cost of fixing the stock ROM
Just a heads up, a factory reset is always required after flashing back to stock firmware. You did nothing wrong. Cheers
Thanks Everyone! I will try out the suggestions!
Related
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
wings9130 said:
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
Click to expand...
Click to collapse
If you can get into recovery mode, you can just restore a nandroid backup (if you have one made). If you don't have one, you can wipe /system, /data, and the caches and reflash your Rom (provided you have it saved on your SD card).
If none of the above work, download mode is your best friend.
You can get into Download (Odin) Mode. That's a good thing. Sextape has the md4 TAR file for your over in their thread (warning, outside link). They have the stock unrooted as well as stock rooted file. Since you have already wiped your data, you might as well flash the "Restore" version:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
If you know how to use Odin, you can just downlaod the TAR file, but I recommend using their auto-extractor (the exe file), since it's well tested and there's less chance of user error.
All that being said, I'm curious to how your phone became "softbricked." Did you install any apps or mods recently that could've caused it? Custom Kernel?
It sounds like you eventually ended up wiping /system, which would be why you can't boot up now. I haven't heard of it automatically going into download mode because of that, but I haven't tested it on my phone, either.
try rwilco 12's android file repository. he has everything you will need
http://www.rwilco12.com/
You can also take the sd card out plug into a computer download a rom zip put it on the sd card pop it back into the phone and flash through the custom recovery which should be there.
Sent from the future via Xparent Green Tapatalk 2
Thanks for the help everyone. I guess I didn't soft brick the phone I just wiped it and there was no rom on it.
Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.
EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.
TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)
This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
re: phone issues
6uPMAH said:
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
Click to expand...
Click to collapse
Go into recovery mode and do a complete wipe including "Factory Reset", wipe data, wipe system,
wipe cache, wipe dalvik cache and then if you have a working nandroiod backup restore it.
If you don't have a nandroid backup then go into download mode and flash the official stock
firmware for the N900T phone from http://SamMobile.com
Either one of these two options will get your phone back up and running.
Good luck!
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
6uPMAH said:
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
Click to expand...
Click to collapse
Google zedomax you will find his website for unrooting note 3. Will walk you thru with ever step.
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
6uPMAH said:
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
Click to expand...
Click to collapse
Did you try the "boot loop fix" flashable? It's essentially a script that sort of recreates the efs partition in recovery. It's been linked a few times in the twrp thread, and there may be a thread dedicated to the topic (search for "brick loop") - I don't have the links handy though, apologies.
The mans right^ that helped me out through my "soft brick". Totally out of the blue. Wasnt even messing around with anything I didnt knew I was doing
Sent from my SM-N900T using Tapatalk
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
6uPMAH said:
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
Click to expand...
Click to collapse
The method is outlined in the OP of this thread but the flashable version of what is outlined there can be found in this thread - hope that helps!
Thanks. I'll give it a go after work.
UPDATE: All is well in the world again. Thanks everyone for all your help. Thanks dwitherell ! The thread you pointed me to was the solution!
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
ladd76 said:
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Larry2999 said:
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Click to expand...
Click to collapse
yes i747 thanks
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
That is actually what i was flashing when I encountered my problem. I was finally able to get one of my old ROM's to install after re-flashing the newest CWM through ODIN and reinstalling my bootloader. I am not sure what the problem was as the stock rom 4.3 shouldnt have downgraded it? Perhaps a random crash which corrupted something. The developer on the stock rom has provided a tar file which I may try this time around. Thank you all for your help.
So here's what happened. First I had Cyanogen 12.1 (Lollipop 5.1.1) working fine. I was looking to upgrade so I flash ed Emotion AOSP rom (Marshmallow 6.0.x) (LINK). But it didn't quite fly with my system and I was getting random crashes on my system. These crashes would leave my phone unbootable, until I plugged my phone to charge. This was pretty funky, so I figured there's something up with my kernel. So I thought of flashing beastmode kernel (Marsmallow PD1) (LINK).
This made sense to me because the ROM was Marsmallow, so Marsmallow kernel would work right? I then flash the kernel, which made it so my phone couldn't even boot past the Emotion ROM app load sequence. After, I tried factory reseting and clearing cache + dalvik but that didn't work. By now, I've had enough and just wanted stock marshmallow.
I then try flashing PD1 stock tar and PC1 stock tar with and without factory reset + full wipe (with TWRP) before it. Here, I get stuck on the boot splash screen (the "Powered by Android" screen for clarification) every time, no errors on odin though. I've also tried, after much forum browsing, flashing PIT and Nand erase along with PD1 + PC1 stock tar flashing to no avail (also getting stuck on boot splash screen, and no errors on odin).
Does anyone have an idea of what can be done to hopefully fix my device?
Device (for clarifcaiton purposes): N910P
Thoughts on Methods for Repair:
1) JTAG
2) Go home (call it quits) and switch to iPhone.
EDIT:
Problem turned out to be battery.
Where did you get the TAR files from? there are some on here that are COMPLETELY full stock with bootloaders and kernels.
Also, after you use odin I would suggest booting to recovery and wiping all caches and factory reset
joshka89 said:
Where did you get the TAR files from? there are some on here that are COMPLETELY full stock with bootloaders and kernels.
Also, after you use odin I would suggest booting to recovery and wiping all caches and factory reset
Click to expand...
Click to collapse
I get the TAR from here (xda).
For OK1 I've used this one (LINK).
For PC1 I've used this one (LINK).
For PD1, I've used this one (LINK).
I want the ones that are completely stock right? How do I know if they are? By their size?
Also, after Odin, should I factory reset and wipe cache immediately after?
-Thanks
Eluderei said:
I get the TAR from here (xda).
For OK1 I've used this one (LINK).
For PC1 I've used this one (LINK).
For PD1, I've used this one (LINK).
I want the ones that are completely stock right? How do I know if they are? By their size?
Also, after Odin, should I factory reset and wipe cache immediately after?
-Thanks
Click to expand...
Click to collapse
The stock tars are just that... stock. Rom tars are complete roms. ota update zips are usually just patches meant to update an existing software and can only be applied by download it and applying the update on the phone itself. These ota zip files can't be used for any other purpose. Odin flashable tars are meant to be used on your pc and are complete rom, modem & bootloader, carrier packages so this is the best way to updat if you want a clean slate and don't mind backing up your internal storage and wiping your device first. As for your boot problem... Sometimes you can have leftover data on your internal storage or sd card that can cause the phone to hang at boot. When this happens just do a factory reset in the stock recovery and reboot the phone and it should boot up just fine. Always try this first when that happens after flashing a known good rom whether custom or stock.
tx_dbs_tx said:
The stock tars are just that... stock. Rom tars are complete roms. ota update zips are usually just patches meant to update an existing software and can only be applied by download it and applying the update on the phone itself. These ota zip files can't be used for any other purpose. Odin flashable tars are meant to be used on your pc and are complete rom, modem & bootloader, carrier packages so this is the best way to updat if you want a clean slate and don't mind backing up your internal storage and wiping your device first. As for your boot problem... Sometimes you can have leftover data on your internal storage or sd card that can cause the phone to hang at boot. When this happens just do a factory reset in the stock recovery and reboot the phone and it should boot up just fine. Always try this first when that happens after flashing a known good rom whether custom or stock.
Click to expand...
Click to collapse
I tried fr + fw and then Odin flashing Odin Flashable OK1 from (LINK). After installing, I went to recovery mode and did as you said fr and also clear cache. After, I sitll had bootloops. What can I do about this?
Thanks for the response
-Eluderei
Eluderei said:
I tried fr + fw and then Odin flashing Odin Flashable OK1 from (LINK). After installing, I went to recovery mode and did as you said fr and also clear cache. After, I sitll had bootloops. What can I do about this?
Thanks for the response
-Eluderei
Click to expand...
Click to collapse
Make sure you flash the stock OK1 kernel. then do a factory reset once more.
tx_dbs_tx said:
Make sure you flash the stock OK1 kernel. then do a factory reset once more.
Click to expand...
Click to collapse
Flashed stock OK1 kernel from here (LINK). Tried to boot in to recovery. Phone would boot to android robot, but would crash back to boot screen and wouldn't load the recovery menu. I flashed TWRP via Odin to FR and clear Cache + Dalvik and rebooted, phone still has bootloops. Also, interesting thing, the phone can't boot to TWRP recovery unless it's plugged in to a computer/outlet. What do you think this means? Also, where do you think I can go from here?
Thanks again
-Eluderei
Eluderei said:
Flashed stock OK1 kernel from here (LINK). Tried to boot in to recovery. Phone would boot to android robot, but would crash back to boot screen and wouldn't load the recovery menu. I flashed TWRP via Odin to FR and clear Cache + Dalvik and rebooted, phone still has bootloops. Also, interesting thing, the phone can't boot to TWRP recovery unless it's plugged in to a computer/outlet. What do you think this means? Also, where do you think I can go from here?
Thanks again
-Eluderei
Click to expand...
Click to collapse
It sounds like there is a system app that isn't optimizing at boot and/or your bootloader doesn't match the software & kernel. they all need to be from the same software version. If you get that done it should boot fine.
tx_dbs_tx said:
It sounds like there is a system app that isn't optimizing at boot and/or your bootloader doesn't match the software & kernel. they all need to be from the same software version. If you get that done it should boot fine.
Click to expand...
Click to collapse
Brought it to Sprint today, problem turned out to a battery. Tech guy put his battery in my phone, it booted up just fine. Buying battery soon. Can't wait to install the MOAR Rom that you've worked on. Thanks in advance for that. Thanks for all the help along the way as well