Phone is bricked bad, please help! - Sprint Samsung Galaxy S7 Questions & Answers

Alright, so I have an S7 that I bought off of ebay, it was originally sprint, but I use it on Metropcs.
Today, I attempted to Odin root it and it got me stuck in a "Galaxy s7" boot loop. As a result, I looked for the stock, which also put my in a "Recovery booting" loop. Now I don't know what to do. Recovery mode does not work. The only thing I can do is go into download mode.
Some notes: I have/had nougat on it, don't. I wanted to use smart switch, but it needs a serial number, and when I tried to find mine using the IMEI from the download screen to find mine, it said it couldn't find the Serial, so I'm just going to assume it's a fake S7.
If anyone can help at all, or even have an S7 serial, please let me know. I've tried several of the main threads for sprint with the 2.2gb stock AP/CP/CSC, and none of them worked, they all result in boot loop.

View attachment 4059711

Use Odin 3.12.3 from here: https://drive.google.com/drive/folders/0B1BCqa80fJFCNHAyamhvR2ZpZkE?usp=sharing
Assuming you were on the PL6 firmware, use this to get the PL6 firmware: https://drive.google.com/file/d/0B1BCqa80fJFCZk9odGhpQ256d2s/view?usp=sharing
Grab the pit file from here: https://mega.nz/#!EIxXEKoC!-2Rf4ZsDcm4q-By1-C8kgmf47GLcsr_5rqsZ90EnFME
Open odin and click pit on the side tab.
Put the pit file in its slot.
Put the BL,CP,CSC, and AP files in their corresponding slots.
Start it and wait.

Related

Stuck on boot screen after Stock Rom Flash

Hi, im selling my S5 so wanted to unroot it and put the stock Rom back on it.
So using Odin 3.12 I have put the phone into download mode, added the .tar file to the AP part of Odin and hit start. I get a pass and the phone reboots, then states it is sorting out the App's, then it reboots again and just sits on the Samsung screen.
Can anyone help me? I've obviously gone wrong some where.
Opened Odin as Admin, think that may have been the issue as all working fine now, or 3rd time a treat, whop knows!!

Recovering from FRP Lock, did I brick my phone?

Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.

Samsung Galaxy Note 4 System software not authorized by ATT has been found

Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
vmmessage said:
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Grab latest firmware for N910A from here
https://androidfilehost.com/?fid=745425885120746376
Make sure samsung usb drivers are properly installed on your pc before you begin.
STEPS
1 Download odin and Firmware and Extract it.
2 open odin tool and upload firmware in AP slot.
Odin can take up to 5 minutes to upload firmware so be patient
3 put phone into download mode
4 connect phone via usb cable and hit start.
5 After FLASH once odin shows pass boot into stock recovery by pressing 3 button combo volume up+ home+ power.
6 in recovery do wipe cache+ wipe data factory reset.
7 reboot system and wait 10 to 5 minutes.
DONE
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Thanks
Thanks for the reply! Great! I will try that - very hopeful
tattmann said:
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Click to expand...
Click to collapse
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Trex888 said:
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Click to expand...
Click to collapse
in my case, whoever flashed my phone flashed an f file instead of the v file. It lost the imei and would not recognize a sim card. I tried flashing original firmware but the imei was still gone. The ONLY thing that saved mine was to find the correct pit file and flash it before firmware. It fixed my issue and got me back up and running. every original fw flash for me failed until I flashed just the pit. I cannot explain why the original fw included in the odin package would NOT work. Hence the statement of "you may need to" instead of "you will have to".

Samsung Tab 4 8.0 (T337T) stuck at T-MOBILE boot up screen.

My son no longer uses his Tab 4 8.9 T337T tablet.
I was able to root it using CF Auto Root.
But, the TWRP recovery that was made for it might had messed up the tablet.
It boots up as far as the T-Mobile screen.
I found the T337T firmware to use with ODIN and I can get to download mode and the tablet is recognized by ODIN.
However, when I go to place the files into ODIN, the program goes to eventually a not responding state.
I had encountered a Set Warranty Bit: Kernel issue.
Amy suggestions on how to fix this would be appreciated.
Also, is there any way for me to change the firmware to a wifi-only model firmware?
Looks like I figured it out after trying a half dozen options...
pit file could yuo have it

Root attempt fail, "kernel is not Seandroid" bootloop.

Bought a Galaxy S7 Edge today from a coworker, SM-G935F, Verizon variant (as far as I know. She bought it brand new and used it on Verizon.) First thing I tried to do was root it using this method -- https://theunlockr.com/root-samsung-galaxy-s7-s7-edge/
(basically used Odin to flash Samsung_G935x_QC_Rooted_BOOT.TAR)
Got a "Pass!" message in Odin, rebooted the phone.
Was greeted with a pretty red-colored message on the top left, "kernel is not Seandroid" followed by a continuous bootloop. Would automatically shut off on its own, etc. Had to boot into recovery to actually power it off. (Still stock recovery, by the way)
Anyway. Googled the error, didn't seem like a big deal with so many results and "Solved" also being prominant. Tried to revert back to the stock firmware and got this in Odin's log:
<ID:0/003> Re-Partition operation failed.
Came across another post suggesting to un-tick the "re-partition" option in Odin, which it already was/is. Now I'm kind of lost on what to do. Came across one thread suggesting that the firmware on my device doesn't match the one that I downloaded which.. I have no idea how to check that given I'm unable to even boot the device. I do recall seeing 2017 briefly when scrolling through the build/kernel section, possibly December 2017 if my memory serves me correctly.
Another thread suggested something about flashing a .pit file.
Does anyone know I how I can get this back up and running? Preferably rooted?
Thanks much in advance!
- D
..

Categories

Resources