Samsung galaxy Tab A7 CF stuck in odin mode. - General Questions and Answers

Hello,
I have a Tab A SM t285, that I tried to root using cf autoroot. The process didn't work and now the device shows "There was an error while updating software. Use emergency recovery from smart switch software". But the smart switch emergency recovery is not detecting my device. I also forgot to enable OEM unlocking. Is there anything I can do to fix this?

pAcMaN0 said:
Hello,
I have a Tab A SM t285, that I tried to root using cf autoroot. The process didn't work and now the device shows "There was an error while updating software. Use emergency recovery from smart switch software". But the smart switch emergency recovery is not detecting my device. I also forgot to enable OEM unlocking. Is there anything I can do to fix this?
Click to expand...
Click to collapse
If you know exactly which version of stock firmware was on the device before you did this, find a copy of that version stock firmware then flash the stock firmware via Odin. You dont have to be in download mode, Odin can flash the firmware while the device is booted into the "encountered an issue" screen, I've done it many times.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If you know exactly which version of stock firmware was on the device before you did this, find a copy of that version stock firmware then flash the stock firmware via Odin. You dont have to be in download mode, Odin can flash the firmware while the device is booted into the "encountered an issue" screen, I've done it many times.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Does it have to be the exact same version of firmware? I have downloaded the latest version but I'm not sure which version I had earlier.

pAcMaN0 said:
Does it have to be the exact same version of firmware? I have downloaded the latest version but I'm not sure which version I had earlier.
Click to expand...
Click to collapse
It has to be the version you had or anything newer, it can't be anything older than what you had. That is all.
Sent from my SM-S767VL using Tapatalk

It says custom recovery blocked by frp lock.
Is there a way to disable frp lock?

pAcMaN0 said:
It says custom recovery blocked by frp lock.
Is there a way to disable frp lock?
Click to expand...
Click to collapse
It says that when you flash the full stock firmware?
Find a combination firmware for your specific model number. Do a Google search for:
"Combination firmware for (your specific model number)"
Find a combination firmware that has the same Binary version as the firmware that you downloaded or at least a Binary version that is 1 number lower than the firmware that you downloaded. As long as the combination firmware has a binary that is equal to or newer than what was on the device before this happened and at the same time lower than or equal to the binary of the firmware that you downloaded, it will work.
You can find the binary version by looking at the 5th character counting backward from the right end of the firmware build number.
Flash the combination firmware, let it boot, when it boots to system, open system settings and enable developer options then find the OEM unlock setting and enable it. Then enable USB debugging. Then find and disable the Google "find my device" setting, then power off the device. Then boot the device into stock recovery and use the options to factory reset the device then wipe the cache partition.
Then, power the device off and boot into download mode and try flashing the full stock firmware.
Sent from my SM-S767VL using Tapatalk

Thank you so much @Droidriven. I was able to Boot into combination firmware and I hope I can flash stock without any further problems after enabling OEM unlock.

I'm facing one more problem. In factory binary mode I'm not finding an OEM unlock option in developer options.

pAcMaN0 said:
I'm facing one more problem. In factory binary mode I'm not finding an OEM unlock option in developer options.
Click to expand...
Click to collapse
It isn't "required", you can try flashing the full stock firmware. If you signed into the combination firmware with your email address, go to system settings and remove your account before flashing the firmware. That should prevent FRP from blocking you again.
Sent from my SM-S767VL using Tapatalk

Related

HELP!! Custom Binary Blocked by FRP

Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?
rishab_s said:
Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?
Click to expand...
Click to collapse
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD
daveuk87 said:
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD
Click to expand...
Click to collapse
I have already tried that.
rishab_s said:
I have already tried that.
Click to expand...
Click to collapse
This could sound like a really dumb suggestion but remove your google account and retry. Could it be the factory reset protection?
Sent from my SM-T810 using Tapatalk
I returned it, will be getting a refund and will buy another one
I have the exact same problem with my SM-G955F
It has FRP lock on it
It originally could boot up, but then the google screen would ask for a password
I then went to try and flash TWRP on it which did not work
I then tryed to install the samsung stock firmware for android 8.0.0 which brings up "Custom Binary(RECOVERY) Blocked by FRP Lock"
I dont know the password, so could not enter one
I only have access to the Download screen on the phone
Flashed AP "AP_G955FXXU1CRB7_CL12993656_QB17006520_REV00_user_low_ship_meta.tar.md5"
ON PHONE SCREEN IN DOWNLOAD MODE: KERNEL REV. CHECK FAIL. DEVICE:11, BINARY:1
What can i do to remedy this ?

Bricked Samsung SM-J700F please help me guys

Hello guys I am noob please help me guys
Yesterday i installed [ROM][7.0][STABLE][BUILD 1.5][GENISYS XPERIENCE ROM][J700F/H/M]
it was working fine but issue is kernel seandroid enforcing but phone was working
i tried to install EDGE PANEL GENISYS XPERIENCE patch
here i switched off USB DEBUGGING AND OEM LOCK
i tried volume+home+power phone got off
when i trying to on it says custom binary custom binary blocked by frp lock
i tried to flash many recoveries + stock rom but no use please help
after reading many posts i tried to download stock firm from sammobile.com but unable to download
now only working is i can get in download mode nothing else
sorry for my bad english can say wrost
~KUMAR~ said:
Hello guys I am noob please help me guys
Yesterday i installed [ROM][7.0][STABLE][BUILD 1.5][GENISYS XPERIENCE ROM][J700F/H/M]
it was working fine but issue is kernel seandroid enforcing but phone was working
i tried to install EDGE PANEL GENISYS XPERIENCE patch
here i switched off USB DEBUGGING AND OEM LOCK
i tried volume+home+power phone got off
when i trying to on it says custom binary custom binary blocked by frp lock
i tried to flash many recoveries + stock rom but no use please help
after reading many posts i tried to download stock firm from sammobile.com but unable to download
now only working is i can get in download mode nothing else
sorry for my bad english can say wrost
Click to expand...
Click to collapse
The issue is you turned of oem unlock which is always needed. I think only option is flashing of stock rom through odin no other option i know of. i guess its hardbricked mostly.
Download the latest samfirm tool available on xda.
Open the samfirm tool. Enter model and region. Tick Auto and binary nature.
Click on Check update. It will show the latest firmware available on samsung server.
Then click on download. It will download four file full firmware. Then flash it through odin.
You need a strong internet connection to download the file.
All the best.
rajnikant574 said:
Download the latest samfirm tool available on xda.
Open the samfirm tool. Enter model and region. Tick Auto and binary nature.
Click on Check update. It will show the latest firmware available on samsung server.
Then click on download. It will download four file full firmware. Then flash it through odin.
You need a strong internet connection to download the file.
All the best.
Click to expand...
Click to collapse
Thank you rajiKanth as gou said Everything done
Now i got back My phone but thing Is not supporting voLTE
Have you flashed CSC OR HOME_CSC ?
If you have flashed CSC then check with the Network setting
What is your phone model and region?
I flashed only AP file only I don't have CSC
I got but it's md5 error
My phone model is SM-700F
Region INDIA
~KUMAR~ said:
I flashed only AP file only I don't have CSC
I got but it's md5 error
My phone model is SM-700F
Region INDIA
Click to expand...
Click to collapse
Have you checked Binary Nature before Check Update?
~KUMAR~ said:
I flashed only AP file only I don't have CSC
I got but it's md5 error
My phone model is SM-700F
Region INDIA
Click to expand...
Click to collapse
Simply install TWRP using odin. And flash hyperion v2 rom alongwith fix file. I hope it'll sort out ur volte problem as well you'll get a high quality rom experience for this model. I am using the same in India.
Samfirm is completely garbage.use updato from play store, it's called android updates after u search for updato.download and Search up your firmware. Copy to computer and unzip then reboot to download mode.load firmware into AP slot. Tick nand erase and reboot. Begin flash of firmware. When it reboots u are fully stock. Start over, flash twrp then whatever ROM and root etc. Samfirm never even works. Don't waste your time.
pkjha.dylangroup said:
Simply install TWRP using odin. And flash hyperion v2 rom alongwith fix file. I hope it'll sort out ur volte problem as well you'll get a high quality rom experience for this model. I am using the same in India.
Click to expand...
Click to collapse
Thanks for replay I did same as you said but I installed enigma ROM which is awesome rom

Can I flash TWRP backup through ODIN?

I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.
Thanks! Already figured it out ?
please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.
Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it
Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?

Rooting Samsung Galaxy J3 (2018)

Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
ben480 said:
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
Click to expand...
Click to collapse
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Droidriven said:
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
ben480 said:
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
Click to expand...
Click to collapse
I'll explain the "OEM unlock" setting a bit first. The OEM unlock setting does not necessarily unlock your bootloader. On some devices, enabling this setting unlocks bootloader but on most devices it does not actually unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked using some form of unlock method after enabling the setting. In these cases, the unlock method would not work without enabling OEM unlock setting before implementing the unlock method.
So, basically, what I'm saying is that even though you have the OEM unlock setting, this does not necessarily mean that your bootloader is unlocked just by toggling this setting, it may still be locked even after toggling the setting. You'll have to verify whether your bootloader is actually unlocked or not. Do some Google searches for:
"Check bootloader status on Samsung devices"
This should give you results to find a method to verify your bootloader status.
Once you have verified that your bootloader is unlocked, you can use the Magisk rooting method. Read the "Boot Image Patching" section in the link below, there are also several other guides all over the internet and videos on YouTube that give instructions on patching your boot.img. As for actually flashing the boot.img, you will be flashing it using Odin. Use 7zip to compress the patched boot.img into a .tar compressed file. When you flash the file using Odin, place .tar file in the AP slot in Odin.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Sent from my LGL84VL using Tapatalk

SM-J530F not booting after android 9 update with odin

My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
kevin50206 said:
My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
Click to expand...
Click to collapse
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
kevin50206 said:
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
Click to expand...
Click to collapse
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Droidriven said:
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Click to expand...
Click to collapse
Yes i matched the model number and no i was not running anything that isn't for it
kevin50206 said:
Yes i matched the model number and no i was not running anything that isn't for it
Click to expand...
Click to collapse
But are you using the most up to date firmware? Older/downgraded firmware won't work, it has to be exactly the same binary as what is already on the device or a firmware with a newer binary, it can not be a firmware that has an older binary than the firmware that is already on the device.
Sent from my SM-S767VL using Tapatalk

Categories

Resources