Related
Hi guys
I need some quick help identifying what happened to my S4. It's not bricked by the way, it's just some weird debugging mode which became enabled.
I have just sold it on eBay, and therefore I performed a standard factory reset followed instantly by a standard ODIN flash of the official latest firmware to remove root (which is something I've done many times on this phone without an issue).
However this time, since I did it, everytime I turn the phone on, just before the standard Samsung Galaxy S4 logo appears, I get a strange flashing screen which displays some technical details on the phone (different to the one I used to have when running a custom kernel) which include: serial number, Knox status, power on reason, some CPU details and in particular, a line saying debug mode level: medium. I have never came across it so I tried removing the battery and re-flashing the software, neither of which have helped.
I would like to find out if anyone had come across this and if so, how could this be revered back as I need to ship the phone to the buyer.
Attached is the photo I managed to capture with my DSLR which shows more detail... Please help.
Thanks a lot
Regards
Please can someone take a look at this?
mateuszd said:
Please can someone take a look at this?
Click to expand...
Click to collapse
mateuszd said:
Please can someone take a look at this?
Click to expand...
Click to collapse
Go to recovery and make a factory reset, when the galaxy s4 logo shows up remove the battery immediately, wait 5 seconds then go to download mode and flash the firmware, after the device reboots make a factory reset again
Will try that, what I did so far is flashing the latest Black Edition rom which removed the issue and then flashing back the latest normal ROM and the issue came back straight away. It's like a weird bootloader it comes with.
I'm downloading an older ROM from March as this is the one I flashed a while ago and had no problems with.
Fixed it, just downloaded I9505XXUFNB8 which is from March and flashed it, then, updated over OTA. It's now on latest version without the weird bootscreen issue.
What's strange is that it was an official (latest) build downloaded from SamMobile and later downloaded again though SamFirm tool and both produced same behaviour yet upgrading to it though OTA did not cause the issue.
Thanks
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
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.
Hi All.
Thank you for any help you might give me in advance with this issue...
Last week, I tried to root the phone with the SM-G930P CF-Autoroot heroqltespr files with Odin found in this forum. I have rooted a few other phones but am no expert. The root after a few attempts failed (verified a few ways), however, some files must have been affected because the phone "identifies" as heroqltespr. Identifies as when I could plug into my PC heroqltespr would be the name. It was not set this way in the obvious name your device areas. I ended up doing a hard reset to clear the phone and other than the ghost naming everything was working fine.
A day or 2 ago Sprint rolled out a new OTA update which the phone installed. Since then the phone was draining battery life. After uninstalling and reinstalling the SD card today, it seems to have tripped a "Security Notice: Unauthorized Actions". That is when the trouble started. The phone started running hot, basically leaking battery power, and was all lagging. I'm assuming the CPU going Ludicrous speed.
Now, I am in a Samsung Splash screen loop, or or a recovery loop. The only thing it does is go into download mode.
I have tried flashing stock firmware, it fails. I've tried flashing with and without the SD or Sim card. Not really sure what I should be doing. The "P" version of my phone seems to be the bastard child of S7s. Any help you guys cold give me would be great. THANK YOU!
The Download Screen Reads:
Odin Mode (High Speed)
Current Binary: Samsung Official
System Status: Custom
FAP Lock: Off
Warranty Void: 8x8
Qualcomm Secure Boot: Enabled
AP SWREV: 85(2,1,1,1,1) K1 S4
I get this error when I try to flash back to stock SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
Stupid question but is your phone in a case?
Sw rev check fail : [aboot]fused 5 > binary 4
freakboysays said:
Stupid question but is your phone in a case?
Click to expand...
Click to collapse
No it isn't.
I get this error message on the download screen. SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
If you dont mind me asking, did you ever find a way to root the G930P with the 5th bootloader updates? Is it even possible at this point in time? Im new when it comes to rooting but with the amount of time Ive spent browsing the web it seems as if there is nothing. Thanks.
tonysak said:
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Click to expand...
Click to collapse
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Chanman said:
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Click to expand...
Click to collapse
EDIT: Nevermind...sounds like you aren't on sprint.
lvpre said:
EDIT: Nevermind...sounds like you aren't on sprint.
Click to expand...
Click to collapse
Actually, I am on Sprint, and your directions were awesome, thank you so much! The only thing I had to do was change the line to:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
I'm going to put a link to the thread so others can refer to it. https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
Hi all,
EDIT: I posted this in another thread that was about two years old, where I followed the instructions that caused this: https://forum.xda-developers.com/sp...msung-galaxy-s7-sm-g930p-root-xposed-t3503599
That thread seems dead-ish and if you managed to fix this issue maybe you can help me also. Also what was lvpre's original post before he edited it, and would it apply here?
So the worst has happened - got a new (used) phone from Boost Mobile, tried this guide, and now I can only boot to the "An error has occured while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software." screen. Sometimes it does take me to the original "Download mode" screen.
Now, I should be able to resolve this by flashing the original firmware correct? (As in, the firmware that was installed when it came)? Or does it just need to be firmware from the same date range that has the same bootloader? ODIN will still let me attempt flashing on this screen, but I still get the same error when I try again, which on the Download mode screen showed "SW REV CHECK FAIL : [system]Fused 4 > Binary 1"
Any advice here? My S6 bricked when somehow OEM unlock enabled itself and I can't get around the FRP lock, I will be VERY annoyed if the same thing happens with a NEW phone. If I can't fix this I am never buying Samsung again. Any advice on this is very welcome! I emailed Boost to ask them which firmware is installed (because I'm an idiot and didn't write it down but have never had flashing go this wrong before).
EDIT: Booting to recovery just shows a blue "RECOVERY BOOTING...." for a second in the corner and gives a recovery bootloop, just keeps flashing that.
EDIT: I apparently tried to flash an earlier bootloader/etc through ODIN according to the directions in the post I linked above, and after that I now have this problem. Nobody else in the thread seems to have had this problem, and your post is the closest to anything I can find on this issue. I would be in your eternal debt if you could help me out here.
PLEASE HELP!
EDIT: Theoretically if I can find the original firmware it was on I should be fine, right? Everywhere I read if flashing goes wrong you just flash the original stock on it. I guess worst case scenario I download gigs upon gigs of firmwares for Sprint 930P over the last year and find the one that sticks? Or is the fact my recovery is bootlooping and I can only go into download mode mean I'm bricked?
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
slvmecha said:
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
Click to expand...
Click to collapse
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Switched from Sprint to T-Mobile. Am I out of luck?
lvpre said:
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Click to expand...
Click to collapse
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
jbuck2 said:
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
Click to expand...
Click to collapse
If your phone is uicc [sim] unlocked from sprint... you can try the following.
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Here is an article https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/
Is this triggers the knox counter ?
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?
PA_Pyroholic said:
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?
Click to expand...
Click to collapse
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.
Fear_The_Fluff said:
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.
Click to expand...
Click to collapse
I did get the update to 5 unfortunately and am no longer with sprint, paid everything off an account is closed. I did some more digging and realized many mistakes yesterday. I tried the latest 'U' FW (binary 4), it failed, and then I tried the latest 'P' FW (binary 5) right afterwards and it failed... But I didn't cycle the phone in between attempts so of course it was going to fail. Ended up reflashing with the latest 'P', and went through the easy, "just say yes to everything" set up and all the bloatware reloaded onto it. Reflashed and wiped device, and was careful this time... 90% of the bloatware I wanted was gone. Package disabled the rest. Only thing I can't seem to get rid of is the Sprint logos on start up.
After stumbling my way through this first attempt, I'll do better research next time!
Sent from my SM-G935P using Tapatalk
PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
Unfortunately, your phone is on the newest firmware, B5. You'll only be able to flash one of the latest sprint firmwares to get your phone to work. All the other carriers and U firmware are still running an older binary boot. You may also need the special version of ODIN...you can probably find it in the same forum about installing the U firmware. But if you download the latest sprint firmware, your phone should boot again.