[Q] Need help! Can't unroot/unbrick Galaxy S3! - Verizon Samsung Galaxy S III

So let me start from the beginning;
I have Verizon's Galaxy S3 and had CyanogenMod 10.2 installed on it. After installing CM 10.2, I no longer had 4G/3G connection. After some research, I had discovered that it had to do with my device's APN. Anyways, what I found online was to unroot, and flash to a stock ROM, and wipe/reset factory settings, etc.
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop. After pulling the battery, I tried flashing the image again in ODIN, but the same thing happened, I figured this is what was known as a "soft brick". I followed another guide on here to unroot/unbrick the phone, which had me download another stock rom (stock.vzw_root66), as well as VRALEC.bootchain.tar.md5, and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5. Following the instructions had me PDA flash the VRALEC-bootchain.tar.md5 first, followed by the bootloader, and finally the stock image. However, I continued to get "FAIL!" after attempting to flash the VRALEC-bootchain.tar.md5.
Following another guide, it said to just try flashing the stock.vzw_root66 file, which I had done, and it succeeded, however, after the phone reboots, it says that I am using unauthorized firmware on my device, and to bring my phone to the nearest Verizon store.
Now, I have no idea what to do.
I'm using ODIN3 v3.07
Both the VRLEC.bootchain.tar.md5 and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 fails when trying to flash them onto my phone, and I don't want to proceed from here unless I know how to fix it, as to not damage the phone any further. Any help would be greatly appreciated!
The phone still boots into a stock recovery, and can still enter download mode. At this point, I just want my phone completely stock, as if I had just purchased it.

You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?

Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2

BattsNotIncld said:
You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?
Click to expand...
Click to collapse
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
BadUsername said:
Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!

I'm pretty sure those download mode stats you have are from the new bootloader. When you said this:
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop.
Click to expand...
Click to collapse
... I'm thinking you flashed a stock 4.3 ROM in ODIN and therefore locked your bootloader. This would also explain the yellow triangle when trying to flash root 66 afterwards. If I am correct, the good news is all you have to do is flash a stock 4.3 ROM to get back up and running. The bad news is you re-locked your bootloader and are stuck with TouchWiz.

WildWildWest42 said:
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!
Click to expand...
Click to collapse
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're a life-saver! I just did this and my phone now works again! I couldn't thank you enough!

Related

[Q] Going back to stock Directions step by step

I am rooted and have cwm on my phone, also I have ice cream sandwhich Rom. Step by Step how do I go back to Stock, thankyou to anyone that can tell me.
There are so much stuff that isnt really clear on going back to stock. If anyone can explain step by step and If they have the file and can upload the stock rom thankyou
having problems reading the sticky that already explains how to do this???
The TAR ODIN sticky thread? Be careful, it is not clear whether or not that method will trigger your flash counter. So far I have not found a clear explanation of how to return to stock without triggering the flash counter.
Flashing stock firmware will not trip the counter. You need to download odin here http://forum.xda-developers.com/attachment.php?attachmentid=725858&d=1316556218
Then the stock tar found here http://k0nane.info/rom/SGH-I727-UCKJ2-k0nane.7z
Download and install the program 7zip. Unzip the. 7z file you downloaded above.
Open odin. Click pda and select the stock.tar file you unziped. Then start odin.
Make sure re-partition is not checked.
And make sure you have the usb drivers for the skyrocket installed.
You also must have your phone in download mode to use odin.
^^ Should be added to a stickie, as the TAR ODIN thread gives a different solution for going back to stock that does trip the flash counter.
Can you verify that using odin for the stock tar does trip the flash counter? I have read using odin with a stock tat does not
only thing that SHOULD trip your counter is a custom kernel flash from ODIN....
this is why I started this question and yes I saw the sticky but everything is so unclear I was hoping without getting to technical someone could explain it in a simple way without confusion. But I was wrong
Thank you pirate and thats what i thougt. Ok so the instructions in the reaturn to stock thread are really simple. There not to technical 1. Download Odin 1.85 - see section below. 2. Download the stock TAR for your device - see section below. 3. Extract the contents of odin-185.zip and the 7zip archive. 4. Run Odin3+v1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options. Click PDA and select the TAR you downloaded.
5. Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device. Remove the battery. Reinsert the battery. Hold down Volume Up and Volume Down keys. (NOTE: It may be just Vol Down. Try that first!) Insert the USB cable into your device.
6. You should now be at Download Mode. Click Start in Odin.
That's it! Your device will autoreboot, and your phone should be working properly again.
so you dont have to go in cwm and do a factory reset and delete anything, you can just follow your directions and its good to go?
When you odin the stock tar it erases everything. And takes you back to 100 percent stock
thankyou very much
I have flashed back to stock a few times using Odin and konanes stock.tar and I have never used Odin for anything else and it Does trip the flash counter at least for me it did.
Sent from my SAMSUNG-SGH-I727 using xda premium
niezek said:
I have flashed back to stock a few times using Odin and konanes stock.tar and I have never used Odin for anything else and it Does trip the flash counter at least for me it did.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
geterdone18: you'll have to post back and let us all know if your flash counter tripped flashing the stock tar (as it did for niezek).
I just flashed back to stock, how do you check for the flash counter?
well hold on I just flashed the recovery tar using Odin, it worked fine but for some reason when I go to Odin and try to pull up the stock rom in PDA it doesnt show it there in the folder, does anyone know why it is doing this? And where do you go to check and see if the flash counter was tripped
niezek said:
I have flashed back to stock a few times using Odin and konanes stock.tar and I have never used Odin for anything else and it Does trip the flash counter at least for me it did.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I've used only Odin per the instructions in the sticky to root, go back to stock once then root again with the tar provided in the sticky and can confirm it did trip my counter
i think if you flash the stock kernel in CWM, then flash a /system in ODIN, it wont trip anything. AFAIK, the counter only trips when installing kernels via ODIN/Heimdall
Pirateghost said:
i think if you flash the stock kernel in CWM, then flash a /system in ODIN, it wont trip anything. AFAIK, the counter only trips when installing kernels via ODIN/Heimdall
Click to expand...
Click to collapse
When I used Odin to go back to stock I had a rom installed which I'm sure had a custom kernel so maybe that's what tripped it?

[Q] P6810 Problem! - Won't go to Recovery - Bootloop

Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery
P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.
edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app
All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium

[Q] Status 7 Error flashing Cyanogenmod 11

Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Zackpip said:
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Click to expand...
Click to collapse
Flash the latest @Android-Andi Philz Touch or TWRP recovery and that should solve the problem (I recommend flashing the recovery with Odin or Heimdall.) Status 7 error usually means outdated recovery.
Link to @Android-Andi's recovery thread: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Zackpip said:
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Click to expand...
Click to collapse
What exactly did you do that it did this? Did you attempt to flash the recovery in Odin or Heimdall? If Odin, which version?
Sent from my SGH-T989
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Zackpip said:
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Click to expand...
Click to collapse
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
jrc2 said:
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
Click to expand...
Click to collapse
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Zackpip said:
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Click to expand...
Click to collapse
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
jrc2 said:
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Zackpip said:
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Click to expand...
Click to collapse
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
jrc2 said:
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Zackpip said:
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Click to expand...
Click to collapse
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
jrc2 said:
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Zackpip said:
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Click to expand...
Click to collapse
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
jrc2 said:
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
Click to expand...
Click to collapse
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Zackpip said:
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Click to expand...
Click to collapse
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
jrc2 said:
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did exactly that.
Zackpip said:
Yes, I did exactly that.
Click to expand...
Click to collapse
So it must have been a bad download then. You used Odin v1.87 or what? Also, you should add [SOLVED] to the thread title.
Sent from my SGH-T989

Help! Galaxy amp prime (SM-J320AZ) stuck in bootloop

So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Rororoolz said:
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Click to expand...
Click to collapse
Point to the firmware you downloaded and also which version of odin you used.
ashyx said:
Point to the firmware you downloaded and also which version of odin you used.
Click to expand...
Click to collapse
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
you actually posted right above me in that thread!
Rororoolz said:
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
Click to expand...
Click to collapse
I suggest you flash the entire firmware not just AP.
ashyx said:
I suggest you flash the entire firmware not just AP.
Click to expand...
Click to collapse
Do u happen to know where i can find the rest?
Would i have to re partition it? Because im trying to research and learn, but i was under the impression that AP was the only spot to put firmware
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
seaf0ur said:
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
Click to expand...
Click to collapse
The files say md5 error, binary failed
I think im missing something here
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
johnny.goldy said:
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
Click to expand...
Click to collapse
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Rororoolz said:
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Click to expand...
Click to collapse
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
ashyx said:
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
Click to expand...
Click to collapse
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Rororoolz said:
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Click to expand...
Click to collapse
This probably means you had a newer firmware revision on your device.
ashyx said:
This probably means you had a newer firmware revision on your device.
Click to expand...
Click to collapse
So do i have any options left? Or should i just chuck it into the cornfield
Rororoolz said:
So do i have any options left? Or should i just chuck it into the cornfield
Click to expand...
Click to collapse
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
johnny.goldy said:
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
Click to expand...
Click to collapse
IT WORKED! Omg IT wOrked!
ashyx said:
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Click to expand...
Click to collapse
It wasnt the firmware you said, but thank you so much for the help!
Rororoolz said:
It wasnt the firmware you said, but thank you so much for the help!
Click to expand...
Click to collapse
Doesn't matter it was still revision 3 firmware.
The one linked is the latest revision 3 firmware.

i need help FRP unlocking my Galaxy S7 SM-G930W8

Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Kemako121 said:
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Click to expand...
Click to collapse
Flash stock then log in with your Google credentials
*Detection* said:
Flash stock then log in with your Google credentials
Click to expand...
Click to collapse
well could you please link me the stock of my phone because i cannot find it myself.... i was looking for a while and tried some but now my phone is just stuck on the boot screen..
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
audit13 said:
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
Click to expand...
Click to collapse
thank you a lot but i have another question after i ran a boot.tar from firmware.obi my phone is stuck on the boot logo what can i do to move on and is it safe if i boot the files u sent me with the current state of my phone? also the download will be ages since the speed for non premium is 15kb/sec
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
audit13 said:
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
Click to expand...
Click to collapse
i have tried going into the boot menu for factory reset but no luck the phone just resets,im starting the odin method right now with the thing you provided, also do i fill all the blanks (like the csc,ap and cp?) in odin?
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
audit13 said:
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
Click to expand...
Click to collapse
help when i put in all the things it says: SW REV. CHECK FAIL DEVICE:2 BINARY:1
Odin recognizes the phone? Are you seeing the message in download mode?
audit13 said:
Odin recognizes the phone? Are you seeing the message in download mode?
Click to expand...
Click to collapse
so i managed to get this phone back to its original state when it was frp locked by downloading software from sammobile but it still remembers the google account... i will try to download a older version of android and run that to hopefully get the phone to 6.0.1 or whatever the original version was and try some older ways to frp unlock my phone because the older version will have less security patches. hopefully this works! thanks for the help so far .:good:
I'm not sure that you can downgrade once the phone has been updated.
Good luck.
same here, stuck without solutions. tried pretty much everything found on the internet carefully and taking the time to do it.. but still...
i still need help can someone find a way to unlock my phone?
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
coto39 said:
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
hi could you please link the stuff i need to download in order to to this my phone is SM-G930W8

Categories

Resources