AT&T S3 possibly bricked - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I've flashed plenty of custom ROMs on this phone and my old Captivate so I'm not new to the process, but I have come across an interesting issue. At first, I had a version of RootBox (4.2.2) on my phone. I don't remember exactly what it was and I can't go check anymore. When I tried to install a new custom ROM, any, it said that my phone was d2spr even though it should be d2att and promptly failed. Never had the happen before so I thought I might need to go back to a stock ROM. Used Odin to flash a stock ROM, tried I747UCDLK3 first. Flashed successfully, but now it won't boot. So I'm stuck with a non-booting ROM and stock recovery. I tried flashing CWM using Odin. Flashed successful. When I try to boot into CWM it just shows a blank screen. Phone is still on since holding the power button doesn't attempt to start it. And that's where I'm now stuck. I'm attempting to get a Sprint ROM for this phone, figured it couldn't hurt at this point. I've tried TWRP and some other stock AT&T ROMs, but same things happens. I'm not really sure where to go from here since it seems to be unusual circumstances.
Does anyone know what's going on or what I should try?

Did you run an OTA update to take your d2att to 4.3? If you did, you cannot flash anything that is lower than 4.3 because the 4.3 update upgrades the bootloader.

I am assuming from your post you are not on the 4.3 mjb boot loaders.
Can you get into download mode. If so you could try the Odin back to stock again. Once complete you may need to boot into factory recovery and perform a full reset to clear the boot loop.
Did you root before flashing CWM?
Sent from my I-747 using xda app-developers app

Related

Help, went from AOSP to Stock rooted

Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
hunter99507 said:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
Click to expand...
Click to collapse
You might want to try flashing the "UCALH9 Kernel, Modem and TWRP Recovery Tar" from here with Odin. Make sure the "Auto Reboot" switch is not checked in Odin. When the flash is done, disconnect from the computer, pull the battery, then boot into recovery by holding Home and Vol Up and then pressing Power. Hold Home and Vol Up until you see the Samsung logo and some little blue text, then release. If you can get there, do a factory reset, then you should be able to flash the rooted LG1 image with Odin. Or, you can flash LH9 from the same thread or from here by flashing the Bootloader, ROM and Kernel files from the PIECES section (in that order) before rebooting.
Wipe cache and devlik and it will fix your issue. I had the same problem before.
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
I had the same issue a few days ago and ultimately fixed it by doing factory reset, wipe cache, dalvik, etc.. I had forgotten to do it after flashing back to stock. You were probably smarter than me and did those things BUT if you didn't it's usually something simple like I did to fix the problem.
\Hey hunter you prolly figured it out already but I was in the same situation today going from AOKP to stock rooted.. what fixed it for me was after flashing, booting into the stock recovery (HOME + VOL UP + POWER) and doing a wipe data and wipe cache. Then going back to download mode and reflashing the stock rooted tar. not sure if reflashing was necessary but it worked like a charm after that.
well as i wasnt in clockwork i was pushing a stock rom through odin i don't beleive i iclearly the cache that could of helped but nonetheless im stuck and i can't get into cwm or regular recovery etc
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
My suggestions including flashing a bunch of stuff. Which one caused the error? The flash of the modem/kernel/recovery tar file in Odin or the subsequent flashing of the zips in recovery? What was the exact error you received?
It's pretty hard to help you if you don't provide all the details.

[Q] Bricked S4

Hello XDA,
it appears as though I have somehow managed to brick my S4 when using odin to return the phone to stock (MDL the device was never updated to 4.3 or 4.4.2)
Here is what I tried;
1. put the phone into download mode an flashed firmware (UVUAMDL, as mentioned above, I never updated)
2. put the phone into stock recovery to perform a data wipe
3. rebooted and the phone; once the t-mobile screen appeared, the phone went black.
Whenever I attempt to boot the device, I am presented with the main S4 splash screen for about 2 seconds, and then the phone turns itself off.
I can only enter download mode
I also cannot enter recovery mode
please help, thanks
Nightfrost95 said:
Hello XDA,
it appears as though I have somehow managed to brick my S4 when using odin to return the phone to stock (MDL the device was never updated to 4.3 or 4.4.2)
Here is what I tried;
1. put the phone into download mode an flashed firmware (UVUAMDL, as mentioned above, I never updated)
2. put the phone into stock recovery to perform a data wipe
3. rebooted and the phone; once the t-mobile screen appeared, the phone went black.
Whenever I attempt to boot the device, I am presented with the main S4 splash screen for about 2 seconds, and then the phone turns itself off.
I can only enter download mode
I also cannot enter recovery mode
please help, thanks
Click to expand...
Click to collapse
First, if you have updated your baseband/modem to MK2, NB4, or NH7, you need to find the MDL baseband/modem files and manually revert your modem. Once you've done that, you can then attempt to revert by simply flashing the MDL firmware in Odin again. If that still doesn't allow you to do anything but get into download mode, try the next suggestion.
Download an Odin-flashable custom recovery and a non-TouchWiz ROM... Cyanogenmod 11, SlimKat/Bean, etc... any Odin-flashable custom recovery will work for this purpose as well as any CM/AOSP-based ROM. No need to download GApps unless you plan to use whatever ROM you download some point in the future.
Using Odin, flash the recovery you picked.
Using the recovery you just flashed, flash the ROM you downloaded.
Boot into the ROM <Optional>
(Re)Boot into download mode
Use Odin to flash UVUAMDL.
At that point, since you're still on the MDL bootloader, you can then use TriangleAway to reset your flash counter or whatever else you want to do.
I've found that when using Odin to revert to stock while already running a TouchWiz ROM (custom or stock, doesn't matter) data and settings will, for some reason, survive the flash and cause problems. If you begin the process while already on a CM/AOSP ROM, going back to stock tends to go much smoother and there's no need for a factory reset after that.
Got it! Thank you
+Thanks button

[Q] Softbricked 4.4.2?

No O/S - can only boot into download mode
I've got an interesting one. I was prepping my phone for selling, decided to clear out all the memory. Somehow I must have deleted more than I meant to b/c when I restarted the phone, it just hangs on the Samsung screen. I can get into download mode, but not into recovery and nothing ever loads. I tried at least one version of installing CWM but it doesnt look like I can boot into recovery even after the Odin install appears ok. Before the crash, I was running a modded 4.4.2 rom with the bootloader and other things that come with it. Is there anything I can do to get this thing up and running again?
Thanks!
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
audit13 said:
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
Click to expand...
Click to collapse
Thanks. I'm positive I was running 4.4.2 on the phone before I decided to turn it into a paperweight
Flashing a custom recovery would be the goal, problem is that I can't find a recovery that I can flash. I've tried the latest version of PhilZ Touch recovery and that doesnt seem to work. ODIN shows it as a good install but when I restart the phone, I can't get into recovery. So was hoping for some direction on a different way of going about it. Basically, had 4.4.2, now I can only get into Download mode...
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Open Odin, connect phone, uncheck everything except f.reset time. Flash Philz. When you see reset in the status windows, remove USB cable, pull battery, replace battery, boot into recovery, flash ROM.
There are different versions of the 4..4.2 so it is best to determine the exact bootloader.

Trying to get S3 back to stock after CM12.1

I got an S5 and want to sell my S3 that I've been running CM12.1 nightlies on now for the past year.
I'm having issues though just getting it back to complete stock through various stock TARs I've downloaded. I've soft bricked it a few times but it has bounced back after installing a recovery again in Odin. They're all on the front page of the Sprint S3 Android XDA forum, so it's not like I'm flashing something non-Sprint.
Here's what I've been doing:
I wiped and factory reset within TWRP recovery.
Then I flashed the stock recovery in Odin. That worked just fine.
Go into download mode, tried to flash the Stock NJ2 tar and it fails at aboot. Phone then says: SW REV CHECK FAIL: Fused 2 > Binary 1
I get the 'connect to Kies' error both when powering up and in recovery. Throw it back into download mode, flash stock recovery again. Works fine -- boots in CM12.1 again with no data fresh.
I then tried to flash stock MK3 and it failed too.
I've tried the latest Odin and 3.07 but both give me the same results.
Re-flashing any recovery (I've used stock and TWRP) both get it back to where it boots into CM12.1.
Any guidance on how I can get this thing back to a stock Touchwiz ROM with OTA updates so I can sell it on Craigslist or Swappa or something? I'd appreciate anything, I'm a loss here!
Nevermind! Thank goodness I found an old nandroid backup on an HD and it worked.
numero9 said:
Nevermind! Thank goodness I found an old nandroid backup on an HD and it worked.
Click to expand...
Click to collapse
Any chance you could share your nandroid backup with me? I'm having the same problem getting my S3 back to stock.
numero9 said:
I got an S5 and want to sell my S3 that I've been running CM12.1 nightlies on now for the past year.
I'm having issues though just getting it back to complete stock through various stock TARs I've downloaded. I've soft bricked it a few times but it has bounced back after installing a recovery again in Odin. They're all on the front page of the Sprint S3 Android XDA forum, so it's not like I'm flashing something non-Sprint.
Here's what I've been doing:
I wiped and factory reset within TWRP recovery.
Then I flashed the stock recovery in Odin. That worked just fine.
Go into download mode, tried to flash the Stock NJ2 tar and it fails at aboot. Phone then says: SW REV CHECK FAIL: Fused 2 > Binary 1
I get the 'connect to Kies' error both when powering up and in recovery. Throw it back into download mode, flash stock recovery again. Works fine -- boots in CM12.1 again with no data fresh.
I then tried to flash stock MK3 and it failed too.
I've tried the latest Odin and 3.07 but both give me the same results.
Re-flashing any recovery (I've used stock and TWRP) both get it back to where it boots into CM12.1.
Any guidance on how I can get this thing back to a stock Touchwiz ROM with OTA updates so I can sell it on Craigslist or Swappa or something? I'd appreciate anything, I'm a loss here!
Click to expand...
Click to collapse
Don't try to flash mk3, you will hard brick if you've updated to nd8 or newer. You don't flash stock recovery at all. Just the stock tar in odin. Have you flashed the stock nd8 or nj2 .tar? Those are the ones you should be flashing. Just the stock .tar, nothing else. It has the right recovery in it. You may be messing up flashing stock recovery. Every build has a different version of recovery ,( like nd8 or nj2).
Yeah I flashed both and they didn't work from Odin. I was on NJ2. MK3 just soft bricked me only. Anyway it's a moot point now that I got it working.

SGH-I747 - 4.4.2 Soft Bricked after trying to update

Hi all,
I am new here and I am having trouble with my Galaxy 3 SGH-I747 from at&t
I rooted the phone using KingoRoot and everything was fine.
I used the phone for about a week and decided to update from kitkat 4.4.2 to lolipop 5.0.
I have a micromax phone that is rooted and I didnt have any trouble updating it while it was rooted, so i figured it wouldnt be a problem but when I updated the s3 it said update failed at 94% and started rebooting and got stuck in an update loop.
I searched and searched and tried finding recovery options using odin but I cant find a 4.4.2 stock firmware, and cant find much information on recovering my device.
I am unable to boot in to recovery. I cant find a link for the SGH-I747 to philz recovery, the links all seem to be dead.
I can boot in to download mode.
I want to install a custom recovery via ODIN but i cant find one for my phone.
After I install the custom recovery, how will i know which stock OS my phone is currently at
I appreciate any advice you can give me, thanks.
Use TWRP for custom recovery. CWM and Philz haven't been updated in quite a while. You can get odin flashable tars from here.
Flashing TWRP should get you to working recovery, and you can find the rom zips you need to get back up and running in the development section here.
Unrooted stock will overwrite TWRP with stock recovery upon boot. Depending on how far your phone is getting into the booting process that might happen if you let odin auto-reboot. Your best bet is to uncheck auto-reboot in odin, so it won't restart on you automatically. Upon success remove the USB cable and pull battery. Replace battery and boot straight to recovery by holding home+vol up+power until you see tiny blue text in the upper left corner then releasing.
Thankyou! i was able to install the recovery by TWRP.
I just need to figure out what firmware to install and where I can get it... I was on kitkat, I tried to update to lollipop but it didnt work. My phone is bricked so I dont know how i would see the firmware version on it.
I really just want any kind of stable firmware that is rooted. Any ideas where I could find one? I'm trying to sift through the forums
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
audit13 said:
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
Click to expand...
Click to collapse
I appreciate all the help - It seemed really hard because I was finding roms and flashing with ODIN but it always failed TWRP is giving me results. I flashed slimkat and got my phone working again! the only problem is my sound is a bit junky, idk why.
I plan on trying out Octos - M, because I heard marshmallow OS has a lot better battery life among other things
If i upgrade to a custom marshmallow OS, is there any coming back to a former custom OS like 4.4.2? or is it a permanent upgrade?
Do you guys recommend any custom OS? I need something stable, that uses the resources efficiently.
Before flashing additional ROMs, make sure the phone is running the latest bootloader and modem.
To verify the installed bootloader and modem, install the Samsung Phone Info app from the Play store.
With a custom ROM, you can flash from one to another, usually without any issues as long as you perform a complete wipe (system, data, cache) before flashing a new ROM. If you are upgrading an existing custom ROM with a newer custom ROM (e.g. CM12.1 2016-01-01 nightly to CM12.1 2016-01-02 nightly), you can just flash the updated ROM over the existing ROM.

Categories

Resources