Man I bought a used phone.
On back it says SM-G935S but in about phone it is SM-G935FD. My phone said my device is modified and I couldnt update it, I checked to see if warranty is void in download mode. And I was greeted with downloaded mode in korean language. It it said warranty void: 1 and also had model as G935S. I restarted device after knowing that it is moded, and then my phone NEVER boots, it says custom binary blocked by FRP lock. I looked specs of G935S and it is a single SIM variant but dealer sold me it as dual sim? It had firmware of dual SIM variant FD.
What kind of sorcery is this? Why S runs on firmware of FD, why it locked up by just having look at download mode, how do I fix it? I am completely unsure what to flash at this point. I tried to flash CF auto root for S but it fails and in download mode same FRP lock error. Please help!!!! I bought it 3 days back fml.
Related
Hello everyone!
I need a little advice to fix my softbricked note 4
So here are the facts:
I boght a bricked N910F i tryed different roms from sammobile using odin and twre, more than 7 to be specific, and most of them did t work as it shoul. My imei was the same as on the case but i noticed SN was different in system and knox 0x1.... I got a version of android 6.0.1 to work but there were different little, big problems like not rememering wi fi passwords, fingerprint not working version :null in testing, and often restarts and bootloops after installing different aplications. i tryed many things even repartition with proper pit file, i still had back-up of my efs but considering the serial number was screwed up i gave up trying anything else. I tryed rooting with different methods but everything failed.
I boght another N910F with screen broken but working mainboard and knox 0x0
Swaped the mainboard, tryed samsung kies 1, entered serial and model and it gave me the fw i needed to flash. Tryed flashing with kies and at the middle of transfer it said failed and phone froze, didnt even power on for a while. Tryed again after a few howrs, same rezult with message emmc read fail, and at the bottom emmc write fail.
kies said i need PDAG2/CSCE2 / PHONEE3 CNX
Now, later in the evening i managed to power it on agan and i dont know what to try so i dont screw up with knox
Here are some pictures of my current status:
Current status: cant post picture...
ODIN MODE (HIGH SPEED)
PRODUCT NAME SM-N910F
CURRENT BINARY Samsung Official
System Status Official
REACTIVATION LOCK OFF
Knox 0x0
qualcomm secureboot enable csb
RP SWREV S1 T1 R1 A1 P1
secure download enable
UDC STAR
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
What should i try next?
Thanks
Later Edit:
looked up on youtube and found that smart switch can do the work, tryed it and seems it went all the way and installed proper rom without fail. LOL
Morning edit:
So everything worked perfect last night so i left it on fastcharger. In the morning i found it in download mode with dii emmc read fail, could not do normal boot.... After this i have to let it rest a bit without battery, then it boots up ok, works a few minutes then it shuts down and never wake up
faurionutz said:
eMMC from phone is damaged harware
Click to expand...
Click to collapse
I found the only way to keep it working is by preventing it to go into sleep mode. Play music on repeat muted keeps it working
Lucky i have fast chargers and 3 battery
i tried different keep alive apps but they eventually fail and phone dies
hi!
i just agree to the update from my phone, he download the update and start install it. i had 60% of battery.
in the end of the update, the phone is stock with Samsung logo and make a 2 restart until he show my black screen and blue light.
i try to flash new ROM from samoblie. with i chose g935fd. and he back to do a 2 restart and blue light.
the phone is a gift i do not have warranty. the phone is international from Emirates
i need some help plz! i try fix him a 4 days.
in odin mode:
product name: SM-g935f
current binary: samsumg official
system status: custom
frp lock: on
secure download : enabled
warranty void : 0 (0x0000)
rp swrev : B:2 k:0 s:0
Download Samsung smart switch and install through that
in the smart switch it write "model are not supported "
Hello guys, I'm also facing the same issue. My phone is the S7 Edge duos black and never been flashed but has gone through an update from Marshmallow to Nougat. The problem is, one day it suddenly restarts itself and gets the bootloop issue everyone is facing. I can't even go to recovery mode to wipe cache partition as instructed everywhere.
I already tried to flash the phone using the firmware available on Sammobile.com but it still experiencing the bootloop right after it has been completely flashed.
Please help,
Hex
Ok so the phone i have is/was actually a G935T, and had G935T firmware (BRC1) even though it says G935A on the board inside the phone. I tried to flash a different firmware, foolishly without turning off FRP, or turning on OEM, yeah im dumb. I ended up being stuck with the SBL error upload mode and couldnt even get back to download mode no matter how many times i tried, eventually i learned about EDL mode and took the phone apart and shorted the TP and re programmed the phone etc. and got it back to download mode.
Everything i flashed would always be successful in Odin, however nothing would ever boot past the looping S7 edge boot screen and recovery on every single firmware would also loop and ultimately give me kernel panic errors. i began to suspect that maybe i left something unplugged inside so i took it apart again and tried to keep the heat shield pressed down a bit more (since i had to open it up to access the test point) as i assembled the phone back together. No more kernel panics, but the boot looping was still present. I have tried G935T, A, P, V and U firmware and all of them do the same thing. Ive used the proper PIT files.
To make things worse, i flashed Oreo without realizing that i was putting my bootloader in handcuffs. To make things even MORE worse, i used a tool which claimed to convert an odin archive to be ADB enabled. now my device boots and says S7 edge etc, but then immediately goes to SBL error upload mode. Recovery still loops. Whats interesting though, is that since i used the converted archive, my device says exactly this in download mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0xffffffff (0x0)
QUALCOMM SECUREBOOT: ENABLE fffffffe
RP SWREV: B-2 (-2, -2, -2, -2, -2) K8 S8
RP SWREV: TEST DEVICE
SECURE DOWNLOAD: ENABLE
IDDQ: G(25), S(7) mA
CPU SERIAL NUM : 0X1b9cea13
Fused open loop voltage: 1030mv
RPMB PROVISIONED
Any help would be much appreciated. Its going on nearly a month now trying to get this thing to work. I dont care about warranty, i dont care about knox i just want my phone to work....i cannot find any information about test device, how to go back to system status official or how to properly reformat all partitions that effect FRP or whatever the hell is locking me out of it. Also i am now not even able to flash ANY firmware because it keeps failing saying something about aboot fused -2 and none of the firmware i have will successfully flash. Im stumped.
I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?
How to change Fuse -2 -> 1
Elem3nt0 said:
I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?
Click to expand...
Click to collapse
Fuse -2 happened to my T380 Tab A tablet when I flashed wrong aboot and boot in the same TAR package.
So steps to fix it:
find the right combination firmware;
unzip it with 7zip archiver;
download TAR_MD5_PACKAGER;
open folder with unzipped comb_firmware and delete all files below from it:
-aboot,
-apdp,
-boot,
-devcfg,
-msadp,
-rpm,
-sbl1,
-tz.
copy all files what left to TAR_MD5_PACKAGER\parts;
start TAR_MD5_PACKAGER and press 1 to make tar file;
flash this file with Odin as AP;
now the fuse should switch to 1;
next flash the full combination file or stock firmware.
FUSE Number stands for software version,
samsung has protection against downgrading software,
So once you flashed firmware with number 2 in it, the device will change the fuse to 2 and after that
you will not able to flash anything less than with number 2 and so on.
S7 edge up and running
Dude thanks a lot!!! I read through multiple threads. Some more technical than others but this one was plain simple and it worked. Some of the files I deleted were a bit different, but hey, it got bit to work. One other thing for anyone experiencing the same issue, just look for a combination file matching your phones actual bootloader. Once you find it, just start deleting the files Odin is indicating are not letting the flash complete. In my case, files: hyp.mbn, pmic.elf, emmc_appsboot.mbn, xbl.elf. once I deleted those files I was golden. :laugh::laugh::laugh:
HI
I have smiliar problem.
I have a problem with a friend's phone. they give S7 Edge to the service because he have problem witch turn on telephone
When he received the phone displays an error: "An error has occured while updating software.. Use the Emergency recovery function in the Smart Switch PC"
Smart Swhitch doesn't recognized the phone
I try update firmware with odin but when i flashing i have error: SV rev. check fail(bootloader) Device: -1 Binary: 6
I try to insert TWRP and i have next error: Custom binary (recovery) blocked By FAP lock
I can not insert custom recovery witch TWRP, and I don't have any idea what official rom was uploaded last time :/
Sorry for my English :/
Ok so the phone i have is/was actually a G935T, and had G935T firmware (BRC1) even though it says G935A on the board inside the phone. I tried to flash a different firmware, foolishly without turning off FRP, or turning on OEM, yeah im dumb. I ended up being stuck with the SBL error upload mode and couldnt even get back to download mode no matter how many times i tried, eventually i learned about EDL mode and took the phone apart and shorted the TP and re programmed the phone etc. and got it back to download mode.
Everything i flashed would always be successful in Odin, however nothing would ever boot past the looping S7 edge boot screen and recovery on every single firmware would also loop and ultimately give me kernel panic errors. i began to suspect that maybe i left something unplugged inside so i took it apart again and tried to keep the heat shield pressed down a bit more (since i had to open it up to access the test point) as i assembled the phone back together. No more kernel panics, but the boot looping was still present. I have tried G935T, A, P, V and U firmware and all of them do the same thing. Ive used the proper PIT files.
To make things worse, i flashed Oreo without realizing that i was putting my bootloader in handcuffs. To make things even MORE worse, i used a tool which claimed to convert an odin archive to be ADB enabled. now my device boots and says S7 edge etc, but then immediately goes to SBL error upload mode. Recovery still loops. Whats interesting though, is that since i used the converted archive, my device says exactly this in download mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0xffffffff (0x0)
QUALCOMM SECUREBOOT: ENABLE fffffffe
RP SWREV: B-2 (-2, -2, -2, -2, -2) K8 S8
RP SWREV: TEST DEVICE
SECURE DOWNLOAD: ENABLE
IDDQ: G(25), S(7) mA
CPU SERIAL NUM : 0X1b9cea13
Fused open loop voltage: 1030mv
RPMB PROVISIONED
Any help would be much appreciated. Its going on nearly a month now trying to get this thing to work. I dont care about warranty, i dont care about knox i just want my phone to work....i cannot find any information about test device, how to go back to system status official or how to properly reformat all partitions that effect FRP or whatever the hell is locking me out of it. Also i am now not even able to flash ANY firmware because it keeps failing saying something about aboot fused -2 and none of the firmware i have will successfully flash. Im stumped.
Hello everyone,
This is a SM G975F exynos model
Please note that the bootloader is locked!
I tried to root the phone and it sort of succeeded but now its stuck on bootloop
And moreover Knox is tripped ... if that even matters at all?
I can access download mode, recovery and charges normally with no issues at all.
Problem is i cannot get into the home screen or the setup screen
I have used odin to flash 2 versions of android 10
Since i cannot downgrade because of bootloader being locked....
The odin flashes two versions of 8 bit roms one is G975FXXU8DTH7 and other is G975FXXU8CTG4
Both are android 10
If i do try to downgrade odin gets stuck at boot image flash stage and doesnt work again due to bootloader being locked
can any one help me on what the issue might be?
i can get into download mode , recovery mode, the flash results in a success and i get a pass on odin as well
all it does is get stuck on samsung (non animating) stock splash screen and it restarts again and again
Some relevant information i fetched from download mode screen
KG State : Prenormal
FRP Lock : Off
OEM Lock : On (U1)
please assist me on further on this issue if you can
I can even share the video of the phone behaviour if needed via discord
Thank you
Hi,
Did you fix this problem, I'm in the same situation. Trying to flash all versions of ANdroid 10 and 11 now with Odin, as I don't know which stock formware it was on when it went into bootloop.
Update: When in Recovery Mode, go to the Recovery Logs, then one off those log histories shows all the System build numbers and their installation dates. FRom there you can work out which system was installed when it went into boot loop.
I installed the last system it was working on, then left it in boot loop for 2 hours and it suddenly started to initiate. Leaving it overnight didn't work as I think it turns itself off when the prompts aren't responded to.
Can you please post a photo as I am wondering if we have the same problem as described in this link:
Samsung S10 + bootloop ERASE FAIL: READ ONLY
Samsung S10 + SM-F975F/DS IMEI stating Taiwan (Update: Very contradicting information if the phone is Snapdragon OR Exynos) if it even matters to solve the issue I dont know Owner of the above since 2019 without issues; USB debugging mode...
forum.xda-developers.com