Hello,
i have a Samsung Galaxy A5 (2015) SM-A500X Live Demo Unit.
It came with it's stock Kitkat ROM and does not find any updates, but i know that there is a 6.0 update for this phone. So i tried to modify the DBT-Germany Stock 6.0 that i downloaded with those guides:
https://www.reddit.com/r/oculus/comments/40rsdv/if_you_get_a_samsung_s6_live_demo_unit_store/
https://forum.xda-developers.com/showthread.php?t=2349948
In the first guide i could only remove the "modem.bin" but both the other files are not in the stock Rom .tar file. i tried to Flash it anyway, but Odin gave me an error that it couldn't Flash one part, the phone showed some error in download mode "couldnt Flash secured" or something like that. i think the Partition is missing for a specific file?
So i used the second guide and removed EVERYTHING besides the files which are Name in the guide (like stated there), the Flash in Odin went fine, but the phone only shortly Shows the Splashscreen and then Comes back to download mode which tells "Could not do normal boot"
Then i began to Panic, because recovery was dead too...
So i could save the phone, i flashed the twrp recovery, i could atleast go into a working recovery and then i was able to restore the backup of the stock Rom (glad i did this one)
So the phone is working again, at least. But could somebody tell me what i have to do to Flash the 6.0 stock Rom?
Or: Do i really Need to do this since i only want to use lineageos (Nougat), but in the guide it is telling me, that i Need to have at least the marshmallow bootloader and modem. i know that a LDU has no modem but what about the bootloader?
I am very sorry for my bad english! :angel:
I would really appreciate some help...
Thanks a lot!
I've looked around, and there's only a Germany DBT rom for the SM-A500FU:
http://updato.com/firmware-archive-select-model?record=61451820219F11E7963AFA163EE8F90B
You could try that one out, rather than trying to modify some other rom.
Thanks for the answer, this was also the ROM i modified, but if i flash it unmodified with Odin, i always get this log:
<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..
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone:
"Secure Check Fail: aboot"
It seems that the bootloader is somewhat locked?
I can still flash a recovery (TWRP) and this is working, the kitkat stock Rom is also working (from backup in TWRP) but i cant get anything else to work, especially lineageOS doesnt boot :/
EDIT:
Slowly i begin to understand: https://techusall.com/solved-secure-check-fail-aboot-error-flashing-firmware/
If i am right, my baseband/bootloader ist not compatible with the normal A500FU so i can't update it?! So there's no solution to this Problem?!
Ok, i think this is the end... I even tried to flash the 4.4 Stock ROM for A500FU but it still get the damn aboot.mbn auth error. I think the bootloader on demo phones is somewhat locked and can't be flashed at all, so i am stuck with Kitkat Bootloader preinstalled. So i only can flash 4.4 ROMs i think, this is sad :/
Especially because there is official 6.0 for this phone.
I still have the same Problem. Does some dev have some advanced Knowledge of those Errors?
It would be okay if it's simply not possible, so i can sell the unit again, but i would like to be sure to not waste an opportunity to use this nice device.
Related
Good Evening.
I had issues with my Rooted 4.2.2 (knox enabled firmware) and i wanted to unroot and flash my phone back to the Stock non Rooted Firmware.
Im well aware I cant Downgrade to a stock firmware With no Knox..So What i am trying to do is to flash the Official non rooted
I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_HOME (EUR) firmware That my phone had before it got Soft-brick.
I get to errors from Odin When i am doing the recovery Process
1) I Got this:
There is not PIT partition Table
so Ive Used a .pit file From this http://forum.xda-developers.com/showthread.php?t=2265477 Thread
and Ive retried the Process with CSB_signed_Fusion3_EUR_0325_V2.pit file But i got the Following Error:
2)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_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> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
So I am Pretty Much At a dead end with not knowing what else to do I would appreciate if anyone can Help me With this Issue
Thank you in advance.
P.S
I am using Odin 3.07 or 3.09 and i get the same issues
my Knox_warrinty_void is at 0x1
My Phone Model is GT-9505 region unlocked
also I have tried every Usb Port on My computer and used 2 different Cables 1 from My S4 and 1 from my S1
Unfortunately i don't have access to a different computer atm, but the above Process is done to a fresh install of Windows 7 SP1 PRO (x64) Partition on my Current PC.
If i check NAND erase all in odin and then Try to Flash The.pit along with Firmware will this help or it will make it worse?
Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.
Dertheante said:
Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.
Click to expand...
Click to collapse
Can you explain in more detail as to how you use those files to resurrect your i9505? The thread's description does not explain how to use the files: (galaxy_S4_9505.exe, bootloader + pit.bl)
The bootloader file is not recognized by odin and there is no indicator as to what the galaxy_S4_9505.exe file actually does.
Thanks much
Ok, so I rooted my phone using a method where i flashed an older kernel then used towelroot to root, and then flashed back to NJ4. All was going well, and i installed the safestrap recovery. Then, today i was tryin to install the CM12 for the S4, and i messed up where i put the files for this, so when i was in safestrap, it told me it failed. I hit reboot, and that is when my phone essentially 'soft bricked'. I tries to boot up, fails and goes into download mode. I tried pulling out the battery, tried to go into recovery, but i cant do it. I tried to flash 4.2.2. stock s4 firmware thru odin, but it kept saying "Can't open the serial(COM) port." and fails. I can't do anything right now, please help im panicking Dx
UPDATE: I tried again to flash stock and now when i try to boot it tells me "firmware upgrade encountered an issue.." now when i try to flash something it won't let me because odin fails and says
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.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> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
McAwesome said:
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
Click to expand...
Click to collapse
I updated my last post btw. Dumb question but...what is adb?
EDIT:
Got it. I found a link to a rootable 4.4.2 md5 file and flashed it and it worked!
Not compatible
Well CM12 CM11 no CM period is compatible with out S4 because of the locked bootloader and youre trying to use the wrong firmware in odin once you upgrade to 4.4.4 or 4.4.2 you can no longer downgrade and go down to 4.2.2 so stop trying that you need to either download NB1 or NI1 odin files and restore it that way thats if you havent completely messed up youre phone Good Luck!
All,
As I noted in another thread, when I worked on my wife's new Galaxy S5, I let it upgrade to Android 5.0, then rooted it, then made some mistakes while restoring apps via Titanium Backup. In order to undo those mistakes, I want to roll back to the beginning and start over. To that end, I have been trying to reinstall stock firmware on the phone but I keep running into the same problem:
Code:
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1ANCB_G900PSPT1ANCB_G900PVPU1ANCB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL! (Auth)
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Based on reading here and elsewhere, I have tried the following:
Factory reset the phone
Verified that USB debugging is enabled and that allow remote lock is disabled
Ran Odin as Administrator
Use different versions of Odin (have tried 1.3, 1.85, 3.07, and 3.09)
Tried different firmware versions
Reinstalled Samsung drivers
Tried different computers and different USB cables
Regardless of what I have tried, I keep getting the same error.
The phone still works - I can boot it, so it is not bricked. I was also able to successfully re-root the phone (using the CF Auto Root approach). Based on my reading, it seems that replacing the PIT file is a next step to try, but it also seems that this is a fast way to killing a phone, so I am hesitant to try.
The phone in question is a Sprint Samsung Galaxy S5, SM-G900P. The kernel is currently Android 5.0, build version LRX21T.G900PVPU2B0D3. I would like to replace with with the stock 4.4.4 kernel (found here: http://stockroms.net/file/GalaxyS5/SM-G900P/G900PVPU1ANCB_G900PSPT1ANCB_SPR.zip). If replacing the PIT file is the next thing to try, can you please point me to the specific one to use? If not, can you suggest something else to try?
Thank you.
Same here
I'm having exactly the same issue. Trying to downgrade from BOD3 to kit kat 4.4.2 NE5 in order to unlock my S5 G900P.
Hope someone has a workaround for this.
Sorry dumb question, what did you use to root a 5.0 firmware? I thought towelroot only works on 4.4.2?
Starting with BOD3 u cant downgrade anymore
Hope this will work 4 u.....it worked on my G900P :
1. Install CWM with odin...Philz: http://downloadandroidrom.com/file/G...2-klte.tar.md5
2. Download Galaxy S5 Rooted Stock ROMs and kernel, flashable zips, and copy to your SD card
3. Reboot in recovery ...wipe data/cache/dalvik....install the zips(kernel and rom)
4.Reboot to system and enjoy ur downgrade
thanks to bto001 here: http://forum.xda-developers.com/sprint-galaxy-s5/general/solution-to-sim-unlock-od3-downgrade-t3128120
What finally worked was to install the same version of the stock firmware.
Code:
Hi, I have a serious problem with my Note 4 (SM-N910F).
Since the phone where lagging a lot from a few days, yesterday I choose to do a restore to factory condition, but after that it begun to bootloot.
So I flashed the latest 5.11 firmware available (this from Sammobile for Italy.
As soon as I did, I thought that all my problems were gone, but no. After the firmware, I wanted to get root, so after a quick search on Internet, I choose to get this kernel.
But after the flash of the kernel, I begun to have A LOT of problem. So I decided to flash again only the firmware.
Today I tried again to flash the TWRP recovery to flash the kernel .zip to get the root, but as soon as I did it, the phone didn't go beyong the Samsung logo.
I tried to take these steps: firmware-recovery-root, but after a while, ODIN gave me the error of "PIT binary missing" (or similar).
So, I downloaded a .PIT file for the 5.1.1 (I don't remember where) and I reflashed the firmware with the .PIT file and I didn't got any errors.
After I checked that there were no problems, I tried again to install that kernel.
And I tried again, and again, with different 5.1.1 firmwares.
A thing that I think it's important, it's that I noticed that sometimes while powering on the phone, it went automatically to Download Mode, with a message saying that it couldn't boot in "normal mode" and "MMC read error".
Also I noticed that everytime a powered off, or I rebooted the phone, I had to take off the battery in order to turn on again the phone. It seems like the phone never really turns off.
Now, the phone doesn't boot, the recovery isn't working, and the only thing I have is the download mode.
I tried on 2 pcs, with 2 usb cables, with 2 ODIN versions (3.09 and 3.10.6) to flash a couple of 5.1.1 firmware with and without the .PIT file.
Every time I start the flash on ODIN, while flashing the SYSTEM.img, the flashing stops and on the phone I get this message "ODIN: flash write failure".
I don't really know what to do, unless took it to a warranty center. I think that this problem could be caused by a faulty EMMC, or a brick caused by me.
PS: this is the log from ODIN
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COH4_N910FITV1COH1_N910FXXU1COH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>[COLOR="Red"] FAIL! (Write)[/COLOR]
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE:
I successfully installed the TWRP recovery (twrp-2.8.6.0-trltexx.img.tar) with ODIN, so I wiped all the partitions but one: SYSTEM. The error is "E:Unable to mount '/system'.
At this point I think I messed up with the partitions.
UPDATE2:
I installed the CWM PhilZ, and with that I formatted the /system partition.
So I tried to re-flash the firmware with no success, but I tried again with the .PIT file and it succeeded!
Do you think I should retry to root it?
UPDATE 3:
So, after the first setup (google account, samsung account, time, etc.) I turned the phone off to insert my SIM card.
But as soon as the smartphone turned off, it powered on itself again in Download mode, showing me this error:
Could not do normal boot.
ddi : mmc_read failed
I think that maybe, there's a problem with the eMMC
Hi there
Do you want to flash the firmware?
i have s6 edge and when i choose file(in odin) for (PA) it falis so i tried for (CSC) and it worked.
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
landerhazard said:
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
Click to expand...
Click to collapse
i had a simialar problem with odin but my problem was that the adb wasnt successful i had to do it twice before it said successful then when i ran odin it worked not sure if this will help but i was stuck for days with the odin fail it was frustrating but good luck hope you find a solution
So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
alexsheff said:
So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1005)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
cm.bin
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.
ashyx said:
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.
Click to expand...
Click to collapse
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch
alexsheff said:
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch
Click to expand...
Click to collapse
If part of the firmware doesn't install then it is not the correct firmware for your particular device, simple.
The bootloader does a sanity check via Odin on any firmware attempted to be installed.
If it doesn't meet the requirements it fails to install.
It's pointless arguing the case because it's a fact and I've been down this road with others who have eventually got the correct firmware of which you've almost proved my point by stating that downloading through Smartswitch installs the correct firmware.
Several factors come into play, model, carrier, region and revision.
Any of these mismatch and installation could potentially fail. Simply being the right model no. isn't enough.
You could probably help yourself if you post more details:
Exact firmware your device is currently running, the firmware you are attempting to install and screenshots or post a log of the output from odin and the info provided on the device display itself after failure.
I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.
alexsheff said:
I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.
Click to expand...
Click to collapse
Post the details as requested above and we'll get it sorted.