My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Related
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
Hi All,
The short of a long story is that I just changed carriers and found out way late that I couldn't bring my Sprint phone to MetroPCS. So now I'm using the budget PCS On5 that came with the deal when we signed up.
I successfully loaded TRWP and then rooted however, I didn't know about FRP until it smacked me in the face. The root went fine but later SU prompted me to update the binary and when it did, it tripped factory reset protection and soft bricked my phone.
I want to reinstall stock OS on this phone but it appears that I have a software version that I haven't been able to find on the web yet. I found the stock rom for the MetroPCS On5 easily enough but it's Revision 0.0 and the box I have for the phone says REV0.4.
When I try to Odin Flash the REV0.0 version, I get SW REV CHECK FAIL DEVICE 2, BINARY 1 fail. So I guess I had the latest software on my phone and the phone thinks I'm trying to roll back using the 0.0 revsion.
My question is this, does anyone here have the stock rom for G550T1 REV0.4? Help!
If nobody does, maybe I can still fix this phone. I have a TRWP backup from the sister phone (same model same revision 0.4) that I'm using right now but I can't get back into TRWP on the soft bricked phone to recover that way to use the backup file.
Next I thought I might take the backup files and turn it into a rom and just flash that. However, with the tutorials I followed I kept running into problems. When I went to unpack the files per the tutorial, my rar software said that the file was corrupt. Maybe it is. but maybe not. It was my first time attempting to make a rom. If I can't find the software I need, could any of you Android geniuses help me get this backup into a flashable format?
I have to admit I'm daunted by the FRS in 5.0 and above. Is it defeatable? How do you root newer Android versions?
Thanks!
I did the same thing to my phone. did you get yours fixed?> if so could you provide me with the rom?
I haven't found the fix yet. Hopefully somebody will come through with a helping hand!
I finally got it figured out! So here is what i did and hopefully it will work for you.
1. I Odin flashed a good BL from the ROM REV0.0 floating around on the net. So at least I could now get into download mode.
2. Then I used Kies3 > Tools > Firmware Upgrade and Initialisation. It will ask you for your model number and then when you click ok it will ask you for a SN.
3. The trick is that Samsung doesn't put the SN that you need on the phone or the box. (personally, I couldn't find it on the phone either once I got it up and running) so go here: https://forum.xda-developers.com/android/general/root-samsung-galaxy-on5-t3435457/page46 and get a SN from post #454 and use that. (don't forget to say thanks)
4. Click Ok. Let it work, and max and relax.
Mine took about 10 minutes. Hopefully this will work for you too! Thanks XDA!
Help!
What is BL from the ROM REV0.0? I need your help, I have the MetroPCS On5 and I installed Reborn ON5 I want to go back to the MetroPCS ROM because the camera and the audio do not work and I tried to install the original ROM through Odin but it does not work I get an error. What I can do? I would like to use this method but I do not have very clear files needed.
You could help me bro, I'll thank you
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Try to connect with smart switch.
On windows pc or laptop
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
It will flash stock firmware and solve all binary problem
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Intall smart connect or smart switch in pc
Sent from my [device_name] using XDA-Developers Legacy app
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Flash latest stock firmware for your region and enable OEM unlock in developer settings to avoid FRP in future. Also try to remember your google account password :silly:
Solved. I flash the latest firmware with an old version of odin
frp lock
marcoar said:
Solved. I flash the latest firmware with an old version of odin
Click to expand...
Click to collapse
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
kira31390 said:
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
Click to expand...
Click to collapse
Odin 3.12.5
Firmware: fxxu2drb6
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Matty1993 said:
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Click to expand...
Click to collapse
after the combination file flash, the phone normally starts with the combination firmware
marcoar said:
after the combination file flash, the phone normally starts with the combination firmware
Click to expand...
Click to collapse
Thanks so much for the reply i appreciate it i might try my combination file with the G930FXXU2DRB6 firmware you used as i need to test my hardware and fix imei but cant get the factory binary to boot on G930FXXU2DRBE firmware my thinking that it wouldnt boot was as its FA60 is android 6.0 MM where as my U2DRBE firmware is FA70 7.0 nougat is your device nougat or marshmallow ? Just trying to work out whats going wrong where for it to not boot on my device as ive lost my imei number flashing a custom rom and dont have access to my TWRP back up for another 3 weeks
Thanks
Hello. I have a similar problem. I have the latest firmware on it: G930FXXS2DRDI There are no ways to lift the Google lock. I have tried everything possible: Bluetooth does not work, Talkback, Realterm, etc. Please for help
My Android Version is: 7.0 (Nougat)
Frp g930fxxu2ara1
Hello my friend, i have this problem too. Have you a fix? this security patch for FRP is incredible....
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
ATRAC3, do you have the combination files and firmware for the SAMSUNG S7 SM-G930FD please and thank you for your wonderful tutorial here.
my odin(tried on v3.12.5/v3.12.7/v3.13.1 ) keep failing while flashing HOME_CSC but will success with CSC, and still required to login google account, what is the issue here ? (are we supposed to insert the pit file by ATRAC3 ? )
flashing at the lastest FW G930FXXS2DRCE
phone version:SM-G930F
ATRAC3 said:
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
Click to expand...
Click to collapse
Hi mate ive used the G930FXXU2DRBE XSA Firmware and also G930FXXU2DRB6 firmware with the G930FXXU2ARA2 combination rom however it will not boot past the samsung logo the nad passes and is provisioned in top left corner and when plugged into the computer comes online with ADB bypass flasher but it just sits there even if i do a cache wipe and factory reset it comes up with a tango console error or something like that when reset then reboots back to samsung logo and when re installing firmware HOME-CSC will fail every time the only thing ive been able to put it down to is that (1) the firmware is FA_70 which is nougat OS and the combination rom is FA_60 MM or (2) my knox warranty bit is tripped and will not allow a samsung factory binary to be run on it, may i ask what would be the difference with the firmware you have listed to the firmware im already using with the combination rom ? Need to sort my imei number out with the factory nad asap dont have access to my TWRP backup for another week and a half, if it helps my device is not FRP locked and is oem unlocked.
Thanks
Matthew
P.S to all those whom have a bit 2 bootloader on S7 all the loopholes have been patched the only way is to use the combination files ive been through absolutely everything and tried everything this new bootloader update is impenetrable i can google unlock samsung S8 and S9 no dramas and with S9 the OEM lock option dissapears for a week if tampered with but still 15 minutes and its done this **** but got me goin loco holmes !!!!! Maybe they figured this out also as there is only bit 1 bootloaders for both the S8 and the S9 however with S8 i found a stock firmware that allows another way to unlock the device without the need to flash any combination rom.
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
LEVY P said:
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
Click to expand...
Click to collapse
If it gets stuck on the console error and wont reboot to download mode then hold the power button volume down button and power button for 40 seconds and it will re boot to download mode for stock firmware re installation in short basically no theres way to remove the FRP unless you can get the combination rom to boot which from what ive seen some will boot the binary but then it also depends if HOME_CSC will flash to keep usb debugging enabled to use adb bypass program im now using the new G930FXXU2ERE2 8.0 OREO so I've given up on the binary 2 nougat FRP unlocking for now might be best to wait a while for someone to receive a factory binary on the nougat or oreo when sent off and returned so it can be dumped and built into a flashable rom until then not much can be done and i may have to wait another week and a half for my EFS backup :'(
We will be waiting from u for the new combination file when out bro, our hope are hinged on u!
No one is coming up with any method about the bootloader binary 2 for the Samsung S7 G930FD...?
Sent from my SM-G930F using Xposed Modules
FRP can be done so easy from any GSM tool by combination, anyone need it it will be my pleasure to help
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
thedan55 said:
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
Click to expand...
Click to collapse
Flash full firmware not just AP file. Flashing AP file only is more than likely the reason for difference in storage size.
No need for pit file. If it is needed it can be exacted from the firmware that you have downloaded.
I did flash all 4 files not just the ap. I only wanted to show the version etc
Now when I try to flash Odin says failed
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
spawnlives said:
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
Click to expand...
Click to collapse
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
thedan55 said:
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
Click to expand...
Click to collapse
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
spawnlives said:
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
Click to expand...
Click to collapse
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Why do I get this message every day? Throw the darn thing out already.
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Buy your nephew a damn phone
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
pego99 said:
Buy your nephew a damn phone
Click to expand...
Click to collapse
I did buy him this phone. Just because it's a little messed up right now doesn't mean I should just thrown it out. This entire forum is dedicated to invigorating devices and keeping them going. XDA didn't accept the philosophy of throwing out devices when they can be repaired. I've been here long enough to know that.
Ffs people are still developing for the hp touchpad and m7 Windows devices!
Unsubscribe from this thread mate. Delete your replies so you don't notifications.
There's no need for your unhelpful comments when others are trying to be of assistance.
spawnlives said:
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Click to expand...
Click to collapse
Thank you very much for your replies. It's very much appreciated mate.
I did flash the pit file and subsequently got errors in odin. I want aware that I was trying to downgrade. I've download from official site and will try flashing today.
Again thanks for the help. Been a while since I've had to do this lol I think the last device I was rooting and roming was my note 3! The support for it is still going strong though!
Cheers
I guess at some point its best to move on. My grandsons S8 had the digitizer go bad tried to fix unsuccessfully bought him a used on on fleabay for $150.
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
thedan55 said:
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
Click to expand...
Click to collapse
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
pego99 said:
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
Click to expand...
Click to collapse
It took less than an hour to fix this phone, that's a cost I can stomach.
if you had actually READ the post instead of commenting asinine remarks them you would know how the phone for corrupted in the first place.
Please stop replying to this now.