phone fully boots then reboot/bootloop - Sprint Samsung Galaxy S7 Questions & Answers

so my phones on pk1, my phone decided it wanted to update while rooted with the rooted boot image flashed via odin and this is what happens. can i downgrade or reflash pk1 to fix this? i dont want to touch it and render it a paper wait as when my friend gave it to me it was a paper weight only would go into download and recovery said you get it working again you can have it, any options/advice is greatly appriecated, i am unsure what to try, ive been told samsung isnt hard to figure out but i had rendered 3 galaxy s3s paper weights them being a verizon, tmobile and att

Related

[Q] Help! I keep digging myself further into a hole

I have a Samsung Galaxy S4, the Sprint version. I wasn't able to send or receive picture messages and I thought it might have something to do with my APN being wrong (I bought the phone on eBay and had it flashed to nTelos, my provider) but I wasn't able to edit the APN and nTelos was, as usual, no help. So I figured I'd just root it and be able to edit it then!
It was at that moment I stuck my shovel into the soft dirt and started digging.
Essentially, I believe my phone is without an OS at this point. I have tried using ODIN to put a recovery on there so I can at least do something, but now even ODIN is freezing up when I try and flash the Clockwork recovery. I am stuck on the Samsung S4 logo screen and while I can enter download mode I don't think I can enter recovery mode - at least, it hasn't been working tonight. I don't remember everything I've done to my poor phone, but it has to be hurting after the beating I've put it through. I originally tried to root it though I don't think I was successful because the Root Checker said I wasn't, though I'm not sure what I was doing wrong then. Things went downhill from there.
I've read through thread after thread hoping for something that would work, but I've given up trying to use other people's problems to solve my own. This is me saying "Uncle". I require assistance. Let me know what you need from me to provide me with the help I need.
Also - I have ADB on my computer and I think I have a basic understanding of how to use it, but since I can't enter recovery mode I can't do anything other than pat myself on the back for figuring it out. I think my first problem at this point is ODIN. I uninstalled KIES so that's not interfering (and don't even get me started on KIES - I installed KIES and it told me to install KIES3 which told me my device wasn't supported... which is crap because it's running Android 4.3 - or was before I got to it).
Thanks,
If you're sure the phone was on 4.3, then your options are limited thanks to Knox. You can only restore a 4.3 (MJA) based ROM to the phone via Odin, whether it is stock or custom. Easiest giveaway is if you see a line for "Knox" on the Download Mode screen.
At this point you should look in the ROM directory here for a full ROM (xxxxx.tar.md5), either MF9 (4.2.2) if it doesn't have Knox or MJA (4.3) if it does. If you cannot use Odin to put a full ROM on there, then you will need some more serious help.
Odin the stock 4.3 MJA OEM. Will return your phone to a stock unrooted state.
http://forum.xda-developers.com/showthread.php?t=2522810

Did I make jewellery out of my s7 edge? :S

I have the S7 Edge SM-G935F, which is the exynos version I believe.
It starting with unrooting, which boot looped my device. I have tried samsung kies firmware recovery but the download always stopped at a certain percentage saying an error was found in the dowloaded file. I tried to fix it by flashing what I believed was the stock bootloader with odin but that made my problem worse.
It turns on and shows a red coloured screen, and the voice assistant kicks in to babble but seems to not respond to touch at all. I think I can go into download mode, because I've seen a shop assistant get into it when I took it to see if they can fix it. Unfortunately It would cost 230 euros, which I cannot afford. And in case you are wondering, no I didn't buy the phone. I got it as a birthday gift, as I never owned a smartphone before that.
I loved trying out apps and tweaking the phone with root, but unfortunately I wasn't careful enough.
Is there any hope for me? Thanks in advance if anyone could help me out.
EDIT: Thank you to both replies! I did as you said and I downloaded the correct firmware. It seems the one I flashed before was actually incompatible. Everything works now thought, I lost all data but better than having no phone.
LuckIsWithMe said:
I have the S7 Edge SM-G935F, which is the exynos version I believe.
It starting with unrooting, which boot looped my device. I have tried samsung kies firmware recovery but the download always stopped at a certain percentage saying an error was found in the dowloaded file. I tried to fix it by flashing what I believed was the stock bootloader with odin but that made my problem worse.
It turns on and shows a red coloured screen, and the voice assistant kicks in to babble but seems to not respond to touch at all. I think I can go into download mode, because I've seen a shop assistant get into it when I took it to see if they can fix it. Unfortunately It would cost 230 euros, which I cannot afford. And in case you are wondering, no I didn't buy the phone. I got it as a birthday gift, as I never owned a smartphone before that.
I loved trying out apps and tweaking the phone with root, but unfortunately I wasn't careful enough.
Is there any hope for me? Thanks in advance if anyone could help me out.
Click to expand...
Click to collapse
Go to sammobile.com, create an account & download the latest firmware for SM-G935F. Install Samsung Drivers on pc. Boot device into download mode. Extract the downloaded firmware and use odin to flash it.
In case you don't know there are 2 S7 phones, S7(930F) and S7 Edge(935F) and their firmware files are not exactly interchangeable.
I think you might flash s7 firmware on your s7e since red screen is the same symptoms when you flash S7flat kernel on S7 Edge. The fix is easy, just reflash again with the correct file.
Sent from my SM-G935F using Tapatalk

note 4 (N910A) verity error after stock ota update from 5.1.1 to 6.0.1

Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Mal-0 said:
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Click to expand...
Click to collapse
Make sure samsung kies or samsung usb drivers are installed on your pc.
Download stock marshmallow firmware and flash through odin .this method does not require root.
After flashing dont let the phone boot just go to recovery and wipe cache+wipe data factory reset then reboot.
Wait 10 to 15 minutes.
Stock rom link.
https://www.androidfilehost.com/?fid=24651430732238073
Extract file and choose AP tab in odin.
Upload firmware file then connct device via usb cable to pc.
Hit start in odin.
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Mal-0 said:
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Click to expand...
Click to collapse
Thanks for the compliment. you just made me feel like i am a Hercules :victory:
If you want my advice dont ever take ota updates.
Just go to www.sammobiles.com/firmwares and grab latest rom for your model and flash in odin as you did.
Latest rom comes with the same security patch update the 1 comes in ota.
I personally do this way all the time.
Hope that helps and have a good day.

How to bring a Verizon Note 3 back to life?

I found my old Note 3 in a closet and decided I would gift it to my 12 year old as a faux-tablet. I powered the Note 3 up and got to the Verizon flash screen where is just locked-up. I then attempted to go through recovery and factory reset (keep in mind that I am using the stock recovery). I rebooted and still stuck on the verizon flash screen. So what is the trick to get past the boot screen? Personally, I would like to blow away all things Verizon and change to another ROM, but I need to get past this issue. Any pointers would be greatly appreciated!
From where i can see it, u can just flash it with stock Rom or another as u like, cz the other option is what u have tried already.
flash firmware with odin

Need help flashing stock on ubuntu

so heres the situation, a couple weeks ago my sammy a5 meet a horrible end and ive been without a phone. My buddy gave me his old s7 edge, its got cracked screen and has been sitting inn a drawer(hes rocking a pixel xl instead). so got it home charged it up turn it on and it got this blue sceen says there was a problem updating.
so longer story short got the stock 6.0.1 for bell 935w8 but i only run ubuntu, now while im able to flash smaller tars or img files flashing all stock at once wont work with either heimdall or Jodin3.
thought i could maybe flash twrp and go straight into custom roms i cant flash anything onto the device because of FAP lock in download mode.
Can anyone help me out? i know this would be easier with a windows comp but i dont have one.
can anyone help me

Categories

Resources