Hello!
I have problem with GT-I9195.
It was hardbricked. I unbricked it with SDcard and debrick.img. Now I have bootloop problem. I put phone to download mode and flash with stock ROM but it has bootloop again and there is No command in Recovery Mode. I tried to install Custom Recovery and still same No Command.
I tried this method:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
I get this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is Status in Download mode:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
And on FAIL! (Auth) Error
SW REV CHECK FAIL: Fused 2 > Binary 1
Can anyone help me?
Hi all, my S4 mini won't turn on, while i was messaging, the display shutting down and can't turn on it.
When i connected it to my pc, my pc found new driver: QHSUSB_DLOAD. I searched it on google and i discovered that my phone was bricked without doing anything. So i flashed a sdcard with debrick.img and my phone finally showed:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
BOOT RECOVERY
WRITE 139008 sectors
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
So i tried to flash it with Odin and after Odin said:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_shi p_MULTI_CERT.tar.md5 is valid.
<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> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULT I_CERT.tar.md5 is valid.
<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> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_M ULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So i searched on internet PIT files and i found "CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit", i tried to flash with it and Odin show same thing:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/004> There is no PIT partition.
While on the phone showed:
Code:
PIT FAIL : TOTAL SECTORS 0
ODIN flash read failure
I tried nand flash erase and show me other errors.
I think emmc died, if not, can anyone help me?
if emmc died, how can i install all partition ( bootloader ecc.) on sdcard for start the phone with it?
Have exact same fault, so do others.
Be nice to know if this is hardware or soft fault and possible remedy.
Alright so I'm trying to figure out what I'm doing wrong. I downloaded a copy of the pre-borked Note 7 firmware and I'm trying to flash it through ODIN. Every time I try, I get errors on both the phone and on the software.
I've been Googling all day and I can't find an explanation or a workaround. Can the experts here help with this?
ODIN log:
<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..
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note 7 display:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N930A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
OID:
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B2 (1,1,1,1,1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC:S2MM005 HW:3 Boot: 5 Main:ab
Then the actual error:
SW REV CHECK FAIL : [about]Fused 2 > Binary 1
[1]eMMC wrie fail: aboot
where did you find the firmware from ?
Having same issue
<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.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I got the file from: https://www.androidfilehost.com/?fid=24651430732236681
ALL_SPT_N930PVPU1APH3_N930PSPT1APH3_CL8706608_QB10617237_REV00_userdebug_low_noship_MULTI_CERT.tar.md5
for the Samsung Galaxy Note 7(SM-N930T), by freeza
Good thing it failed, thats for T-Mobile, if it completed it would have bricked your phone. I am searching also for the AT&T version
I believe that the SM-N930P version is for Sprint. My carrier is Sprint
From my understanding, the firmware available online, which ends in PH1 has the old bootloader. Once the battery warning update hit (Green Battery Icon for those who have the replacement model) the firmware came with a new bootloader and firmware version ending in PHE.
Because of this, we cannot flash PH1 due to the bootloader change.
The 60% battery update (PK1), I BELIEVE, still uses the same bootloader as PHE.
The only solution I think would be as follows:
1) Immediately disable any future software updates. (We dont want another bootloader change)
2) Someone needs to find and or upload the PHE version firmware (which lets you charge 100%, and only has the annoying original message sometimes)
3) Backup everything.
4) Using the methods described in other places, flash the PHE version, charge to 100% and deal with only a few warning mesages. (Phone startup and Attach to charger)
4) Immediately disable any future software updates by following the instructions for Package Disabler PRO or EZ Disabler. (Making sure you're on airplane mode, SIM card out, and wifi is turned off)
These are my thoughts. I cant seem to find PHE firmware anywhere. One place has it supposedly, it seems shady cause the download link goes to an arabic website and the forums require you to pay for each download. (hmmmm.....)
I could be 100% wrong, Im not an expert by any means, just another user trying to join the community to help find a solution. Can anyone confirm Im wrong and they have been able to somehow flash the PH1 baseband firmware? Any and all help would greatly help me and the many others who have been held down by the man
SM-N930A Update
I have the N930AUCS1APH1_N930AATT1APH1_ATT_FULL_SAMFIRM.NET ROM with 4 .md5 files in it (BL, AP, CP, and CSP) and I can not get the phone to flash using Odin 3.12? Any ideas on what to do? This is my log, but basically just says failed!
<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/004> 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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
next update will knock us all off the network. They are telling people that in the support calls to carriers and samsung.
Here is the PK1 firmware image
Hey guys, I am going to give you guys looking to get back to 100% charging a good new. I found the PK1 image for AT&T Note 7 N930A version. I just re-flashed my phone and it worked just fine. Got to charge my phone back to 100%. Got the green battery sign back. Here is the firmware image.
androidfilehost.com/?fid=312978532265363403 (I had to skip the www prefix because I am not allowed to post url at the moment. You guys know what to do with it. Just copy and paste.
Had to use Odin 3.12.3 version. I tried with Odin 3.10.7 version but got Odin protocol version error. So use Odin 3.12.3 version. Good luck.
---------- Post added at 09:58 AM ---------- Previous post was at 09:53 AM ----------
Sorry, my previous post should have said PKE firmware image.
---------- Post added at 10:03 AM ---------- Previous post was at 09:58 AM ----------
Got to check my spelling. PHE. Not PKE.
Thanks hachika88, that worked great. Does anyone know what I need to disable to prevent it from updating again. I have disabled com.samsung.knox.appsupdateagent and com.ws.dm, but is there anything else that should be disabled?
Use this link to go back to 100% on Rev 2 Firmware flash win Odin 3.12.4 or 3.12.3
androidfilehost.com/?fid=457084094631641284
Use Samsung Package Disabler Pro to disable Software Updates apk but you must do it fast after you reset your phone because once your phone checks for updates you can no longer disable it. Keep your SIM card out the phone and disconnect from wifi until absolutely necessary to get it disabled.
Good Luck
I used abd script to block th updates instead. A friend had her phe firmware pulled so that people could use it. If you look
http://www.n7r.co/
im looking for SM-N930A pl2 firmware. anyone?
Dear readers,
I tried to root my Note 10 plus (Dual SIM) via modifiying the firmware with the magisk manager, later on I have realized that I have downloaded and tried to install a not supported version of the firemware on my device.
Now I am struggling to flash a blank firmware, to revive my phone, but every time I am trying to flash a firmware that is made for my Note 10 plus version (SM-N975F [dual SIM] Germany), odin stucks while flashing and my phone reports a not valid version, that was tried to be installed.
Information:
-My phone shows me on the download mode (SM-N975F)
-I have downloaded and tried to flash the firmware for SM-N975F (Android 9)
-My Android version, before trying to root my device was Android 10 (June update)
-And I have removed the OEM lock,
download mode shows, while odin is stuck: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 1
Pit_flash_binary – Unsupported Version.
Odin information:
<ID:0/004> 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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8350 M
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> up_param.bin
<ID:0/004> cm.bin
<ID:0/004> keystorage.bin
<ID:0/004> uh.bin
<ID:0/004> vbmeta.img
<ID:0/004> boot.img
Has it to do something with the dual SIM variant, what can I do?
I’m so thankful for every answer
I think Android 10 version has higher BL version and you cannot downgrade to android 9 with lower BL version.
Try flashing the latest FW version for your phone.
Try flashing the latest version of the version of the firmware. You are trying to flash a firmware that cannot be flashed to your phone as it has an older (unsupported) bootloader.
How did this turn out for you ? It sounded correct to me but last i had this problem i was on a s7 edge dual sim exynos . I was able to downgrade at lease from 8 to 7 or some variation of nougat to a much earlier one by mixing the new modem and bootoader with the older firmware of nougat that was previosly working. I learned my lesson about upgrading the modem only when absolutly neccesary or if i am completely done playing with the older roms that are not compatible if you upgrade the modem and bootloader. If youll notice alot of times devs pf ressurection leave thier modem and bootloader on a older version than most while still bringing the newest android to all the zombie phones. It doesnt hurt to mix and match in this particular way just a little bit but be sure you understand what a modem bootloader flash and a firmware flash are and read around a bit to make sure theres no red flags and i have never went backwards more than say one version of android. But i DON'T EVER UPDATE MODEM UNLESS THERES NO OPTION TO DO IT SEPERATE AND IVE DECIDED ITS TIME TO MOVE ON to the newer set of roms that has presented itself. Good luck
I was curious if this worked for you because i just got my note 10 plus today.
Zaraio said:
Dear readers,
I tried to root my Note 10 plus (Dual SIM) via modifiying the firmware with the magisk manager, later on I have realized that I have downloaded and tried to install a not supported version of the firemware on my device.
Now I am struggling to flash a blank firmware, to revive my phone, but every time I am trying to flash a firmware that is made for my Note 10 plus version (SM-N975F [dual SIM] Germany), odin stucks while flashing and my phone reports a not valid version, that was tried to be installed.
Information:
-My phone shows me on the download mode (SM-N975F)
-I have downloaded and tried to flash the firmware for SM-N975F (Android 9)
-My Android version, before trying to root my device was Android 10 (June update)
-And I have removed the OEM lock,
download mode shows, while odin is stuck: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 1
Pit_flash_binary – Unsupported Version.
Odin information:
<ID:0/004> 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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8350 M
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> up_param.bin
<ID:0/004> cm.bin
<ID:0/004> keystorage.bin
<ID:0/004> uh.bin
<ID:0/004> vbmeta.img
<ID:0/004> boot.img
Has it to do something with the dual SIM variant, what can I do?
I’m so thankful for every answer
Click to expand...
Click to collapse
What happened now. did you fixed it...
I can't flash my Samsung A320 (A3 23017) with the original firmware usin Odin. I previously did the flash, but now Odin fails with the exact firmware I used before. I rooted the device with TWRP to rid some bloatware before and now my second attempt to flash fails. Any suggestions? Thanks
Here's the log:
<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..
<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/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4296 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PS: I tried both clean and partial flash.
version of binary must be same or upper
A320FLXXS9CTK2 - binary 9