Develop Bugs

[Q] Soft Bricked my i747- HELP!

So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?

exarkun631 said:
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
Click to expand...
Click to collapse
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III

yeah I tried that
BWolf56 said:
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
Click to expand...
Click to collapse
So I am able to boot into recovery but it's the stock recovery, not the one I intalled after root.
I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.

exarkun631 said:
So I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
Click to expand...
Click to collapse
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).

what about...
BWolf56 said:
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
Click to expand...
Click to collapse
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.

exarkun631 said:
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
Click to expand...
Click to collapse
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com

Strange
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
BWolf56 said:
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Click to expand...
Click to collapse

lol
exarkun631 said:
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
Click to expand...
Click to collapse
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.

exarkun631 said:
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
Click to expand...
Click to collapse
Did you do a clean flash? Sounds like you didn't factory reset.
Make sure you backup your apps before doing so if you wanna keep your app data.

Bootloop on grey battery icon, doesnt power off and unable to flash custom roms

So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.

Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk

Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'

Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?

Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk

Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.

[Q] Help me fix this phone...

Some background here. My son has screwed up his phone.
S3 i747 AT&T
was rooted using Kingo Root.
No custom ROM.
He tried to update to 4.3 OTA a couple days ago. Now it will boot to the Galaxy SIII logo then go black. I can get to ODIN mode and stock recovery mode. I am just at a loss as to what to do next. Reading the forum has gotten a little overwhelming as to exactly what I need to do to get it back.
Can someone give me some instructions as to what to do?
If you need more info I will check this thread and provide it. As far as any specifics that can be found in the 'About phone' menu, I cannot remember what the specs were so that isnt possible for me to provide.
Thank you very much for any help.

First of all, don't panic. If you still have download mode and recovery working the phone is very fixable. Second of all, don't start flashing stuff willy-nilly. You have to be a little careful with this phone once it is on 4.3 and later firmware, and from what you've posted it is not entirely clear how far the update proceeded.
I don't think download mode or stock 3e recovery will tell you what firmware your phone is running, and it is important to know that before proceeding. Do you see anything about "warranty bit" when you're in download mode? If you see warranty bit then you successfully updated to a 4.3 (or higher) bootloader. Definitely don't try to use Odin to flash any full firmware updates if you see warranty bit in download mode. It would probably just fail, but if it actually proceeded it would attempt to downgrade the bootloader and hard brick the phone.
At this point, my recommendation is to use Odin to flash the latest TWRP recovery on the phone. Just in case, don't let the phone auto-reboot after flashing with Odin, uncheck everything but f.reset time in Odin. Upon success unplug the USB cable and pull the battery. Replace the battery and boot straight to recovery by pressing and holding vol up + home + power and releasing when you see the blue text in the upper left that says recovery booting.
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Another thing you can do with the phone booted in TWRP is connect it to a PC via USB and transfer files from the phone to the computer in case anything needs backed up. The PC should automatically mount the phone as a media device. It might end up being necessary to format the phone's internal storage to get it booting a ROM normally again, so this wouldn't be a bad pre-planning step.

How do I download the recovery file from the TWRP link you provided? I cant really tell how to download but I can see the file I need.

Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3

peckaldee said:
Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3
Click to expand...
Click to collapse
Since you see warranty bit, you're definitely on a 4.3+ bootloader. Do not download and try to flash the full firmware file from sammobile.com to restore the phone. It would either fail or or hard brick the phone if it did proceed due to attempting to downgrade the bootloader.
Download this TWRP https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar. Flash the tar file using the PDA menu from Odin. Most people recommend Odin 3.07 for use with this phone. If you've never used Odin before, you'll have to get the samsung USB drivers working on the PC too.
Get Odin and the samsung drivers from this thread if you need them.
It would be nice if you could just restore the phone using Odin, but AT&T never let a firmware past jellybean 4.1.1 be released. And since you now appear to be on a 4.3 bootloader you cannot downgrade.

I will try this when I get home from work in the morning and report back. Thanks for the detailed help!

jason2678 said:
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Click to expand...
Click to collapse
It outputs:
I747UCUFNJ2

I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080

peckaldee said:
I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080
Click to expand...
Click to collapse
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.

jason2678 said:
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.
Click to expand...
Click to collapse
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.

peckaldee said:
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.
Click to expand...
Click to collapse
At NJ2 you seem to have updated to the newest bootloader for the AT&T S3. Never ever try to downgrade it. You're stuck :silly:
enewman rebased his ROM to NJ2 shortly after it came out. Download this one https://www.androidfilehost.com/?fid=24052804347829298

That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.

peckaldee said:
That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.
Click to expand...
Click to collapse
No problem. Happy to help. Hope it works out well for you.

Seriously Stuck!

A couple days ago, I tried to flash my i747 back to stock, but unfortunately it froze at the Samsung Galaxy S III logo, and is no longer accessible. Another mistake that I think I made was I failed to realize that my phone would go back to stock recovery with flashing the stock rom. As a result, I now can't flash any custom rom or recovery due to "signature verification failed" error. Lastly, my phone can't seem to connect to the computer, so I can't use Odin either. When I connect my phone (in download mode) to the computer, an error would pop up saying that "one of the USB devices has malfunctioned"...I already tried to use different USB cables, different computers, update driver, battery pull, wipe data/factory reset, wipe cache, etc...but nothing prevailed. I'm a newbie to the android system, and I would really appreciate any suggestion on how I might get out of this conundrum, and get my phone back. Thank you!

Before you attempted to flash back to stock what ROM were you running?
What bootloader and modem were on your device before trying to flash stock?
Which stock rom did you attempt to flash to your phone?
If you were not flashing an older bootloader than was on your phone, you may need to do a factory reset from the stock recovery and reflash the stock rom. If you attempted to flash an older bootloader than had been on the device, you may need to search the forums for a debrick image with the same bootloader that was on the device before this started.

Before you attempted to flash back to stock what ROM were you running? __Dirty Unicorns 5.1.1__
What bootloader and modem were on your device before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom); does flashing a custom rom change the bootloader/modem? if not, i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash to your phone? Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!

zynl said:
...what ROM were you running? __Dirty Unicorns 5.1.1__
...before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom);
i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Click to expand...
Click to collapse
No, flashing a custom ROM will not change bootloader and modems, but stock ROMs will.
Baseband and modem are the same thing, as is radio (in most instances). Since you had DU running successfully, in all probability your bootloader and modem were both NJ1. Everything I have seen indicates all AOSP and CM 5.x.x and their derivatives must be on at least NE4 bootloader and modem. If you can get into download mode, and their is anything on the screen about "Warranty Bit" you were on a 4.3 or higher bootloader.
Now for the negative; if you were on a 4.3 or higher bootloader downgrading the bootloader will brick the device. Once you are on any of the 4.4.2 bootloaders, NE4 or newer, you must keep the bootloader and modem versions paired. That is: they must both be NE4, or both NJ1, or both NJ2 otherwise you risk bricking the device. (This is why I think your bootloader was NJ1.) More negative is that the 4.1.1 stock rom you flashed contains the LK3 bootloader and modem.
zynl said:
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
Click to expand...
Click to collapse
I am surprised you were able to boot at all after flashing the stock ROM. If you are still able to boot froman external sdcard, flashing a debrick image is what I would suggest next. Once you boot, install a custom recovery and verify bootloader and modem on the device from the recovery terminal if possible. The next step would be flashing the NJ1 bootloader and modem. Two threads for reference:
http://forum.xda-developers.com/galaxy-s3-att/general/solution-hard-brick-fix-amazing-t2962611
http://forum.xda-developers.com/showthread.php?t=2549068
If this doesn't work you may be looking needing a jtag service. Worse than that would be a new motherboard for the phone.

Hello
To me it look like you get stuck in boot. First you will need to download correct ATT ROM. Then you will need to select appropriate option in ODIN. Let me know if you have any question. I will help you out. Guaranteed))

If you are able to boot into recovery and download mode, the debrick sdcard method won't do any good. Not saying to not try it if you want to, but I've never seen it work unless the device is truly hard bricked (totally unresponsive). It's only in those cases that it will even look for the image on an SD.
When you boot download mode and connect to the computer, does Odin show a COM# in the upper left? Does it respond in any way at all?
Also check to make sure kies is NOT installed on the computer. It can interfere with Odin. If you still cannot connect, try an older driver version. (See my sig).
Uninstall the old first. Then install the other version and reboot. Connect the device and open device manager. Right click on the USB device that isn't working and update driver. Try auto if you want, but if that doesn't work select manual. Browse to the Samsung folder in Program files and try selecting it that way. (I can't recall the exact location, but you should be able to find it if you poke around a little).
Hope that helps.
Good luck!
Sent from my SGH-T999 using Tapatalk

thanks everyone for helping. after abt a week trying to revive my phone, i finally gave up. recently though, i bought a bricked motherboard for cheap and successfully unbricked it. everything seems to be working fine except i can't switch on the wifi. I already tried wiping cache, factory reset, and even reflashing stock rom (4.3 from samsung) via odin but nothing worked. So, i wonder what could be the source of this? (hardware?.... software??... bc the volume up button also does not work!) and is there something that i can try to possibly fix this? The phone is currently on 4.3, bootloader and modem are both i747UCUEMJB.

Error RP SWREV A3 - Constant rebooting - Unable to reinstall rom

Hi there, yesterday I updated some play store apps and a while later the tablet rebooted, it does it constantly. That is all I did in the past few months, I haven't installed a newer rom for a few months.
In Download mode, I see an error I haven't seen before: RP SWREV A3. I was on Resurrection Remix 5.7.4 (android 6). I tried re-flashing the rom from TWRP but I think it reboots before it completes flashing. I tried flashing with ODIN Stock 4.4 and 5.1.1, it finishes installing but it keeps rebooting at the Samsung logo. I don't what to do since I didn't do anything except update my apps... Please help
Here is the recovery.log:http://pastebin.com/raw/Kt5SDECf

Hey mate
That isn't fun but when I have installed stock Rom's via Odin I too have been stuck in the logo. Usually if you then go into recovery and wipe cache and do a factory reset it usually solves the issue, I would assume you have done this, if not give it a go. Be patient sometimes it does stay on the logo for a few minutes whilst it provisions the ROM, best of luck.

kypreo said:
Hey mate
That isn't fun but when I have installed stock Rom's via Odin I too have been stuck in the logo. Usually if you then go into recovery and wipe cache and do a factory reset it usually solves the issue, I would assume you have done this, if not give it a go. Be patient sometimes it does stay on the logo for a few minutes whilst it provisions the ROM, best of luck.
Click to expand...
Click to collapse
I have no idea what else to do, this my last_kmesg and my dmesg and the recovery.log if any one knows please help, the tablet switches off during install in TWRP and `adb`. I get the Error `RP SWREV A3` in Download mode.

malim20 said:
I have no idea what else to do, this my last_kmesg and my dmesg and the recovery.log if any one knows please help, the tablet switches off during install in TWRP and `adb`. I get the Error `RP SWREV A3` in Download mode.
Click to expand...
Click to collapse
You haven't stated if you get the error flashing a stock ROM, irrespective I have found some info on other forums and Google, see below:
https://forum.xda-developers.com/showthread.php?t=2671068
http://forums.androidcentral.com/t-...elp-please-odin-mode-bootloader-rp-swrev.html
https://www.sammobile.com/forum/showthread.php?t=14425
http://www.ultratechy.com/stuck-on-downloading-do-not-turn-off-target-problem/
https://www.tapatalk.com/topic/3392...hing-phone-that-boots-into-download-mode-only
I think you should try a stock firmware and I think it a bootloader issue which you can get past with your original stock ROM. What was the last factory ROM you had 4.4.2 or 5.1.1? Download a stock ROM and flash with an Odin version above 3, good luck.

kypreo said:
You haven't stated if you get the error flashing a stock ROM, irrespective I have found some info on other forums and Google, see below:
https://forum.xda-developers.com/showthread.php?t=2671068
http://forums.androidcentral.com/t-...elp-please-odin-mode-bootloader-rp-swrev.html
https://www.sammobile.com/forum/showthread.php?t=14425
http://www.ultratechy.com/stuck-on-downloading-do-not-turn-off-target-problem/
https://www.tapatalk.com/topic/3392...hing-phone-that-boots-into-download-mode-only
I think you should try a stock firmware and I think it a bootloader issue which you can get past with your original stock ROM. What was the last factory ROM you had 4.4.2 or 5.1.1? Download a stock ROM and flash with an Odin version above 3, good luck.
Click to expand...
Click to collapse
Thanks for your reply,
With a stock Rom, I am able to install completely with ODIN but it still keeps on rebooting, I installed 4.4 and 5.1.1 from my region and other regions, even the last stock one I installed (ODIN doesn't fail, in fact it shows that it installed correctly). Through Recovery, it switches off before the install is complete, and then it keeps rebooting just like when I try with a stock Rom

malim20 said:
Thanks for your reply,
With a stock Rom, I am able to install completely with ODIN but it still keeps on rebooting, I installed 4.4 and 5.1.1 from my region and other regions, even the last stock one I installed (ODIN doesn't fail, in fact it shows that it installed correctly). Through Recovery, it switches off before the install is complete, and then it keeps rebooting just like when I try with a stock Rom
Click to expand...
Click to collapse
Mate on the stock ROM you say it keeps rebooting, can you bring up recovery? If so you can wipe cache and do a factory default, this may resolve the issue, Failing that if you can get TWRP on it you can try and wipe all files from the system internal storage. Then try and install the stock ROM and try and load it from there.
I think in ODIN too you can wipe the partitions, you can also try that as a last resort.
You can also wipe away the entire internal storage file system in the advanced system settings and start from new with a custom ROM and install these off the SD card.
Good luck