Related
I rooted my galaxy s7 edge (snapdragon) and everything was fine and working except I couldn't get SuperSU to install properly. I would get the app screen, but nothing else. A couple of apps would show up (Root Checker, Flashfire) after I had run them but I didn't get the typical SU screen with settings. I'm not including the softwares used (I did have debugging enabled in Develper options on the phone, secure boot unchecked, and the correct Samsung USB drivers installed) because I don't think it's relevant to my question - if not so, let me know and i'll be glad to provide the info - I'm a newbie at this so please bear with me). I read about the warning to not update the 2.74 version of SuperSU but then I saw the update beta for 2.77 so I tried that. It appeared to run ok; I could see all the commands being executed and then ending and then the phone rebooted, as it's suppose to do. This is when the problem emerged; a screen came up saying "start up failed" and at the top left of the screen it said 'Custom binary blocked by secure boot (boot.img). I rebooted to TWRP recovery mode and tried rebooting which again resulted in the start up failure screen. I then tried the wipe data\factory reset setting and the same thing happened. I then booted to maintenance mode and got the warning screen about a custom OS installation can cause problems but if you want to proceed press volume up key which I did and got the usual Downloading page. At the top of the Downloading page I noted it said, among other identifying info: Odin mode (high speed), FRP lock: off, QUALCOMM Secure Boot: enable, and Secure Download: enable.
But, when connecting the usb cable to the phone and pc, my computer (Win 10) doesn't even see it. Not sees and doesn't recognize, but doesn't even see it. I tried a second USB cable and different ports but got the same results. I tried a second computer and got the same thing.
I am guessing that if I could still access the phone to run rooting apps I could get past the lock. If not now, maybe later on when someone figures our a way to do so. But without a working connection to the phone I am helpless. I am wondering if Verizon disables USB intentionally, so that the phone essentially becomes useless. Or, is it a coincidence and perhaps there is something wrong with the usb hardware.
Is there a way out of this other than having to pay for it to be fixed (which Samsung won't do - I called - and maybe Verizon not either).
Thanks in advance -
j-brah
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!
Hey there, I think my J3 2016 is bricked.
I accidently disabled the "OEM Unlock" in Developer Settings and now I am stuck at the samsung boot screen with a green text in left upper corner saying "Custom Binary blocked by FRP Lock".
I tried to flash the stock firmware with latest version of Odin, but the device isn't showing up. I have windows 7 and I reinstalled several times the drivers. My computer is recognizing it just as an Unknown Device.
Please help me, this is my only phone and at the moment I can't efford another one.
s4ss0 said:
Hey there, I think my J3 2016 is bricked.
I accidently disabled the "OEM Unlock" in Developer Settings and now I am stuck at the samsung boot screen with a green text in left upper corner saying "Custom Binary blocked by FRP Lock".
I tried to flash the stock firmware with latest version of Odin, but the device isn't showing up. I have windows 7 and I reinstalled several times the drivers. My computer is recognizing it just as an Unknown Device.
Please help me, this is my only phone and at the moment I can't efford another one.
Click to expand...
Click to collapse
It can be recovered (I've done that myself). Install Kies and smart switch for the drivers, reboot PC, Open Odin, put the stock firmware (preferably from sammobile) in the AP section, in options turn off auto-reboot, start phone in download mode (volume down, home button and power button together) and connect it,flash the firmware. When it's done reboot using vol up, down, home and power together until it turns on then switch on normally.
That's what worked for me, step by step.
Wulfie217 said:
It can be recovered (I've done that myself). Install Kies and smart switch for the drivers, reboot PC, Open Odin, put the stock firmware (preferably from sammobile) in the AP section, in options turn off auto-reboot, start phone in download mode (volume down, home button and power button together) and connect it,flash the firmware. When it's done reboot using vol up, down, home and power together until it turns on then switch on normally.
That's what worked for me, step by step.
Click to expand...
Click to collapse
The problem is that the phone isn't even showing in Device Manager. Installing and reinstalling drivers isn't useful.
s4ss0 said:
The problem is that the phone isn't even showing in Device Manager. Installing and reinstalling drivers isn't useful.
Click to expand...
Click to collapse
Hmm, I occasionally have issues if I use the wrong cable, have you tried changing that over?
The drivers should have sorted it out and made the phone visible really. I seem to remember that mine doesn't pop up in device manager if its in download mode (though that may be me remembering it wrong).
Wulfie217 said:
Hmm, I occasionally have issues if I use the wrong cable, have you tried changing that over?
The drivers should have sorted it out and made the phone visible really. I seem to remember that mine doesn't pop up in device manager if its in download mode (though that may be me remembering it wrong).
Click to expand...
Click to collapse
I have 6 cables, I've tried them all, not a single one works.
s4ss0 said:
I have 6 cables, I've tried them all, not a single one works.
Click to expand...
Click to collapse
Update; sometimes, if i connect the cable, the phone gets phisically found, but it isn't found like a device, just like "Unknown device". Can I do something?
s4ss0 said:
Update; sometimes, if i connect the cable, the phone gets phisically found, but it isn't found like a device, just like "Unknown device". Can I do something?
Click to expand...
Click to collapse
If no cables are working at all then I'm out of ideas sorry.
Ignoring Windows is a good bet, in download mode it often doesn't show up, focus more on whether or not you can see it in Odin, trying different versions of Odin can't hurt either I suppose.
Wulfie217 said:
If no cables are working at all then I'm out of ideas sorry.
Ignoring Windows is a good bet, in download mode it often doesn't show up, focus more on whether or not you can see it in Odin, trying different versions of Odin can't hurt either I suppose.
Click to expand...
Click to collapse
hey there, i just used an older version of odin as you told me and now it works. thanks for the help!
s4ss0 said:
hey there, i just used an older version of odin as you told me and now it works. thanks for the help!
Click to expand...
Click to collapse
No problem s4ss0, I'm glad it ended up being something fairly simple so you could get your phone back.
Connection issues
It is possible to get round the connection issue: Turn off the phone. Turn on the phone in download mode (vol-down, home, power). Connect a Samsung USB cable. Launch ODIN on your PC. Wait a few moments and you should see green text on top left of phone 'ODIN MODE'. Your phone is ready to take downloads.
Im having unique issue with my s 7edge.
I cant boot the phone it says Custom binary blocked by frp lock.
I cant access recovery mode it says Recovery is not seandroid enforcing.
I can access download mode but its not connecting to any pc, kies, odin. The download screen says FRP lock: ON, Secure Download: Enabled.
So there is no way to flash the phone or access recovery or boot the phone.
What is the solution, im stuck.?
FYI: I have searched all over the internet for hours but I couldn't found same issue.
Try using Samsung Smartswitch for emergency recovery
more info here
https://forum.xda-developers.com/tm...p/flash-stock-firmware-using-samsung-t3079176
EasyAndroidPro said:
Try using Samsung Smartswitch for emergency recovery
more info here
https://forum.xda-developers.com/tm...p/flash-stock-firmware-using-samsung-t3079176
Click to expand...
Click to collapse
Hi sir,
Thank you for the swift replay. However I went through the guide and tried so much thinks to connect my phone to the smart switch but with no luck.
When I connect the cable the PC is not detecting and and no windows sounds for cable connecting. Tried other phone with same cable and the windows could detect it. Tried on other PC and s7edge is not detected by window also. I tried reinstall the drivers by smart switch and not detecting. I have rebooted my PC without luck also. I have tried all the combinations you can imagine but nothing makes the phone detected by PC.
In my download mode screen in my phone shows the following
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secured Download: Enabled
WARRANTY VOID: 1 (0x020c)
RP SWREV: B:1 K:0 S:0
There is something in the phone is locked and not allowing to connect to any USB PC.
zevozki said:
Hi sir,
Thank you for the swift replay. However I went through the guide and tried so much thinks to connect my phone to the smart switch but with no luck.
Click to expand...
Click to collapse
i see the real problem is not connecting to pc then...
try:
updating drivers with this : http://developer.samsung.com/technical-doc/view.do?v=T000000117
Try:
manually deleting the drivers all together in windows and then plugging in your S7 while it is in Download Mode
Try:
unplugging all your USB in devices connectd to your pc (apart from keyboard/mouse) and then trying again
Try:
Using a different Cable (preferably the original one that came with the phone, this is the most common cause)
i see the real problem is not connecting to pc then...
try:
updating drivers with this : http://developer.samsung.com/technical-doc/view.do?v=T000000117
Click to expand...
Click to collapse
I tried that not detecting s7
Try:
manually deleting the drivers all together in windows and then plugging in your S7 while it is in Download Mode
Click to expand...
Click to collapse
I tried that not detecting the s7, all other USB devices detected
Try:
unplugging all your USB in devices connectd to your pc (apart from keyboard/mouse) and then trying again
Click to expand...
Click to collapse
I tried that, and not detecting s7
Try:
Using a different Cable (preferably the original one that came with the phone, this is the most common cause)
Click to expand...
Click to collapse
I tried with all cables including the original not detecting s7.
Generally there is no issue with PC to connect to mobile phones it connect perfectly with my other phones. Even the yesterday s7 was connected to my PC until I triggered the security and the phone stuck in the boot screen. The issue is in the s7 when its locked by (FRP Lock because of custom binary) its not allowing to connect to any PC. Something related to the phone security here.
zevozki said:
I tried that not detecting s7
I tried that not detecting the s7, all other USB devices detected
I tried that, and not detecting s7
I tried with all cables including the original not detecting s7.
Generally there is no issue with PC to connect to mobile phones it connect perfectly with my other phones. Even the yesterday s7 was connected to my PC until I triggered the security and the phone stuck in the boot screen. The issue is in the s7 when its locked by (FRP Lock because of custom binary) its not allowing to connect to any PC. Something related to the phone security here.
Click to expand...
Click to collapse
When you are trying to use samsung switch emergency recovery feature, it is a stand alone part of the program which does not require you to connect to smart switch.
It should see the phone and fix the problem. FRP happened to me and smart switch emergency recovery was able to fix it. As long as the phone can be accessed it can be fixed.
All you need is the model name and your serial number which should be posted on the back of your phone or maybe the box you have still have it.
Cosmic Blue said:
When you are trying to use samsung switch emergency recovery feature, it is a stand alone part of the program which does not require you to connect to smart switch.
It should see the phone and fix the problem. FRP happened to me and smart switch emergency recovery was able to fix it. As long as the phone can be accessed it can be fixed.
All you need is the model name and your serial number which should be posted on the back of your phone or maybe the box you have still have it.
Click to expand...
Click to collapse
I have gone through that path, the phone cable unplugged initially. Then I selected more>emergency software recovery and initialization>
two tabs are there, 1- Emergency software recovery, 2- Device initialization.
1- Emergency software recovery: there is no update failed in the list, also I dont have recovery code for the same. no use of this option
2- Device initialization: I have entered the model and SN correctly and it found the stock software, I selected OK for the warning dialog until it reached the stage asking to put the s7 in the download mode, I did that with phone plugged in by USB. I waited forever for the "OK" button to be active, its grayed out because the s7 is not detected at all. So I am in the same loop again, the phone locking all the USB connections.
screenshot of smart switch
http://imgur.com/a/jUj7q
zevozki said:
I have gone through that path, the phone cable unplugged initially. Then I selected more>emergency software recovery and initialization>
two tabs are there, 1- Emergency software recovery, 2- Device initialization.
1- Emergency software recovery: there is no update failed in the list, also I dont have recovery code for the same. no use of this option
2- Device initialization: I have entered the model and SN correctly and it found the stock software, I selected OK for the warning dialog until it reached the stage asking to put the s7 in the download mode, I did that with phone plugged in by USB. I waited forever for the "OK" button to be active, its grayed out because the s7 is not detected at all. So I am in the same loop again, the phone locking all the USB connections.
screenshot of smart switch
http://imgur.com/a/jUj7q
Click to expand...
Click to collapse
leave the phone with the screen showing the FRP lock, plug the cable in and use smart switch device initialization.
It should start without asking you to put it in without going to download mode. If it asks that, just unplug and replug the usb to the phone, that usually lets smart switch to bypass that request.
Cosmic Blue said:
leave the phone with the screen showing the FRP lock, plug the cable in and use smart switch device initialization.
It should start without asking you to put it in without going to download mode. If it asks that, just unplug and replug the usb to the phone, that usually lets smart switch to bypass that request.
Click to expand...
Click to collapse
here is something odd and not as all people see it, when I turn the phone power on it start with samsung welcome screen with red sentence in top "Custom binary blocked by FRP Lock" the screen stays on for 5 seconds then the phone goes off.
If I do the same thing with USB cable plugged in with phone off, its automatically power on with charging screen with red sentence on top "Custom binary blocked by FRP Lock" and then the phone goes off and restart the same thing in infinity loop. So when I tried what you said in smart switch to install the firmware it didnt do anything, no installation started, no bypass FRP, the phone still looping on off, OK button grey.
I am reaching to no clue after all your guidance and help. I think the USB port is damaged and not reading data, only charging.
zevozki said:
here is something odd and not as all people see it, when I turn the phone power on it start with samsung welcome screen with red sentence in top "Custom binary blocked by FRP Lock" the screen stays on for 5 seconds then the phone goes off.
If I do the same thing with USB cable plugged in with phone off, its automatically power on with charging screen with red sentence on top "Custom binary blocked by FRP Lock" and then the phone goes off and restart the same thing in infinity loop. So when I tried what you said in smart switch to install the firmware it didnt do anything, no installation started, no bypass FRP, the phone still looping on off, OK button grey.
I am reaching to no clue after all your guidance and help. I think the USB port is damaged and not reading data, only charging.
Click to expand...
Click to collapse
Can you tell me the resolution of this problem in your case? I have the same problem, although I haven't gotten word back from the seller who may or may not have the serial number, so I haven't been able to even try Smart Switch at all.
Dave Kelsen
Dave Kelsen said:
Can you tell me the resolution of this problem in your case? I have the same problem, although I haven't gotten word back from the seller who may or may not have the serial number, so I haven't been able to even try Smart Switch at all.
Dave Kelsen
Click to expand...
Click to collapse
I had taken it to shop and replaced the whole motherboard in my case. That fixed my problem, yours better luck than me you only need serial number.
zevozki said:
I had taken it to shop and replaced the whole motherboard in my case. That fixed my problem, yours better luck than me you only need serial number.
Click to expand...
Click to collapse
I was able to use Odin to reset my phone, after downloading the correct firmware from SamMobile. It took me a very long time to download, as my wireless connection is through my phone, and my household was over 60GB this month.
But I got it done, and have a working S7 Edge again. Sorry that you apparently had a hardware issue, but at least you got it working again.
Dave Kelsen
Howdy,
I've used the Tab A for a couple of months now as literally a daily driver, since I modified it to fit into the multimedia slot in my car. It was rooted, had TWRP and even Viper4Android on it.
Long story short:
Since it's laggy I thought to test project Treble on it, since it's supported.
I wiped the tablet with TWRP and installed arm64 A/B (since it's Android 10) and it wouldn't boot anymore. It showed "Samsung Galaxy Tab A", shut off, vibrated and repeat. Also tried "Only A". Same result.
I thought to install it via fastboot. Since TWRP effectively replaced Fastbook afaik, I tried to flash the original "BL" downloaded form sammobile for this exact model. Flashed it, it succeeded and then...
It turns on with a blue screen that essentially says "This phone has been modified and is locked" with red letters on top stating "SECURE CHECK FAIL: recovery.img"
I can't get into download, it always jumps to this message. I tried all possible combinations, plugged the tablet into my pc while holding down buttons - nothing.
If I hold the pwr+down for circa 10-15 seconds while in this screen, it reboots and goes to a slightly different message stating: "SECURE CHECK FAIL: boot.img"
My PC doesn't recognize any USB devices, not even in the device manager.
What should I do? Any help would be greatly appreciated.
(I guess no music on the daily commute tomorrow lol)
Tried a Samsung JIG adapter. Still no success
Finally good news!
I tried it again with new combinations.
Turns out, if you hold all three buttons (pwr, down and up) eventually DOWNLOAD mode appears.
Worked here and am flashing stock now.
For rooting on latest bootloader (Rev:4, U4) which is the one you've installed already, you must purchase a subscription on this page and download that file for root:
https://support.halabtech.com/index.php?a=downloads&b=file&id=452768
As you described, it seem that you updated the bootloader and there's no way to get back at Rev:3 U3 bootloader, having the same trouble in rooting terms, I just hope a developer or an advance user that have a subscription in such page can help us and share the file that is on that page
Mafworld said:
For rooting on latest bootloader (Rev:4, U4) which is the one you've installed already, you must purchase a subscription on this page and download that file for root:
https://support.halabtech.com/index.php?a=downloads&b=file&id=452768
As you described, it seem that you updated the bootloader and there's no way to get back at Rev:3 U3 bootloader, having the same trouble in rooting terms, I just hope a developer or an advance user that have a subscription in such page can help us and share the file that is on that page
Click to expand...
Click to collapse
No it wont work i have tried it. It gets secure check fail boot.img