I have spent the better part of two days searching for a solution with no avail so I thought I would post up what I see and determine if someone else has found a solution (I have found similar posts with either no answers or successful outcomes).
I was on OG5 and kept postponing the OTA update (phone was stock, not rooted as I received it with OE1 on it and eventually took the OG5 update since the bootloader was already locked). Last week I fell asleep and forgot to plug in my phone, and when I woke up the battery was dead. When I plugged it in I got the bootloop (without the RECOVERY BOOTING banner at the top). I have Odin 3.09, and have tried flashing different images including just the ROM, the ROM & recovery, etc, as well as the full factory image with the bootloader included. If I try to flash anything with a bootloader in it older than OG5 I get the error (as expected). However, all flashes end up in the blue "RECOVERY BOOTING...." loop. If I force it to recovery I get Maintenance Recovery and not the full factory recovery so that i could clear cache and Dalvik (as many have suggested). Basically, I'm trapped when trying to boot into regular recovery and cannot get there. Even tried repartitioning when flashing, all to no avail.
I saw a thread somewhere a couple days ago back on something with two phones (known good, another with issues) and a way to recover the dead one with the help of the other, but have not been able ot find it since.
Can someone hopefully provide me counsel on how to either fix what I am seeing or perhaps to the other thread as I have access to a working S5 with OE1 on it that I can use to make any custom image and/or something to help out? Below is my output from Odin - appears to work every time it flashes anything that doesn't contain a bootloader older than OG5:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU2BOG5_G900VVZW2BOG5_G900VVRU2BOG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This is conjecture, based on what I've read recently.
I believe what you're asking about is the Unbrick image, but my understanding is that is only needed when you are not able to get Odin to recognize that your device is even a phone. In any case, you would need to use one that matches the firmware and bootloader version of your phone.
Your Odin output reports that it IS connecting to the phone, that factory image md5 is valid, and that it is flashing successfully.
You cannot downgrade below BOE, but you can always go up. Maybe try using Odin to flash the BOK3 image linked in this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Update 2/1/2016
Well, I was fed up last night and left the phone in the boot loop as I headed off to bed (watched it boot loop about 10 times). Woke up Sunday and it had booted up and was running with all the data intact, even after I had tried to do a Factory Reset from the Maintenance Recovery menu. Got curious, powered it down and it it boot looped a couple times (without the RECOVERY BOOTING banner) and then came up ... after that it seemed to be OK as later in the day I powered it down a couple times and it came up fine.
Thanks for the reference @painiac - I was able to flash either OK3 or OG5 with success from Odin (the full factory images) but behavior was the same.
I got curious and tried to boot into recovery this morning and now it's boot-looping again - sigh... Was going to let it run the battery out trying to boot and after about 12-15 loops it finally came back! Hopefully the patience theme seen above may help others who are in the same scenario as this phone never seems to boot into standard recovery even after flashing full factory images.
At this point, I am planning on (hopefully) getting it booted up one last time, copying all my data off of it, and then walk into Verizon and try to get an exchange as this is not normal behavior and smells to me a bit like a hardware issue but my searches have determined that I am not the only one with this issue - HTH someone...
I agree, it's probably a hardware issue because a fresh factory image should have wiped out any problems that would be causing a bootloop. That combined with the fact that the problem persists across different version flashes.
Related
Hey there guys, I have the i337M Galaxy S4 (since then it has been changed to i9505), but I recently had enough of flashing roms and chose to go back to stock touchwiz firmware. I downloaded the right firmware for my device, and I tried flashing it with odin. When the flashing was done, the odin onscreen said "pass!", however, when my phone rebooted, it was still on the old rom, and nothing has changed. I tried a different computer, a different cable, everything, and I am very sure it's an issue with the phone.
I don't know why it does this, but now I have seen when after it reboots, it reboots into stock recovery, and there is a green bar that moves with the green android above it, but once the green bar reachs halfway, the phone reboots and it remains the same, as if there was no stock rom flashed onto it. I flashed a custom rom (CM11) through custom recovery, and then I used odin to flash stock rom. It seemed to work, but the bootscreen got stuck on the samsung logo(the samsung logo was just pulsing).
This is what it says on ODIN (When I flash the Official 4.3 Samsung update for I337M):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md 5 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Funny thing is, I restored a backup I had, and the data works fine with that (rooted touchwiz backup). However, as soon as I try to factory restore it through the phone, it completes, but data stops working. The same issue happens with ODIN as described above if I am on the restored ROM.
Please help me!
victoriousbig said:
Hey there guys, I have the i337M Galaxy S4 (since then it has been changed to i9505), but I recently had enough of flashing roms and chose to go back to stock touchwiz firmware. I downloaded the right firmware for my device, and I tried flashing it with odin. When the flashing was done, the odin onscreen said "pass!", however, when my phone rebooted, it was still on the old rom, and nothing has changed. I tried a different computer, a different cable, everything, and I am very sure it's an issue with the phone.
I don't know why it does this, but now I have seen when after it reboots, it reboots into stock recovery, and there is a green bar that moves with the green android above it, but once the green bar reachs halfway, the phone reboots and it remains the same, as if there was no stock rom flashed onto it. I flashed a custom rom (CM11) through custom recovery, and then I used odin to flash stock rom. It seemed to work, but the bootscreen got stuck on the samsung logo(the samsung logo was just pulsing).
This is what it says on ODIN:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md 5 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Funny thing is, I restored a backup I had, and the data works fine with that (rooted touchwiz backup). However, as soon as I try to factory restore it through the phone, it completes, but data stops working. The same issue happens with ODIN as described above if I am on the restored ROM.
Please help me!
Click to expand...
Click to collapse
are your apn settings intact?
aandrichaci said:
are your apn settings intact?
Click to expand...
Click to collapse
Yes they are
aandrichaci said:
are your apn settings intact?
Click to expand...
Click to collapse
Ok so it turned out to be that the APN settings were messed up lol, but I still don't understand why they get wiped after each factory reset, AND why when I try flashing with ODIN, nothing changes...
victoriousbig said:
Ok so it turned out to be that the APN settings were messed up lol, but I still don't understand why they get wiped after each factory reset, AND why when I try flashing with ODIN, nothing changes...
Click to expand...
Click to collapse
So did that fix the issue?
MrKhozam said:
So did that fix the issue?
Click to expand...
Click to collapse
It fixes the issue, but I would like to know why the APN settings get wiped after a factory restore? Just curious lol, I know they can be put in manually, but before this they would automatically be there. It's a minor frustration
victoriousbig said:
It fixes the issue, but I would like to know why the APN settings get wiped after a factory restore? Just curious lol, I know they can be put in manually, but before this they would automatically be there. It's a minor frustration
Click to expand...
Click to collapse
It seems to be a carrier-specific issue. Might have something to do with frequency. I know that when I sold my old S3, which was an original factory unlocked phone from T-Mobile, detected my APN settings fine on the Bell network here in Canada. However, when I put in a Wind SIM (same frequency as T-Mobile), I needed to re-configure the APN settings. Which is a bit ironic, if anything.
I have looked and tried and still can't fix my bootloop.
I was on Factory 4.3 rooted with towel and had OTA blocked. I need to update to 4.4 for a bluetooth device I have so set superSU to save root and removed the OTA block, although the updates would fail over OTA. I then downloaded the 4.4 NC4 image and used odin to image the phone. No I didn't do any of the recommend pre-imaging because I failed to look up the procedure as I had done other phones in the past.
I am now in a bootloop where it boots into the setup wizard, locks up after 2-3secs and reboot. Over and over. The phone still shows custom after a factory image flash. i've tried every recover from softbrick option I could find and nothing. It boots into setup, freezes, and reboots. Even went as far as erase nand because nothing else worked and the same thing happens.
These images all give me an auth failed: MJE, MI9, MJ7, MJE, NC2. The NC4 image will let me flash, but still results in a bootloop. Again, the lock still shows custom.
Any chance in saving this thing?
I went thru this very same thing just the other day. Go to my post. I posted the link for all the downloads on it. You'll have to Odin flash a complete stock 4.4 Ota. Then you can root with towel root and go from there. Here is the link.
http://forum.xda-developers.com/showthread.php?t=2914890
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Here is the link for all carriers stock files.
http://galaxynote3root.com/galaxy-note-3-stock-firmware/
i think I tried every image, although i'm more then willing to try again. I'll use the link you provided and see what happens.
Thanks for the reply.
Same thing using the image link provided, still in a bootloop, still showing custom/unlocked.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
pretty desperate at this point so i decided to try a flash the nc2kernel ontop of the nc4 as described in some rom hack, i figured what do i have to lose. it did flash, although never made it passed the vzw screen during the boot. i flashed the factory nc4 image to get it back and was surprised to see a android running an upgrade, i was excited for about 3mins until it went right back to the boot loop again with the unlock/custom screen. damn.
still looking for help if anyone has any ideas i'll try them tomorrow.
Calzoniee said:
pretty desperate at this point so i decided to try a flash the nc2kernel ontop of the nc4 as described in some rom hack, i figured what do i have to lose. it did flash, although never made it passed the vzw screen during the boot. i flashed the factory nc4 image to get it back and was surprised to see a android running an upgrade, i was excited for about 3mins until it went right back to the boot loop again with the unlock/custom screen. damn.
still looking for help if anyone has any ideas i'll try them tomorrow.
Click to expand...
Click to collapse
Make sure you have the right PIT file or use KIES.
Sent from my Note 3 via Tapatalk
donc113 said:
Make sure you have the right PIT file or use KIES.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Kies comes back with "phone not supported", the PIT file I'm using is HLTE_USA_VZW_32G.pit which I believe is correct.
I've tried the verizon recovery assistant as well; it goes through the whole process tell me it's repaired and then just go right back into the bootloop, the lock still showing unlocked/custom.
I tired another computer and then another cable as suggested in another thread, still stuck in bootloop.
Calzoniee said:
I tired another computer and then another cable as suggested in another thread, still stuck in bootloop.
Click to expand...
Click to collapse
Have you pulled battery booted into stock recovery and done a factory reset yet?
RomsWell said:
Have you pulled battery booted into stock recovery and done a factory reset yet?
Click to expand...
Click to collapse
Thanks for the reply, yes I have. I have done all the steps to repair a softroot and to restore to factory. The factory restore steps were not tried until the phone was softbricked and stuck in the bootloop.
I called Samsung, they recommend I take the phone to the Best Buy Samsung repair center. I guess I'll try that tomorrow if nothing else works today.
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
Hi,
Recently my phone autoupdated to marshmalow, and since then it keeps freezing and crashing. I read somewhere that the final fix to this is to reflash the firmware, so I tried and since then odin gives me an error message and the phone wont start.
I am quite new to all this, but I followed instructions from many different youtube tutorials and other online tutorials. ODIN keeps giving me a write error.
I am using different versions of odin, different usb ports and even different cables with the same end result. ODIN flash ends with error.
My note 4 has reactivation lock off, and never been rooted before. It is a UK N910F model and usually on Three mobile.
I really hope someone can help as I have struggled with this for past 2-3 days with no luck.
Here is the details from odin.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1DPE1_N910FEVR1DPE1_N910FXXU1DPB1_HOME.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers
Odin kept failing at the hidden.img.tar.ext4 file so i googled, and found that extracting the hidden file and then flashing that file separately in odin may work. I tried that and worked!
Phew!
night-mayor said:
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
Thanks form your input and help
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers
Click to expand...
Click to collapse
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.