I restored my phone to factory default recently, with the intent of moving on to a new Cyanogenmod version. After the factory settings were restored, it took an OTA update to 4.1.2. I then tried following the guide on androidable to root it (would post the link, but apparently newbies can't)
After trying and failing several times to flash the VRALEC bootchain to my phone (I am not sure why it failed, Odin just gave me an error message every time I tried), I decided to go back to factory default again, thinking 4.0.0 would accept the VRALEC bootchain and that 4.1.2 might be the issue, but after flashing the stock image again I get the yellow triangle of death.
I have since tried flashing the VRALEC and VRBMD3 bootchains, tried flashing clockworkmod recovery, and though the phone appears to take the stock image and VRBMD3, I can't get past the yellow triangle screen on startup. Because of this, I can't check to see if USB debugging is still enabled, and I can't access the phone memory to attempt to delete whatever software is causing the issue.
Is anybody able to help me?
UPDATE: I followed the entire guide here: http://forum.xda-developers.com/attachment.php?attachmentid=1190002&d=1341959095
I successfully flashed VRALF and Root66, but VRALEC would still not install. While the rest of the process transpired as described in the guide, the end result is still giving me the yellow triangle of death.
UPDATE 2: When trying to flash VRALEC, this is the output message I get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could you post exactly what's on your screen when you just boot into download mode? Secondly, are you absolutely positive that you accepted OTAs up to 4.1.2? Any chance you accepted 4.3?
Sent from my SCH-I535 using Tapatalk 4
Securitom said:
I restored my phone to factory default recently, with the intent of moving on to a new Cyanogenmod version. After the factory settings were restored, it took an OTA update to 4.1.2. I then tried following the guide on androidable to root it (would post the link, but apparently newbies can't)
After trying and failing several times to flash the VRALEC bootchain to my phone (I am not sure why it failed, Odin just gave me an error message every time I tried), I decided to go back to factory default again, thinking 4.0.0 would accept the VRALEC bootchain and that 4.1.2 might be the issue, but after flashing the stock image again I get the yellow triangle of death.
I have since tried flashing the VRALEC and VRBMD3 bootchains, tried flashing clockworkmod recovery, and though the phone appears to take the stock image and VRBMD3, I can't get past the yellow triangle screen on startup. Because of this, I can't check to see if USB debugging is still enabled, and I can't access the phone memory to attempt to delete whatever software is causing the issue.
Is anybody able to help me?
UPDATE: I followed the entire guide here: http://forum.xda-developers.com/attachment.php?attachmentid=1190002&d=1341959095
I successfully flashed VRALF and Root66, but VRALEC would still not install. While the rest of the process transpired as described in the guide, the end result is still giving me the yellow triangle of death.
UPDATE 2: When trying to flash VRALEC, this is the output message I get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you use the bootloader option when you tried to flash the Boot chain VRALEC. Don't use PDA option.
buhohitr said:
Did you use the bootloader option when you tried to flash the Boot chain VRALEC. Don't use PDA option.
Click to expand...
Click to collapse
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1
Securitom said:
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1
Click to expand...
Click to collapse
I hate to tell it to you but that's the latest 4.3 VRUCML1 software. Download mode for 4.1.2 and older only has (notice what is missing):
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
You'll need to do this soft brick method to recover. Since you're on 4.3, you can not flash a custom recovery, custom rom/kernel, nor downgrade your software via Odin to anything except 4.3.
Securitom said:
I tried it both ways, no results on either.
I confirmed that I didn't get 4.3 because I checked in the "about phone" right after I did that.
Download mode screen shows the following:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWAEV: 1
Click to expand...
Click to collapse
What Odin version did you use? Try different Odin version see if it helps. http://forum.xda-developers.com/showthread.php?t=2189539 Also reboot your PC to start fresh. If still not working then try to reflash with Pit file and MF1 full stock rom using Odin.
SlimSnoopOS said:
I hate to tell it to you but that's the latest 4.3 VRUCML1 software. Download mode for 4.1.2 and older only has (notice what is missing):
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
You'll need to do this soft brick method to recover. Since you're on 4.3, you can not flash a custom recovery, custom rom/kernel, nor downgrade your software via Odin to anything except 4.3.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU! You brought my phone back from the dead!
So I'm stuck only using the stock firmware for the rest of the phone's life? Unfortunate, but at least it's not bricked anymore.
Securitom said:
Thank you, thank you, THANK YOU! You brought my phone back from the dead!
So I'm stuck only using the stock firmware for the rest of the phone's life? Unfortunate, but at least it's not bricked anymore.
Click to expand...
Click to collapse
My pleasure but all of the thanks is owed to @ThePagel. Make sure to drop by his soft brick thread (the one that worked!) and express your success! I feel the more people that express their success there, the less fear down the road someone else may have with the method. :highfive::good:
As of this moment, all anyone knows is that you're stuck on TW 4.3 unless a tool is ported to allow custom roms/kernels. You can only root 4.3 using Saferoot which is linked in our TW 4.3 discussion thread. You can be sure if any big developments on cracking 4.3 open will be covered there.
Related
I did the verizon pushed update to 4.4.2 today on my SCH I535 S3 which was totally stock with encryption. After the install finished "upgrading apps" it then did a re-boot and asked for my encrypt pin then showed the outline Andy. Then after a couple of vibrations it re-boot again and will continue this cycle until battery is removed. After sitting on the phone for several hours and conversing with Samsung and Verizon they pointed me to Samsung Experience in a Best Buy and if that doesn't work I have to send it to Samsung for re-flash. They said they couldn't get their software to recognize my phone. The guy there recommended using odin to download a stock rom.
I have downloaded odin 3.07 and have downloaded a 4.3 stock rom. I set up odin with auto reboot and F. reset time checked and nothing else. I select the .tar.md5 in the bootloader and here is my odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUCNC1_I535VZWCNC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECURE BOOT: ENABLE
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL : Found 2 > Binary 1
Please tell me how to recover my phone. I am new to this so give me detail please.
I believe since u pushed the 4.4.2 ne1 update u need to Odin the 4.4.2 ne1 tar file, not the 4.3 file
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
4theluvof2 said:
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
Click to expand...
Click to collapse
No problem!! Glad it worked, hit that thanks button if you don't mind!
SCH-I535
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
hammadsalik said:
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
Click to expand...
Click to collapse
No I didn't get the 4.3 working. I did get the 4.4.2 working though. I am not sure how exactly you'd revert back to an older version, Sorry.
So I decided to try and root my SM-P900. Everything I read online said it was fairly easy to do. Download Odin 3.07 - 3.09, Download the samsung usb drivers, boot into download mode, plug tab in, put in the CF-Auto-Root md5 and off you go. I get a bar that makes it a quarter way accost and then a bunch of red dotted lines come down the screen and a few minutes later Oden gives me a Fail! This is my first adventure into rooting and its seemed to have gone horribly wrong and I need some help. Right now I'm downloading what I think is the stock firmware and will be trying to push that though Odin (P900ueu1anc5). What am I doing wrong and am I doing the right thing to fix it?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Originally Posted by Bizack View Post
1st thing. When you root your tab knox gets tripped. no way around this. So if this is a deal breaker, step on it and take it back. you will not get root love however.
If you do want Root, knox is tripped so why not? Follow these steps.
1. charge your tablet.
2. Down load these files.
Recovery Boot img nb3
TWRP Custom Recovery
Stock NC5 Firmware
CF-AutoRoot (go to His Post in General Section)
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
When that is done you will be back to stock, original just like you bought it.
Now boot back in to download mode and this time you are going to flash the NB3 recovery image tar... same place in ODIN as before. ( uncheck reboot in ODIN)
When that completes, disconnect your tablet and boot it back into download mode.
When you are back in Download mode, then you can safely flash the CF-AutoRoot.... (leave checks default and flash it in same slot in ODIN.
Finally, when that reboots, go back into odin and flash the custom recovery and then you will be able to boot into recovery and make a back up, (always good to make a back up) you can restore back to point in time. (that you made the backup.)
after you are all done, you can get Xposed installed and tweak the hell out if your rom. At minimum install Titanium Back up and freeze all of the knox apps.
Click to expand...
Click to collapse
Did this, got it back to stock. Letting it juice up seeming how it only has 28% battery life left before I try and press on. Bizack, I don't know who you are man but I owe you a beer ( more like a case).
Read this thread. http://forum.xda-developers.com/showthread.php?t=2761352
dodo99x said:
Read this thread. http://forum.xda-developers.com/showthread.php?t=2761352
Click to expand...
Click to collapse
Yup, thats where I found my answer. Thanks!
I do have another question now that I'm rooted. Im trying to use titanium back up and it wants me to tic the "Unknown Sources" box. Where is it in settings?
ZeroXephon said:
I do have another question now that I'm rooted. Im trying to use titanium back up and it wants me to tic the "Unknown Sources" box. Where is it in settings?
Click to expand...
Click to collapse
Settings - General - Security
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Flash the latest Firmware .tar file with ODIN
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
Download the latest firmware for your Galaxy tab 2.
Use odin to Flash the file.
This is the method i always use whenever i get into some type of trouble. However in my case the open recovery or philz recovery method is useless. !!!
I download last ROM P5113UEBLH3_HOME.tar.md5
I tried to install with Odin, at middle of proccess, fail:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do?
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Samsung Galaxy Tab 2
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Galaxy Tab 2 Q&A, Help & Troubleshooting
Good luck!
Is tab rooted?
Not mentioned in op.
Without root flash will fall and you get stock recovery.
Pp.
Root?
Root, no was rooted.
Roby007 said:
Root, no was rooted.
Click to expand...
Click to collapse
Don't know what this means?
But check your root, it may be borked.
Use root checker from play store.
Pp.
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
I'm experiencing this exact issue, however it's with the LTE version of this tablet, model # SGH-I497.
It should be noted, starting with a stock tablet without root, I've TWRP'd + restored a "master image + rooted" backup on many of these same tablets in the past, all without any issues whatsoever.
The TWRP I'm using is an unofficial build by @tselling, filename recovery_twrp2.6.3.0_tselling.tar.md5 (can't remember which thread I found it in exactly)
Now, no matter what I do, I can't replace the Stock Recovery. Tried uninstalling and reinstalling the drivers (Samsung USB v1.5.14.0), disabled and re-enabled USB debugging, multiple flashes of the recovery.tar.md5 via Odin v1.85, different USB cables and USB ports on my computer, etc. I even tried a Factory Reset using the Stock Recovery, and doing everything again. This particular tablet has given me more trouble than the 10+ I've done in the past couple weeks.
Right now I'm just downloading this firmware from SamMobile, and I'll try the instructions listed at the bottom of that page. Will try using Odin 3.09 as instructed.
Here is the most recent Odin report I received after my latest attempt at flashing the recovery:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery_twrp2.6.3.0_tselling.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
---------- Post added at 12:44 PM ---------- Previous post was at 11:47 AM ----------
So I tried flashing the stock firmware, no luck. This is the report I got from Odin:
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I497VLAMJ2_I497XACAMJ2_I497VLAMJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sbl1.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If it helps, while in Odin Mode my tablet says that Qualcomm Secureboot is ENABLED. It also displays a "Secure Check Fail: sbl1" message after the flash failure.
Anybody have feedback/fixes for this?
I am unfortunately still stuck
Also of note, my previous successful attempts on these tablets never added to the flash counter, i.e. it always remained at 0.
I checked this morning on the tablet that's giving me so much trouble, and it counted each one of my 6 unsuccessful attempts.
I got TWRP to stick!
@Roby007
MAJOR UPDATE - after racking up a healthy 10 on my flash counter, I finally got TWRP to work!!!
My SGH-I497 has just been sitting on my desk since my original post, completely Stock Samsung and non-TWRP'd. Today, I decided that I would give it another shot.
What I did, step-by-step:
1. Settings > ensure that USB debugging is enabled > ensure that when using Minimal ADB and Fastboot that "adb devices" returns the Device ID > disconnect device's USB cable from PC.
2. Right click on Odin3 1.85.exe file > Run As Administrator > click PDA option and select twrp2.6.3.0.tar.md5 recovery file.
3. Power the device down > boot into Odin/Downloading Mode using Power + Volume Down buttons then Volume Up button to continue > reconnect device's USB to PC and ensure that device gets "Added" in Odin.
I repeated above process four times, each time with a slightly different iteration, detailed below:
Iteration #1 - USB Port 1 with Auto Reboot checked and F. Reset Time unchecked
Iteration #2 - USB Port 1 with both Auto Reboot and F. Reset Time checked
Iteration #3 - USB Port 2 with Auto Reboot checked and F. Reset Time unchecked
Iteration #4 - USB Port 2 with both Auto Reboot and F. Reset Time checked
Despite receiving no errors and Success/Pass messages each time, Iterations #1-3 did not work - I still had the Stock Recovery after each flash.
Iteration #4 however was successful, and I finally have TWRP on this device! I wasted no time in restoring my carefully-crafted master image.
I really hope this post helps you out - I know from firsthand experience how frustrating this can be.
(Apologies if I'm keeping this thread alive unnecessarily, however it's proving very useful for documenting my ongoing challenges with this TWRP-not-sticking issue. Hopefully someone else will find it useful as well.)
MAJOR UPDATE 2
I encountered the same "TWRP not replacing Stock Android Recovery" issue today, this time with a different device, a Samsung Galaxy Tab 2 10.1" tablet (model # GT-P5113, WiFi-only).
I tried the method that worked for me above, i.e. changing the checkbox options in Odin and switching USB ports/cables. 16 flashes later on the counter, and still no TWRP.
After doing some more research, I came across this post by @Android-Andi. Following the steps, especially numbers 9-14, resulted in a successful TWRP flash. I actually unchecked both Auto Reboot and F. Reset Time, waited 2-3 minutes after Odin's "Success/Pass" message, then disconnected the USB cable and booted directly into TWRP Recovery from there.
I also found this guide for the S4, although the steps that refer to Odin appear to be relevant for any Samsung device. Right after Step 7, there is instruction that follows a similar process outlined above, however with an added battery pull for good measure.
I have looked everywhere for a solution to this problem and found a few posts refering to similar situations but not once did I find an answer that worked. I will go into as much detail as I can about what caused it and what I've tried so far. 6 hours of failed attempts and I've made absolutely no progress whatsoever.
Before I Begin:
I have flashed different firmwares and ROMs to my G870A over the last couple years and occasionally ran into a soft brick here and there but never had any issues recovering with ODIN or a factory reset. I'm slightly familiar with the process.
-Installed and reinstalled Samsung drivers including the ones provided with Kies.
-Running ODIN as Administrator
-Using stock firmware files I have saved in the past that worked 100% of the time
-Factory reset/wiped cache
-Using the USB cable provided by Samsung
-Running Windows 7
-Service is AT&T
How I Bricked It:
It's been a year since I last did a major flash so I don't remember all the specifics but I believe I installed the 5.0 update from stock and applied the ROM file G870A_OC5_Stock_Rooted_ROM.zip and left it at that. It ran perfectly fine until I unrooted via SuperSU as I no longer needed root access. Immediately afterwards the app crashed and refused to open so I rebooted the phone. I did not apply any updates but I found myself stuck on the AT&T logo. I waited 15 minutes and nothing happend. Booted into recovery and factory reset/wiped the cache. Booted up again and waited 15 minutes at the logo. Nothing.
What I've Attempted So Far:
-Flashing G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 with Odin.
Results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-Flashing the original ROM I used to root the device: G870A_OC5_Stock_Rooted_ROM.zip. Same results.
-Flashing 2 other stock firmware files including one from sammobile. Same results.
-Tried a different version of Odin
-Tried to connect with adb from the command line. All commands result in error.
-Samsung Kies fails to detect the phone
Bootloader Screen When Attempting Flash:
ODIN MODE
PRODUCT NAME: SM-G870A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRENTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Recovery Screen Firmware Version:
Android system recovery <3e>
LRX21T.G870AUCU1BOC5
I would really appreciate any kind of help resolving this problem and retrieving access to my phone as its WAS in great condition. At this point I no longer care about tripping KNOX. Let me know if you need anymore information as I probably forgot something.
Nothing at all? I had to resort to calling the AT&T service store, Samsung support in Best Buy, as well as a cell phone repair place. One lady **** herself, one referred me to the Google search engine, and cell phone repair said XDA was a forum for meeting up with local software engineers. If anyone could refer me anywhere more specific then Google.com I would really appreciate it. Thanks.
Hi,
Try posting your question here:
http://forum.xda-developers.com/sprint-galaxy-s5/help
The experts there may be able to help.
Good luck!
Samsung Galaxy S7 (SM-G930T) T-Mobile
Info on ODIN Download screen
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: On
WARRENTY VOID: 0x0
QUALCOMM SECUREBOOT: Enabled
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: Enabled
I have referenced the guide I followed. GUIDE. I followed all the instructions. After root I used the Debloater and my phone was incredibly slow and inefficient. So, I used the fix V15. Yet again, slow, hot and a whole host of problems. So, I follow the unroot guide. I continued encounter this error on odin when attempting to unroot.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And this error on my phone:
Code:
SW RV CHECK FAIL: [system]Fused 3>Binary 1
After trying at least 4 different AP's
Code:
TMB-G930TUVS2APB8-20160317155535
TMB-G930TUVU2APC8-20160402115527
TMB-G930TUVU1APB6-20160310103828
TMB_G930TTMB4BQB1
I got frustrated and Held any button I could to get that stupid screen to go away. I was met with "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software. So, I go to do that. And the smart switch software does not support my phone. So, I boot into Recovery mode Wipe Cache, Wipe everything I can and try to reboot and I can only go from DOWNLOAD mode to recovery mode. I read somewhere on here that you can't Rollback firmware so I try the newest firmware and maybe that will work. I encounter no issues in ODIN and no issues on my phone Once my phone reboots it goes to the Samsung Galaxy S7 splash screen with the Unlocked lock and doesn't do anything past that. So I try to boot to recovery mode and that's when I get caught in a loop. My phone went from a flashing "Recovery booting" then if I tap a bunch of VOL UP/DN HOME and POWER combinations It will go to splash screen and flash the splash screen numerous times. I can now get it back to Download mode after messing around with it. But I have no idea what I need to do.
If I need to provide any more information let me know.
How Do I mark this as solved? I Used ODIN to update my bootloader to the newest version. then used the most current AP CP and CSC there is. It's booted up and installed. Now I'm just restoring and Going to restart to make sure everything is working correctly.