Related
My cousin just got me a new S7 Edge from Shanghai/Hong Kong/Singapore, somewhere like that where he goes for holidays.. Two problems.
First.
It's not remembering the wifi password after a restart. I checked and this seems to be an issue after rooting. Checked, its not rooted BUT it has a "custom" firmware on it.
When the phone boots up, it says Custom with an unlocked logo on it. In download mode, it says custom instead of official. Smart Switch doesn't support this phone model. SM-G935V.
Second issue.
What is the phone model? On the box it says SM-G935F. On Smart Switch and Internal it detects it as SM-G935V. In download mode its says SM-G935A. Checked with CPU Z, its a Snapdragon 820. So, it's obviously the U.S Verizon model that I got. I tried using odin to restore firmware for SM-G935F and V, it gives me. FAIL! SHA256 is invalid. Trying the Samsung G935X_QC_Rooted_Boot.tar method gives the same error code.
In Root Checker, the bootloader is G935AUCS4API2, that's for AT&T. Display and other firmware infos that I'm not familiar with are for G935VVRU2APB5, and that's for verizon. What is this bull****?
How do I fix this? Everything works fine. Except the wifi issue and the "custom" firmware that's on it that's not updating or giving me the ability to root to fix the wifi issue.
Download Samsung info from playstore check your pda, csc, etc... Save screen shots of those as wrong things might happen later, check updato for that specific firmware, double check that firmware csc with yours, flash using odin then reroot
Sent from my SM-G935F using Tapatalk
Alright. I found this thread and this software seems to work on this shanghai phone with a At&t bootloader and a verizon model and firmware. Weird thing. Its now working. Wifi issue fixed. So now, I'll try and flash an international firmware on it to see how of it works. Will update.
Update: Found this. Installed it and it worked. No carrier bloatware or bootscreen. Great. Hopefully this will help anyone in the future with the same issue.
Hello, All!
I have a G930V (Verizon S7) Non-EDGE, and I wan't to convert it to a G930U Unbranded (Or at least bloat free).
## BY THE WAY ##
Yes, I have seen other threads on this topic. Doesn't answer my confusions though.
Threads by:
tvm2487 (G930U Firmware)
James.Markham0757 (Can someone send me in the right direction...)
DeathAngel66669 (Using SamFirm to download SM-G930U-G930UUEU2APG9...)
## BY THE WAY ##
So anyways here are my questions.
##
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
7. Chances of bricking the phone? Would it be reversible?
##
My current S7 VZW Details:
Model: SM-G930V
Ver: 6.0.1
Patch Level: October, 1, 2016
Baseband Ver: G930VVRU4API3
I appreciate the help and your time. Thanks !
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
I don’t think it would flash as it is bootloader 2(5th character from right) latest firmware is 4!
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
From what I understand all the USA variants of the Galaxy S7's are the same hardware
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
I have an AT&T branded S7 SM-G930A and have flashed the U firmware and used it for a while. I have now switched carriers to T-Mobile used the U firmware without issues and now flashed the T-Mobile firmware and it works fine. KNOW IS NOT TRIPPED.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
Not sure, Odin may just fail to complete install?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
I never had luck flashing the HOME-CSC file, had to use straight CSC.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
One thing I did notice is the visual voicemail app tends to work better when using the specific carrier firmware(both AT&T & T-Mobile).
I'm using T-Mobile and I don't see a need to go back to U at this time as their is not much bloat on the T-Mobile firmware.
7. Chances of bricking the phone? Would it be reversible?
##
I just installed T-Mobile Nougat on my phone and got the error on phone and it was stuck on “You will need to use Smart Switch Recovery” to fix phone! SCARY!!! I managed to finally get firmware installed and running!
Understood.
When I get home today I'll try to install a newer version from SamMobile.
Updato has older versions. Sammobile has the latest which is.
G930U with code (VZW) on
G930UOYM4APL2
(https://www.sammobile.com/firmwares/download/118975/G930UUEU4APL2_G930UOYM4APL2_VZW/)
Would this be compatible?
G930UUEU4APL2 is the latest U-firmware. Everything flashes correctly, it won't trip KNOX, and it is super easy to go back to G930V firmware if you decide you want to send it back for warranty. You can't brick the phone by flashing signed files with Odin. The bootloader won't allow Odin to flash anything that could brick it.
I had already started replying before you posted above me. I'd recommend using my link to the firmware, as Sammobile downloads take FOREVER.
I see, I'm glad.
So, What would i need to make sure to do and not do in Odin 3.11.1?
AP/BL/CP/CSC from your zip? Just flash everything or only certain things?
Re-partition tick box? yes or no?
Flash all four of those files and DON'T CHANGE ANY Odin settings.
Okay. I just flashed it and now my phone repeatedly keeps booting into recovery.
The recovery logs and the red text at the bottom says:
dm-verity verification failed
Need to check DRK first...
Any ideas?
##PREVIOUS##
I think it might have to be because I used HOME_CSC rather than CSC.
What's the difference between both? Can i revert later?
##PREVIOUS##
@CVertigo1
I reflashed with the CSC file rather than the HOME_CSC file as according to your instructions in your thread (Latest G930U Firmware) and it worked perfectly fine!
KNOX is still at 0x0 and warranty void is fine.
( https://forum.xda-developers.com/verizon-galaxy-s7/how-to/g930u-firmware-pl2-g930v-success-t3558214 )
No bloat, amazingly fast, and some features i like are present. I'll report back to your thread on the battery life when i get more time with it.
I appreciate your patience.
(Will post screenshots later).
Home_CSC doesn't wipe user data, which causes issues when swapping firmware. That's what caused your bootloop.
Followed this, today, was sick and tired of the damn Verizon bloat slowing the phone down.
The phone runs faster - notably faster.
After installing the SIM, the phone returns, "Your device will restart to configure features supported by the new SIM card."
And then" It's useless. If I hard-power reset it, and take out the SIM, it's viable - it's just useless otherwise.
Phone is a G930V, flashed to G930U.
Any Suggestions? The phone is *NOT* rooted, so I can't easily take out or rename the AutoPreconfig.apk package.. Argh.
Will I get the android nougat update on this ROM?
Just converted G930V to G930U, all 100% working here in the UK. Fully debranded and no verizon warning about sim change. perfect
Mind telling me what thread you used to find the latest firmware? This forum for the phone is so rarely used anymore, it's hard to tell what info to go even go on anymore.
Is PL2 the latest for 930U? I'm VZW but US, not UK
I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.
Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.
So since I had OEM unlock enabled after disabling it, it passes and safetynet now.
I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???
Very weird. Working just fine on my rooted s8+ with magisk.
I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk
I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe
xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?
Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it
Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?
mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Are you sure that it is an original 935F?
Pet1981 said:
Are you sure that it is an original 935F?
Click to expand...
Click to collapse
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?
dleeII said:
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?
Click to expand...
Click to collapse
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.
X1ras said:
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.
Click to expand...
Click to collapse
I flashed the combination software and in the Factory Binary, it says MODEL: SM-G935F [SS]. Is the information reliable? Is there a possibility that the phone is fake? If so, is there a way to tell for sure?
EDIT: I checked the IMEI I got from the Factory Binary at IMEI.info and it seems to be valid.
I don't know
THIS
can help you or not
Try to use z3x box i read some function of z3x box but i'm not sure if it will fix your phone. Just go to gsm-forum for more details.
I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app
Sorry for the delayed response. I left my phone with some technicians with a ZX3 and Octopus Box and they were unable to fix the phone. But they didn't seem very interested either so maybe they just blew me off. Not sure. I'll try to find someone else soon.
speedyjay said:
I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
This may be the problem. I have tried flashing the stock firmware with Odin but maybe I'm flashing the snapdragon variant instead of the exynos. How can I tell the difference?
My warranty is 1 (0x0500). That means that Knox was tripped right?
mashardpro said:
I don't know
THIS
can help you or not
Click to expand...
Click to collapse
I've tried this guide and it didn't solve the issue.
I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.
dleeII said:
I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.
Click to expand...
Click to collapse
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..
misterashman said:
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..
Click to expand...
Click to collapse
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?
I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
dleeII said:
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?
Click to expand...
Click to collapse
Did you ever find a solution?
Hey, I was able to unbrick the phone. But I had to take it to a technician that used a very interesting technique to reset the phone. Apparently, someone had tried to flash another IMEI on the phone. To reset the device, he switched out one of the memories (there are 3 or 4 slots). Then when you boot up the phone, it is tricked into thinking you are booting up for the first time. At leas that is what I understood. Maybe someone more familiar with phone hardware could explain the solution better.
Rymcbc said:
I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
Did you ever find a solution?
Click to expand...
Click to collapse
Did you ever find a solution?
dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
You tried smart switch if identify the device and instal stock rom?
bricked S7 Edge with a dm-verity error
dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
I Also Have this problem with Samsung SM-G935F
I Solved This Problem With Small Trick
1. Flash Phone With Official Firmware
2. Flash Twrp Recovery
3. Wipe All Data Leave System
4. Reboot
Now I got My device back Alive
You Can Try May Be Its Works For You
I tried the same and my fone booted but its very unstable with crashing apps and random restarts...
With smart switch it ends into dm varity verification hash tree error or dm-varity error
Any solutions...
Please check my answer for the S8+ I believe it should be the same process.
https://forum.xda-developers.com/showpost.php?p=75342726&postcount=10
Good Luck
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.