A520F Binary -1 cant flash - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

Hello everybody,
Today I tried to flash the following firmware with Odin. As in the instructions, I first flashed step 1 and then step 2 using Odin.
SM-A520FXXS8CSh5_8.1_REMOVE LOCK SCREEN WITHOUT LOSE user DATA WITH FRP ON bootloader ON
when booting I got the message:
Code:
NAD: PASSED
RPMB PROVISIONED
then i have flashed Step 1 and Step 2 with the following Image:
firmware.gsm-social
A520FXXS7CSAB_8.0_REMOVE LOCK SCREEN WITHOUT LOSE DATA WITH FRP ON OEM ON
Code:
FRP LOCK: ON
RP SWAEV: B: -1 K:8 S:8
sw rev. check fail(bootloader) device: -1, binary: 8
after that the phone did not start anymore. It can only be booted in download mode. I can no longer flash firmware because the binary version does not fit. I know that I need the right binary version, but of course there is no version -1. Is there a way to get the phone working again without losing the data.
many thanks for your help

Related

Can mtty erase startup logo in trinity ROM?

I have my trinity briked and want to bring it to service centre. But ROM version I tried to flash before briking was in different region which may breach the warranty.
Now it boots and stops with a start up logo in different language. I am worried that service centre may refuse my repair request. Can I erase the image file from ROM? or any suggestion to avoid showing this screen? It is possible to use mtty and erase the image file? where is the image files' address? or how to erase the main ROM so that it will not show the image?
I tried most of the recovery method from here http://forum.xda-developers.com/showthread.php?t=286755 but still failed. My case is "Hybrid Bricks: combinations of both type 1 and type 2 bricks"
Model: D810 (trinity)
ROM Before Flash: 1.??
Radio Before Flash: 1.07??
Bootloader Before Flash: 1.07.??
Flash failed at: It seems completed at 100% but cannot boot after finish all
Flashing ROM: 1.23
Flashing Radio: 1.13.00
Bootloader After Failure: 1.07.0000
tried unlock and using SSPL to flash
CID Before Failure Super CID: tried unlock but don't know if success
CID Corrupt: Yes, info 2 shows HTCSF ?? HTCE
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: HTCSF ?? HTCE
Current Device Status: hang at welcome screen when power on

I9195 secure fail: Kerne

Hello People,
I have a samsung galaxy s4 mini GT-I9195, whenever i turn it on :
Image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I tryed few original roms , but none working.
I tryed this procedure from this theread : http://forum.xda-developers.com/showthread.php?t=2364980
and still not workin.
Here's what it shows on Odin Mode:
Product name: GT-I9195
Current Binary: Samsung Oficial
System Status: custom
Knox kernel Lock : 0*fffffffc
Knox warranty Void: 0*fffffffc
CSB-CONFIG-LSB: 0*30
Bootloader AP Swrev :2
Write Protection : Enable
but when i press volume up+home.. its not entering in recovery mode..
on the phone was instaled Cyanogen
Thanx!!
nik23 said:
Hello People,
I have a samsung galaxy s4 mini GT-I9195, whenever i turn it on :
Image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I tryed few original roms , but none working.
I tryed this procedure from this theread : http://forum.xda-developers.com/showthread.php?t=2364980
and still not workin.
Here's what it shows on Odin Mode:
Product name: GT-I9195
Current Binary: Samsung Oficial
System Status: custom
Knox kernel Lock : 0*fffffffc
Knox warranty Void: 0*fffffffc
CSB-CONFIG-LSB: 0*30
Bootloader AP Swrev :2
Write Protection : Enable
but when i press volume up+home.. its not entering in recovery mode..
on the phone was instaled Cyanogen
Thanx!!
Click to expand...
Click to collapse
The problem was resolved. i instaled few original roms, and it worked at last!

restart loop with V10.3.5.0.ODEMIXM after factory reset

I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?
hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img
So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM
hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13
I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html

a50 system REV CHECK FAIL DEVICE: 2, BINARY: 1

i can't flash my phone with officiel firmware
he say : system REV CHECK FAIL DEVICE: 2, BINARY: 1
my phone is A505F/DS
I think its because you are flashing an older firmware version, check the latest version for your device.

SM960F - re lock bootloader no OEM unlock

Hi there,
Since I can not get pass thru "Custom binary (Recovery) blocked due to remaining installemnt balance" error while flashing TWRP I would like to ask, hot wo relock my bootloader...
KG STATEL Normal
FRP Lock: off
OEM Lock off
Varanty void: 0
latest Android 10 update...
I was waiting like 10 days OEM Unclock option didn't come....
any help?

Categories

Resources