Galaxy S5 + Root safely. - Galaxy S 5 Q&A, Help & Troubleshooting

Hi guys, today I made a big mistake by thinking that it would be so easy to root on my S5 +, I was wrong, because it appear that I had the bootloop problem, i resolved it by mistake i was so lucky, I tried to put a BootLoader on Odin on AP section, an error occured on my phone, It reset it and it did come back to life Yeah WTF right ? So now that i've got my phone back ! I'm happy but still, I'm worry about my sim and I want to know if someone is listening to me (because strange things happened lately), that's why I did some research and It appear that an app does exist to prevent such thing ! it's called Snoopsnitch, Amazing isn't it ?
I've got hope that you might be able to help me to root my phone properly this time and avoiding the loopboot issue. If you can led me to do it, it would be amazing.
There is my config. I wish you a good day, night or whatever you are doing on this planet. Kiss. :victory:
https:// ibb.co/FqssRkM
https:// ibb.co/5BPrc7p
Sorry i'm new and i'm not allowed to share my image link so I had to trick the system ><
Thanks for your time and your answers guys. :highfive:

Oh hi, im having the boot loop / logo problem too.
could you explain more clearly what you did to resolve that and is it still good to this day?
ive already used odin3 v3.11 and put the latest stock firmware successfully but the phone still boot loops or if lucky it will get passed the carrier screen (O2) but then as soon as i restart the phone it will boot loop again. (or boot loop randomly, if i dont restart it myself, eventually).
I havent tried TWRP or PIT as im a basic user and just wanted the stock rom.
Any updated advice? ...im worried its the memory/emmc/hardware prob
thanks

Related

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.

Samsung Galaxy S5 keeps shutting down after Flashing build.prop bootloop., Help pls!

Hello there,
i need help with fixing my phone, i tried to change the model of the phone by changing the build.prop file, like everyone else who does something like this for the first time. i bricked my phone and it went into a bootloop.
after ton of research on multiple websites and especially xda-developers, i managed to flash the phone with a suitable frameware form the galalxy S5, the first time i did it i accidently put the firmware into the BL position into ODIN. then i put it into AP and reset the device.
the download was succesfull, but the phone didnt start up. the next day i turned the phone on, and after 5 mins being stuck on the Samsung logo, it finally booted up and i managed to get inside the phone. i thought it has been fixed, the device asked if i wanted to apply updates, which i said yes to. It updated and tried to restart itself.
now it wont turn on, everytime i try restarting it it is just shutting itself again animated samsung logo fades.
i don´t know what i should do right now, i tried looking for similar situations to mine but i couldn´t find anything similar.
Can someone tell me what i should do in oder to get it fixed pls.
model: SM-g900f
thanks in advance.
edit: it is working again, but it has been completely reset. for now it worked. going to update it again, i will put if the same problem accours again.
bayar16 said:
i tried to change the model of the phone by changing the build.prop file, like everyone else who does something like this for the first time. i bricked my phone and it went into a bootloop.
Click to expand...
Click to collapse
Most likely you forgot to set permissions 0x644 for this file after editing it.
It's a common mistake.

Boot help Galaxy S7 Edge

Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks
shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.
Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones
The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.
Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.
Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.

S7 Edge, Won't boot OS.

Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
JTec11 said:
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
Click to expand...
Click to collapse
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
xTweeBy said:
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
Click to expand...
Click to collapse
Love a good Samsung lmao, thanks for your reply

Samsung S8+ Stuck in the boot loop, I think

Hi guys and gals
I am probably duplicating a thread for which I apologise in advance, but I have no clue for what key words I should be using to search for to find an existing answer, assuming there is one!?
I have the s8+ (SM-G955f) purchased in the UK via Vodafeon.
The battery died some weeks ago and I've had no money to be able to buy a replacement until now. I did try to use it now and again, but it last no more than a minute, but what did seem to happen is what is referred to as the boot loop saga.
I have followed other threads for instructions and downloaded Odin v.3.13 along with the varoius files (BL,AP,CP,CSC) from a zip file (G955FXXU9DTF1_G955FOVF9DTF1_VOD.zip) I was doing this late last night and do no remember which website I got it from, it took sooo long to download.
I am now at the point where I have connected the phone via USB and I have run the program and the status went to green, said 'pass' and the phone rebooted, however it is back to the Samsung welcome screen and sometimes keeps rebooting, other times, just stays there.
Where do I go from here? would it be that I have used the wrong firmware? I have never done this stuff before and have no clue, but am desperate to have a working phone as I have no money to replace it
Any advice, very welcome
If the battery went bad why flash firmware. Replace the battery
TheMadScientist said:
If the battery went bad why flash firmware. Replace the battery
Click to expand...
Click to collapse
I guess the issue was when the battery had issues, it would last maybe a minute or 2 before shutting down and then having to wait a full day before trying again. I did this for about a week as needed to get phone numbers from the phone along with some other info.
On the last occassion the phone turned on before the battery finally gave up, it seemed to go into the bootloop.
So now, I have tried various versions of Firmware via Frija and using Odin 3.13 to instal, but the phone doesn't seem to want to accept it.
The phone was originally purchase via Vodafone in the UK. I have tried VOD and BTU.
I am now in Asutralia, so have also tried TEL and VAU as have had sims from them also.. if that makes a difference?
I cannot get into the recovery mode at the moment, no clue why, just the download screen. The last time it went into recovery it kept mentioning about ATT which I don't understand as the phone has never had an AT&T connection which I think is in the USA and the phone has not been there..
Does anyone have any other suggestions? Would it be crazy to try and instal a custom OS and then revert back, or does the phone always remember the original firmware? I hope this all makes sense as this is all new to me..
Thanks in advance.

Categories

Resources