EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?
bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).
Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.
Possible not a genuine Note 3?
This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..
Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.
Flashed Rom zip. Note 3 back to health.
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.
If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.
Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?
I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?
I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...
Related
So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression
samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe
@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware
samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!
S4 I9505
Problem:
Start up screen top left corner shows:
kernel is not seandroid enforcing
Hangs up or Reboots.
I updated my S4 to Version: I9505XXUEMKE
Then I used Odin to Flash a Root with Stock recovery & SU, something went WRONG!
Knox is now 0x1, which should not have happened, but what can I say.
BaM, I got the Reboots & Hang ups.
But, I still could get into Recovery & Download Mode!
SO HERE IS THE FIX:
1. Download, Odin 3 - THx 2 - daerragh
--- I used Ver.: Odin 3.07
2. Download, http://www.sammobile.com/firmwares/2/
--- Register
--- And download your Firmware, if you know which you had before it crashed choose that one otherwise Upgrade to latest.
--- For me it was the latest version - I9505XXUEMKE ---- THx 2 -- Repulsa for the tip.
3. Start Odin 3.07 --- [Should it "FAIL" Read note at the Bottom #6].
--- Make sure - Auto Reboot & F. Reset Time are checked - Nothing else.
--- Click on PDA choose your Firmware file in my case "I9505XXUEMKE"
--- this can take a minute or two, WAIT, the PDA will check mark itself.
4. To start Turn off your phone completely ! Now hold following buttons to get into Download Mode,
--- Volume Down
--- Home
--- and last Power
--- S4 will enter into DL Mode
Seeing you have already tried to root you phone, you should have you Samsung USB drivers.
5. Press Start
--- This will take time, after it Reboot itself,
--- remove the USB Cabel & wait
--- at least 5 minutes don't remember how long, I came back after 5 Minutes and it was done,
---------- so then if everything went well for you, have fun :good: .
6. FAIL
--- Should it Fail while uploading to your phone,
--- A. Remove Battery
--- B. Remove USB cabel
--- C. Restart.
--- Should it Fail again (which happend to me), then Do A. B. C. again.
--- and this time Touch your screen about every minute.
I Know that sounds weird, but it worked for me maybe something to do with "Stand by? no clue".
If this has help you in anyway please hit that :good: Thanks Bottun
I AM NOT RESPONSIBLE for anything happening to your phone as a result of you flashing this Rom.
[Help Please] TMO-S4- Kernel is not seandroid enforcing
Hello,
Let me start off by saying, I'm a complete newbie when it comes to rooting (Infact - It took me a few days to even convince myself to do this) and I did look around for several guilds on how to remove this error (Downloaded Odin - Got Stock TAR.MD5) But I still get this error on my phone when I start the phone, it wouldn't be much of a probelm, except it hangs for a while and then restarts.) It also gets stuck for a long time at the T-Mobile load screen. The Wifi Wont turn on their... Please Help.
Galaxy S4: SGH-M919
T-Mobile...
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
You are right :highfive:
Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks
illias9 said:
Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks
Click to expand...
Click to collapse
I tried to install the Gummy Rom but I got the same problem. It gets stuck in the rebooting or something. It wont pass the samsung start screen. What should I do?
Tried all of the above and no go.
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.
Lennyz1988 said:
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.
Click to expand...
Click to collapse
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?
Natza09 said:
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?
Click to expand...
Click to collapse
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.
Lennyz1988 said:
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.
Click to expand...
Click to collapse
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
---------- Post added at 11:40 PM ---------- Previous post was at 11:05 PM ----------
Natza09 said:
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
Click to expand...
Click to collapse
Ok so i put TWTP back on and i was able to install Goldeneye Rom 4.4.2, Which is working great. However when i reboot im still getting the Kernel is not seandroid enforcing message in red. As i can not restore to stock Rom as Australia XSA 4.4 isn't out yet is there any other way to get rid of this message. Thanks again.
did anyone tried this ??
Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade
franny23dmt said:
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade
Click to expand...
Click to collapse
Yeah its all sorted now as version 4.4.2 has been officially released as stock on my Samsung S4, So back to "factory" now and no more message. Off to ebay it goes and Hello HTC One M8 .
Hi,
I'll Install WizCyan custom Rom on My GT-I9505 by TWRP mode. Its not a Error its a Premission That are allow when we use other roms.
●Press Volume Up and Volume Down Key at same
time and Hold it. This methode is use to Force Start your Rom
Hi
I have AT&T Note 3 , sim unlock from carrier, successful kingo root 0x0 Knox (startup splash screen says Custom Unlock)
So, I was hopped up on percocets because of my recent surgery and i decided i was in conscious enough mind to tackle getting AWS unlock. I wasn't.
I was reading about chainfire regionaway app, so i went to the app store and downloaded the first chainfire app that popped up - 3D. so now i am stuck in the note 3 splash screen. yes i know i should have read it more carefully, etc. but i just wasn't all there at the time. Please help me save this $500 brick!
I've been reading these methods:
http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/
i can get the phone recognized in ODIN, but the secure check fail: cache occurs
http://forum.xda-developers.com/showthread.php?t=2567133
i can't download any of these files...
http://forum.xda-developers.com/showthread.php?t=2507403
tried this but didn't work.
i'm really not making any headway... any help would be much appreciated.
side note:
can i send this in for warranty? Since AT&T just release the kitkat update can i claim that i tried to update and it failed?
current binary: samsung official
system status: custom (not official)
Knox lock 0x0
Knox warranty void 0x0
EDIT: After doing the ODIN fail - it is stuck in ODIN mode and says "firmware upgrade encountered an issue. Please select recory mode in Kies & try again."
Can not enter download mode. But still connects in ODIN
thanks!
Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?
kenny1991 said:
Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?
Click to expand...
Click to collapse
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood
firstsx said:
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood
Click to expand...
Click to collapse
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
I don't know. But flashing kitkat may tripe Knox i don't know atnt models. If you don't want to flash then return it.
kenny1991 said:
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
Click to expand...
Click to collapse
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
firstsx said:
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware. http://www.sammobile.com/firmwares/3/?download=25106
You know how to flash?
kenny1991 said:
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware.
You know how to flash?
Click to expand...
Click to collapse
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
but when i run it, it fails and says this on my phone
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
firstsx said:
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
Click to expand...
Click to collapse
hm. Still no recovery mode?
Past your Odin log so someone can see why it fails.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_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> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Need pit file?
kenny1991 said:
Need pit file?
Click to expand...
Click to collapse
sammobile doesn't say anything about pit file?
i only used the AP file from there
i have HLTE__USA_ATT_32G_pit file even when i use that PIT file with the AP file it still gives me the same fail error...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
firstsx said:
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
toastido said:
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
firstsx said:
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Markudsc said:
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Click to expand...
Click to collapse
can i use this method
http://forum.xda-developers.com/showthread.php?t=2559715
it seems pretty much the same, except yours includes updating to kitkat.
if i do kitkat, can i still keep root?
will this trip knox?
Ok i did this method
http://forum.xda-developers.com/showthread.php?t=2559715
i re-downloaded all the files because the files i had just wouldn't work in ODIN or anything. so based your advice i just downloaded new files.
ODIN flash was successful
then i did the rest of the steps successfully! and i am back!
Okay so I am using a AT&T Galaxy S5, SM-G900A. I was being an idiot and I wiped everything on my phone. So now when I downloaded Odin, downloaded the SM-G900A stock firmware, tried to flash it with odin and I kept getting this error no matter what I do, someone please help me....
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When my phone is in download mode, after I get the error in odin heres what my phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Nevermind, got it fixed. All thanks to Davew41's post: http://forum.xda-developers.com/showthread.php?t=2785363
Hi, I have j510fn and I was a rom tester,
I have a problem since I flashed
J510FNXXU2APK6_J510FNODD2APK2_J510FNXXU2APK2_HOME.tar.md5
to test light stock rom v3 from Kingraheel
what happens is that NOW I can't flash any other firmware by odin... when I click START it says FAIL and in my device there is this text in red
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I just want to flash my OFFICIAL firmware
J510FNXXU1APG1_J510FNPHE1APG1_J510FNXWU1APFC_HOME.tar.md5
but I can't... only APK6 firmware works on odin... any other firmware works.... can you help me?
I don't have any NANDROID backup of previous versions... only of my actual firmware... APK6
My computer does not detect my device... I have the drivers installed, and I tried on all the USB ports... it charges but not open files.... PLEASE HELP
TheWalkingSans said:
Hi, I have j510fn and I was a rom tester,
I have a problem since I flashed
J510FNXXU2APK6_J510FNODD2APK2_J510FNXXU2APK2_HOME.tar.md5
to test light stock rom v3 from Kingraheel
what happens is that NOW I can't flash any other firmware by odin... when I click START it says FAIL and in my device there is this text in red
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I just want to flash my OFFICIAL firmware
J510FNXXU1APG1_J510FNPHE1APG1_J510FNXWU1APFC_HOME.tar.md5
but I can't... only APK6 firmware works on odin... any other firmware works.... can you help me?
I don't have any NANDROID backup of previous versions... only of my actual firmware... APK6
My computer does not detect my device... I have the drivers installed, and I tried on all the USB ports... it charges but not open files.... PLEASE HELP
Click to expand...
Click to collapse
have you tried a different cable? I know it sounds rather sophomorish, but its a very common cause of the computer not being able to flash via Odin. Or can you get to another computer to try it there?
youdoofus said:
have you tried a different cable? I know it sounds rather sophomorish, but its a very common cause of the computer not being able to flash via Odin. Or can you get to another computer to try it there?
Click to expand...
Click to collapse
I just changed CSC with solid explorer, and flashed another stock firmware from samfirm downloader
But my computer continues without detecting my device... but ODIN does
TheWalkingSans said:
I just changed CSC with solid explorer, and flashed another stock firmware from samfirm downloader
But my computer continues without detecting my device... but ODIN does
Click to expand...
Click to collapse
that is odd indeed. I have 4 computers that all recognize all of my samsung phones. Are you getting the unrecognized device message in the area down by the clock?
My other computer detects it, okay, but I still cant flash any other stock firmware by odin AND BEFORE I COULD
---------------------------------------
EVERYTHING SOLVED, SAME PROBLEM? CONTACT ME
Here is HOW I SOLVED IT:
This error happens when you before have updated from "U1" to "U2" and then you try to flash a firmware with "U1" (UX appears in the firmware "name")
So, the simple solution is to flash the stock firmware with the same "UX" that you had before your device gor bricked.
In my case, testing KingRaheel's ROMS I flashed an Indian firmware (...U2APK6...) at this moment I didn't know I ****ed up. But don't worry, I simply had updated the "U" and how I didn't know it, I tried to flash lots and lots of firmwares with "U1" without knowing what was happening. After long nights, I tried to flash my last firmware from SPAIN (PHE) with "U2" and it worked.
I hope I helped you. I used SM-J510FN (J5 2016)
If you have another device, try the same but with your current model, any questions, ask by twitter/dm
Sent from my SM-J510FN using XDA Labs