"Only Official released binaries are allowed to be flashed" Galaxy A8 - Samsung Galaxy A8 (2018) Questions & Answers

Hello, my Samsung galaxy a8 (SM-A530W) was in bootloop saying "only official released binaries are allowed to be flashed". So, I downloaded the stock firmware and tried to flash it and this came up.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5165 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
what do i do to fix this

another port usb ?

adek89 said:
another port usb ?
Click to expand...
Click to collapse
ok
thnx

adek89 said:
another port usb ?
Click to expand...
Click to collapse
can you give me instructions??

SkyWasTaken2032_ said:
Hello, my Samsung galaxy a8 (SM-A530W) was in bootloop saying "only official released binaries are allowed to be flashed". So, I downloaded the stock firmware and tried to flash it and this came up.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5165 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
what do i do to fix this
Click to expand...
Click to collapse
did you turn on oem unlocking ? from developers option !

Related

[Q]Please Help!!!!!! Wrong recovery flashed on SGH-i337 At&t S4

By mistake I Flashed Philz touch recovery on my s4 i337 through a phone application "RASHR" and when i restarted my Phone it says
"System Software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest At&t store for help"
The I googled it and found that my phone is softbricked and I have to reflash the stock rom. Then i downloaded the stock roms I337UCUAMDB and I337UCUAMDL .
But while flashing them I get this
Log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
The phone displays this:
Start [224, 1440]
SV REV. CHECK FAIL : FUSED : 2, BINARY : 1
I get this message from both the above roms.
Please help!!!!! :crying: :crying: :crying:
Amisaini said:
By mistake I Flashed Philz touch recovery on my s4 i337 through a phone application "RASHR" and when i restarted my Phone it says
"System Software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest At&t store for help"
The I googled it and found that my phone is softbricked and I have to reflash the stock rom. Then i downloaded the stock roms I337UCUAMDB and I337UCUAMDL .
But while flashing them I get this
Log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
The phone displays this:
Start [224, 1440]
SV REV. CHECK FAIL : FUSED : 2, BINARY : 1
I get this message from both the above roms.
Please help!!!!! :crying: :crying: :crying:
Click to expand...
Click to collapse
At your service
What version of android were you on before, was it 4.3 or later touchwiz? also can you boot to recovery?
REMEMBER TO HIT THAT THANKS BUTTON IF I HELPED

My note 10.1 is only white striped screen

I have a 2012 edition galaxy note 10.1 wifi. GT-N8010
I can only start it up and the black with white stripes screen shows up.
When I put it in chargeing the screen cames up again and can't turn it of. No charging lights or symbol.
I have early rooted this device so it coul run as 64gb memory from sd card, but after it have not been used abot 4 monts, it have been this now.
I can go into Odin mode when I push power and volume up. Then it says downloading mode. No notofication screen. No recovery screen when i push volume down. only the screen with white stripes. (see attachments)
The status i download mode is:
ODIN MODE
Product name:
Custom binary download: no
Current binary: samsung official
System status: Custom
I have tried to get it communicate with two pc's, but no ones finds it. No green com port in odin software on both pc's. I believe it's because I don't have usb debugging on. I can't activate that, because my pad not starts. No boot logo. How can I solve this. Please help.
I have installed all necessary drivers on both pcs.
Hey, did you find any solution to this problem? I had this same issue in my 10.1 but donĀ“t seem to find what the problem is.
ASA OP has not been on the forum since 2015 you are asking a ghost.
The answer for the OP would be flash stock rom through Odin .
Upgrade Fail - Samsung GT-N8010
:crying:
I have a similar problem needing to updrade Android to Kit Kat on my Samsung Note 10.1 (GT-N8010). I bought the unit in the UAE and am now in Australia. I turns out that I need the UAE version (XSG). Downloaded and then
Entered C:\Users\chris\Downloads\N8010XXUDNF3_N8010OJVDNF3_XSG\N8010XXUDNF3_N8010OJVDNF3_HOME.tar.md5 in AP Window
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1794 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tablet is showing "Downloading....Do Not Turn off Target"
Any Ideas would be greatly appreciated
White stripped screen ??
sboot.bin fail
Reasons .
Sboot.bin is failing because the ROM is not for your phone, the bootloader in the phone is newer than the bootloader in the ROM,
you need to use the original Samsung USB cable, or a different USB 2.0 port.
Cannot Upgrade Android on Samsung Galaxy Note 10.1 (GT-N8010)
Thanks for the response would you suggest another thread for this problem? I get the white screen intermittently.
I am using the original cable and have tried all three USB ports on the laptop. I am using the right file in the AP section? C:\Users\chris\Downloads\N8010XXUDNF3_N8010OJVDNF3_XSG\N8010XXUDNF3_N8010OJVDNF3_HOME.tar.md5
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1794 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1794 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1794 M
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1794 M
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Can't open the serial(COM) port.
Try removing Kies and installing Samsung USB drivers .
Check
1. You are using an original quality USB cable and not a thinner USB charging cable.
2. You are connecting directly to the PC USB port and not through a USB hub.
3. Try another PC USB port.
4. Try another Odin version.

Trouble flashing the T-Mobile Firmware on my MetroPCS S7

So, I know there are ways to flash different firmware on to each Galaxy S7, Metro and T-Mobile are pretty much the most similar of each version. What I'm trying to do is make it so my G S7 is stock T-Mobile so that I can update it to the Nougat Beta. I'm sort of impatient lol. Here's the errors I'm getting:
This one is in Odin and I'm using the modified version that I used originally to root my S7 which BTW is back to stock unrooted.
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone shows this in RED:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
[1]eMMC write fail: aboot
I'm not sure what the problem is, I have my drivers installed, I have debugging checked and I'm using an HTC usb cord only because they are better with data transfers than the stock Samsung cord in my experience. I'm not sure what I'm doing wrong.
Help? :fingers-crossed:
jawshdarnit said:
So, I know there are ways to flash different firmware on to each Galaxy S7, Metro and T-Mobile are pretty much the most similar of each version. What I'm trying to do is make it so my G S7 is stock T-Mobile so that I can update it to the Nougat Beta. I'm sort of impatient lol. Here's the errors I'm getting:
This one is in Odin and I'm using the modified version that I used originally to root my S7 which BTW is back to stock unrooted.
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone shows this in RED:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
[1]eMMC write fail: aboot
I'm not sure what the problem is, I have my drivers installed, I have debugging checked and I'm using an HTC usb cord only because they are better with data transfers than the stock Samsung cord in my experience. I'm not sure what I'm doing wrong.
Help? :fingers-crossed:
Click to expand...
Click to collapse
Use the unmodified version
Okay will do. I'll post again if any issues arise.
kitila said:
Use the unmodified version
Click to expand...
Click to collapse
Used the most up to date version and still getting same error message.
kitila said:
Use the unmodified version
Click to expand...
Click to collapse
I downloaded the zip file from sammobile and used the newest version of Odin and it worked! Thank you so much for your help sir! :good:

Help Flashing back to stock.

I'm trying to get back to stock and odin keeps throwing an error.
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
After the error, my phone reads "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2" and after a good search, someone said it was because I was installing a custom rom with odin, but I'm flashing over the stock one.
Flash latest rom
amarshah said:
Flash latest rom
Click to expand...
Click to collapse
I'm trying to do that, that's the error I get.
Charmeleomander said:
I'm trying to do that, that's the error I get.
Click to expand...
Click to collapse
Ohh ...than flash 4 firmware file together here it is
https://forum.xda-developers.com/galaxy-j7/development/j700h-marshmallow-update-method-rom-t3399433
My imei is null after flashing Rom
And now my SIM is not detected in this mobile
I tried flashing stock Rom via odin nothing works throws errors as 'sw rev secunity check fail device 3 binary 2' and ' security check fail bootloader'
though I flash latest Rom!
If I flash custom Rom still SIM is not recognised
Help me how to fix?

I NEED HELP!!! 955U ODIN Failed, then recovery failed and FRP LOCK

So the other day I was going to try rooting my s8+ with Snapdragon processor and US model. I downloaded Prince comsy ODIN 3.12 and then was going to flash the SAM PWND software for my model. Odin failed and then at the point, my phone would not load past the Verizon logo on bootup. So after multiple tries I decided well mabye a factory reset will work. I was wrong, so now the reset erased data then started updating software and the android guy dies and says no commands. I can get to recovery mode and I have tried safe mode, normal reboot and even if i turn device off it turns right back on and will continue in a boot loop. I was using a USB 3.0 Port when I first tried the Odin flash, but then i read that is bad so ive only used my usb 2.0 ports after that.
** After odin fails my phone Sometimes says " SW REV CHECK FAIL : [ABL] FUSED 4 >BINARY 3
It always says FRP lock: ON will this be my cause?
So now I downloaded
AP_G955USQS3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT_meta.tar
BL_G955USQS3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT.tar
CP_G955USQS3CRE2_CP9619736_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT.tar
CSC_OYN_G955UOYN3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT.tar
HOME_CSC_OYN_G955UOYN3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT.tar
USERDATA_USC_G955USQS3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT.tar
I have tried only flashing the BL and the CSC but still a no go. It keeps failing. I also placed the AP with AP, BL with BL, CP with CP, and the HOME CSC with CSC, and the log fails as shown below... I have spaced the log where the fails are located..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Removed!!
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> apdp.mbn
<ID:0/004> msadp.mbn
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4636 M
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> apdp.mbn
<ID:0/004> msadp.mbn
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4636 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> abl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> apdp.mbn
<ID:0/004> msadp.mbn
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4636 M
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Removed!!
<ID:0/004> Removed!!
<ID:0/004> skip file list for home binary
<ID:0/004> apdp.mbn
<ID:0/004> msadp.mbn
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4636 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port. WHAT!!!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4636 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4636 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4636 M
<ID:0/003> SetupConnection..
I have tried multiple usb ports and cables. I have read many forums of ODIN fails, some reset phones without odin and it works, others try over and over then normally get it on try 3 or 4, some reset odin, I even have a normal un modded version of odin 3.13 and thats what im currently using and that is what the log above is from. I was on Oreo 8.0 before messing up the phone. I have spent alot of time messing with this phone but cant figure it out. Im on a laptop with windows 7 premium 64bit.
ANY and all help is greatly appreciated :/ THANK YOU FOR YOUR TIME!!!
Also please note during the time I use odin, I never see a status on the top in the squares, untill it fails then I see a red FAIL. I noticed in other threads I looked at it showed status like Boot, recovery, etc... even a green PASS when it works. I see NOTHING untill it fails and I see the red fail.
bad signal
Hello can anyone help me please with a quick response my data connection (here in Algeria) is always on H+ and never 4G. I've been around other phones that will get 4G everywhere but I won't and the signal bars are to bad and many people's caled me and i dont reserve there calls please any solution !!?
Phone has been flash to the last frameware from sammobile by odin and reset to factory and still doing this. Any ideas?
Hasanberkdar said:
Hello can anyone help me please with a quick response my data connection (here in Algeria) is always on H+ and never 4G. I've been around other phones that will get 4G everywhere but I won't and the signal bars are to bad and many people's caled me and i dont reserve there calls please any solution !!?
Phone has been flash to the last frameware from sammobile by odin and reset to factory and still doing this. Any ideas?
Click to expand...
Click to collapse
This is considered thread hijacking and is considered rude.Please post in your own Q&A thread
Did you get anything fixed?? If I was in this situation I'd use this modified Odin and the most recent update for the phone. It's Verizon right?? The link is a Verizon firmware with Oreo 8.0.
https://updato.com/firmware-archive-select-model?record=3F235DC8792011E89F15FA163EE8F90B
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------
overclocked636 said:
Also please note during the time I use odin, I never see a status on the top in the squares, untill it fails then I see a red FAIL. I noticed in other threads I looked at it showed status like Boot, recovery, etc... even a green PASS when it works. I see NOTHING untill it fails and I see the red fail.
Click to expand...
Click to collapse
Something similar happened to me first. I used the Odin provided from the link. Sometimes I'd have to re-extract the file for it to work.
Thanks I'll try it
eddyo1993 said:
Did you get anything fixed?? If I was in this situation I'd use this modified Odin and the most recent update for the phone. It's Verizon right?? The link is a Verizon firmware with Oreo 8.0.
https://updato.com/firmware-archive-select-model?record=3F235DC8792011E89F15FA163EE8F90B
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------
Something similar happened to me first. I used the Odin provided from the link. Sometimes I'd have to re-extract the file for it to work.
Click to expand...
Click to collapse
I'll try that when I get home I appreciate the help!!
That updato link does not work. I found same one on Sam mobile but it's being a pain to download, It wants me to log in so I log in then I clicked the link then at wants me to log in again or pay
overclocked636 said:
That updato link does not work. I found same one on Sam mobile but it's being a pain to download, It wants me to log in so I log in then I clicked the link then at wants me to log in again or pay
Click to expand...
Click to collapse
The link seem to work for me. Go to updato.com then type in your model number
overclocked636 said:
That updato link does not work. I found same one on Sam mobile but it's being a pain to download, It wants me to log in so I log in then I clicked the link then at wants me to log in again or pay
Click to expand...
Click to collapse
This is the firmware with CRE9 update.
https://ibb.co/eB5P8U
See photo attached , this happens when I click the download button. :/
I do appreciate your time and helping me , can't wait to fix this darn phone
I got it downloading from Sam mobile
overclocked636 said:
I got it downloading from Sam mobile
Click to expand...
Click to collapse
Never seen that happen before. Try using the Odin I sent you that's what I used before on my phone and it worked. Did you manually looked up the firmware on updato? Also if sammobile is sill an issue I could upload the firmware on Google Drive and send you the link.
---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------
overclocked636 said:
I got it downloading from Sam mobile
Click to expand...
Click to collapse
Also please press the reply button so I get notified.
eddyo1993 said:
Did you get anything fixed?? If I was in this situation I'd use this modified Odin and the most recent update for the phone. It's Verizon right?? The link is a Verizon firmware with Oreo 8.0.
https://updato.com/firmware-archive-select-model?record=3F235DC8792011E89F15FA163EE8F90B
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------
Something similar happened to me first. I used the Odin provided from the link. Sometimes I'd have to re-extract the file for it to work.
Click to expand...
Click to collapse
eddyo1993 said:
Never seen that happen before. Try using the Odin I sent you that's what I used before on my phone and it worked. Did you manually looked up the firmware on updato? Also if sammobile is sill an issue I could upload the firmware on Google Drive and send you the link.
---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------
Also please press the reply button so I get notified.
Click to expand...
Click to collapse
I did look up on updato and I got a error still, I downloaded the Odin you provided so I will be trying that either tonight if I get home early from class or tomorrow after work, I got the firmware downloaded late last night so should be good to go now I hope!! Sam mobile is no longer a issue it successfully downloaded ... I don't know why I was having issue before. Thanks so much. I'll let you know how it goes. Do I need combination firmware to unlock my FRP?
overclocked636 said:
I did look up on updato and I got a error still, I downloaded the Odin you provided so I will be trying that either tonight if I get home early from class or tomorrow after work, I got the firmware downloaded late last night so should be good to go now I hope!! Sam mobile is no longer a issue it successfully downloaded ... I don't know why I was having issue before. Thanks so much. I'll let you know how it goes. Do I need combination firmware to unlock my FRP?
Click to expand...
Click to collapse
I'm not sure on the FRP. Is that when Google ask you to sign in before you can use the phone? Keep me updated if it worked.
eddyo1993 said:
I'm not sure on the FRP. Is that when Google ask you to sign in before you can use the phone? Keep me updated if it worked.
Click to expand...
Click to collapse
Eddy, it worked!!!!! Thank you for your time it is much appreciated. I guess I was trying to flash the 3 bootloader is was blocking it out , maybe i already had bootloader 4 on it so had to go back to 4. Thank you again!!!
overclocked636 said:
Eddy, it worked!!!!! Thank you for your time it is much appreciated. I guess I was trying to flash the 3 bootloader is was blocking it out , maybe i already had bootloader 4 on it so had to go back to 4. Thank you again!!!
Click to expand...
Click to collapse
Yes, you can only SAM PAWND and other similar ROMs ONLY if your bootloader is V3 or earlier.
Samsung has patched V4 and V5 already, so until another work around is found, we are stuck with no root..
You can try the safestrap (Bootstrap) thing if you are feeling brave...
https://forum.xda-developers.com/ga...recovery-locked-nougat-7-0-safestrap-t3772761
overclocked636 said:
Eddy, it worked!!!!! Thank you for your time it is much appreciated. I guess I was trying to flash the 3 bootloader is was blocking it out , maybe i already had bootloader 4 on it so had to go back to 4. Thank you again!!!
Click to expand...
Click to collapse
Hey!!! No problem I'm glad it worked!!! Just help others out if they need it as well. You had 200+ people see your post but none helped out. Anything comes up please feel free to PM me.
did you try to flash the firmware with proper binary?

Categories

Resources