Related
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!!!
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...
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 guys, I have a Samsung Galaxy S4 from Canada, specifically Rogers. The phone is currently on the CM11 Nightly ROM. (I can check specifically which nightly, my phone is just backing up at the moment so I can't see!)
I have this problem, which is, when the phone automatically locks or I myself lock it, the radio signal completely drops. Sometimes the signal will come back, but to get it back for sure is to turn the phone on airplane mode then off again. It is annoying because when the phone is locked for a while, it will receive signal at some point. During that time I'll get a call and it'll ring but once the screen turns on the signal will drop, also dropping the call. I have a slight understanding that it could be a problem with the phone's radio firmware?
Now that you guys have an understanding about my problem, this is what I am hoping to accomplish. I want to update the phones ROM, as it is probably old, along with the proper fix to the phone's radio firmware. How do i go about doing this? The kind of ROM that I want is something in between stable version and nightly (not nightly as I think nightly was the one that caused my radio problem), I think that's SNAPSHOT M12? Please correct me if I am wrong. I would rather not lose any of my data but if I have to then I will but please do guide me because I am scared to lose any of my data.
Thank you guys for reading my long post, I hope my English and grammar is fine! I look forward to hearing from you guys!
The current version of Cyanogenmod is 12.1 (Android 5.1.1). The two release channels for 12.1 are nightlies and snapshots. As of yet there has been no CM12.1 snapshot I'm aware of, meaning all CM12.1 ROMs are nightlies.
You haven't said what version of the stock ROM you had before moving to CM11, but if the radio is too old, you'll want to update it. You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Thanks for the reply!
Strephon Alkhalikoi said:
You haven't said what version of the stock ROM you had before moving to CM11
Click to expand...
Click to collapse
I don't know how to answer this, It's been quite a long time since I moved to CM11. Basically what I did was, when I bought the phone I went home and installed CM11 on it, haha.
Strephon Alkhalikoi said:
You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
Click to expand...
Click to collapse
I am quite confused, sorry. What I'm doing right now is I'm downloading the newest radio firmware from the link you have given me. After that I'm going to follow the instructions of:
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
That will fix my radio problems?
Now to update my ROM. This is where I am mostly confused. In your opinion, should I stick with CM11 Nightly? Can I somehow go from nightly to a more stable version like cm11 snapshot m12? Should I update to CM12? Will my phone keep up with the CM12 ROM?
Strephon Alkhalikoi said:
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Click to expand...
Click to collapse
Sorry I will keep that in mind! Mind you, I carefully chose this and looked at all my other options. I didn't see the AT&T forum to fit because AT&T is in the United States and my carrier is in Canada, I just didn't want to have problems with anything else
Guys, I think i screwed up.... So when i downloaded that firmware from Sammobile. I flashed it with ODIN and made sure re-partition was not checked. Everything looked fine and when my phone rebooted (its still rebooting at the moment) the welcome screen was the default "samsung" splash screen, not the Cyanogen Mod . I thought this method was only going to flash the phone's modem, not the ROM too
EDIT:
No....my worst nightmare came true .........NO!!!!
So my phone finished rebooting and its just a black screen. All I can see is the status bar at the top right that displays the WiFi signal and the Phone's network signal and the battery. Okay so I figured something out. When the phone is locked and I press the Home button, Battery Doctor's charging wallscreen shows up, meaning my device wasn't wiped ? When I tried to unlock from Battery Doctor's charging screen, it would just show the black screen with just the status bar .... PLEASE HELP ME !!!
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Strephon Alkhalikoi said:
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Click to expand...
Click to collapse
D'awww Well I guess a clean slate isn't so bad. I backed up my text messsages and my photo's should be backed up onto the google drive anyways. I don't know if you saw my edited post but the UI is not loading. Its just showing the status bar at the top right (signal, wifi signal, battery).
Thanks.
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
EDIT: ROM installs don't wipe data when done through Odin unless you tell Odin to partition the device. Thus you'd need a factory reset to ensure Touchwiz works. But where you're going to put Cyanogenmod on, don't worry about Touchwiz.
Strephon Alkhalikoi said:
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
Click to expand...
Click to collapse
The problem is, I can't. There's nothing there on the phone. Its just a black screen. Unless, thats what you meant.
I tried searching for a CM 12.1 Canadian version and I found this thread. http://forum.cyanogenmod.org/topic/104233-jfltesgh-i337m/
apparently theres no canadian version of the CM 12.1
what should I do ?
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Strephon Alkhalikoi said:
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Click to expand...
Click to collapse
Thanks for the replies! I'm sorry if im asking for too much but could you please confirm that this is the right one? link
So, I don't need to root? how can i verify that my phone is still rooted? If my phone is still rooted, I download Canadian Galaxy S4 SGH-i337M (Bell, Rogers, Telus) – CWM Recovery v6.0.4.4
Then flash that with Odin ?
edit: I think I know why this failed miserably....On Odin V3.10.6 I clicked "AP" for some reason, when I was flashing the firmware. Could that be the problem? If so, is there a fix ? i can't access my phones SD card .
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
i just installed cm-12.1-20150625-NIGHTLY-jfltexx on my s4 with cm-12.1-20150623-NIGHTLY-jfltexx but there is a problem with the phone functions. It can't make any call. .it do not find my sim card!! Same thing with cm-12.1-20150624-NIGHTLY . The last one that works is 20150623 . Is there anyone that can confirm my problem?
Strephon Alkhalikoi said:
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
Click to expand...
Click to collapse
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
flipboi15 said:
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
Click to expand...
Click to collapse
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Lennyz1988 said:
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Click to expand...
Click to collapse
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Flashing CM is easy. It doesn't require root access because this phone has no bootloader lock. Download a custom recovery with TAR file format, install drivers, go to the download mode of your phone, connect your phone to your computer, and use Odin to flash the recovery. Then copy CM zip file to a SD card and flash it in recovery. That's all!?
For recovery I recommend TWRP: teamw.in
If you've installed Kies you should have drivers on your computer. Otherwise install Kies or only drivers if you can find them on Samsung official website.
flipboi15 said:
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Use a different usb port / different usb cable.
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
flipboi15 said:
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
Click to expand...
Click to collapse
Try redownloading the .zip file. Maybe it's corrupt.
So after trying to install the ROM in TWRP and failing. I couldn't load up the phone anymore, it got stuck at the Samsung Logo screen. I am now re-flashing I337MVLUGOC4 - 5.0.1 Lollipop.
edit:
So at the moment, my phone is working fine on stock rom. I redownloaded the CM-12.1 optimized. I moved it into my SD card. I need to know if there are certain steps I need to do to get this right. These are the steps I took the first time.
Rebooted into TWRP recovery mode, then clicked install then I navigated to the CM-12.1 ROM zip and swiped to install.
Was I supposed to wipe anything? The only time I wiped(the default wipe in twrp) was after I installed the 5.0.1 Lollipop firmware. By the way, i noticed that my phone's internal memory is almost full, it only has 2GB of 9.69GB left in the internal. I checked it out and all my old files were still there!
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
I would first attempt to flash TWRP and see if it boots.
ashyx said:
I would first attempt to flash TWRP and see if it boots.
Click to expand...
Click to collapse
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
Where do you find the image, it should also be available in tar format?
kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
The Odin version of TWRP can be found here https://dl.twrp.me/gtaxlwifi/ When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.
lewmur said:
The Odin version of TWRP can be found here... When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.
Click to expand...
Click to collapse
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.
kstehling said:
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.
Click to expand...
Click to collapse
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?
ashyx said:
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?
Click to expand...
Click to collapse
Odin 3.13.1
I'm not sure how to include a picture. I have several.
On the Odin/Download screen is says:
Odin Mode
Download Speed: Fast
Product Name: SM-T580
Current Binary: Samsung Official
System Status: Custom
FRP Lock: ON (or off depending on the day)
Secure Download: Enabled
Warranty Void: 1 (0x030c)
the last numbers are B:4 K:1 S:2
This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
kstehling said:
This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?
ashyx said:
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?
Click to expand...
Click to collapse
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.
kstehling said:
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.
Click to expand...
Click to collapse
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI
ashyx said:
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI
Click to expand...
Click to collapse
SamMobile and Samfew
kstehling said:
SamMobile and Samfew
Click to expand...
Click to collapse
I doubt that is the combination firmware.
Use the one I posted.
ashyx said:
I doubt that is the combination firmware.
Use the one I posted.
Click to expand...
Click to collapse
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.
kstehling said:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.
Click to expand...
Click to collapse
I suppose its worth now trying with nand erase.
ashyx said:
I suppose its worth now trying with nand erase.
Click to expand...
Click to collapse
Ok. I'll try it now. Should I use the PIT file? Or any of the others? BL, CSC? And just to be sure the file you gave me the link to should be in the AP spot, right?
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
So you are able to flash the bootloader files?
Have you tried just AP?
kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
I don't recognize the file you are using. The latest T580 stock ROM can be found here: https://www.sammobile.com/samsung/galaxy-tab-a-2016-101-wi-fi/firmware/SM-T580/
For the U.S. it is the one for Cellular South. It is a zip file that needs to be extracted. You only want to flash two of the four. The one starting with AP and the one starting with BP.
The Odin screen should look like the attached image before you click start. Don't change any of the default options.