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
Related
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
I just flashed the OK4 tar via odin to go back to stock and take the MM update again. I wiped everything but internal and external storage in TWRP first. It's currently downloading the MM update.
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
pyrochance said:
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
Click to expand...
Click to collapse
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
djxn40 said:
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
pyrochance said:
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
Click to expand...
Click to collapse
I assumed you couldn't revert. That's awesome though thanks
Sent from my SM-G900P using Tapatalk
I can also confirm that too, I just did a downgrade to OK4, after I unsuccessfully tried to downgrade to OA6. I assume that pyrochance (http://forum.xda-developers.com/showpost.php?p=66266625&postcount=138) is right.
If i was helpful, feel free to hit the thanks button on those posts
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
ZedDedd said:
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
Click to expand...
Click to collapse
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Kreatur3 said:
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Click to expand...
Click to collapse
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
ZedDedd said:
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
Click to expand...
Click to collapse
They could allow it but won't. It's obvious with the direction they are going with the s7. I can see why maybe providers don't want you to have that power but don't know why the manufacturer cares. Beyond the pressure from cell phone companies. I don't care about knox personally. I'm way beyond the warranty period and trip it every time the day I gety phones.
highspeedfelon said:
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
Click to expand...
Click to collapse
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
alphadude said:
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
Click to expand...
Click to collapse
You are welcome.
I'm having a bit of trouble. I was on MM, then the phone started freezing up. So I went back to OK4 but I can't get past the Samsung boot up logo. It stays on there forever and doesn't move past it. I even tried to replays through Odin multiple times but still not working. I'm stuck.
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 ?
My Samsung S8 Plus G955FD not detecting SIM card after upgrade from Custom OS 8.0 to Official Android 9.0. I have downloaded another stock ROM 8.0 to downgrade back but it is not working. I also downloaded another Stock ROM Nougat but it is showing error on ODIN tool.
Please help me, any way out?
immesd said:
My Samsung S8 Plus G955FD not detecting SIM card after upgrade from Custom OS 8.0 to Official Android 9.0. I have downloaded another stock ROM 8.0 to downgrade back but it is not working. I also downloaded another Stock ROM Nougat but it is showing error on ODIN tool.
Please help me, any way out?
Click to expand...
Click to collapse
Boot into stock recovery and factory reset the device in recovery then wipe the cache partition.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Boot into stock recovery and factory reset the device in recovery then wipe the cache partition.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i have done this but still not booting pass SAMSUNG LOGO
immesd said:
i have done this but still not booting pass SAMSUNG LOGO
Click to expand...
Click to collapse
Was the firmware that you flashed made for G955FD? If it was not specifically for the G955FD, that is the issue. You need a firmware specifically for G955FD, the other G955 versions of firmware might not be completely compatible.
Sent from my SM-S767VL using Tapatalk
droidriven said:
was the firmware that you flashed made for g955fd? If it was not specifically for the g955fd, that is the issue. You need a firmware specifically for g955fd, the other g955 versions of firmware might not be completely compatible.
Sent from my sm-s767vl using tapatalk
Click to expand...
Click to collapse
thanks for your time. I will confirm and feed you back
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
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Skulper said:
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
brokboi said:
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
Click to expand...
Click to collapse
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Droidriven said:
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Click to expand...
Click to collapse
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
brokboi said:
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
Click to expand...
Click to collapse
Have you used TWRP to create a android backup of your stock ROM after you got it fixed? If not, do so, then store a copy of the backup on a PC or USB flashdrive, external sdcard, etc.. That backup can be used to restore your device, if needed.