Hello all
I've got a S4 mini here which I'm hoping I can use to upgrade from my old S2.. Problem is.. it doesn't turn on, charge, or anything. If i plug it into a Windows 10 machine I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
I'm just curious what i can do to get this thing running as its a really nice little phone and seems a nice upgrade from an S2.
I'm fairly technical and I have used tools such as Odin and such to root older Android phones but I thought I would seek advice here before trying anything as It has been awhile!
I look forward to any replys
Regards,
Jason
Ok some progress...
I've been running it inside an XP virtual machine as Windows 10 hates Odin and other tools. Anyway, Virtualbox does notice the device and names it "Qualcomm CDMA Technologies MSM QHSUSB_DLOAD" Is this some form of basic boot loader or recovery or?? I'm unsure myself and I hope maybe someone can tell me what Virtualbox is actually seeing and hopefully it's showing life to a point where i can reflash the device or at least get it running to a certain degree.
Also I've noticed if i say press and hold the power button in Windows 10 the USB disconnect sound with occur swiftly followed by a reconnect sound. Same applies for VOL Down + PWR + Home botton. I've tried running Odin which see's nothing on the COM port. My S2 shows up right away but the S4 mini shows nothing.
I think at this point it's worth mentioning this phone has come from an ex office environment so a failed custom ROM flash or anything is unlikely but of course whatever the case may be its certainly not well... I guess it's not completely dead as it's connecting as a USB device. Can anyone please advise me on how to get this re flashed/fixed or even just tell me what's actually going on here? As this is a bit bound me.
:good:
Ok so I've made some progress...
I added some files to a micro SD card (from the debrick.img) I used win32imager to write to the card and put it in and tried powering it up which has now made the phone vibrate twice and then turn on to a basic "BOOT RECOVERY MODE" screen in plain text.
It also says the following:
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
Now if i load up Odin i can see it on COM5. At this stage I've downloaded a stock firmware from sammobile and I'm ready to load it. I tried it and it requested a PIT file so i found the correct one for my phone and it still wouldn't work. So i looked around on here for answers and found a guide someone had made. Downloaded the "kit" he had which has the following files:
BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
I've added all these where they should go, tried to run it and i get a red FAIL sign above ID:COM along with this error log:
<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_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..
<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..
<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)
Can anyone please help me from here as I'm really not sure what is wrong? I've got it from a black screen which would do absolutely zero to doing something at least but I could really use a hand now... please? anyone?
By the way I'm using Odin3 v3.07 which i know isn't the latest but it is said to be the one to use for my S4 mini, could it be that a need the latest version?!
Help please. :good:
dreamscape440 said:
Ok so I've made some progress...
I added some files to a micro SD card (from the debrick.img) I used win32imager to write to the card and put it in and tried powering it up which has now made the phone vibrate twice and then turn on to a basic "BOOT RECOVERY MODE" screen in plain text.
It also says the following:
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
Now if i load up Odin i can see it on COM5. At this stage I've downloaded a stock firmware from sammobile and I'm ready to load it. I tried it and it requested a PIT file so i found the correct one for my phone and it still wouldn't work. So i looked around on here for answers and found a guide someone had made. Downloaded the "kit" he had which has the following files:
BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
I've added all these where they should go, tried to run it and i get a red FAIL sign above ID:COM along with this error log:
<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_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..
<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..
<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)
Can anyone please help me from here as I'm really not sure what is wrong? I've got it from a black screen which would do absolutely zero to doing something at least but I could really use a hand now... please? anyone?
By the way I'm using Odin3 v3.07 which i know isn't the latest but it is said to be the one to use for my S4 mini, could it be that a need the latest version?!
Help please. :good:
Click to expand...
Click to collapse
Have you found the solution dreamscape440 ?
Related
So... a guy brings me a Galaxy S3 SHG-T999 and says it won't boot up..gets stuck on the Galaxy Boot Logo Screen.
The phone will not go into recovery mode,
PC will not charge the phone while plugged in.
PC does not recognize the phone when at boot up screen.
When plugged in not booted, a gray battery Icon appears and disappears.
The phone will go into download mode
When in download mode the Text shows that everything is still stock and no binary has been downloaded.
All correct drivers installed
I have tried using Kies and Odin to flash using the Stock Rom
Kies see the device but fails, Odin sees the device and reads the file but fails to write
in Odin I have Reboot checked F Reset checked
Is there anything I can do to get the phone to boot from an SD card so that I can reset the phone and reflash to stock ROM?
If Odin Failed while the phone was in download mode, please post the Odin log.
Odin Log
Perseus71 said:
If Odin Failed while the phone was in download mode, please post the Odin log.
Click to expand...
Click to collapse
This is my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.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> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Second Odin Log Fail
I tried a different Stock rom and did not get a fail but it also did nothing at all
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Something's wonky here. Did you check the .PIT checkbox ?
Hi Guys ,
When I connect my phone just vibrate so my last solution is to root it .so below my issues :
-Using Odin3 v1.85 ,I got that :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-clockwork-6.0.5.1-serranoltexx.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using other Odin versions ,I got :
Stuck on initialization .
Also be informed I tried with different usb port ,different cables.
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
linol said:
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
Click to expand...
Click to collapse
When I plug my phone just vibrate and nothing happen after. when I want to power it also vibrate and nothing on screen .but I can enter on odin mode >
What's could be ? I need your support .
Thanks in advance
How about you plug your USB cable directly at the backside of CPU incase of desktop pc. and also Turn off AntiVirus and kill kies in task manager if its running.
But before doing any of that try connecting your phone to kies. and check if it can be connected. if not install the drivers.
thanks for your but didn't help ,below what I got :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
You can try flash emergency firmware from Samsung kies. Never tested but maybe can bring back to life your phone.
kies can't detect my mobile
Have you installed the Samsung drivers?
Yes,installed
bingozingo said:
Yes,installed
Click to expand...
Click to collapse
Looks like your eMMC is dead.
How can I confirm that ?
bingozingo said:
How can I confirm that ?
Click to expand...
Click to collapse
IMO, the only way is to look for a full restore image of your device.
Keywords to use in your search are: i9195xxucnh5, rev01, low_user_ship, tar.md5
The full restore image is the one used by Kies to initialise the devise to its factory state. It can be a single file or, in most cases, 4 files (BOOTLOADER, AP, CP and CSC).
It contain the PIT file, necessary to re-partition the entire eMMc, and every image for each new created partition.
If you find that image, or a member can provide it, there are good chances that your phone come back to life.
If Odin fails to flash the image and says "can't re-repartition", then your are good to look for another chipset.
Sorry, i can't help you with links.
pls ,have you the steps to do that ?,also did you have the full name of the all files that can help for search .
pls help
<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_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..
<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..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
I wanna be crazy .
Can you note exactly what is written on the Download Mode screen ?
Downloading
Do not turn off target!!
bingozingo said:
Downloading
Do not turn off target!!
Click to expand...
Click to collapse
No, i mean what is written in the upper left corner.
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
bingozingo said:
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
Click to expand...
Click to collapse
Nothing strange here...
Your bootloader can see the content of system partition.
Can you access stock recovery (Power Button+Volume Up) ?
If you can, do a factory reset then reboot.
When I want to enter on recovery mode( power+volume up ) ,it's just vibrate .nothing on screen
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?
Greetings, I'm attempting to stock firmware my samsung galaxy s7 sm_g930a.
The problem arrose when I accidentally loaded the root file (theunlockr, I can't give the url due to the youth of this account) into the BL section in Odin. I tried loading a stock firmware from samsung/at-t and I get the the following message.
<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..
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is still able to load to download and boot options but the boot screen itself just loops. Comes on, stays for 2-3 seconds then blacks then comes back for 2-3 then blacks again. I have tried clearing the data, clearing the cache, kies says it isn't compatible, tried swapping ports, the only other option i need to try after posting this is trying a alternate usb cable. I have tried both odin3 v3.11 and Odin3 V3.12.
The download screen on the phone at the top left corner reads Odin Mode (high speed)
product name: SM-G930A
Current binary: Samsung Official
System Status: Official
FRP lock: on
Warranty Void: 0x0
Qualcomm secureboot: enable
AP swrev: B4(2, 1, 1, 1, 1)K1 S3
Secure Download: Enable
wrong thread
just realized this is the wrong thread apologies